@Lost_N_BIOS

So, I restore windows to a previous to start from scratch. First of all I installed the driver before plugin de programmer, than I put the clip at the chip, than connected the programmer to computer. Used versions 1.30 and 1.34 but no luck... still says "device state: not connected" at the bottom right corner, tried to reconnect a bunch of times and everytime the same thing. the device doesn't appear active at the device maneger, but at devices and printers he is there and it seems to be working... I'm sending some pictures.

*Edit*
Also, tried what tou mentioned about psu and battery. Tried with psu only, battery only, and the 2 together, but still same thing.

And one question, the software should say device state: connected, and give me the option to read chip only when chip is connected to programmer properly, or should say device state: connected with only programmer pluged in?

@fairestmeat - Please put all those images into a max compressed zip, thanks
Not detected has nothing to do with software version, this is due to physical issue (incorrect connection, clip not on perfectly, board needs to have power connected (or not), bad cable, etc) - Device manger has nothing to do here

It looks like you are missing jumper on CH341A, there should be a jumper on the lever side, first two pins in the middle (look at all stock images of device online, you will see it there)
This is the main issue I see here, then you just need to struggle to get the perfect clip/chip connection and find out of this board needs power connected or not.

@Lost_N_BIOS

Hhmm ok, If i can't find jumper, can i short that connection by taping paper chip in It? Sorry about the pics...

Best to find a jumper, check on old motherboards, maybe in old systems you aren't using now, or at least one you can borrow from some system you are using.
Taping paperclip in there wont work very well.

@Lost_N_BIOS

Found a jumper! Just to be sure, the jumper connects pins 1 and 2 (according to the back of the device) wich are the First 2 pins further from the Lever, right?

*Edit*

Got it! I made a backup of the bricked BIOS, but I'm not sure what file to program back. Why the extracted BIOS is 8mb and the original file has 6mb?

I'm uploading a file with the backup and the other BIOSes for some assistance. Thanks alot for the help guys!

https://drive.google.com/file/d/1Te6_s2BD1hA1hDeNz4zr-cPMoP94DEWT/view?usp=sharing

@fairestmeat - Yes, - 1-2 = pins furthest from the lever, on the lever side. Look at any for sale images, this is usual stock position that it should have been in when it arrived.

* edit - Just noticed your edit after I replied. Please upload the dumped BIOS only and I will fix for you (with BIOS From #13, so you'll be back to square one with unlocked BIOS again).
Stock BIOS download is only partial BIOS, that is why it's smaller than dump

@Lost_N_BIOS

That's great! Sending dump

bricked BIOS

Here you go, I unlocked FD and put back your already tested and confirmed unlock OK BIOS region
Erase, blank check, the open BIOS file and write/verify
http://s000.tinyupload.com/index.php?fil...419092536877373

If it fails, then ME FW may need fixed, but it looked OK generally, so I left alone for now.

@Lost_N_BIOS

Thanks! Trying right now, I'll send feedback in a minute.

When you say you unlocked FD, what exactly means? All regions are unlocked?

And to fix a bad BIOS like this one, you replaced the BIOS region on the file by the working file at the #13 post? Or there is more into it?

@fairestmeat - Yes, I mean I unlocked your Flash Descriptor for all regions.
And one more yes, that is all I did currently to fix (so far), replaced BIOS region in dump with known good working BIOS region, can be done via Hex or UEFITol 25 (I used)

@Lost_N_BIOS

I see, thanks for the information. Everything worked like a charm here! Up and running again

Thanks alot!!

@fairestmeat - Awesome to hear it man!! I knew it would be working nicely, provided the write in didn't fail on you
You're welcome Now, this time, be careful, or at least you know how to fix it now And you can now always use that same BIOS if you have to recover again

@Lost_N_BIOS

Yeah!! thanks once more!

Just one more question, is there any way to brick a system beyond recover? I'm talking about BIOS and hardware misconfigs...

@fairestmeat - You're welcome!
Once you have programmer, really nothing is beyond recovery, especially when you plan in advance and have confirmed working backups.
But even without that, someone can always make you a BIOS that will boot, or find one to get you started, then work/rebuild from there etc.
As long as you don't physically damage something, scratch, short etc, you can fix always fix it if it's BIOS related once programmer is in your hand

Speaking of that, you should now also find and backup your EC FW chip too, just in case it ever gets messed up. Should look same as BIOS chip, but only 128kb-1MB usually.

Zitat von Lost_N_BIOS im Beitrag #16

---

@fairestmeat - Changed checksum is expected, as long as your edited BIOS opened in app after (close app, then open new instance and your new mod vBIOS), as long as it's Green/OK then it's OK
UEFITool does not correct that checksum, the Maxwell app should. I meant when you reinsert vBIOS body into BIOS it will correct the checksum on that GUID in the BIOS itself, if there is one in the header. We're discussing two possible checksums here

What GUID is the vBIOS you are editing, there is several vBIOS there so I'm not sure. Ohh, doesn't matter, I checked a few of them, and each GUID has it's own checksum.
So yes, once you replace with UEFITool (be sure it's same way you extracted), the UEFITool will correct the checksum on rebuild and new file will have different checksum for that GUID than the original.
You can see these checksums if you use UEFITool NE Alpha (version 51-x), ohh, sorry, I see you can also see this in the regular versions too (such as 25), it's in the info on right side when you select a GUID at it's base/root

Be careful here, without flash programmer if vBIOS is a brick then you wont have any display output to recover BIOS! If I were you, I would wait until I have flash programmer in hand so you can recover if necessary.

---