Please help with asus black screen (no logo, no bios)

[junjo]

Yes, that guide applies, you need to use a .rom or .bin BIOS, that is 2KB smaller than the stock BIOS (So, yes, I think the file you linked is that)

Be sure, before you write anything to the chip that you get a verified and valid backup made, or you will loose your board specific details (UUID, Serial, DTS Key, LAN MAC ID)
Run read, then verify, once it says "Chip/Buffer match" then that is verified, click save and then open that file in hex editor and make sure it's valid BIOS and not all FF's
If it is all FF's, that's verified invalid blank and you need to use another software version or CHIP ID and try again until you get verified and valid backup)

Unfortunately, it don't work

My bios chip is 25Q64FVSIQ (or G I'm not sure)







Version 1.30:

[Lost_N_BIOS]

Use BV on chip selection and use software 1.29, but first you have to have it all connected properly.
1.30 works as well, but you get the access violation error like your 4th image, but it will still program properly after that (I think, tested erase and blank check OK)
Some of those errors indicate it's not connected properly, especially image #3 w/ 1.29 software, rest could be due to software version used.

Here's some posts on another forum where I tried to explain this, hopefully soon I will have time to make a proper guide with many images to make this easier on everyone!
https://www.win-raid.com/t3953f16-Insyde...l#msg61695 << Post #85
https://www.win-raid.com/t796f16-Guide-U...l#msg60679 << Post #218
https://www.win-raid.com/t3882f12-ga-z-x...l#msg60493 << Post #17 & Also see post #23 for my suggested method

And finally, many replies by me here, with lots of user images shown. So you can see his images, then see how I tell him to make corrections to get it all connected properly
https://www.win-raid.com/t3855f16-Proble...perly.html

Here's how the programmer will look once connected and detecting the chip properly, this is version 1.29
I tested again just now to be sure, this is using your exact chip W25Q64FVSIG (detect chip, then use BV instead - this I know from previous testing)


Here's how it will look once finished with a write


For backing up chip -
1. Close app and open app, to make sure buffer is clear
2. Detect chip, in this case for W25Q64FVSIG choose W26Q64BV
3. Hit Read
4. Hit Verify
5. If above verify ends with Chip and Buffer same, then hit Save
6. That is all until you are sure the file is valid as mentioned previously

On the write to chip, do like this, I find this best method.
1. Close app and open app, to make sure buffer is clear
2. On auto option, uncheck erase and blank check (Do these manually).

3. Click erase
4. Click blank check
5. Open BIOS file to write
6. Click auto (Which is now write, verify only)
7. If buffer and chip match then all is done!

[junjo]

Now I'm not at home. Then I try it and I tell you something. Really, thank you very much for your help.

[Lost_N_BIOS]

You're welcome! Don't worry, you'll get it figured out!

Just be sure you do not write anything to the chip until we are sure your backup is valid, so you don't loose system specific details

[junjo]

Hi,

For the moment I have this:



All data is 00 and no device ID and unique ID

[Lost_N_BIOS]

Save and upload that file, let me check, don't write anything yet, it may still all be zeros or FF's

Are you sure connection is correct, and stays secure entire time? If the cable is moved, or it's not fully connecting, you will get verified 00 or FF filled file, and no ID's like you have. Just have to keep trying when this happens.

[junjo]

OK. Thanks again.

[Lost_N_BIOS]

I can see without downloading that is not correct, 8KB zip
I checked, it's all zeros. Keep trying, reseat the cables and make sure it's all correct.

Upload images of the cable connection to the programmer, and to the board if you want me to try and check it over for you. It will be hard for me to see the board's Pin1 BIOS connection, so add an image of the BIOS chip on the board without the cable, so I can see it's orientation and then another with cable attached to BIOS on the board so I can look it all over.

It may be on there in correct way, just not making solid stable connection just yet.

[junjo]

Okay. No problem

Please wait a few minutes.

[junjo]