[GUIDE] Unbrick hard bricked Moto Z - Moto Z Guides, News, & Discussion
.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.
My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.
So, things you'll need:
-A dead Moto Z with no boot/charging at all
-Drivers
-Blankflash file
-Stock Rom/Custom Rom
How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.
Cheers :highfive:
Thanks, dude, but it didn't work.
My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.
Here's the log, if it helps:
**** Log buffer [000001] 2017-04-15_15:21:57 ****
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]
martonto said:
Thanks, dude, but it didn't work.
My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.
Here's the log, if it helps:
**** Log buffer [000001] 2017-04-15_15:21:57 ****
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]
Click to expand...
Click to collapse
Try a different port. And avoid USB 3.0 ports
Still no go. I've been looking for another solution, but I'm yet to have any luck.
It seems there's a qualcomm utility to fix this called BordDiag, but I haven't found one that supports the msm8996 chipset.
Thanks, anyway!
Solved!
It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!
If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:
Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Thank you again, Manish54! I wouldn't have done it so soon without your help.
martonto said:
It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!
If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:
Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Thank you again, Manish54! I wouldn't have done it so soon without your help.
Click to expand...
Click to collapse
You're welcome
Manish54 said:
.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.
My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.
So, things you'll need:
-Drivers
-Blankflash file
-Stock Rom/Custom Rom
How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.
Cheers :highfive:
Click to expand...
Click to collapse
Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?
twitchfidelis said:
Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?
Click to expand...
Click to collapse
Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?
Manish54 said:
Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?
Click to expand...
Click to collapse
I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?
I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.
https://forum.xda-developers.com/showthread.php?t=2317790
twitchfidelis said:
I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?
I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.
And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.
Here is the adb driver: http://adbdriver.com/downloads/
Manish54 said:
It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.
And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.
Here is the adb driver:
Click to expand...
Click to collapse
Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".
twitchfidelis said:
Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".
Click to expand...
Click to collapse
Well man... Then this thread is not for you. It is for a dead phone with no boot/charging at all. If you're already on the bootloader then what's stopping you from flashing a rom?
I managed to flash it with a different set of instructions. There is an issue it appears with Windows 10 and RSD Lite maybe it's related to this but who knows. Thanks for your help anyway!
hello i have a hard bricked moto z and i can't get it detected on the pc. i have tried on multiple different pc's ALOT of times but it never shows up. any advice?
MOTO Z Hardbricked
Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks
Code:
C:\Users\pterion\Desktop\blankflash\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2375 (0x947)
[ 0.000] ...cpu.sn = 43926045 (0x29e421d)
[ 0.000] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.elf
[ 0.016] Sending programmer
[ 0.094] Handling things over to programmer
[ 0.094] Identifying storage type
[ 0.094] Waiting for firehose to get ready
[ 3.141] ...UFS
[ 3.141] Identifying CPU version
[ 3.156] ...MSM8996 3.1
[ 3.156] Determining target secure state
[ 3.156] ...secure = yes
[ 3.266] Configuring device...
[ 3.297] Skipping UFS provsioning as target is secure
[ 3.297] Configuring device...
[ 3.594] Skipping 'setbootablestoragedrive' as target is secure
[ 3.594] Flashing GPT...
[ 3.594] Flashing partition:0 with gpt_main0.bin
[ 3.594] Initializing storage
[ 3.828] ...blksz = 4096
[ 3.828] ...part = "SAMSUNG KLUBG4G1CE-B0B1 0800 "
[ 4.641] Flashing partition:1 with gpt_main1.bin
[ 4.672] Flashing partition:2 with gpt_main2.bin
[ 4.703] Flashing partition:3 with gpt_main3.bin
[ 4.750] Re-initializing storage...
[ 4.750] Initializing storage
[ 5.781] Flashing bootloader...
[ 5.797] Flashing xbl with xbl.elf
[ 5.938] Flashing cmnlib with cmnlib.mbn
[ 5.985] Flashing cmnlib64 with cmnlib64.mbn
[ 6.047] Flashing prov with prov64.mbn
[ 6.094] Flashing aboot with emmc_appsboot.mbn
[ 6.188] Flashing keymaster with keymaster.mbn
[ 6.250] Flashing rpm with rpm.mbn
[ 6.281] Flashing pmic with pmic.elf
[ 6.313] Flashing hyp with hyp.mbn
[ 6.360] Flashing tz with tz.mbn
[ 6.485] Flashing devcfg with devcfg.mbn
[ 6.512] Rebooting to fastboot
[ 6.528] Waiting for device to disconnect
[ 8.535] Total time: 8.535s
randomthots said:
Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks
Click to expand...
Click to collapse
If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.
unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)
benzinerwin said:
If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.
unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)
Click to expand...
Click to collapse
Thanks a lot.
Much appreciated
randomthots said:
Thanks a lot.
Much appreciated
Click to expand...
Click to collapse
In case anyone had a more recent stock rom OTA runnning you'd been updated to bootloader version 91.07, requiring the following unbrick files...
unbrick package with bootloader 91.07 files from 25.221.12 OTA,
GPT seq#0008 (timestamp: 2017-03-30 04:41:31, build id: git=MBM-NG-V91.07-0-gd081b7e)
The package was built from the 25.221.12 OTA update package. Not updated items were taken from when last supplied (i.e. 25.11.14). The GPT sequence counter reached #0008.
Will this work on z play? I have a XT1635-02 bricked now and I tried with v91.03, v91.05 and v91.07, they all give me output like below.
Do I need specific blankflash file on different phone models / bootloader versions?
From the cmd:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
In the log:
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
[ 4.007]
[ 4.007] qboot version 3.40
[ 4.007]
[ 4.007] DEVICE {
[ 4.007] name = "\\.\COM5",
[ 4.007] flags = "0x64",
[ 4.007] addr = "0x61FE5C",
[ 4.007] api.bnr = "0xFB2920",
[ 4.007] }
[ 4.007]
[ 4.007]
[ 4.007] Backup & Restore {
[ 4.007] num_entries = 0,
[ 4.007] restoring = "false",
[ 4.007] backup_error = "not started",
[ 4.007] restore_error = "not started",
[ 4.007] }
[ 4.007]
Hard Brick Moto Z Play
Fellows, I hope you can help me with the Blankflash file for the MZP.
I left it in full brick, I was locating MM and Nougat going down with the script Downgrade and going up with adb sideload and it happened when installing Nougat again.
It should be mentioned that I was with the April patch, I downgraded to MM Brazil patch November, restart and install the apps as always and personalize, then by adb add patch December, restart and reinstalled N but when finished instead of reboot , I chose to boot bootloader and alli brickeo.
All this only with the Bootloader open, no Root or any modification, now it does not turn on anything and if I connect it to the charger or pc only the charging led flashes, when connecting the pc I recognize it as ¨Qualcomm hs-usb qdloader 9008 COM5¨ I used e Blankflash for the bike z and did not finish the process and the 1,2 and 3 dce XDA and neither.
If someone can pass me the Blankflash will thank you, please.
I arrived here:
Blur_Version.25.211.10.addison.retail.en.US - Security April 2017
NPN 25.137-24-1-9
Download here:
Blur_Version.24.221.12.addison.retail.en.US - Security November 2016
MPNS24.104-44-10
Install this:
Blur_Version.24.231.19.addison.retail.en.US - Security December 2016
MPNS24.104-44-16
Then bricke it at the end of the process:
Blur_Version.25.21.2.addison.retail.en.US - Android 7.0 Nougat January 2017
NPN25.137-15.2
By the way a colleague Ali Guzman from the face group I passed this compilation NPN25.137-24-1 with the included blankflash but in the middle of the process notifies me of package error.
I pass the link in case someone serves:
Https://mega.nz/#!nMdEFLxY!4x0BZWr45...anoX16JZv5B5-E
Http://lenovo-forums.ru/files/category/140-moto-z-play/
Here are two archives with blankflash available so far
ATT Channel Software
thank you very much.
Related
Moto G dead Help! [SOLVED]
Hi, mi moto G suddently dead... i will try to share the history
Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash
so i run blankflash.bat and my phone now go to the fastboot :victory:
but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000
and don't start (Failed to initialize partition table)
anyone can help me?
here some pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on... but works :highfive: EDIT: yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone EDIT2: found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files
I've had my shares of problems with that mbn files myself. And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them.
moto g bricked hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows? please help i'm panicking...
darkeingel said: I've had my shares of problems with that mbn files myself. And after I was searching more things about them - I did notice that Moto X users have the same problems. The thing is that once you upgrade those files, you can't downgrade them. Click to expand... Click to collapse u cant downgrade them until you blank-flash the bootloader... the problem is you really dont need to flash the .mbn files because motoboot file do that and is downgradable cancheritos said: hi, i'm sorry, but i need help urgently. I unlocked the bootloader and flashed an international firmware so i can update to 4.4.2, since kitkat is not available in my country yet. then i tried to root my phone using superboot-windows.bat, and when the phone restarted it showd the moto logo, but it faded to black. so i turned it off, but now it doesn't turn on. is there a way to turn it on via adb or fastboot from windows? please help i'm panicking... Click to expand... Click to collapse view if in the pc show as qhsusb_bulk and i will explain how to unbrick
open multi failed hi everytime i tried the blank-flash.bat it shows this log: from Boss442 to XDA opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode OKAY [ 0.974s] identifying device ...serial = 0x1D18785 ...chip-id = 0x800 (MSM8226) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.009s] finding files ...programmer = programmer.mbn ...singleimage = singleimage.bin OKAY [ 0.006s] validating files OKAY [ 0.002s] switching to download mode OKAY [ 0.006s] greeting device for image downloading OKAY [ 0.004s] sending programmer OKAY [ 0.013s] flashing singleimage Target LOG: Open multi failed, unknown error Target ERROR: 7 - Open multi failed, unknown error Failed to open multi image, status = 7 FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image) Presione una tecla para continuar . . . someone can help me?
Boss442 said: after 30 attempts using the same method (via fastboot) the same firmware the same pc. the phone reboot bootloader and show unlocked, let me flash all the system and work good ._. really i don't know what is going on... but works :highfive: EDIT: yes, work using the .bat on 4.4.2 not 4.3 so the problem is the bootloader who i can't downgrade... maybe i make a guide to save the phone EDIT2: found the problem, never, NEVER flash the .mbn files on the firmware folder, only flash motoboot who take care of these flash files Click to expand... Click to collapse Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you!
gavinft said: Did you get back you data(like photoes、music)?Please tell me because I'm facing the same problem.Thank you! Click to expand... Click to collapse The data is formatted when you clean userdata partition Enviado desde mi Moto G mediante Tapatalk
I hope it will be solved soon.
Minervamc said: I hope it will be solved soon. Click to expand... Click to collapse i forgot to mark as solved, sorry
will be lesson in here....... i have problem...boot loop on flash cm11
Boss442 said: i forgot to mark as solved, sorry Click to expand... Click to collapse No problem.
xkorex said: hi everytime i tried the blank-flash.bat it shows this log: from Boss442 to XDA opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.002s] greeting device for command mode ReadFile() failed, error=31 opening device: \\.\COM40 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM40 OKAY [ 0.003s] greeting device for command mode OKAY [ 0.974s] identifying device ...serial = 0x1D18785 ...chip-id = 0x800 (MSM8226) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.009s] finding files ...programmer = programmer.mbn ...singleimage = singleimage.bin OKAY [ 0.006s] validating files OKAY [ 0.002s] switching to download mode OKAY [ 0.006s] greeting device for image downloading OKAY [ 0.004s] sending programmer OKAY [ 0.013s] flashing singleimage Target LOG: Open multi failed, unknown error Target ERROR: 7 - Open multi failed, unknown error Failed to open multi image, status = 7 FAILED (sdl-transfer-image:send-image:sdl-open-multi:error opening multi image) Presione una tecla para continuar . . . someone can help me? Click to expand... Click to collapse Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next?
gavinft said: Did you get your problem sloved?I've met the familar error "FAILED (sdl-transfer-image:send-image:sdl-open-multi:error reading packet)".What did you do next? Click to expand... Click to collapse Same problem here. My Moto G is dead
Hello !!! Some solution to problem moto g ?
Boss442 said: Hi, mi moto G suddently dead... i will try to share the history Suddently my moto g don't start after doing a downgrade, only if i plug on my pc show a driver (qhsusb_bulk) on xda very people have this problem so i download the qualcomm drivers... in the firmware folder for my stock phone, have some things (...)\mbm\blankflash so i run blankflash.bat and my phone now go to the fastboot :victory: but show as locked, they dont let me flash nothing and i can't unlock, my imei is 00000000000000000000 and don't start (Failed to initialize partition table) anyone can help me? here some pics: Click to expand... Click to collapse do you have MBM_CI files? as i can see by your moto g bootlaoder version which is 41.19. correct me if i wrong... how did you flashed i mean there is no such solution for Lollipop, how did you do it? if you have solution why don't you share it with others?
@sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images.
Hello @Boss442 Can you explain better how do you unbrick your moto g i got the same problem with mine, you can pm me and we can speak on spanish. Enviado desde mi XT1063 mediante Tapatalk
lost101 said: @sahir1993 - V41.19 is the Bootloader version included with GPE 5.1. It's available as motoboot.img in the GPE 5.1 Factory Firmware Images. Click to expand... Click to collapse http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 see this you 'll know what i'm asking for?
AYUDAAA Hola! Cada vez que ejecuto el archivo blankflash.bat me dice: "FAILED <sdl-transfer-image:send-image:sdl-open-multi:error reading packet>" y no puedo reestablecer el bootloader Ayuda por favor Moto G 1032 :crying:
Moto G XT1031 Won't Power, Detected as QHSUSB__BULK - Problem attempting recovery
The phone (XT1031, 16GB, Republic Wireless, 4.4.4) is low use and nothing different was done the day it developed the problem. It worked Monday, on Wednesday it flashed indicator and the screen wouldn't power. It was hard-powered off (held power) and it wouldn't turn on again. The computer does not detect it. I have installed the 64-bit driver for my Windows 7 and am attempting to 'blank-flash' without success. Can anyone assist? Attached is the log. Thanks in advance. C:\Users\Test\Desktop\blankflash>qboot.exe blank-flash opening device: \\.\COM3 OKAY [ 0.016s] greeting device for command mode OKAY [ -0.000s] identifying device ...serial = 0x3598E90 ...chip-id = 0x801 (MSM8626) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.016s] finding files ...programmer = programmer_8626.mbn ...singleimage = singleimage_8626.bin OKAY [ 0.031s] validating files OKAY [ -0.000s] switching to download mode OKAY [ 0.016s] greeting device for image downloading OKAY [ 0.016s] sending programmer OKAY [ 0.047s] flashing singleimage Target LOG: Open multi failed, unknown error Target ERROR: 7 - Open multi failed, unknown error FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
Anyone? Can anyone supply a copy of the corrupted file? Ideas? Any help would be appreciated.
Have a look here: http://forum.xda-developers.com/moto-g/development/guide-qhsusb-dload-workaround-t3182477
systemupdate and empty battery - bricked?!?
Is my moto g xt1032 dead? i started an systemupdate on my device not really reading what im clicking on, but it started to update. the little android was lying there and the update goes on when i wanted to look for progress after a while the moto g was black nothing worked i think the battery went down and the update couldnt complete the only thing is that the led is blinking for a while when i put it on usb cable to load the battery, but after hours of loading nothing happens can someone tell me how to turn it on again?
Try this: http://forum.xda-developers.com/showpost.php?p=63831563&postcount=2
lost101 said: Try this: http://forum.xda-developers.com/showpost.php?p=63831563&postcount=2 Click to expand... Click to collapse i tried all types of button pressing but nothing works so after reading many posts on different forums i came to jtag and i tried this : http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 but Motorola qboot utility v2.4 only shows me this message: opening device: \\.\COM3 OKAY [ -0.000s] greeting device for command mode OKAY [ 0.000s] identifying device ...serial = 0x1F48A61 ...chip-id = 0x800 (MSM8226) ...chip-rev = 0x0 ...sv-sbl = 0x0 OKAY [ 0.000s] finding files ...programmer = programmer.mbn ...singleimage = singleimage.bin OKAY [ 0.000s] validating files OKAY [ 0.000s] switching to download mode OKAY [ 0.000s] greeting device for image downloading OKAY [ 0.000s] sending programmer OKAY [ 0.016s] flashing singleimage FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame) Click to expand... Click to collapse
These may help: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 - but if your Bootloader has been updated then there is no working solution at this time.
lost101 said: These may help: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 - but if your Bootloader has been updated then there is no working solution at this time. Click to expand... Click to collapse fine that people are READING my posts^^ its the same link ive already posted
My phone XT1033 bricked(showing as RELINK HS QDLOADER 9008 (COM11) in device manager
:crying::crying::crying::crying: I have moto g 1st Gen XT1033 and it got hard bricked when I tried to reinstall Lolipop 5.1 (Now understood a wrong file for this phone). From then the device wont start, wont boot into boot loader mode, wont do anything. I tried many things which are suggested on internet but nothing worked. For now, if I long press power on button, LED flashes and nothing after that. Please help me in getting back my device into life. I tried doing a blank flash but getting below message F:\sanjay phone\blankflash\blankflash>.\qboot.exe blank-flash opening device: \\.\COM11 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.004s] greeting device for command mode opening device: \\.\COM11 OKAY [ 0.003s] greeting device for command mode FAILED (blank-flash:greet-device:error reading packet) F:\sanjay phone\blankflash\blankflash>pause Press any key to continue . . . I TRIED DISCONNECTING THE BATTERY AND CHARGING AND TRYING TO RE CONNECT AGAIN BUT THAT DIDN'T WORK TOO. PLEASE HELP :crying::crying::crying::crying::crying:
please reply can someone please reply. If this cant be repaired, I will stop looking for solution at least. :crying::crying::crying::crying:
sanjayuv said: can someone please reply. If this cant be repaired, I will stop looking for solution at least. :crying::crying::crying::crying: Click to expand... Click to collapse replacing the motherboard(which costs more than the cost of a smartphone currently) of your device is the solution other than that nothing can be done
sanjayuv said: can someone please reply. If this cant be repaired, I will stop looking for solution at least. :crying::crying::crying::crying: Click to expand... Click to collapse no solution yet founf for for the bootloader of android 5.0 ..... I am facing same error and have been waiting for 1 month
wellcome in moto g hardbricked club sign here https://secure.avaaz.org/es/petitio..._completo_de_Android_5_para_Moto_G_2013/?copy
Reply I have kept my moto g safe in locker and got xiomi note 3. If anyone find solution to this, do let me know
HELP me Someone moto g7 power hard bricked. i read every post and not fixed it yet
I just bought a moto g7 power xt1955-5 from visible. I managed to unlock boot loader, install twrp, and magisk. While i was trying to flash the cr droid rom it completely went black on me and its been black since. i tried blank flash that i found on here but no go this is what i get for and output on my terminal (down below). I have tried everything and i need this phone i just bought it. I learned everything know about phones on this website and i came along ways form where i started but this time i need someone to help me please. i don't have much money but i will give someone 10 bucks in bitcoin if they can fix this phone for me. Like i have tried everything i have read everything i can find and no luck. Appreciate anyones help thanks Motorola qboot utility version 3.40 [ 0.000] Opening device: /dev/ttyUSB0 [ 0.000] Detecting device [ 0.004] ...cpu.id = 186 (0xba) [ 0.004] ...cpu.sn = 2187712067 (0x8265d643) [ 0.004] Opening singleimage [ 0.004] Loading package [ 0.008] ...filename = singleimage.pkg.xml [ 0.010] Loading programmer [ 0.010] ...filename = programmer.mbn [ 0.010] Sending programmer [ 0.296] Handling things over to programmer [ 0.296] Identifying CPU version [ 0.300] Waiting for firehose to get ready [ 3.311] Target NAK! [ 3.311] ...This version of programmer has been revoked! [ 3.311] ...Rebooting to blank flash mode in 30 seconds... [ 61.251] Waiting for firehose to get ready [122.622] ...MSM8953 unknown [122.622] Determining target secure state [122.627] Waiting for firehose to get ready [184.002] ...secure = no [184.046] Initializing storage [184.049] Waiting for firehose to get ready [245.406] Configuring device... [245.412] Waiting for firehose to get ready [306.788] Waiting for firehose to get ready [368.160] Waiting for firehose to get ready [429.542] Waiting for firehose to get ready [490.910] Initializing storage [490.918] Waiting for firehose to get ready [552.286] Configuring device... [552.291] Waiting for firehose to get ready [613.665] Waiting for firehose to get ready [675.043] Waiting for firehose to get ready [736.417] Waiting for firehose to get ready [797.794] Waiting for firehose to get ready [859.166] Configuring device... [859.169] Waiting for firehose to get ready [920.547] Waiting for firehose to get ready [981.920] Waiting for firehose to get ready [1043.297] Waiting for firehose to get ready [1104.670] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error [1104.670] Check qboot_log.txt for more details [1104.670] Total time: 1104.670s [1104.670] There were some hiccups in backup and restore. [1104.670] Please save the following files and see a Bootloader member. [1104.670] 1) ./qboot_log.txt [1104.670] 2) ./backup_0x8265D643_2020-09-17_033217.img [1104.670] FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
Charge it again. Have you tried booting recovery (vol down + power)? Or tried holding just the power button for 20 seconds? I expect others at this beautiful community XDA will come around & help you.
coreyr1877 said: I just bought a moto g7 power xt1955-5 from visible. I managed to unlock boot loader, install twrp, and magisk. While i was trying to flash the cr droid rom it completely went black on me and its been black since. i tried blank flash that i found on here but no go this is what i get for and output on my terminal (down below). I have tried everything and i need this phone i just bought it. I learned everything know about phones on this website and i came along ways form where i started but this time i need someone to help me please. i don't have much money but i will give someone 10 bucks in bitcoin if they can fix this phone for me. Like i have tried everything i have read everything i can find and no luck. Appreciate anyones help thanks Motorola qboot utility version 3.40 [ 0.000] Opening device: /dev/ttyUSB0 [ 0.000] Detecting device [ 0.004] ...cpu.id = 186 (0xba) [ 0.004] ...cpu.sn = 2187712067 (0x8265d643) [ 0.004] Opening singleimage [ 0.004] Loading package [ 0.008] ...filename = singleimage.pkg.xml [ 0.010] Loading programmer [ 0.010] ...filename = programmer.mbn [ 0.010] Sending programmer [ 0.296] Handling things over to programmer [ 0.296] Identifying CPU version [ 0.300] Waiting for firehose to get ready [ 3.311] Target NAK! [ 3.311] ...This version of programmer has been revoked! [ 3.311] ...Rebooting to blank flash mode in 30 seconds... [ 61.251] Waiting for firehose to get ready [122.622] ...MSM8953 unknown [122.622] Determining target secure state [122.627] Waiting for firehose to get ready [184.002] ...secure = no [184.046] Initializing storage [184.049] Waiting for firehose to get ready [245.406] Configuring device... [245.412] Waiting for firehose to get ready [306.788] Waiting for firehose to get ready [368.160] Waiting for firehose to get ready [429.542] Waiting for firehose to get ready [490.910] Initializing storage [490.918] Waiting for firehose to get ready [552.286] Configuring device... [552.291] Waiting for firehose to get ready [613.665] Waiting for firehose to get ready [675.043] Waiting for firehose to get ready [736.417] Waiting for firehose to get ready [797.794] Waiting for firehose to get ready [859.166] Configuring device... [859.169] Waiting for firehose to get ready [920.547] Waiting for firehose to get ready [981.920] Waiting for firehose to get ready [1043.297] Waiting for firehose to get ready [1104.670] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error [1104.670] Check qboot_log.txt for more details [1104.670] Total time: 1104.670s [1104.670] There were some hiccups in backup and restore. [1104.670] Please save the following files and see a Bootloader member. [1104.670] 1) ./qboot_log.txt [1104.670] 2) ./backup_0x8265D643_2020-09-17_033217.img [1104.670] FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error Click to expand... Click to collapse Using a Blankflash can be tricky I guess. You are using windows 10? How is it listed in device manager? You installed Qualcomm drivers? Sent from my Moto E (4) using Tapatalk
This fixed mine youtube com/watch?v=14PjOkO829U just download the zip in the desc its not my video (i speak english natively) but it worked amazing use v1 as v2 didnt work for me. good luck
GATT_ said: youtube com/watch?v=14PjOkO829U just download the zip in the desc its not my video (i speak english natively) but it worked amazing use v1 as v2 didnt work for me. good luck Click to expand... Click to collapse For me V2 worked. But not straight away. I had to look into a couple of other threads and combined info. Anyways. At 330 am on Friday Oct 16 I got my phone working again.....since 9 pm....anyways thanks for the link suggestion.