Hello,
I have no background in Electronics. Just very basic knowledge building simple clone PCs alongside my brother during our teenage years (needed a computer at home, but it had to be a compromise between feature richness/hardware capabilities and cost).
My educational background is Mechanics of Materials & Mechanical Engineering.
Joining the community in search for help to solve a BIOS boot loop hazard I've gotten myself into after a BIOS update went wrong:
MB: Vendor HSB, BY511 NM-A541
Currently the MB tries to start and it powers up right after I branch the AC adapter. The power LED goes on for about 5 secs then shuts off for about 25 secs, then this same cycle starts repeating.
Downloaded the dump shared in this thread of the forum https://www.badcaps.net/forum/showth...ht=lenovo+y700 and then cleaned/swapped the ME region of .bin file with the matching one found in the INTEL CSME repositories using Intel Flash Image Tool and then again also using UEFItool. Tried and flashed them with SIP programmer and in both cases no luck.
Did also the same thing with a stock image extracted from a .exe and no luck as well.
Tried to just replace the NVRAM volume from my dump (which is corrupted) with the one from the file in the thread. No luck either.
Every time after I flash a .bin to the eeprom (using SIP programmer: reads and writes are successful and verify to be identical every time) I test and branch the MB to power with just the RAM on and nothing else: no HDD, KB, Display,.... Don't even put the CMOS battery back.
I have 2 16GB RAM DIMMS on. 32GB is the max the MB can handle according to the OEM. Don't know if trying to load from this state with this much could be a problem (PLEASE ADVISE).
[PLEASE WOULD LIKE TO KNOW IF MY TESTING PROCEDURE IS CORRECT, since I'm assuming it'd stay on for more than just 5 secs while it tries to search for a bootable device to which hand the control over.]
I did do one test after one of my flashes with the HDD branched and another one with a bootable USB stick, just to see if not finding a bootable device was, for some reason, making it power off.
Same result every time no matter what.
I have absolutely no experience with BIOS patching/stitching/modding and would like for you to check the .bin files i've been trying and determine if they're good and should work.
Cause in that case i'll know this isn't the cause, or the only cause, for the problem.
Would you please, please, please help me ? Please ?
I have no background in Electronics. Just very basic knowledge building simple clone PCs alongside my brother during our teenage years (needed a computer at home, but it had to be a compromise between feature richness/hardware capabilities and cost).
My educational background is Mechanics of Materials & Mechanical Engineering.
Joining the community in search for help to solve a BIOS boot loop hazard I've gotten myself into after a BIOS update went wrong:
MB: Vendor HSB, BY511 NM-A541
Currently the MB tries to start and it powers up right after I branch the AC adapter. The power LED goes on for about 5 secs then shuts off for about 25 secs, then this same cycle starts repeating.
Downloaded the dump shared in this thread of the forum https://www.badcaps.net/forum/showth...ht=lenovo+y700 and then cleaned/swapped the ME region of .bin file with the matching one found in the INTEL CSME repositories using Intel Flash Image Tool and then again also using UEFItool. Tried and flashed them with SIP programmer and in both cases no luck.
Did also the same thing with a stock image extracted from a .exe and no luck as well.
Tried to just replace the NVRAM volume from my dump (which is corrupted) with the one from the file in the thread. No luck either.
Every time after I flash a .bin to the eeprom (using SIP programmer: reads and writes are successful and verify to be identical every time) I test and branch the MB to power with just the RAM on and nothing else: no HDD, KB, Display,.... Don't even put the CMOS battery back.
I have 2 16GB RAM DIMMS on. 32GB is the max the MB can handle according to the OEM. Don't know if trying to load from this state with this much could be a problem (PLEASE ADVISE).
[PLEASE WOULD LIKE TO KNOW IF MY TESTING PROCEDURE IS CORRECT, since I'm assuming it'd stay on for more than just 5 secs while it tries to search for a bootable device to which hand the control over.]
I did do one test after one of my flashes with the HDD branched and another one with a bootable USB stick, just to see if not finding a bootable device was, for some reason, making it power off.
Same result every time no matter what.
I have absolutely no experience with BIOS patching/stitching/modding and would like for you to check the .bin files i've been trying and determine if they're good and should work.
Cause in that case i'll know this isn't the cause, or the only cause, for the problem.
Would you please, please, please help me ? Please ?
Comment