![]() (Not strictly required, but from my 3DS hacking days I know it never hurts to take a backup of your unique firmware) I’m assuming the motherboard is still at a relatively old BIOS revision.īackup.bin: The BIOS you dump before doing anything at all, just to be safe. bin (which would be the one from HP’s website), would that be of any use? Where would I get said “old” and “new” files? I guess it’s not as simple as editing the. You can very likely copy-paste the 0xFF0000-thru-0xFFFFFF section using two open hex editor windows, but I would triple-check the file afterwards (length, diff against sources, etc) to makes sure it worked, since there are fewer in-between steps to individually check on. I just noticed that you seem to be using Windows if you don’t have a *nix system then my above advice is moot. If it fails, the direct methods are no less viable, right? However, since a soft-brick can be fixed by methods 2 or 3, I would try the software approach first, hopefully sidestepping the entire issue. A lab bench supply would be ideal, but impractical unless you already own one. I unfortunately don’t have any recommendations for 3V3 supplies. I like to size my window so that the number of columns is an exact multiple of sixteen (0xF), it keeps the offsets tidy. Each column is numbered as well, and in hex no less-you might notice that the two panes have the same number of columns. The left margin has the address, or offset, of the first byte in each row, so you know where you are in the file. It’s good for spotting string literals and stuff, but not really for making edits or reading numerical data. The right pane is an ASCII representation of the file (since each ASCII char is one byte). Each digit (0 thru F) represents four bits, so two make up a byte. In a standard hex editor, the left pane is the file represented in hexadecimal. Apologies in advance if not, this will probably sound pretty pedantic if that’s the case. RE: hex editors, it seems like you haven’t used them much. ![]() This would be useful if you want to flash the entire chip’s storage you can just take the section from the new bios if you find a way to do a partial flash. Then stick them together (you can use cat for this) and you should get a 16777216-byte file (decimal)-bytes 0x000000 thru 0xFFFFFF. So the goal here is to extract bytes 0x000000 thru 0xFEFFFF from the old file (16711680 bytes decimal), and extract bytes 0xFF0000 thru 0xFFFFFF from the new file (65536 bytes decimal). What I need to do: “replace boot block contents (FF0000-FFFFFF) with that from newer bios revision and write that onto one of your new bios chips” From what I read Ivy Bridge is meant to ship with ME v8 firmware, but with the ME not in use it really shouldn’t matter anyway. ![]() People on the HP forums, for several different products’ Sandy->Ivy boot block uprades, aren’t sure whether you need to make sure to update the Intel ME firmware from v7 to v8 too or not. In all the situations it seems like I’ll be buying a SOIC16 clip and perhaps some practice/spare SPI chips.Īnother thing to note about Zx20 boot block upgrades is the Intel ME (Management Engine), the Intel corporate PC backdoor management feature. I’ll try to make a video by December of what I’ve found so far and dumping the BIOS (not much time for weekend long projects while im at university). Once we get past the HP-specific stuff it should be the same as flashing any GPU / motherboard / router, and guides for those situations should be relevant. It’s definitely still at the level of “legends in the forums once told of a way…”. That would be great to read someones all-in-one guide on how to dump the memory (and maybe even flashing!) as I couldn’t find one (I think, from what I remember). ![]() I think using a hex editor is the right approach, but you want to dump the BIOS you already have, make a backup, and copy the 2013 boot block from 0xFF0000 - 0xFFFFFF of an update’s BIOS bin to the same region of your dumped BIOS. Reading the HP forum it seems like SalSimp put the new boot block into a dumped BIOS and desoldered the original chip to flash with a programmer, while Scoobis used a BusPirate with the 3.3v Vcc pin lifted to directly write to 0xFF0000 - 0xFFFFFF. I’m still not 100% sure which methods allow just 0xFF0000 to 0xFFFFFF to be flashed, but in the end it’s the same result as flashing the entirety of a modified dumped BIOS. Also I guess what I last attempted by loading the whole BIN file into that program was the wrong approach? Is it possible to flash only certain parts of the IC’s memory, or does the whole IC need to be rewritten to, to make changes to it? How would I solely flash just the boot block? (haven’t looked into this subject since about 1y ago).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |