@chadalu - BIOS file should not be opened just after step #1, it must be done when I mentioned, otherwise you can mess up verification, that's why I made specific outlined steps Do it that way only
Chip legs should not have needed bent at all! It's this same )P*(^$()@^&% guy again isn't it?
Ohh, looking at the images, I guess this is more Asus fault, they did not put a normal SOIC8/WSON connection area there like you'd usually have that would fit either without issue.

This is not "Fine" that is kind of sloppy soldering job, but at least he cleaned up afterwards! If he would have looked at it with a loupe or magnifying glass when he was done he would see it may not all be connected, and some cold solder joints etc.
And it looks like he's possibly damaged the chip too, can't tell for sure, but it's damaged, deep gouges and scratches into the chip body.

Also, in second image, looks like he possibly damaged the board traces on the PCB from BIOS too, two traces look scratched, I can't tell if cut through trace or not
I'm talking about the two ones on left side, and those same two legs do not look soldered in very well either, so this may be a point of no contact, thus no power on.
Have him reflow those two legs only, possibly third too on this side, and see if it helps, this may be the only issue, unless those traces are cut through where it's scratched/gouged on the board PCB
And then also first leg on left side of first image, may be cold solder joint, reflow this too.

For SOIC8 clip, you may need power cable, and or main battery, or both, or only one or other, connected, before you can detect chip.
And yes, sometimes clip is a pain, it may take you many times reclamping before it's perfect, keep trying, but wait until he reflows that solder otherwise you are wasting your time (since you know the chip is already programmed)

If you have to, yes, go back to WSON, if so, use this BIOS, this will be 100% square one (hopefully your ME FW is not corrupted in the first dump you made, I did not touch it in this BIOS, only unlocked FD and put back your original BIOS region)
This BIOS CANNOT Be used with W128Q128FV chip - http://s000.tinyupload.com/index.php?fil...102789566079162

You do not need other dumps, the BIOS I sent you previously, and the follow-up should work, once chip is on there properly
Good to hear this guy is more friendly to now! Hopefully he is not charging you an arm & a leg to do this work, since if you've been watching him you can see it's very easy to do

Do you have a good image of the board, not cropped off like your first image linked in this thread, but showing that same area before you did anything, so I can see that chip/area?
This concerns me, and I wanted to see if it was maybe there before, or what it looks like in another image, in case it's hair or dust etc (or possibly scratch or ?)

Yeah, Asus really made my life more dificult in this one! i was there while he is doing this, the region is so small and there is a ton of micro things around!
The Soic8 chip would not fit there without a bend, the pad on the board is wson format!
He is the best person in my city to do this job(Small City Problems), others that i know would have melted my board at this point!

I didnt know about the batery or power cable, since i programed it using the clip without any power, i thought would work at same way using the clip on board
at this point i ill not try anything , i dont want burn anything plugging the baterry or power cord since the solder is no good.

I see the 2 traces that you talking about, i cant tell either if it is damaged or not, since im using my s20 camera to zoom in, and not a real zoom lens, looks like a little damaged, cant tell for sure, i would need a Magnifying glass to be sure

I think i ll go back to wson, im afraid of damaging the board or something else with soic8 soldering, he is not charging me anymore
He wants to see this notebook working, more than i!

about the image you sent , i was scared to hell when read it from my celphone, but it was just my cat hair!
And NO, it dont have acess to my Office!

I dont have any picture of the area before flashing, i take pictures of the entire board , But the most importante part, i dont have any, just the picture of the eproom chip that i have sent to you on first PM

i take other picture of the area , and a best zoomed image of the solder points, thr board pictures are from now

https://imgur.com/a/9srWr8o

Yes, it's not often chip area like this is constructed into WSON form footprint only, that's why I initially said no issues with SOIC8 because it's generally simply swap without having to mess with anything, same in inverse as well
At least now this guy isn't being such a pain for you

Yes, with chip on the board, sometimes you need battery or main power cable attached, or only one, and sometimes you need them both removed. This all varies from board to board
You wont burn anything, but yeah if connection not good is the issue here, trying to program the chip (which is already properly programmed) wont help anything. Chip should be fine and programmed, so no real need to attach CH341A to it
Before you go back to WSON, have him reflow those 4 legs I mentioned, two look really bad, this may be the only issue.

You have an image of the entire board, you showed me the WSON chip at first post (but image cropped to that chip). This was the image I wanted to see, uncropped. But I guess this is cat hair
Wow, third and fourth image (and last), looks like 3 possibly scratched traces on the board, not just two I mentioned being able to see in those initial images. Hopefully those are not through the coating and breaking the traces! << If so, then even WSON will not work now

I could try a reflow before going WSON, I ill ask him to take a look to see if there is any real damage on trails,( the worst part is reassemble the notebook, the eprom chip is on the back of the board ! it happens to have a power button onboard, so i dont have to put everything together, but at least 60% of the parts)
i think he has ability to make a jumper if trails is damaged (dont know if is possible, i realllllllllly hope is!!!!),

This zoom of s20 camera use some kind of AI that mess with image when you zoom to much,
Using my eye zoom, i think the worst was the botton one that looks like a small hole, the others looks "fine"

That picture was a zoomed image at full resolution, i didnt croped it.
But yes it was my cat hair!i they were sitting in the same location when the picture was taken!!!
I just blowed them, and no more cat hair scratch on mobo!

Here is a new package for WSON ONLY, this includes a 100% Stock Asus BIOS region (minus one volume) + your dumped FD (unlocked) and OG ME, this will not have your system specific details, we'll fix later!
Second same as above but with clean/UPD ME, both this and the above also have unlocked FD. And, third is the BIOS I posted at #31. And as a final last resort, I've also included a 100% untouched known working dump from another user
If it comes to that last resort, and then boots, then we know your original dumped ME FW was bad and carried over into the clean/updated ME FW and all other BIOS I made you.
That, or your original FD was corrupted possibly, or both. I'm asking another user for FD dump below, to have third comparison.
Anyway, this way you have four BIOS to try to boot from on WSON, if you go back to that. Keep in mind, these BIOS will ONLY work on the WSON chip!
http://s000.tinyupload.com/index.php?fil...612440331816375

None of these are unlocked, other than unlocked FD, we'll redo your menu properly once you're back up and running

Before going back WSON though, I suggest you have him reflow those 2-3 legs on one side and the one leg on other side, then try again and see if it boots.
During boot up attempts, do not connect HDD/SSD, and put in only one stick of memory in first slot, or at least attempt to boot with only one stick first, then put in second.
This way, if CMOS is retaining anything in any of these non-stock BIOS it will reset things.

Yes, if traces are damaged you can jump past, but if he did damage it during this work, it's unlikely that he's steady handed enough to do that kind of re-work without possibly making things worse. Unless he just jumps from leg or pad to the dots and copper pad well past the trace area.
Yeah, I can't tell from those images, if the protective coating right near the legs is just scratched, or the actual copper trace underneath is scratched too. Those are so fine, that if it's scratching into the copper trace it's probably broken the path.
Hard to tell this in person even, unless you put under good light, look with magnification, and or maybe get it wet or put clear flux on it, so you remove the "white-ness" of the scratch itself and can see what's actually scratched and what's not.

The image above is 100% scratches, not cat hair, just so we're clear, that I was talking about two different things there with the above and then what I assume you mean as cat hair on the other area (not BIOS chip location)

@cowpod - Would you mind, dumping your FD and ME from your GL504GW for me with FPT, so I can check something for user here, thanks
FPTw.exe -desc -d fd.bin
FPTw.exe -me -d me.bin

Fine, just to be clear this is the order i should try first.

1-SQ1FD.bin
2-SQ1FD-STKRGNVol1-6UEFIT-Vol7SH.bin
3-SQ1FD-STKRGNVol1-6UEFIT-Vol7SH-MECUPD.bin
4-noah0105.bin (last resort)

I ill check the traces first, if it is damaged or close to be, i ill give up on soic8, since he used the iron to solder the soic8, more damages are possible!

And yes, the car hair was on the image that you sent on post #33, not the bios area!

should i wait the cowpod bios dump before try anything?

I hope tomorrow i ill bring you good news !

Yes, that order would be best to try You can add this to top of that list too >> OGRegInMEFWUPDVSCCAddFD
If the traces are damaged, it does not matter what kind of chip you use, any damage to trace will affect either chips connection to the rest of the board.

That is not cat hair on image #33, can't be, especially because it exactly follows the traces, if you think so please show me new images and I will look again but I can already tell you this isn't cat hair for sure.
That image I posted is from your new images from post #32, after you said you seen cat hair
On image #31 maybe yes, but not #33, that is scratches to the PCB, I can see on all images easily.

No, I only asked cowpod for FD and ME, so I could look at something, in case maybe later we need to try other things.
The BIOS I sent you to put on SOIC8 chip should work on either, so it can really be tested first, then the 4 above if you wanted
If it gets down to noah01015 BIOS and still nothing, then anything cowpod sends me wont matter either, because really if none of the BIOS I made you based on your dump work, and then noah0105's BIOS does not work, something else is wrong.

Sorry , i mencioned the wrong post, the right one is #31, as you said!

Ok, lets begin @Lost_N_BIOS

The soic8 chip soldering was fine and all the legs were sodered. So i decided to move to WSON.

I flashed the SQ1FD.bin, like the first file you sent to me, it boots on asus splash screen, but remains there, so i cant give any command or enter bios,

So i moved to last Resort (sorry i was late and need to leave, so i skipped the 2 and 3, and i was afraid that the board could suffer any damage by solder and remove the chip 4 times),and the same thing happens as the other files

It first boots flashing all leds colors (it does this show when you flash a bios update), them it reboots, so the leds become red, the splash screen apperas and right after they go all colors again (supposed to stay red and boot).
the funny thing is,if turn off and on again this process repeat again! there is any chance that bios have some write protection that prevents notebook from set it defaults settings and boot? or something like that?
i think the bios is fine, looks like something is preventing it from move foward!

I cant tell what is going on, since i used the last resort, it supposed to boot, maybe it was the bios version? i have a ftp dump of my bios on 305 version! (but dont have chip dump on this one),

The guy says that he can solder 8 thin wires on the pads just after the eprom chip, and make me like a jumper cable, so it ill work like the clip, and i dont have to teardown the notebook every time.
He said if the uses too much hot air on the area, the protective coat of the board will go off, and there is a risk of damaging the trails

I made a video when i turn it on

https://youtu.be/8Dss6JBmGjk

here another pics of the area, looks like no damage on the trails

https://imgur.com/a/tD7tmKi

and the 305 dump

http://www.mediafire.com/file/qbsuvnvqy26c20h/file

@chadalu - The soldering was not "fine" for sure at least 3 legs needed properly reflowed, no matter what that guy said or thought, this should be done

Did you try, remove hard drive and one stick of memory, then try to boot it again, to try and reset CMOS even though BIOS programming should have done that anyway this may help.
Try this, and try remove the CMOS battery and boot once too

It may be that when you change the setting you changed about XTU, this changed something on EC/KBC FW, and that may be the issue. This is on other chip, sometimes you can't even read/write this chip without doing via KB ribbon cable.
BIOS version does not matter in this case, we're using the one you were on so it would match EC/KBC FW if that were to be any issue.
Dump the Winbond W25Q80EW with 1.8v adapter, and send to me, I can check it to see if anything looks corrupted, and see if this is the EC/KBC FW chip or not (may be vBIOS, we have to see)

The image link above does not load any images Can you please re-up, or put in zip would be better, thanks

The two files you skipped were most likely to be bootable, vs the first one. Unsure about last one, since it's another users, but it should boot too I assumed
The two you skipped though, were 100% stock BIOS region, but yes, it's not good to continually remove/reapply this chip, that's why I suggested you put on the SOIC8 to begin with (Should really leave, once properly soldered in).

Yes, maybe wires soldered in place would be helpful for you, but you'd need an adapter on the end that would fit either SOIC8 or WSON, or DIP8 and you purchase a DIP8 chip.

Hi , @Lost_N_BIOS

Here are the images
http://www.mediafire.com/file/2hyi1h8a4e...os+(6).zip/file

Zitat

---

Yes, maybe wires soldered in place would be helpful for you, but you'd need an adapter on the end that would fit either SOIC8 or WSON, or DIP8 and you purchase a DIP8 chip.

---

I mean, i cant just make 8 wire solders on the pads next to chip, and just plug them in the right order in the CH341A programmer slots 1-8?it ill work like it a soic8 clip.

_____________________________________________________________________________________________________________________________________________________________

Zitat

---

It may be that when you change the setting you changed about XTU, this changed something on EC/KBC FW, and that may be the issue. This is on other chip, sometimes you can't even read/write this chip without doing via KB ribbon cable.

---

So , when i flashed the other guy mod, it kinda messed with other chip config? it is even possible

On bios 307 bios, asus locked undevolt via windows using Xtu or throttlestop, something related with plundervolt

So the Guy that moded my bios said said:

Zitat

---

Try this mod and response the result.
https://userupload.net/7xvobo5j3oec
Also testing undervoltage with xtu or throttlestop again ,then response the result.

---

So there is any change that he messed up with something else , like moded some module that changed something on EC/KBC ?
There is any way to lookup it on his mod?
And, if so, there is any way to change it back?

______________________________________________________________________________________________________

The file 2 and 3, they are entire stock from asus? or they have some part of my dump ? i can try flash file 2 or 3 as last attempt before losing my hope and send to asus (ill take eternity to fix it)


----------------------------------------------------------------------------------------------------------------------------------------

I tried removing the hd ,memory and cmos battery, same results.

I made a dump using CH341A v1.31(1.4) (CH341AFree) and asp 1,41 , i attached it in the post

Ubu says VBIOS in Padding

Man reading this one was easy !

@chadalu - You need wires connected to an adapter, otherwise pointless to connect wires. You cannot have wires connected to nothing like you mentioned, to then plug into programmer, there would be nothing to program.

No, I meant maybe when you changed the XTU setting it changed something on other chip, I am not sure, only thought it may have happened. It's not about that BIOS, or flashing it, it's about the settings change you made.
I have ONLY seen issues with XTU when users use both BIOS and XTU software, sometimes if XTU is installed, or some default settings changed before mod BIOS Flashed, this can cause issue. Sometimes changing settings in software later can cause issue etc
So to me, never a good idea to have both, only use one or the other, reset and remove the software if you plan to change XTU stuff in BIOS, or do not use BIOS to change XTU stuff if you make changes in software

HE did not change anything in other chip, only BIOS. Mod BIOS worked fine until you made BIOS setting changes, I thought, correct?

BIOS 2-3 I sent you in that WSON package are 100% stock BIOS region + one has your original ME FW, and other has ME FW I cleaned and updated (using your original ME FW as base) << That may be messed up in both, but usually would only cause loss of ME FW functionality if it was.

What is above dump from, and why? If you're wanting me to compare to something, tell me what you wrote to chip, so I don't have to compare one by one against 10 things.
Ohh, I see! This is E4914 SKU 30 (RTX 2070) vBIOS chip dump. Do you see any other SOIC8 chips on the board?
The UBU vBIOS thing is about the onboard Intel vBIOS rom for integrated graphics

If you try to send back to Asus for RMA, be sure that guy cleans BIOS chip area good with alcohol to remove all flux he may have used, and then hopefully they wont noticed the scratched PCB and deny the RMA
Ohh, never mind, I can clearly see the scratched and no repaired (due to solder reflow) traces, and there is large blob of solder out of one corner/contact side of chip. They will immediately notice this if/when they look at board and deny RMA
Not good You will have to get VERY Luck and them send you replacement without opening this up and looking, or opening up to reflash BIOS etc, otherwise they will deny RMA On this. So if you send in, have everyone you know cross their fingers.
Sorry, I would have suggested you did this initially if I knew you was still under warranty. If you can, however, return it to place of purchase for replacement instead, that may go over a lot smoother, if you still have time for that.

@Lost_N_BIOS
On bios 307 there is NO way to change any voltage settings on xtu or throttlestop, the option was locked due the patch to "fix" the plundervolt exploit.
What i was tryng to say, is that the guy who moded the bios tried to bypass this "fix".
What i asked you to compare, are these 2 dumps, one is the dump that i made using FTP "my original dump" and the other is the moded bios file that i flash using FTP , to see if there is any changes that the guy changed anything related to voltage and bricked my pc!


http://www.mediafire.com/file/8dif24vdwz...ompare.rar/file

So to be clear here what i did :

1-I was on 305, i flashed 307 from ezflash bios utility ->Pc was working (at this point i cant change any voltage settings anymore,)

2-I made the dump using FTP 307 (the file i sent to you) -> Pc was working

3-i Flashed the moded bios (didnt received any error msg)-> Pc rebooted and never boot up again, I dont have any chances to change any settings ! and at this point the screen was all black, not even showing that fancy Rog logo

4-I asked you for help and we started this thread

5-I never used Xtu and throttlestop together!
Throttlestop has a simple and better UI, so i prefer using it

6-When i flashed the moded bios, i was tryng to solve the NVMe drivers problem, so I've made a clean windows install and Throttlestop was not automatic launching on boot or running,
Even it was running, i wont be able too change any voltage settings because of the lock !

Update 1 __________________________________________________________________________________________________________________________________________________________________

There is any changes of using another user Base?

I lookup the entire board, and there is no other Soic8 chip !

I dont have warranty anymore, the notebook made 1 year, Rma is out of option.
Asus just responded my ticket, and there is no support for my notebook in my country

I ill try to flash File 2 and 3 late today !

Update 2 ____________________________________________________________________________________________________________________________________________________________

There are 2 JDEBUG Pads on the front side of the board, Is there any utility to them? i can buy the socket and make a cable if we can work something out of them.


https://imgur.com/a/Xz8KGkd

Lost_N_Bios, My computer is currently in for repairs (not realated to BIOS :D). I'll post my FPTW dump as soon as I get it back

@chadalu - Ohh, Ok, thanks for the info. I assumed the mod was a menu unlock! The BIOS worked for a while though right, and then you changed something in BIOS and it bricked, correct? Or, did you flash it in, boot to BIOS once, change nothing, save and exit and it was bricked?
Ohh! So, to confirm, you sent him FPT dump, he modified and you flashed in and it bricked right then? If yes, then it's a bad mod, and nothing to do with you changing any settings in BIOS. Sorry, I thought you changed something, then it died.

The files you uploaded to mediafire at post #43, I already have these and have compared them in some of my questions or comments to you previously
Did you ask him exactly what he changed? If not, ask him to explain to you, I've never seen anyone deal with this, so I don't know what changes to settings or other mods may be required (ie change to ME FW, changes to BIOS modules, or just BIOS setting change, or what etc)
I kinda need to know some answer from him on that, it's not easy to blind compare. I can compare some usual modules to see if/what settings have been changed, but other than that it's MUCH easier if he tells you what he edited so I can find and look vs a blind hunt through 100's of BIOS modules.
Just looking at three modules, which we usually edit to change BIOS settings and or menu visibility, I see only the following changes >>
#1 unnecessary edit to Setup (adding a name "tag >> 239Mod" so he knows he edited). << Maybe I mentioned this in PM to you already? If not, then I've also seen him edit same/similar change to someone else bricked BIOS too, so this may be what's bricking BIOS he's edited recently, not sure.
^^ I also see menu renamed item (Overclock Performance Menu changed to Overclock Menu). Additionally this module has been rebased/re-assembled, probably due to rename of menu, but other possible changes may be there too, which I cannot tell, but no actual "settings" changes
#2 - Menu related changes, revealing menu's and or hiding original menus etc
#3 - Me FW Image Re-Flash enabled, this will disable ME FW, unless/until user disables this setting in BIOS - This also changed in NVRAM
#4 - BIOS Lock Disabled in NVRAM

All files I've sent you were either using stock BIOS or your "original" FPT backup, or some have ME FW from your original chip dump, so none of it would have any of his changes
I never mentioned throttlestop and XTU being used together, my comments where about XTU and BIOS changes only.

How is #6 possible, if BIOS bricked right when you flashed it in, and what lock are you talking about, you can change BIOS settings, there is no lock on that?

Debug port may be connected to/same as BIOS connections, you'd have to have that guy check for you, if he knows how/can etc

If I were you, I would have this guy put back on SOIC8 chip again, and check with loupe all solder points are good. Then you can try to fix at home without having to have him keep resoldering chip.

@cowpod - Thanks! I think maybe this wont help, since even direct flash in of other users known working dump didn't help, but I would still like to look at what I originally tagged you about, so thanks
What happened to your system??