Bios Mods -The Best BIOS Update and Modification Source

Full Version: General method to remove whitelist from Insyde BIOS
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
(12-01-2010, 10:20 AM)TTAV134 Wrote: [ -> ]
Quote:I have an HP DV7-4083cl that has an insyde bios, the bios executable is 4 MB...

Thank you! This is what I got:

http://www.entouchgraphics.com/Hewlett-Packard-F.13.rom

Hope you can fix it!

before flashing the mod it's better to prepare a recovery solution
edit platform.ini in BackupROM section change Flag value from 0 to 1, save change.

[BackupROM]
Flag=1

then execute InsydeFlash.exe, you will have 2 files, copy them on a USB stick.

http://www.sendspace.com/file/hj9lul

Thanks for patching the bois, however, when I went to flash, my laptop restarted.... and said "There is a new bios update, to update now press enter" so i pressed enter and then it said "bios update failed"

I don't know if i am doing something wrong or what. Can you please help?

Quote:Thanks for patching the bois, however, when I went to flash, my laptop restarted.... and said "There is a new bios update, to update now press enter" so i pressed enter and then it said "bios update failed"

I don't know if i am doing something wrong or what. Can you please help?

That mean the method doesnt work for this model, dead end.
(12-02-2010, 03:44 AM)TTAV134 Wrote: [ -> ]
Quote:Thanks for patching the bois, however, when I went to flash, my laptop restarted.... and said "There is a new bios update, to update now press enter" so i pressed enter and then it said "bios update failed"

I don't know if i am doing something wrong or what. Can you please help?

That mean the method doesnt work for this model, dead end.

What? There is no way to use an after market Card with this machine?
(12-02-2010, 10:30 PM)zman21295 Wrote: [ -> ]
(12-02-2010, 03:44 AM)TTAV134 Wrote: [ -> ]
Quote:Thanks for patching the bois, however, when I went to flash, my laptop restarted.... and said "There is a new bios update, to update now press enter" so i pressed enter and then it said "bios update failed"

I don't know if i am doing something wrong or what. Can you please help?

That mean the method doesnt work for this model, dead end.

What? There is no way to use an after market Card with this machine?
I have this same machine and I have F.09 A, here is the link to the HP site that lists the available bioses. http://h10025.www1.hp.com/ewfrf/wc/previ...ob-88202-1&lc=en&dlc=en&cc=us&product=4230592&sw_lang=&os=4063
I was wondering if I could downgrade to F.08? Or if there are fixes for the .09, .12?
Thanks

zman are you trying to install OSX? PM me if you've gotten anywhere please.

(12-02-2010, 03:44 AM)TTAV134 Wrote: [ -> ]
Quote:Thanks for patching the bois, however, when I went to flash, my laptop restarted.... and said "There is a new bios update, to update now press enter" so i pressed enter and then it said "bios update failed"

I don't know if i am doing something wrong or what. Can you please help?

That mean the method doesnt work for this model, dead end.

Ok so is there any way to use an after market card???

I was reading something about a Dirty Hack? Covering the 20th pin? I Tried, it did not work.

Any help?
I was trying to follow this guide but I can only obtain a .bin from the official HP BIOS update or a .rom from a few other utilities.

ftp://ftp.hp.com/pub/softpaq/sp50501-51000/sp50586.exe

This is the current file available that I'm trying to work with. I'd be happy to do it myself but I can't seem to dig up any information on dumping a compatible .fd file.

Thanks for any help.
(12-20-2010, 03:31 AM)APE992 Wrote: [ -> ]I was trying to follow this guide but I can only obtain a .bin from the official HP BIOS update or a .rom from a few other utilities.

ftp://ftp.hp.com/pub/softpaq/sp50501-51000/sp50586.exe

This is the current file available that I'm trying to work with. I'd be happy to do it myself but I can't seem to dig up any information on dumping a compatible .fd file.

Thanks for any help.

don't waste your time this bios cannot be mod.
(12-20-2010, 12:42 PM)TTAV134 Wrote: [ -> ]
(12-20-2010, 03:31 AM)APE992 Wrote: [ -> ]I was trying to follow this guide but I can only obtain a .bin from the official HP BIOS update or a .rom from a few other utilities.

ftp://ftp.hp.com/pub/softpaq/sp50501-51000/sp50586.exe

This is the current file available that I'm trying to work with. I'd be happy to do it myself but I can't seem to dig up any information on dumping a compatible .fd file.

Thanks for any help.

don't waste your time this bios cannot be mod.

Sounds like a challenge to me.
(12-20-2010, 06:41 PM)APE992 Wrote: [ -> ]
(12-20-2010, 12:42 PM)TTAV134 Wrote: [ -> ]
(12-20-2010, 03:31 AM)APE992 Wrote: [ -> ]I was trying to follow this guide but I can only obtain a .bin from the official HP BIOS update or a .rom from a few other utilities.

ftp://ftp.hp.com/pub/softpaq/sp50501-51000/sp50586.exe

This is the current file available that I'm trying to work with. I'd be happy to do it myself but I can't seem to dig up any information on dumping a compatible .fd file.

Thanks for any help.

don't waste your time this bios cannot be mod.

Sounds like a challenge to me.

yes, and the challenge is to develop a tool able to decompress these new HP bios, because today none of the known tools can do that. (EzH2O.exe and Andy's tool from MDL)
(08-03-2010, 02:00 PM)hspumanti Wrote: [ -> ]I have figured out how to remove the whitelist from most (all) Insyde BIOSes. I used the F.34 BIOS for a Compaq Presario C700 series for this how to. You will need the EzH2O and WinHex tools. Using these tools I was able to figure out the byte that needed to be changed to ignore the PCIe wireless whitelist altogether. After not being able to find my subsys codes, I started looking around a bit. I found the 104 - Unsupported wireless network device detected string in the memory dump and the Microsoft EXE signature just above which lead to the breakthrough (at least for me). What follows is a general procedure to allow you to modify your own BIOS safely (I hope).

1. obtain your bios.fd file obtained from HP (or whatever manufacturer)
2. use Insyde BIOS editor - EZH2O (I used EZH20 2.1.0.4)
3. run exh2o.exe, open the file bios.fd
4. run WINHEX
5. Tools -> OpenRAM -> Ezh2o -> Entire Memory
6. Find HEX Values -> «31 00 30 00 34 00 2d 00 55», this should be the be the first part of the '104-U...' error string in wide character format (2 bytes/char) see step1.jpg.

7. from here search up and find HEX values «4d 5a», you can just scroll up a few pages till you see 'MZ' in the ASCII pane. This is the code that MS uses for start of an EXE. Somewhere between here and the 104 string is where we need to find and modify the JNZ (byte code 75)
8. You will notice that there is a lot of blank space around and below the 'MZ', this is header information and is of no interest. Scroll down till the ASCII pane no longer is mostly blanks, about a page, you should see «55 8b ec», this is the start of the program and is setting up the stack
9. Now click on the 55 and drag the mouse down to the next 'MZ' code about 1-2 pages on my BIOS, and then click Edit -> Copy Block -> Into New File and name the file Something.com. The .com is important as we will load it with debug. Refer to step2.jpg.

10. Open a command prompt and navigate to where you saved the file and type debug something.com, you should get a '-' prompt, type u and hit enter and you should see something like this. See step3.jpg.

The first column is memory addresses, the 2nd column is instruction bytes and the rest are Intel mnemonics.
11. Now we need some elementary assembly skills to find what we are looking for. Debug will show the mnemonics for the instructions. Debug doesn't handle 386 instructions well so you may see a few ??? but we should be able to find what we need. Look for a test al,al followed by a jnz {address}. The unassemble should have addresses on the left and they should correspond to the addresses in the debug so you can then -u {address} to see what happens at the jump to locations. See step4.jpg.

12. Now that we know what to change write down a about 6 or so of the bytes ending with the 75 and the following byte (27 in the step 4 example) and go back to WinHex and from the start of our program (the «55 8b ec» bytes) search for the bytes you recorded. Make sure everything around matches your debug window and replace 75 (JNZ short) with eb (JMP short). eb is an unconditional jump and will exit the routine so we don't get to the infinite loop. See step5.jpg.

13. In WinHex save your change by clicking on the disk icon
14. Switch to EzH2O, File -> Save AS
15. Put your modified BIOS (and only that BIOS) where the flash utility can find it and start InsydeFlash and let it do it's thing.
16. Sometimes after flashing the machine may appear bricked but turn it off remove power and battery and then reapply power and turn it on. If it still doesn't come up Google for the procedure to use a USB memory stick to get your computer back. Might be a good idea to prepare the flash drive before you flash your BIOS.

Mark

hey man. is this work for hp dv2000 ?
(08-03-2010, 02:00 PM)hspumanti Wrote: [ -> ]I have figured out how to remove the whitelist from most (all) Insyde BIOSes. I used the F.34 BIOS for a Compaq Presario C700 series for this how to. You will need the EzH2O and WinHex tools. Using these tools I was able to figure out the byte that needed to be changed to ignore the PCIe wireless whitelist altogether. After not being able to find my subsys codes, I started looking around a bit. I found the 104 - Unsupported wireless network device detected string in the memory dump and the Microsoft EXE signature just above which lead to the breakthrough (at least for me). What follows is a general procedure to allow you to modify your own BIOS safely (I hope).

1. obtain your bios.fd file obtained from HP (or whatever manufacturer)
2. use Insyde BIOS editor - EZH2O (I used EZH20 2.1.0.4)
3. run exh2o.exe, open the file bios.fd
4. run WINHEX
5. Tools -> OpenRAM -> Ezh2o -> Entire Memory
6. Find HEX Values -> «31 00 30 00 34 00 2d 00 55», this should be the be the first part of the '104-U...' error string in wide character format (2 bytes/char) see step1.jpg.

7. from here search up and find HEX values «4d 5a», you can just scroll up a few pages till you see 'MZ' in the ASCII pane. This is the code that MS uses for start of an EXE. Somewhere between here and the 104 string is where we need to find and modify the JNZ (byte code 75)
8. You will notice that there is a lot of blank space around and below the 'MZ', this is header information and is of no interest. Scroll down till the ASCII pane no longer is mostly blanks, about a page, you should see «55 8b ec», this is the start of the program and is setting up the stack
9. Now click on the 55 and drag the mouse down to the next 'MZ' code about 1-2 pages on my BIOS, and then click Edit -> Copy Block -> Into New File and name the file Something.com. The .com is important as we will load it with debug. Refer to step2.jpg.

10. Open a command prompt and navigate to where you saved the file and type debug something.com, you should get a '-' prompt, type u and hit enter and you should see something like this. See step3.jpg.

The first column is memory addresses, the 2nd column is instruction bytes and the rest are Intel mnemonics.
11. Now we need some elementary assembly skills to find what we are looking for. Debug will show the mnemonics for the instructions. Debug doesn't handle 386 instructions well so you may see a few ??? but we should be able to find what we need. Look for a test al,al followed by a jnz {address}. The unassemble should have addresses on the left and they should correspond to the addresses in the debug so you can then -u {address} to see what happens at the jump to locations. See step4.jpg.

12. Now that we know what to change write down a about 6 or so of the bytes ending with the 75 and the following byte (27 in the step 4 example) and go back to WinHex and from the start of our program (the «55 8b ec» bytes) search for the bytes you recorded. Make sure everything around matches your debug window and replace 75 (JNZ short) with eb (JMP short). eb is an unconditional jump and will exit the routine so we don't get to the infinite loop. See step5.jpg.

13. In WinHex save your change by clicking on the disk icon
14. Switch to EzH2O, File -> Save AS
15. Put your modified BIOS (and only that BIOS) where the flash utility can find it and start InsydeFlash and let it do it's thing.
16. Sometimes after flashing the machine may appear bricked but turn it off remove power and battery and then reapply power and turn it on. If it still doesn't come up Google for the procedure to use a USB memory stick to get your computer back. Might be a good idea to prepare the flash drive before you flash your BIOS.

Mark

hey man. is this work for hp dv2000 ?-*++++

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26