I have a 2 1050f tablet, try flashing with the intel phone but could not,
Read some forums and restore the bios to kitkat 4.4, then try flashing again with the intel phone flashtool and in 97% sale error
11/26/16 12: 48: 01.725 WARNING: Port 1/1/1: Retry to run fastboot -s Baytrail602451F9 oem eraseRow
11/26/16 12: 48: 03.626 WARNING: Port 1/1/1: Failed to execute "C: / Program Files (x86) / Intel / Phone Flash Tool / fastboot.exe" -s Baytrail602451F9 oem eraseRow ":
...
FAILED (remote: eraseRow)
At the end the flashing is finished but it is in bootloop
no one ?
I had similar problem, and after reboot tablet ended in EFI BIOS, withou possibility use Phone Flash Tools. Maybe this could help you:
SOLVED EFI Bios bootloop - Yoga 2 1050F Lollipop
0. Unpack folder with YT2-1050F_USR_*.rar, install Fastboot, Intel USB driver, Phone Flash Tool
1. Boot tablet into dnx mode (PowerOff .... and then PowerOn+VolUp+VolDown, screen should say "Starting fastboot...")
2. Connect USB from tablet to PC and from CMD line run fastboot:
fastboot flash osloader efilinux-user.efi
fastboot boot droidboot.img
3. In the booted droidboot mode run from CMD line:
fastboot flash osloader efilinux-user.efi
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
4. In the same droidboot mode: run Platform flash tool (Intel) and in options tick "Force fastboot sparsing" 500MB and then choose file flash.xml from unpacked folder with YT2-1050F_USR_*.rar
5. After flash and first boot (5+5 minutes) change language from Chinese to yours
Files (sorry for links, I cannot post links , I am too newbie here , replace * by . (dot)
Fastboot + temporary TWRP - www*androidfilehost*com/?fid=24052804347782876[/url]
Intel Phone Flash Tool - androiddatahost*com/2365a2 or androidmtk*com/download-intel-phone-flash-tool
Intel Android USB driver - androiddatahost*com/285a2 or androidmtk*com/download-intel-android-usb-driver
YT2-1050F_USR_S100256_1601190545_WW52_ROW - yadi*sk/d/FG0tTvy9q8Qtm
Hi sir....
In 3rd step .. fastboot flash osloader efilinux-user.efi ... this command do not take??? What to do?
Thanks... Change and done...Like.... fastboot flash fastboot efilinux-user.efi
But after all process still same Only Lenovo. (((YT2-1050F_USR_S100341_1604081520_WW52_ROW))
Thanks
Br, Raja
Try this old thread. " forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-8-830f-failed-update-led-to-t3372535". post number 2
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
coilspring said:
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
Click to expand...
Click to collapse
Try here,it might work to fix your imei
Hi there I have the same problem with my p8lite and your proposed method didnt work for me. Please help
Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the Moto X Style that died after updating via ota (the bootloader is unlocked and had downgrade) result = does not enter fastboot mode, recovery, nor loads, when it connects on the computer by usb it presents qualcomm hs-usb qdloader 9008, for those with the same problem, I was able to recover my device through a file shared by a colleague of google plus who made a dump of xt1572 that works 100% (loader.img)
File Link to Recovery
drive.google.com/file/d/0Bz770r9yW2iNU29JZkNPdkZmeG8/view
ROM link with bootloader version A0.52
androidfilehost.com/?fid=961840155545596639
MOTO X STYLE XT1572 UNBRICK GUIDE
Initial Reminders: This method has been tested on more than one XT1572 model successfully, but we can not guarantee the success of this guide in your case. NO ONE HERE IS RESPONSIBLE FOR WHAT YOU DO WITH YOUR APPLIANCE. If you have no skill / experience or do not feel confident following such guides, DO NOT GO!
Several members of this community together have come up with a solution to the "Hardbrick" problem of Style, a condition where it gives no sign of life and recognizes on the computer as "HS-USB DLoader 9008".
THINGS YOU WILL NEED BEFORE YOU BEGIN:
1 - A computer with Motorola drivers installed, fastboot files and the DiskImageRev2 program. Your Windows user needs to have administrator access.
2 - A USB cable of good quality and 100% functional.
3 - A USB microSD memory card reader.
4 - A microSD memory card. Recommendation: 16GB, class 10 and ORIGINAL!
5 - The complete ROM file.
Details of this ROM: Dual SIM. RETAIL. Region "LA" - the two simcards operate 100% in Brazil. Android 7.0. Security Patch August 1, 2017. Version Number NPHS25.200-15-3.
6 - The file "Loader.img".
7 - The battery of the unit must be charged so as to allow the unit to switch on in fastboot mode.
Each of the above may require additional steps. For this guide not to get too large these details were not included.
STEP BY STEP
Step 1 - Burn the "Loader.img" file to the microSD memory card using the DiskImageRev2 program.
Step 2 - Insert the memory card into the device and turn it on in fastboot mode. There are three possible options: (1) hold down the Power and Volume buttons for at least 10 seconds. (2) Hold the Volume minus button and connect the unit to the computer. (3) Connect the device to the computer, after it is recognized to hold the Power button until it "reboots" it automatically enters fastboot mode.
Step 3 - With the device in fastboot mode, write the ROM normally complete using the Windows command prompt.
.\fastboot oem fb_mode_set
.\fastboot flash partition gpt.bin
.\fastboot flash bootloader bootloader.img
.\fastboot flash logo logo.bin
.\fastboot flash boot boot.img
.\fastboot flash recovery recovery.img
.\fastboot flash system system.img_sparsechunk.0
.\fastboot flash system system.img_sparsechunk.1
.\fastboot flash system system.img_sparsechunk.2
.\fastboot flash system system.img_sparsechunk.3
.\fastboot flash system system.img_sparsechunk.4
.\fastboot flash system system.img_sparsechunk.5
.\fastboot flash system system.img_sparsechunk.6
.\fastboot flash system system.img_sparsechunk.7
.\fastboot flash system system.img_sparsechunk.8
.\fastboot flash system system.img_sparsechunk.9
.\fastboot flash system system.img_sparsechunk.10
.\fastboot flash modem NON-HLOS.bin
.\fastboot erase modemst1
.\fastboot erase modemst2
.\fastboot flash fsg fsg.mbn
.\fastboot flash bluetooth BTFM.bin
.\fastboot erase cache
.\fastboot erase userdata
.\fastboot erase customize
.\fastboot erase clogo
.\fastboot oem fb_mode_clear
.\fastboot reboot
This solution was the result of a joint effort of several people from the "Moto X Style BRASIL - Official" community on Google+
restores the dump into sd card, is this right ? or can you provide some instruction ?
This is for the XT1572 (not sure about other models), and yeah, you use DiskImageRev2 to write the loader.img to a sd card (32 gb card needed since it writes a 32gb partition)
After that you connect it to the computer, and press power button till it resets, it will start in fastboot mode.... then, just flash the rom you want (got mine back some hours ago with the same procedure)
@Danielo007
Good news.
Can you explain what/how did you unbrick MXP/S?
What to do with this file and after?
can confirm it works
Thank you very much
1. use Diskimage to write .img file on a 32gb card
2. put the card inside the slot
3. boot like you would boot to bootlooder (volume down + power) after some screen flash, it start in bootloader mode.
4. use fastboot to flash rom
Danielo007 said:
Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the x-style bike that died after the update via ota (the bootloader is unlocked and had downgrade) result did not connect in fastboot mode, recovery, did not load and when connecting on the computer it featured qualcomm usb qdloader 9008, for those who are with the same problem I was able to recover my device from a file shared by a colleague of google plus that made a dump from its xt1572 that works 100% o (loader.img)
File Link to Recovery
drive.google.com/drive/folders/0B9SXWV7BgmquVWZJTUp1NHJPb2M
Click to expand...
Click to collapse
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
update...
device boot only with flash card inserted
fdc77 said:
update...
device boot only with flash card inserted
Click to expand...
Click to collapse
Not really, you're using an older version of your rom, you need the same GPT.BIN file to be writen, or else your not "fixing" the bootloader, it will give " preflash validation failed" in it, with the latest rom it worked for me, i'm not using the "emulation sd card" and the phone boots as the first time
---------- Post added at 14:32 ---------- Previous post was at 14:30 ----------
See in here the file "Guia para UNBRICK em inglês.pdf" gives you the instruction needed
you are right......but i don't have stock nougat rom for xt1572 EU, anyway i was able to recover my phone, flashing a nougat flashfire backup that i had made when i install it first time.
Guys, I love you. I DO, REALLY!
Finally my bricked XT1572 is back from the dead, at least it booted into Fastboot mode. However, I don't have the full Nougat ROM for the XT1572-LATAM_DS, only the Marshmallow 6.0 ROM with December security patch. Thus, since the Loader.img is for a Nougat ROM, I can't flash the gpt.bin and bootloader.img from the MM ROM ("Preflash validation failed").
Can anyone share the full Nougat ROM (if it's available), or at least the gpt.bin and bootloader.img (then I can flash a custom ROM, for instance)?
THANKS!!!
EDIT: found it on the Google+ community, downloading now.
EDIT 2: solved!! The ROM worked with the instructions! THANKS TO ALL INVOLVED!!
Amazing... Moto staff hided this secret from people for years ))
Tried this on my xt1575 and it worked initially. Failed to flash gpt.bin and bootloader.img from the 24.49-18-8 full factory MM image. It did initially boot to the stitch screen then powered off and won't power on again. Tried letting it sit and reinstalled the sd card but it won't power on at all now. When I initially put the SD card in the white led lit up and I was able to get to recovery mode. Now nothing happens. So I wouldn't advise XT1575 users to try this loader.img
I hope this interchangeable with X1575. Or some one can create a loader.img for it. BTW you would have to fastboot the last image that was installed?
jason2678 said:
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
Click to expand...
Click to collapse
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Hi:
But finally when flash by fastboot, the destination is the internal memory or the sd card?
Regards
npatel555 said:
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Click to expand...
Click to collapse
On other Snapdragon phones I've seen this work with in the past it is kind of a fickle thing. I looked back over some old threads, and you needed an image specific to the firmware you were running at the time you bricked. I think my phone is too much of a Frankenphone right now to be a good candidate for pulling an image from. I'm pretty sure I'm on the bootloader from the MM Sept 2016 security update and the modem from the MM May 2016 security update. Currently not on a stock rom either. I could make you an image, but based on BuildUpNow's post above I think it would either not work or maybe leave you worse off than you are now.
I could get my phone back to fully Sept 2016 stock for the purpose of making an image, but that's it. The bootloader won't downgrade. The XT1575 packages haven't leaked for Dec 2016 or Nougat, and I'm not touching those OTA's as poorly as they seem to be going. I've never seen so many hard bricks reported on this device as I have in the last month or two.
Our lack of full firmware packages for XT1575 will really hinder this unless you happen to have been on older firmware. Unless you can get your hands on a firmware package same or newer than what you were running, you're going to get preflash validation failure on the bootloader and partition table, and based on the posts above it sounds like you'll still be stuck.
can you please provide loader.img for moto x play???
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
dzidexx said:
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Click to expand...
Click to collapse
I tried that and it didn't work.
I actually got my phone to boot up now though. But the phone will only boot with the sd card it in. I tried wiping it and using it for storage and the phone refuses to boot. The img has to be written to it. I also can't enter recovery mode( pwr + vol dn buttons at all). So now I'm stuck with mm6.0 and I cannot enter recovery at all. Guess I'll have to try and load the sd card on linux and see what files are on the card and see if there's anything to be modified.
Oh my goodness, thank you so much for this quick and easy fix. My phone is back from the dead and it even worked on my Moto X PURE (XT1575). You made my day, honestly, I haven't been this happy for a long time
so im trying this since yesterday
Please help me ive been trying to find solution everything flashes except when i try flashing vendor.img it says vendor error : buffer overreads occured due to invalid sparse header how can i fix this my device is redmi7A with unlocked bootloader using original cable on usb2 slot trying to unbrick it since yesterday using latest flashtool and drivers using this firmware eu version Xiaomi_Redmi_7A_V11.0.3.0.QCMEUXM_20200728.0000.00_EEA_10_XFT also would like to mention i unlocked bootloader installed twrp and formated all partitions (brave man i am) tryed using the default firmware upgrade tool also tryed manually installing vendor.img from the firmware but no success tryed formating the partition under twrp to ext2 and returned it to ext4 didnt try to change the size or anything ....this all because the default firmware couldnt install game me vendor error ... at this point im giving up on it ... if anyone knows what must be done hes welcome :fingers-crossed:
here is the msg :
fastboot flash vendor vendor.img
target reported max download size of 535821312 bytes
sending 'vendor' (290176 KB)...
OKAY [ 9.152s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 12.419s
....last time i ever buy a chinese device from 5-6 different firmwares i could test only 2 because the others didnt have all the files required in the images folder .....chinese piece of trash and thats it...no way of restoring my device even with the default firmware i still cannot understand did i do something wrong or what......
What says when you tried to flash the vendor with twrp?
first check if you using the newest fastboot version via: fastboot --version
are u sure that you have the EEA Hardware?
when u have access to twrp(recovery) try sideload via adb sideload
and here is a how to flash manually link:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
plstanchev said:
....last time i ever buy a chinese device .....chinese piece of trash and thats it...
Click to expand...
Click to collapse
this could happen to you with any device! for me the 7A is a really great device. if you unlocked your bootloader you know that there is always a chance to brick your phone! so take responsibility for your actions and don't blame the manufacturer.
PS: if you use more dots and enter it would be much more better to read through your post if someone is trying to help :/
I am also not responsible if anything goes wrong.
May be your download file is corrupted, have you checked the integrity of that file, the extension (.tgz) fastboot firmware.
And flash them with mitool and always download from official site.
I have bricked my M3, and was successfully revive it using IDT board software. And now i stuck at the old ROM
I was trying to upgrade using SD Card method with many dload file but no one success
Please help me to figure it out, thank you
=====================================================
As I mention before , i was sucessfully flashing board software which bring me to basic firmware.
I try to update using USB OTG and SD Card but I got no luck.
Then I use fastboot to flash this firmware [HUAWEI MEDIAPAD M3 8 FIRMWARE (BTV-DL09 ,C100B009, EMUI4.1+ANDROID 6.0) [ANDROIDHOST.RU].RAR]
Extracting UPDATE.APP and take out boot, recovery, cust, and system then using fastboot to force flash
* Reboot into fastboot by pressing vol down button (phone off) while connect USB
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
This method bring me to EMUI 4.1 on Android 6.0 as mention above
But i have some problem here :
* My SIM got locked
* I cannot update to EMUI 5/ Android 7
What I was done :
+ copy file UPDATE.APP of EMUI 5 to dload folder than update via USB OTG. I use this file [BTV-DL09C683B352CUSTC683D001 FIRMWARE ANDROID 7.0 EMUI 5.0 05014EAR.ZIP]. But I got messaege "No update file found"
+ Exctract boot, recovery, and system from update.zip and cust.img from update_data_full_hw_eu.zip then flashing using fastboot . But it end with bootloop
+ Flashing update.zip via TWRP. It was success but failed to grab EMUI info or firmware version. It show NRD90M test-keys on it. TWRP red log
Failed to mount ........ (forgot what was failed, only remember there were 2 invalid argument) (invalid argument)
Please anyone give me a clue to update my M3 to newer version.
Target : move into M3-BTV-DL09C100B307 or M3-BTV-DL09C100B311
PS: I have M3-BTV-DL09C100B307 file (update and update_data_full_hw_eu)
I also have M3-BTV-DL09C100B311 file (update.zip, update_data_full_public.zip and update_full_BTV-DL09_hw_eu.zip)
Thank you
Update.app should match your device in order to be able to flash it via dload method. As I can see your device it's not properly updated to EMUI 4.x Android 6