New testing version, testers needed! about 1vyrain HOT 32 CLOSED

I've used revision 5 on my x230 which had its TPM stuck in MFG mode since my flash attempt with the first release of 1vyrain. TPM seems fully functional again (BIOS options are back to normal) with revision 5 and setting up BitLocker went perfect where it before it would get stuck on TPM provisioning and didn't allow encryption.

I did change the SSD (Samsung 860 EVO) in the meantime and did a fresh install of Windows 10 Pro so I do need to verify what actually is being used. The recently addressed flaws in hardware encryption/BitLocker updates makes it a bit non-transparent to the end-user to what combination of encryption and software/hardware is being used.

Revision 4 (the Google Drive link) didn't work for me at all. It gave me an "Error: Image size (0 B) doesn't match the flash chip's size" error, which makes me think it was missing a file.

Edit: Checked with "manage-bde -status C:", TPM is utilized. I enabled hardware encryption on the drive, secure erased it, reset the security chip (TPM) through the BIOS and did a clean install of Windows 10 again. Works perfectly and BitLocker was able to software and hardware encrypt and use the TPM.

from 1vyrain.

@Pentaphon If you need the fixed features, you can update by downgrading with IVprep. And then installing the new revision.

from 1vyrain.

I'm getting a no valid BIOS error on my L430, what's the BIOS version needed to perform this on a L430? I recently change the motherboard on my L430 so I'm on G3ET93WW(2.53) instead of G3ET94WW(2.54). Did the compatibility test again and also got a compatible for this BIOS version as well.

from 1vyrain.

@dte102 I just checked, 2.54 and below is compatible according to the report. This is an error in the script, as we forgot to add the L430. Do the exploit "test", after resuming from suspend exit the script, and run the following commands
dd if=/dev/zero of=/tmp/pad.img bs=1M count=4
cat /tmp/pad.img /root/bios/L430.rom > /tmp/padded.rom
flashrom -p internal:laptop=force_I_want_a_brick --ifd -i bios -N -w /tmp/padded.rom
And report back the results, if there are any errors during flashing, or if the worked.

from 1vyrain.

Image and md5sum updated. Link is the same.

from 1vyrain.

@digmorepaka Getting an error when trying to flash for the L430.
Found Winbound flash chip "W25Q64.V" (8192 kb, SPI) mapped at physical address 0x00000000ff800000.
Reading ich descriptor.. done.
Using region: "bios".
Write/erase is not working yet on your programmer in its current configuration.
Aborting.

from 1vyrain.

@dte102 add /root/flashrom/ before the flashrom command to point to the newer binary, Debian's flashrom looks to be ancient

from 1vyrain.

@digmorepaka it went through an initial flash and then came upon the same error again except it ended with the line "verified flash" or something and close after aborting when it was flashing something else. Decided to reboot to test out what flashed but unfortunately it seems like the laptop bricked cause it rebooted to a blank screen, no bios or anything for a couple minutes. Once I unplug everything and re-plug it in, it refuses to boot nor do any indicator lights come on. I've got my previous motherboard that still boots, replaced it because I accidentally ripped the touch pad port off of the motherboard. I can place that inside and still test for things out if needed.

from 1vyrain.

@dte102 do you have an SPI flasher(for example ch341a)? We can recover the bricked board.

from 1vyrain.

@digmorepaka Not at the moment, was always planning to get one before 1vyrain came out for my T430 but still never got around to it. I do have a raspberry pi that can be used in place of it, but I don't have a test clip nor jumper wires either.

from 1vyrain.

@dte102 damn that sucks, both from the standpoint of you having a bricked board, and the inability to test L430 support properly

from 1vyrain.

@digmorepaka I've ordered a SPI kit so we can recover that board whenever it arrives since it was cheap. In the mean time when I have more free time, I'll swap boards and try flashing it again to see what happens on my 2.54 board. I'll take a picture if it comes up with the same error as before.

from 1vyrain.

If you are going to flash, set a custom url and point to the image in the patched-bios repo.

from 1vyrain.

Image updated due to issue pointed out in #39. MD5 of course updated and links stays the same.

from 1vyrain.

Will finally be merging this in later this week if there are no further updates.

from 1vyrain.

Updated with a fix for TPMs. You should now be able to use the TPM normally. Tested on T430 so far there it worked, report any bricks or success

from 1vyrain.

Image was broken. Rolled back debian to known working version with proper roms.

from 1vyrain.

@n4ru If we have Revision 4 already installed, do we just flash Revision 5 over that when it comes out?

from 1vyrain.

you can update by downgrading with IVprep. And then installing the new revision.

Will I experience any issues if I have a non-whitelisted Wifi card installed?

from 1vyrain.

Will I experience any issues if I have a non-whitelisted Wifi card installed?

Yes, you will need to remove the WLAN card. IVprep flashes an unmodified rom.

from 1vyrain.

Tested version 5 on T430s. Fixed TPM issue.
Thanks :)

from 1vyrain.

Tested v5 on T430. TPM fixed. All good. Thanks.

from 1vyrain.

Thank you digmo for staying on top of this while my lazy ass hasn't found time/motivation to push out Rev 5. Will be finally merging the remaining changes and posting the new iso/md5 today (hopefully...).

from 1vyrain.

rev.5 merged

from 1vyrain.

Is tpm supposed to be entirely fixed in this version, or does it still require provisioning in the stock state ? I just flashed the current version, and I can't provision the tpm.

from 1vyrain.

Hi pgera. Did you use ivprep before flashing the new version? As far as i remember, i cleared the TPM from bios after flashing ivprep, and then used ivyrain to update to latest version.

from 1vyrain.

I didn't clear or take ownership on the stock bios. That should work. My question was about whether you can clear and take ownership again on the modified one. Are you able to clear/provision the tpm right now on the modified one ?

from 1vyrain.

Personally i have only tested going from when it was in "inactive". There it worked fine. More testing has to be done to know exactly.

from 1vyrain.

Yes, i can clear it on the latest bios now.

from 1vyrain.

@iXPert12 , after you clear the tpm from tpm.msc, it reboots and you get the confirmation screen, right ? In my case, it reboots, but fails to show the confirmation screen.

from 1vyrain.

@iXPert12 @pgera @n4ru :
Testing on W530, trying to only unlock ifd+flash exposed w530 chip under palmrest with 1vyprepped verson backupd, unlocked and flashed back to then flash internally (ctrl+c after 1vyrain Bios lock exploit chain) to flash heads maximized build internally. No problem there.

Steps

• Use pamona clip not chinese kit alternative, assemble as described under linuxboot/heads-wiki#120 (comment)
• Backup exposed 8mb chip into backup.rom, run ifdtool -u backup.rom, flashrom back backup.rom.new (with unlocked ifd) to 8mb chip.
• Run 1vyprep from windows on laptop (wish 1vyprep was containing wlan chip whitelist).
• Run 1vyrain exploint chain to unlock Bios lock, get to prompt to flash, CTRL-C and then get backup of full 12mb combined flash with flashrom -p internal:laptop=force_I_want_a_brick -r w530_1vypreppred_unlocked_ifd_backup.rom
• Do other experiments below

Problem arises under Heads when attempting to set a TPM Disk Unlock Key, where TPM reset works as expected.
I'm also wondering in which state the TPM should be left in.

Eg:

Past testings from 1vyprep unlocked ifd reflashed to 8mb spi:

TPM active, clear settings

• reflash heads maximized build from 1vyrain ( CTRL+C at flashing choice to drop to shell. flashrom -p internal:laptop=force_I_want_a_brick -w heads-w530-maximized.rom required)
• reset tpm works
• sealing additional secret fails (Add TPM Disk Unlock Key (DUK) from show boot option and selecting new boot default): NVWrite can't set new nvram range

TPM Active, Windows Security chip settings -> clear

• redoing 1vyrain, flashing heads from above manual flashrom command
• From heads, reset tpm works as expected
• adding TPM DUK still fails

TPM clear settings + TPM set to inactive

• redoing 1vyrain, flashing heads from above manual flashrom command
• From heads, reset tpm works as expected
• Same error as in picture...

TPM clear settings + TPM deactivated

• redoing 1vyrain, flashing heads from above manual flashrom command
• From heads, reset tpm works as expected
• Same error as in picture...

Looking to prepare a step-by-step instruction guide here. But cannot replicate a successful TPM reset where TPM is properly owned (TPM presence?! all settings in stock BIOS were set to disabled under TPM. ... Confused here!)

from 1vyrain.

Nevermind, it was linuxboot/heads#1565 which is now fixed.

from 1vyrain.