Hello, I flashed my HP Pavilion dv7-4280us with an AdvancedMenu mod from the bios-mods.com repository. Now, the laptop isn't able to boot. I read that it's due to an RSA signing problem. The fans come on, and it powers up, but it won't do anything else. It may be worth mentioning that the setting I changed before the failure was the graphics mode. I changed it from hybrid to dedicated GPU. I don't know if this matters, especially since I removed the CMOS battery which should have cleared the settings. I used Andy's tool to extract F.23 and F.29 from HP's website. I renamed the 01448F2x.bin.DEC and RSA.SIG to 01448.BIN and 01448.SIG. The ID under the battery on the system is 163D, but upon inspecting a file in the ROM dump, the path its expecting is one of the following: "HEWLETT-PACKARD\BIOS\Current\01448.BIN" "HEWLETT-PACKARD\BIOS\Current\0144D.BIN" (See thread "How do I extract dump an Insyde BIOS A general way to find the name for recovery") I also tried every name in the PlatformName section of the platform.ini, with and without a leading zero, and the only one that reacts differently with the system is 01448.BIN. With any other filename, the system reads all drives, pauses, and then repeats over and over again. With 01448.BIN, the system reads the drive, and then the fans speed up and it doesn't really do anything useful. It will eventually start beeping with each keystroke, indicating to me that the process has stalled. I've removed the CMOS battery and other power sources for hours, shorted the terminals, booted with and without the battery in, and nothing seems to work. I've also tried all of the key combinations (Windows+B, Fn+Esc, Fn+B, all four arrow keys), even though the correct one for this system is Windows+B (or the arrow keys). I'm not comfortable with reflashing the chip with a programmer, mostly because of my soldering skill. So, any ideas? EDIT: Solved by reflashing the chip with a programmer. See post #18 for details.
filename is not 1448.bin [Platform_Check] Flag=2 PlatformName1=1448 PlatformName2=1449 PlatformName3=144A PlatformName4=144B PlatformName5=144C PlatformName6=1447 PlatformName7=147C PlatformName8=149C PlatformName9=1639 PlatformName10=163A PlatformName11=163B PlatformName12=163C PlatformName13=163D PlatformName14=163E
Like I said, I tried all of those names, with and without the 0. If I use just "1448.bin", the machine goes into a loop. The only file that produces different results is "01448.bin"
what versions have u tried so far ? both i imagine F.23 and F.29 have u made UEFI USB with the (newer) sp57448.exe or (older) sp52407.exe ? at last u can buy a chip and have a pro replace it.. and u get a cheapo usb spi programmer and make backup of new chip before soldered on. to flash to old chip as backup.
I've used both UEFI creation tools (Diagnostics and BIOS update) on the drive. I've tried both available versions, F.23 and F.29, and I've even tried the modified one that broke it in the first place.
Some users were able to recover from it by removing the CMOS battery and starting the recovery procedures. I don't know if all of them did, since many of them did not post follow-up information. The modification was apparently known to fail due to the RSA signatures, but I unfortunately found the file before I found the warning.
i wonder if it has to do with EFI settings in hdd HP_Tools try booting with F2 or shift F10 as a wild try. (seen somewhere something about it) see if someone has a full backup of chip u can have a tech flash for u i have to go .. reflow 3 laptops VPCEE31FX M5030 overheated and warped board pushed solder balling.. big mess under chip = reball needed. D620 with nvidia chip.. sometimes intels need it too ,rare tho
Alright, I've got the chip sitting on a Minipro TL866CS right now, and I've dumped the data off of it. I'm trying to find a way to recover it manually, but I've run into a roadblock: the decrypted file from Andy's tool is still larger than the chip, and I don't know which parts to copy into the new image to write. Any idea?
thats why i ask if u made backup.bin so i can compare it .. start search with a common word in middle. then go up til it starts changing.
Here are the backup files. preflash.bin has the status register included and preflash_nostatus.bin does not. dl.dropbox [dot] com/u/7989849/Temporary/preflash_nostatus.BIN dl.dropbox [dot] com/u/7989849/Temporary/preflash.BIN
While you were doing that I took another look at the file and merged in 3 bundles of hex. I wrote it to the chip, and I'm happy to report that the laptop is now fully functional! Thanks for your help, and sorry you had to go to the trouble of creating that bin file.
Final information for searchers: I'm taking down my BIOS dumps now because they contain identifying information for the machine and shouldn't be used on other machines (because they're broken). As a general hint for this BIOS I'll comment that the 3 sections that I copied over were the last three in both the dump, and the decrypted image from Andy's tool. They're separated by lots of 'FF's. I also flashed with the manufacturer utility afterward so that I could ensure there weren't any missing chunks. The dump I used from the Minipro was the one without the status register contents (code only).