Hi Lost_N_BIOS,

Yes, my M2 SSD can only be detected in Linux when using external enclosure. Not when placed in the M2 slot.

>>>In whatever OS you can see the drive in, where you formatted with Win10, delete all partitions so it's a RAW disk (Use some >>>partition tool if Windows wont do this) - then try to use as secondary spare by itself (not in enclosure) in the main system >>>again, see if you see it in disk management or not.

Previously, I have done what you had mentioned, it did not work at all.
Back then, I even tried using Macrium, EaseUS Partition,and Minitool Partition Wizard to detect the formatted M2 SSD (when placed in the M2 slot) as a secondary spare but all failed to detect it. Cannot be detected in Disk Management at all. Only with the external enclosure case, all the software recognise it.

I have even gone to the extent of using the exact diskpart command the last time to clean the eMMC,the main harddisk. After that step, the BIOS did not detect the M2 SSD. During the installation of Win 10, the formated M2 SSD could not be detected.

I am still sensing that the BIOS has something disabled but I may be wrong. Maybe the slot for M2 SSD is faulty too.

Thank you for your assistance so far.

Sounds like this M2 slot is disabled in BIOS, or only configured for certain things in BIOS (Slots can be set for only certain devices, that's what I hoped to check but can't), or you are inserting incorrectly (or it's not compatible for some reason)

Please email the company that makes this, and ask them for a copy of the latest BIOS (preferably a bin file, tell them you need to recover from bad flash and have a programmer)
If they say no, ask them for latest BIOS update copy then

I will keep stabbing BIOS on my end and see if I can coax out what I wanted to see originally!

* Edit - please dump BIOS with this, lets see if BIOS is same as FPT dump (backwards layout, upside down and bottom two volumes broken << That's what contains what I need, of course)
This may setoff virus warning, it's false positive due to access BIOS FW coding, so disable virus program while you download and use. You cannot move it's window, open, click read, then once it's done click save, and send me the file
https://www.majorgeeks.com/files/details...up_toolkit.html

Hello Lost_N_BIOS,
The software that you recommended from majorgeeks did not work.
I tried contacting the manufacturer and they have not answered my emails.
However, I was lucky when I tried the tool, AFUWINx64 from AMI. I think I was able to extract the BIOS file.
Could you help to unlock this BIOS, please?
Thank you for your wonderful assistance.

What did the BIOS Toolkit tell you as error? AFU dump will be same as FPT dump, I assume, checking - yes, same, this must be normal and is how this BIOS is poorly built
I know the module it's in, but can't parse and then extract it properly. Aha, got it, somewhat (one way, but not the way I wanted)! So, this means I can change settings for you, but I can't unlock BIOS due to I cannot extract the necessary modules to do that properly.
All settings are set to UEFI mode right now, so only work on getting that method to work (ie GPT partition on USB and main drive) CSM is disabled on BIOS defaults/optimal and enabled on Fail safe

Can you see this setting SCC UFS Support (D29:F0), never mind, I see you can't even see chipset tab. I think enabling that will speed up performance on your main drive/eMMC and may allow this other to be detected too, unsure (Test BIOS below)
Flash via >> FPTw.exe -bios -f SCCUFSEditRegion.bin

http://s000.tinyupload.com/index.php?fil...622069337080736

@lfb6 - I see this, and have never seen before, do you think it's causing this issue? *** Please note @N.D. - I did not adjust this setting in BIOS above
HDD Connection Order >> Set to "Adjust" >> Help String (AMIBCP 5.02.0023 or 0031 you can check with the full BIOS file above) = Some OS require HDD handles to be adjusted, i.e. OS is installed on drive 80h. - Options are adjust/keep
This is at Advanced >> CSM

Hi Lost_N_BIOS
Thank you for your new BIOS.
The flashing of your BIOS under administrator command prompt was ok. After flashing the new BIOS, it showed a successful message.
But after the restart, the screen turns black. Now I cannot log into Windows.
I tried using a bootable USB but nothing appears on the screen.
Any advices?
Thanks

Zitat von Lost_N_BIOS im Beitrag #19

---

.... I see this, and have never seen before, do you think it's causing this issue? ....

---

Hi Ifb6,
The attached photo shows how the slot of M2 SSD looks like. As shown previously, my M2 SSD drive has its label face downward and is properly installed. They are all working fine with external enclosure case but not with the M2 SSD slot.

No M2 SSD was installed when flashing.

After flashing the upgraded BIOS earlier, the system will then slowly go into BIOS main page. There is a column stating that "Rom Image is not load. Rom Image update denied."

Somehow, I manage to boot up through the USB bootable disk. I tried using the command prompt function to flash the bio, FPTW64.exe -bios -d Biosreg.bin. But it gave me an error message "Error397: There was a communications error betwen FPT and the TXE."

What could be the problem?

Thank you.

It's not impossible that the disk is mounted correctly in this position, but would be very unusual. To judge this properly one should be able to see both contact- rows of the connector, especially on the small slot and maybe on picture being a little more sharp .

Since you opened your Laptop- Do you have a backup of the complete bios (possibly via CH341A programmer)? As far as I can see you were only able to make a dump of the bios region?

Hi Lost_N_BIOS,
After some research, I tried to flash back the original BIOS via Macrium Bootable USB Disk. I used FPTW64.exe -bios -f Biosreg.bin for this flash.

However, after booting up in the BIOS page, the Recovery column showed this message:

Rom Image is not load.
Rom Image update denied.

The BIOS has an administrator password. Could this be the problem ?
What should I do next?

Ifb6: The provided photo of M2 SSD was from another notebook user. I do not have CH341A device. I am attaching a picture of my M2 SSD slot. The pins look fine from the very beginning.

Thank you.

Help is appreciated !

After flashing back the original bios, the problem that I am now facing the following:

The notebook experiences a blank screen for 4 minutes.
Boot into the BIOS main page.
The Recovery column inside the BIOS showed this message:
"ROM Image is not loaded
ROM Image update denied."

Windows Boot Manager was selected in the Boot column. Secure Boot was Disabled.
It then reboots into Windows 10.

In other words: when turning on the notebook, it goes into BIOS. I have to physically exit the BIOS. Next, it boots into the log-in page of Windows. This will happen each time when booting up.

What are your advices in solving this problem?

Thanks for the picture. I can confirm that this slot is "upside down" and your disk was mounted the right way.

Concerning your other problem: I'd strongly recommend to buy one of this cheap CH341A programmers and make a complete backup of the Bios. I suppose one won't be able to find/ get bios images from the manufacturer?

Did you try to load "Optimized Defaults"? It might be necessary after flashing a region- dump?

Were those recovery options active before? It seems to me they are meant to recover Windows from a service partition/ hidden image- I don't think they are the cause for your delayed start.

The "Optimized Defaults" was loaded after flashing.
The Recovery options were NOT there previously as shown in post #10.

@Lost_N_BIOS : Any possible solutions to overcome this slow boot up (as in #25).

Thank you.

Sorry for the delayed replies @N.D. Looks like the main issue you had with reflashing was trying to use Windows version of FPT in DOS, you need to use DOS Version only in DOS. However, password may have been causing an issue too, and that may be what caused the original issue with flashing too.
Please disable that and reflash the BIOS I sent, but be ready to reflash original FPT backup again in DOS in case it fails same as before. It may be a bad BIOS edit, or you have RSA signed BIOS which we can't edit without that always happening (Doubtful)

For now, to fix the issue, put all files from FPT DOS Folder on the root of a DOS Bootable USB stick, along with your original biosreg.bin file. Then remove the password of the BIOS.
Then boot to DOS and >>> FPT.exe -bios -f biosreg.bin

The recovery section of BIOS is for the BIOS, nothing to do with windows @lfb6 (you can see all related in AMIBCP)
This should only be shown when updating BIOS normally, or with BIOS related tools, nothing with FPT so I assume something in the process it didn't like or FPT method used previously wasn't done correctly yet and it's trying to recover

@Lost_N_BIOS
The installation of the original bios and modified bios did not work.
These were what I have done:
I made a DOS bootable disk using the list of commands related to Diskpart. Followed the steps from here: https://bit.ly/2pGStXS
Next enter into BIOS, I select the UEFI: DOS bootable disk in the boot option tab. But it did not allow me to exit into DOS. Only in UEFI shell environment.
Sp I used the shell environment to flash the modified BIOS. See https://ibb.co/Tw34xqz
However, there is an error message in the Recovery tab. See https://ibb.co/ZYDxYMs I guessed the modified BIOS was not compatible.
I went back into the shell environment and re-flashed the original BIOS.
Again, I encounter back the same message under the Recovery tab, “Rom Image is not loaded. Rom Image update denied.” This was mentioned in Post #25
So I am back to square one. Any more solutions to solve this issue?
Just out of curiosity, I ran AFUWINGUIx64.exe. Did not do any flashing. The option on Boot Block is disabled when I loaded the original BIOS. See https://ibb.co/R9djXHM . Is this normal?
Appreciate your time and effort.

Diskpart has nothing to do with bootable USB, so sounds like you could not make DOS Bootable USB and boot to DOS? UEFI also has nothing to do with DOS

I see an issue with your Shell method, the BIOS source file at the end cannot contain an address, so only 16KB is written. Command needs to be like this (FS3 is already active location, do not add to file location)>> FPT.efi -bios -f filename.bin
However, I think this is part of the main issue and causing that recovery tab to come up, the UEFI Shell is doing some internal BIOS update, we don't want any of that we want FPT only.
So, try what I mentioned above about the file name without location in front of it, if that fails boot to DOS and do it again properly.

Here is how to make a DOS Bootable USB stick (Copy all files from FPT DOS Folder to root of this USB once done, and a copy of your BIOS Files).
Then boot to USB once done (Not UEFI - USB either) - if you cannot choose a regular USB by name or without UEFI , disable secure boot and then reboot and hit boot menu again and choose USB
Win98 SE USB Boot (Follow steps 1-4 to create bootable USB)
<Request> Flagship X470 Gaming 7 Wifi Motherboard BIOS Fix

Yes, normal with AFU, many regions of the BIOS you cannot flash with software like this due to locked flash descriptor (FD)