Hi Nominal, Have you got any success finally? I'm curently working on same password issue with E5510 laptop. As I understand you didn't find a way to start recovery process for your unit? Regards
you can flash 2011 bios newer than A01 just not newer than 2012 my grandma just received her laptop 1 week ago.. i had it on hold testing it.
Hi, do you still have the bin for A01 ver bios? I had A13, rewritten with A09 from LatinMcG, but still appears 1F5A.
its 3 chips.. not 2. mine was A09 but the bios has extra chip from what we found and i didnt backup or check if that could be dumped and cleaned of pwd.
I managed to do it last night, and I made some tests. The W25Q64 (U12) is for iAMT firmware, the W25Q32 (U13) is the bios firmware. For ex. if you have A13 ver. bios and write another version of firmware in the U12 (ex. A09) the laptop still displays A13 ver. bios. If you leave U12 with A13 and write U13 with A09, the laptop displays A09 ver. bios. I had on my laptop A13 with 1F5A, I wrote yours bin files to U12 and U13, the laptop displays A09 with 1F5A. I found on internet 2 bin files with A03 ver. I left on U12 the A09 ver from you and I wrote in U13 the file from net with A03. The laptop first starts in diagnostic mode, after restart it displays A03 ver bios with 2A7B, I used an online calculator and the laptop is unlocked. The third chip is for TMP.
On elvikom forum search for Dell Latitude 6410 LA-5471p LA-5471p.7z It's not allowed form me to post links in the forum, or give your mail and I send it.
I've been having a little "fun" experimenting with a very similar model (E4310 / codename lafite instead of rothschild). I've been trying to downgrade to the A01 BIOS as I've got this second hand and not getting much joy getting it unlocked without fees so I thought I would have some fun. Seems like the BIOS files for these may be both structured in a similar way which is stopping phoenixtool (or us humans) from easily figuring out the proper name for .HDR file to recover. I prepared a 2Gb USB stick using the HP Tool. Used the script on this forum and phoenixtool to decompress the BIOS and seem to have got the same results both ways. Getting into recovery mode is easy - no battery or charger. Put USB stick in, hold end button down, then plug in power and release end button while power light is still yellow. If the memory stick is in the left (ESATA) USB port, the LED on it seems to blink a little more than if I try using the other USB port. However every time I just see the LED on the USB blink a very few times, then laptop just sits there flashing it's power button yellow/blue and running the fans fast but not doing much else. (If I unplug and replug power I'm always back to normal at least) I may be totally wrong, but to me this says we know how to enter recovery mode, but we don't know exactly what the computer wants. I've tried renaming the extracted BIOS file to the following and had no luck: BIOS.BIN, BIOS.WPH, LAFITE.BIN/ROM/HDR, LAFITE01.BIN/ROM/HDR - LAFITE100.BIN/ROM/HDR, LAFITA01.BIN/ROM/HDR, E4310A01.BIN/ROM/HDR, PFS.BIN/ROM/HDR, PFS01.BIN/ROM/HDR as well as probably many other ideas. The internet tells me that for the Vostro 3500 the proper name is VINERY50.HDR, and for the XPS 9130 it is VAUB0???.HDR. These are both Dell UEFI based machines which gives me some hope. The only set I can think of that is still worth me trying that I haven't already is LAFITA02 - 100 and LAFI0???.HDR. However I have a funny feeling I still won't find it. I was thinking whether there might be a better way of doing this, but I thought I would throw the idea out for discussion. Thinking to myself, if we were trying to look to see if a computer was requesting a file over a network, there would be signs (e.g. in procmon.exe you can view what a program is reading and trying to read, or say for example viewing a TCP dump of a TFTP session would show which files are requested from which directory). I have no idea whether this approach would actually work, or whether for example the computer just reads the FAT then it automatically knows whether it needs to carry on looking for anything else. I downloaded a free trial of a program to monitor USB traffic but it didn't seem to work very well and I had no idea what the data actually meant so I thought I would ask whether anyone else has considered this approach?
use a hexeditor to read in the hdr for LAF. best is to just buy ch341a and flash both chips with say A02+ never do A01 if possible... many bugss
Hello all, I also had a same problems when I update to a16 bios, are this solution work? flashing those u12 and u13 chip or it must involve the third chip that mention on the comment.