Need some help re-writing a serial to my motherboard for an HP Pro x360 Fortis 11 inch G9. Attached is current bios file on the device that I need to write the new serial to.
Any help is appreciated.
Any help is appreciated.
-
-
Hello everyone, I'm asking for help from anyone who can help me. I've performed a dump of my HP x360 11 Fortis G9 computer, with motherboard: ANOLE10-MV-GMB 6050A3332901-MB-A01 2021-11-09. I noticed that it has two identical chips (W25Q256JVE), one on the top of the motherboard and one on the bottom.
I've performed a dump of both chips (W25Q256JVE), both with the same reference; the top one is marked as BIOS SKT and the bottom one is marked as U351 (screenshots attached).
I used the RT809HSE programmer to read/dump the chips so I'd have them on hand in case I needed to reflash the BIOS if I had any problems and needed to flash again.
I read the chip without removing it using a WSON 8X6 pogo pin and a stable, fixed clamp on the board (no reading errors or poor contact). The connection is stable, as shown in one of the screenshots I added. But I have several problems:
The RT809HSE in automatic detection identifies the chip as: W25Q256FV@WSON8 8X6 instead of W25Q256JVE, and if I manually select: W25Q256JVE, no chip appears in the WINBOND menu, only: W25W256FV@WSON8 8X6, W25W256FV(X4)@WSON8 8X6, W25W256FV@SOIC16, W25W256FV(X4)@SOIC16, W25W256FVC@TFBGA24, W25W256FC(X4)@TFBGA24, W25W256FB@TFBGA24, W25W256FB(X4)@TBGA24, and W25W256FV(ISP).
I've done 3 readings with:
W25Q256FV@WSON8 8X6
W25Q256JVXXQ@WSON8 8X6
W25Q256JVXXQ(ISP)
I've done a full analysis comparison in the HxD program and all 3 are different, so my question is, which is the correct reading? Which chip should I choose in the menu? I've lowered the reading speed on the RT809HSE to the minimum, and I've done the same with the U351 chip in the same way as the first one, and the same thing happened to me. The 3 readings/dumps are different. Which one would be the correct one? Am I doing something wrong? Am I selecting the wrong chip type?
I'm attaching the readings/dumps for the two WINBOND W25Q256FVE chips. I hope you can solve my problem and see what I'm doing wrong.
Thank you very much in advance.Comment
-
Type the laptop serial number, full name and model, motherboard model, etc.
read the forum rules..https://www.badcaps.net/forum/troubl...before-posting
Comment
-
It's true, with so much writing I forgot to provide the computer details. I read the instructions but forgot. I apologize. The computer details are:
Product Name: HP Pro x360 Fortis 11-inch G9
System BIOS: U94 Ver.01.14.00 04/14/2025
Serial Number: 5CG2325GYR
SKU Number: 6Q893ES#ABE
Feature Byte: 476J6S6b7B7H7M7R7W7maBaQapaqauawbVbhcAdWeTfPgFk8mEnVngpnpqpr.tG
Build ID: 21WWA1BZ601#SABE#DABE
Product Family: HP
System Board ID: 89AF
System Board CT Number: PPLQC00WBKL00D
Board: ANOLE10-MV-GMB 6050A3332901-MB-A01 2021-11-09
I hope this helps you solve my problem. Thank you very much in advance.
Best regards.Comment
-
Now I have a serious problem and I ask you for help please; as I could not get any readings, I was doing tests in all possible ways both with the CH341a programmer and with the RT809HSE and with a WSON8 clamp cable, I must say that I did not have bad contacts because I use a clamp that holds it well without movements, from so many readings that I have done I have blocked the equipment; I have connected a reading by putting the charger and the led on the board lit up and I think I have done something to the equipment, since the power button led lights up and the Caps Lock key led flashes 5 times and there is no image, it stays on a black screen and the equipment does not start; it doesn't turn on and before doing the readings it did turn on, I simply wanted to make a copy of the bios reading and now I've messed it up, please can you help me see what I can do? I've given you all the device data and I've read the bios again with the CH341a and it gives me a file identical to the one I had read before it crashed, to all this with the CH341a I have done the reading always isolating pin8 VCC to not supply voltage to the board and both before it crashed and now that I have read it again it gives me the same file, so I understand that I have not damaged the chip but now it won't turn on, and I don't dare flash anything with any programmer because as always they gave me different readings, I'm afraid of making it worse and doing more damage, please I ask for urgent help, please !!, I add all the readings that I have been able to do to see if you can solve my problem,
thank you.Comment
-
Comment
-
Hi, thanks for responding, SMDflea!
I'll explain the problem. The computer doesn't have a BIOS password. I simply wanted to dump the BIOS to save it, and I did it with both programmers. The problem is that when I first did it with the "CH341a" as usual on the motherboard without removing the chip and selecting 3.3 volts, when I did the reading on the board the power LED light came on, then I read in a forum post to isolate the 8 Vcc pin and do the reading without voltage, and so I did and saved the reading, but then I also wanted to do a reading with the RT809HSE programmer and what happened to me was what I mentioned in post #3 each reading I did was different I chose the chip option I chose, it didn't matter, if I repeated the reading and compared it in HxD all the readings were different, and I don't know if it's because it has another chip at the bottom and they share the bios or that I simply can't do a reading on the board with the RT809HSE and I must extract the chip yes or yes, the thing is that I wanted to do something that can't be done and that is: connect the power adapter to the board to give voltage to the chip and I also connected the rt908hse and did the reading with both things at the same time and the led on the board started to blink base while it was reading, and that's where I messed up, because I waited for the reading to finish and now it stays on a black screen with no image, it doesn't start or enter the bios, it just turns on and the power led stays on and the Shift key led blinks 5 times and it stays there, I don't know if I messed up the chip by supplying it with voltage from the programmer and from the board with the power connector connected at the same time, or if I messed up both chips it has or if I could even corrupt the lower chip it has; A Nuvoton NPCX998HA0BX, which is much smaller than the NPCE288 and is soldered with balls underneath without pins...
What do you recommend? Should I try flashing a reading that you know is correct with the CH341A and without VCC on pin 8, as I did to read it on the board? The funny thing is that I think I also repeated some readings with the CH341a, and I also think I compared them on HxD and they were different.
Can you confirm that one of the .bin files I sent you contains my data or is it valid for flashing it on the computer? I've already entered all my data in the previous post. Can you confirm that one of them is valid and try flashing it?
Thanks a lot in advance!!Comment
-
The CH341A backups seem good, all data intact. I don`t know if you`ve corrupted the chip or not but you can try flashing back one of those backups. You could have dislodged a resistor around the bios chip so check around it carefully. With the CH341A the chip has to be erased before programming.Comment
-
Thanks again, SMDflea!
I looked at the board with a magnifying glass and none of the resistors around the chip were damaged. I also didn't remove the chip because I don't have the air conditioning station yet. That's why I took the readings with the chip on the board. However, the RT809HSE never gave me the same reading when comparing data in HxD, which is what surprised me. The RT809HSE is supposed to be better than the "CH341a," but the most likely scenario would be for the chip to be damaged because I've applied voltage to the board with the power supply and voltage with the RT809HSE programmer. However, could you clarify some questions for me? Is the RT809HSE not suitable for taking readings with the chip on the board, not even in (ISP) mode, which is its own mode? Do I have to remove the chip because it could interfere with the other identical chip (W25Q256JVE) underneath it, which shares the BIOS with the main one? (I attached screenshots of everything in #post3).
What I'm going to do while you reply is something else;
I'm going to redo some readings of the two chips with the "CH341a" and without voltage (with an isolated 8 VDC) and I'll upload them here for you to review and compare. You're the professionals, and maybe I'm doing something wrong...
Let's see if we can get something clearer this way...
Thank you very much, I'll upload the files soon...Comment
-
Oops, what I'm realizing is that I had already written in a previous post that I had already done this; I had already read the SKT BIOS chip with the "CH341a" programmer and it gave me the same file as before when the computer was fine and turned on; that means that the problem may not be in the chip but somewhere else; could the other chip have been corrupted? Or the KBC nuvoton? Ugh, now I really think I've screwed up because I don't think the nuvoton can even be read with anything, it's very new and small and without pins, it's with tin balls underneath, and if both W25Q256JVE chips were corrupted, would I have to flash both? and I think they should be the same file for both? I have downloaded the bios softpaq file from the hp website and extracted it but this file no longer gives me the option to unzip to ". bin file" but to extract it normally or "recovery via USB" with the key combination win + b or "win + v" (which I tried and nothing; it no longer detects reading from usb), so I have extracted it normally and it gives me 2 files: U94_01140000 of (31.3 Mb) and U98_01140000 of (31.4 Mb), and I don't know how to make them exactly 32 Mb so I can try to flash them, if you can help me in any way I would appreciate it...
Anyway, I'm going to dump the two chips again with "CH341A" and upload them to see if they are exactly the same as before and see if it's possible do something...
See you soon...Comment
-
Here are the readings for both chips, which are identical. I'll see if anything strange shows up, because I think they're the same as when the device was turned on. I think I've damaged something else or the Nuvoton has become corrupted. I hope not, because otherwise, I think I'm lost. I'll see if I can see anything I'm missing, or if I can run some tests...
I look forward to your opinion...
Thanks.Comment
-
Well, I managed to get the computer to boot with the attached file, but it takes a very long time for the BIOS to boot, and it takes a very long time until Windows appears. There's a problem with the BIOS, because I tried updating the BIOS downloaded from the HP website once in Windows, and I got a firmware update error message: "Update of the Intel management engine firmware failed, because the target Intel management engine firmware update was found to be invalid." (screenshots attached).
Am I missing something in the file I flashed?
In that case, is there anything I can do with all the files I've uploaded in previous posts? Maybe you can see if the firmware I'm telling you is missing is there and add it to this latest file, which at least "takes a while," but boots the computer?
Come on, we're almost there. I'm sure you know the solution. Please, help me out and see if we can fix it...
Thanks...Attached Filesif you find these attachements useful please consider making a small donation to the site
Comment
-
-
Well I don't know if anyone is reviewing my problem, I'm not an expert but I see that it's a problem with the ME Region firmware of my dump that must be corrupt because I flashed above the chip without having a good backup of the chip, I tried to clean the ME region (being a bit lost) in the instructions here in a post I found in the forum and from the dump I used, I used: CSME System Tools v13.50 r3 and CSME 13.50 Repository r7, and through flash image tool, I replaced ME sub partition with my corresponding file which is: CSE ME 13.50.27.1987 Prod Atom N and finally I built the image, I flashed it but it didn't work and believe me all this is too much for me, I'm not able to move forward and for being a novice I think I've given everything I could, I can't move forward and I still have this problem, I also don't know if I should flash the same lower chip or what kind of file it has or if it influences Booting; I can't find any information about this motherboard, neither the datasheet nor any other motherboard that uses two identical W25Q256JVEN chips, so if you could provide any information and help, I'd really appreciate it.
I've tried flashing other files in the main SKT BIOS, but it crashed again and wouldn't boot. The only way I can get it to boot is with this latest file I uploaded, which does boot, but it has the ME Region issue.
I'm attaching the file I created with the ME region cleaned. Please help me, because my head is about to explode...Comment
-
Comment
-
Thank you so much for your help, your time, and for helping me, SMDflea. I really appreciate it. I know I still have a lot to learn and test, and I'm working on it, but I still have a long way to go, so thank you all.
One thing: thanks for the file you offered me, but before testing it, I wanted to tell you:
With so many tests, I think I've also corrupted the other lower chip (the one similar to the SKT BIOS -> W25Q256JVEN), and I don't know if I should flash it and set everything to 00 or FF, or if I should flash some file on it. I'm also not sure if they both work together at the same time communicating with each other when I boot, or if it's just that when I boot for the first time, only the main SKT BIOS works, and then it writes information to the lower one... The fact is, right now I'm sure I have it wrong. I've also done some readings on it, but I don't know if they're good. The thing is, I don't know the structure it should have. The official softpaq for this official BIOS model from HP, when unzipping it leaves 2 . bin that I mentioned in another previous post (U94_01140000 of (31.3 Mb) and U98_01140000 of (31.4 Mb), which makes me think that maybe one file is saved in the main SKT and another in the lower secondary chip...
I also tried (just to test) through the softpaq to do the option to update the bios via USB (when running HpFirmwareUpdRec, it only gives 2 options: "Update on Windows restart and USB Recovery"), on Windows restart I kept getting the ME Region firmware error, and via USB it didn't even read it, but the structure that it set up on the USB was several folders: "HP\DEFW\Firmware" and this file called firmware is 62.8Mb, meaning it must contain information that is saved on both chips because the maximum size is 32Mb on each chip, which It makes me wonder if both chips can work at the same time or if they must contain some joint information in order to boot properly. Do I make myself clear? I hope so....
I also have to confirm that after multiple tests, reading the chips on the board can only be done with the "CH341a" and isolating pin 8 from VCC, but from what I've been observing, sometimes and depending on the file to be flashed, the verification fails. That's why there must be something on the board that can interfere with the reading, writing, or verification (it took me a lot of work and many writing tests to get the computer to boot again). And without isolating pin 8, the board turns on when supplying 3.3 volts and the reading is false or incorrect. The RT809H has been ruled out because it doesn't read correctly and the board also powers up.
The ideal, I know, is to extract the chips from the motherboard and do everything directly on the programmer, but I won't have one for about a month, which leads me to I'm not sure if the lower chip can be removed because it barely has any pins. I hope you can confirm if it's possible to remove and read it.
But since I was able to do something with the "CH341a" and since I already have corrupted chips... having said all that:
Could you tell me what I should do? Should I leave the second chip empty with zeros or FF and try with your file? Should I still try with your file regardless of the state of the other chip? Or should we look at the structure of the file created in USB Recovery and see if the information can be extracted from both chips? In that case, I don't know how to do it...
While I wait for a response, I'll send the file generated in USB Recovery just in case you need it for further investigation...
Thanks!Comment
-
Well, while I waited for news, I ran more tests and nothing. Thanks for the SMDflea file, but it didn't work. With that file, when I plugged in the computer, the motherboard's LED flashes yellow continuously, but it doesn't boot...
Now that I'm done, I've run every test I can. erasing the other chip, leaving it empty, and nothing, the computer does not start, I have noticed that every time I flash any file, the verification always gives me an error, so I do not know what it can be, if some kind of protection or if the two chips are intercommunicated and while you erase one the other is erased and if this is the case it is normal that it never starts, but what is certain is that there is something between them, at the moment I do not know what else to try, in fact I have flashed again with the files that did start the computer and again it did not turn on, I do not know what happens but it is something very strange, when it coincides in some way it seems that it can boot but with the usual ME region problem, but for it to start it is a matter of finding the way or coincidence so that it can turn on without being blocked; It's crazy. I think the only way is to have the files for each chip, extract them, flash them off the board, and then check again on the board, because I don't think there's any way to get this device working... a shame.
Thanks anyway for your attention and help...Comment
-
Make sure you remove the main battery from the laptop when flashing BIOS, it shouldn't turn onI also have to confirm that after multiple tests, reading the chips on the board can only be done with the "CH341a" and isolating pin 8 from VCC, but from what I've been observing, sometimes and depending on the file to be flashed, the verification fails. That's why there must be something on the board that can interfere with the reading, writing, or verification (it took me a lot of work and many writing tests to get the computer to boot again). And without isolating pin 8, the board turns on when supplying 3.3 volts and the reading is false or incorrect. The RT809H has been ruled out because it doesn't read correctly and the board also powers up.
It looks like you're doing it with the battery or charger plugged in, the motherboard shouldn't have any power source connected
If not, please disregard my messageComment
-
Hi m1ch43lzm, thanks for writing.
I've always done dumps and recordings by completely removing the motherboard from the computer, without the battery, CMOS battery, SSD, or Wi-Fi card. The reason the motherboard LED lights up is the programmer itself. Both the "CH341a" and the RT809HSE do this (not the battery or when connected to power). They do this when they power the chip during detection or reading/flashing. It can be seen that the 3.3 volts make the board have enough voltage to try to turn on when reading the chip on the board itself, that's why I did the reading with the "CH341a" isolating pin 8 of VCC because it is the only programmer that detected the chip on the board, (with the RT809HSE I had no way since it always injects voltage to the chip), that's why I think that almost everyone removes the chip from the board and then uses an adapter with the RT809HSE to make the recordings and readings outside in vacuum, but as I have commented I still cannot extract the chip and the only way I had to do it is as I have commented. It's true that, in a moment of total desperation, I connected the power adapter and powered the board, and also powered the chip with the RT809HSE programmer (just to test it), and that's when I screwed everything up, because after that, nothing worked right. It's true that it shouldn't have, but I was already desperate. And I'm also not sure if the chips have been damaged, because as I said, if I try to flash several files on the chips, at some point it starts booting on the 8th or 9th time, but with the same problem, always with the ME region.
I appreciate all your opinions, but for now, things are not working...Comment
-
As an anecdote, and looking through the posts looking for information, I have been able to see a model similar to mine; an HP Elite x360, which is not the same board but has the same system: (2 chips exactly the same as mine, and from what I have seen the lower one is the EC chip and the upper one is the main one), I add a screenshot that I found, based on that could it be built having the softpaq downloaded from the official HP website (which I have already uploaded here in a post) and separate it and create the main BIOS part and the EC part? Let's see if someone can give me some more info, because if so, then a recovery copy is not saved on the lower chip but it is other separate information for ECAttached Filesif you find these attachements useful please consider making a small donation to the site
Comment
-
-
This specification for the HP ProBook x360 Pro x360 Fortis 11 inch G9 Notebook PC Hybrid (2-in-1) can be useful for upgrading or repairing a laptop that is not working. As a community we are working through our specifications to add valuable data like the Pro x360 Fortis 11 inch G9 Notebook PC boardview and Pro x360 Fortis 11 inch G9 Notebook PC schematic. Our users have donated over 1 million documents which are being added to the site. This page will be updated soon with additional information. Alternatively you can request additional help from our users directly on the relevant badcaps forum....09-07-2024, 05:50 AM
-
This specification for the HP ProBook x360 Pro x360 Fortis 11 inch G9 Notebook PC Hybrid (2-in-1) can be useful for upgrading or repairing a laptop that is not working. As a community we are working through our specifications to add valuable data like the Pro x360 Fortis 11 inch G9 Notebook PC boardview and Pro x360 Fortis 11 inch G9 Notebook PC schematic. Our users have donated over 1 million documents which are being added to the site. This page will be updated soon with additional information. Alternatively you can request additional help from our users directly on the relevant badcaps forum....09-07-2024, 05:50 AM
-
This specification for the HP ProBook x360 Pro x360 Fortis 11 inch G9 Notebook PC Hybrid (2-in-1) can be useful for upgrading or repairing a laptop that is not working. As a community we are working through our specifications to add valuable data like the Pro x360 Fortis 11 inch G9 Notebook PC boardview and Pro x360 Fortis 11 inch G9 Notebook PC schematic. Our users have donated over 1 million documents which are being added to the site. This page will be updated soon with additional information. Alternatively you can request additional help from our users directly on the relevant badcaps forum....09-07-2024, 05:50 AM
-
This specification for the HP Pro x360 Fortis 11 inch G9 Notebook can be useful for upgrading or repairing a laptop that is not working. As a community we are working through our specifications to add valuable data like the Pro x360 Fortis 11 inch G9 boardview and Pro x360 Fortis 11 inch G9 schematic. Our users have donated over 1 million documents which are being added to the site. This page will be updated soon with additional information. Alternatively you can request additional help from our users directly on the relevant badcaps forum. Please note that we offer no warranties that any specification,...09-07-2024, 04:30 AM
-
This specification for the HP Pro x360 Fortis 11 inch G9 Notebook can be useful for upgrading or repairing a laptop that is not working. As a community we are working through our specifications to add valuable data like the Pro x360 Fortis 11 inch G9 boardview and Pro x360 Fortis 11 inch G9 schematic. Our users have donated over 1 million documents which are being added to the site. This page will be updated soon with additional information. Alternatively you can request additional help from our users directly on the relevant badcaps forum. Please note that we offer no warranties that any specification,...09-07-2024, 04:30 AM
Comment