Mptool i5188 recovery usb
![mptool i5188 recovery usb mptool i5188 recovery usb](https://www.recovermyflashdrive.com/wp-content/uploads/2017/10/grey-usb-error-0-bytes.png)
I've had a strange combination with FB34A boot block (unable to find such bios anywhere), FBKTD2A main bios block and 00000008 revision 2013's year PCU microcode block.īut but finally found this message, rolled back BIOS to earliest 2013, then fbjy74usa and finished by fbjyd2usa and reflashed EC with utility you've provided in other thread, BOOM, everything is perfecly working now!
![mptool i5188 recovery usb mptool i5188 recovery usb](http://3.bp.blogspot.com/-Y3-s_w5D5v4/VlVB03-x2wI/AAAAAAAAFI4/SqU3CQmz608/s1600/SMI-SM320AC-MPTool%2B-format-tool-SM320%D0%A5s-recovery.png)
Spent 3 days trying to figure out where problem comes from, thought i might damaged some component while soldering msata slot and parts. Successfully tested working with 860EVO mSATA, installed fresh W10 and decided to make a fresh BIOS update, found many new was released since year 2013.
MPTOOL I5188 RECOVERY USB HOW TO
This year found a solution on how to solder and enable mSATA slot in our Tiny, to have a fast SSD with capacious HDD in such a tiny housing. So i decided to leave that 2013's year bios. Tried to upgrade any other versions like years 2015, 2016 leaded me to "SECURE FLASH IS NOT SUPPORTED", "UNABLE TO GET FLASH INFORMATION" etc. I've flashed the most earliest bios i was able to find all over internet - fbjy42usa dated and was very happy that PC was back from dead.
MPTOOL I5188 RECOVERY USB UPDATE
That method with our systems should be called "the one and only possible solution to make a simple bios update procedure". After many panic attempts to recover, found so called "recovering from a POST/BIOS update failure" method.
MPTOOL I5188 RECOVERY USB DRIVERS
All i did after unboxing it was just downloading bunch of drivers with fresh bios back in 2015. My first acquaintance with it was ended with a died device. You're **bleep** right M93p Tiny is a BIOS nightmare product. Mod: edited Subject line to expand the problem descriptionīundies522, thank you so much for this guide! I've had absolutely same, described above problem with CODE43 USB device error, that have VID00000 and PID00005 or viceversa and nothing helped. Here are two other users with the same problems, yet still no reply from Lenovo almost 12 months later. But I'm hoping that there is at least potential for this issue to be fixed with another patch. Unfortunately, all of these systems are out of warranty, otherwise I'd RMA all of them due to Lenovo's horrible failure. This M93p update is the only one that is giving me issues, and I don't know what else to do to fix it. I've updated dozens of M73 systems with no issues. Obviously, I have not been doing anything wrong.
![mptool i5188 recovery usb mptool i5188 recovery usb](https://olympsb.ru/wp-content/uploads/2017/10/925483.jpg)
Once in Windows, the Device Manager shows that there is a Generic USB Hub with an "invalid device descriptor" with Code 43. When rebooting, Windows then hangs for about 30 seconds while booting, which it did not do before. The BIOS does program, however when it gets to the screen where it says "The BIOS update process will continue after system reboot" the process fails with "Error: Secure Flash function is not supported on this platform" This can go on for hours, and the only option is to terminate the batch job and start it again.Īfter restarting the Flash.cmd update, the process begins by skipping over the EC update, and goes straight to flashing the BIOS. On the systems where it has failed, I tried using the Windows package twice, and the USB package once.ĭuring the Embedded Controller Firmware update, the update gets stuck in a loop, failing verification. So far the update has failed on 3 of 4 systems I've installed it on.