Database Info

Moto g xt1033 dead

Hi friend,
Please help me, my moto g xt1033 is dead for last 3 months.
I followed almost all steps mentioned in different forum but still stuck at the same position.
Error after Blank Flash:
D:\MOTO G\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x40A8A85
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.022s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)

amit8091 said:
Hi friend,
Please help me, my moto g xt1033 is dead for last 3 months.
I followed almost all steps mentioned in different forum but still stuck at the same position.
Error after Blank Flash:
D:\MOTO G\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x40A8A85
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.022s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error reading packet)
Click to expand...
Click to collapse
can u just elaborate little more? means which rom were you there before and how moto g got deadc etc etc

abhi0502 said:
can u just elaborate little more? means which rom were you there before and how moto g got deadc etc etc
Click to expand...
Click to collapse
Hii first i have rooted my phone then i downgrade my moto g from lollipop to kitkat using mfastboot.
Again i m trying to upgrade my moto g to lollipop through OTA update . It started first but after few minutes my moto switch off from then it is dead. Unable to go to the recovery mode . when I press power button then notification led start blinking but screen remains black. When i plug it to desktop then it is showing as qhsusb_bulk . So i have tried those procedure for mentioned in this forum for qhsusb_bulk and all of those failed.
Please help me..

amit8091 said:
Hii first i have rooted my phone then i downgrade my moto g from lollipop to kitkat using mfastboot.
Again i m trying to upgrade my moto g to lollipop through OTA update . It started first but after few minutes my moto switch off from then it is dead. Unable to go to the recovery mode . when I press power button then notification led start blinking but screen remains black. When i plug it to desktop then it is showing as qhsusb_bulk . So i have tried those procedure for mentioned in this forum for qhsusb_bulk and all of those failed.
Please help me..
Click to expand...
Click to collapse
while downgrading from lollipop to kitkat did u flash first two commands(partition.gpt and motoboot) ?if yes your mobile got bricked. Visiting service centre is only option left

abhi0502 said:
while downgrading from lollipop to kitkat did u flash first two commands(partition.gpt and motoboot) ?if yes your mobile got bricked. Visiting service centre is only option left
Click to expand...
Click to collapse
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
i have run above commands.

amit8091 said:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
i have run above commands.
Click to expand...
Click to collapse
so you had flashed partition.gpt and motoboot. It will definitely brick your device because you flashed kitkat based bootloader(always follow instructions carefully) . You could have avoided first two commands and started with logo.bin. Your bootloader got corrupted. You need to visit service centre.

[GUIDE] Unbrick hard bricked Moto Z

.
.
.
.
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.

MHA-L29: "Func NO : 11 (recovery image)"

Hello,
I need some help, my MHA-L29C636 doesn't boot to system, go into TWRP recovery or into eRecovery anymore, I have access to fastboot tho.
What happened:
I was on stock clean slate Oreo (MHA-L29 8.0.0.375(C636))
Unlocked bootloader and FRP
Tried to restore TWRP backup I've made earlier when I was on Nougat because I wanted my settings/data back.
Restoration was complete but I could not boot to system, so I used files from https://forum.xda-developers.com/showpost.php?p=75725964&postcount=5 to go back to Oreo (MHA-L29 8.0.0.375(C636)), so I flashed the hwota7_update.zip phone rebooted and since then I can not got into either system, TWRP recovery or eRecovery anymore.
I get this error screen:
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
{
"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"
}
Tried to flash with Fastboot TWRP recovery from https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796 or https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967
But I still get the error screen on boot (normal boot and boot holding Power + Vol Up)
I have unlocked bootloader/FRP and access to fastboot how can I get a working phone back?

_A.T.Omix_ said:
Hello,
I need some help, my MHA-L29C636 doesn't boot to system, go into TWRP recovery or into eRecovery anymore, I have access to fastboot tho.
What happened:
I was on stock clean slate Oreo (MHA-L29 8.0.0.375(C636))
Unlocked bootloader and FRP
Tried to restore TWRP backup I've made earlier when I was on Nougat because I wanted my settings/data back.
Restoration was complete but I could not boot to system, so I used files from https://forum.xda-developers.com/showpost.php?p=75725964&postcount=5 to go back to Oreo (MHA-L29 8.0.0.375(C636)), so I flashed the hwota7_update.zip phone rebooted and since then I can not got into either system, TWRP recovery or eRecovery anymore.
I get this error screen:
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Tried to flash with Fastboot TWRP recovery from https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796 or https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967
But I still get the error screen on boot (normal boot and boot holding Power + Vol Up)
I have unlocked bootloader/FRP and access to fastboot how can I get a working phone back?
Click to expand...
Click to collapse
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.

ante0 said:
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.
Click to expand...
Click to collapse
Hello, thanks for the reply, so I need to
Code:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
Correct? How can I know the exact name each img should go to?

_A.T.Omix_ said:
Hello, thanks for the reply, so I need to
Code:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
Correct? How can I know the exact name each img should go to?
Click to expand...
Click to collapse
They are named the same as the partitions, so your code is correct.

Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash ramdisk RAMDISK.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.169s]
finished. total time: 0.570s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.602s]
writing 'kernel'...
OKAY [ 0.386s]
finished. total time: 0.988s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.802s]
writing 'recovery_ramdisk'...
OKAY [ 0.339s]
finished. total time: 1.141s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.000s]
writing 'recovery_vbmeta'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_vendor RECOVERY_VENDOR.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.400s]
writing 'recovery_vendor'...
OKAY [ 0.179s]
finished. total time: 0.594s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Same error as before.

i have the same problem bit i went on and flashed something wrong and i cant even acceces fastboot or anything. Dont do anything just go to a nearby servis center and let them flash the system. There is no way of recocering your phone now. And dont try to relock the bootloader or your phone will be gone for good.

ante0 helped me get back to stock Oreo, so it's possible if you have bootloader unlocked

I stuck with my Mate 9 Error mode numbers 11 and 2
ante0 said:
Ah, you use my Nougat only hwota zip... You can try extracting and flashing: ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app of MHA-L29C636B375.
But we'll see if that works.
That zip you flashed dd's /dev/block devices directly. On Nougat you have recovery and erecovery on sdd30 and sdd33.
On Oreo that's erecovery_vendor and teeos...
Also, restoring /data from Nougat on Oreo will most likely not work (as you saw). When you can get back into TWRP, flash stock recovery and Factory reset from there.
Click to expand...
Click to collapse
Try the method with DC Phoenix in my case works with the same problem.

Still no solution to this?

DC PHOENIX fix this error mode .. ?

I kinda have the same issue as OP.
I bricked my phone. Neither TWRP Recovery nor ERecovery is working currently. The only thing that works for now is fastboot and it shows me that my bootloader aswell as FRP is unlocked.
I tried flashing ramdisk, kernel, recovery_ramdisk, recovery_vbmeta, recovery_vendor from Update.app.
It's a Mate 9 Dual Sim Europe so it should be MHA-L29C432. I was on an unlocked and rooted nougat before and tried to update today to Oreo via TWRP. Somewhen during installation it restarted and now I am in this state and can't enter any recovery anymore.
Anybody know how to get it to work again?

_A.T.Omix_ said:
ante0 helped me get back to stock Oreo, so it's possible if you have bootloader unlocked
Click to expand...
Click to collapse
Hi
could you (PLEASE ) elaborate further what you or ante0 did to make it work again?
I am in the same situation.
What I don't understand is do I have to fastboot flash the oreo rom files or the nougat ones? And what should happen then? Will it automatically install HWOTA folder from sd card? Or when should I try to install twrp again?
Would be great to get my phone working again.

Mha-l29 (c185)
I was able to revive the mentioned model using fastboot and service ROM mentioned somewhere in XDA forum.
First of all you have to unlock the bootloader and I did buy unlock code from DC Unlocker costed me almost 5 bucks
before you unlock the bootloader you have to enable "OEM Unlocking" option in-order to proceed, then unlock the bootloader.
there are "recovery" and "recovery2" partitions names you have to flash them with correct files.
Then you have the option to flash the whole firmware using Fastboot or Huawei eRecovery

I got my mate 9 on the same situation can you please tell me what you did to go back to normal?
I can't enter erecovery or twrp
I got the same errors 11 and 2

No valid slot to boot - any way to back up data?

Does anyone have a way to get around: "no valid slot to boot"
I have a stock Pixel 4XL and just tried to upgrade to Android 11 with the latest images from Google.
I tried to patch the extracted boot image with Magisk and when I try to boot, I'm stuck in fastboot mode with "no valid slot to boot"
I then tried to recover to unrooted stock using an edited flash-all.sh script (removed -w flag). Now, I see the "G" logo and the progress bar cycles a couple of times, then I'm back in fastboot mode with "no valid slot to boot"
Is there any way to recover the device?

J.L.C. said:
Does anyone have a way to get around: "no valid slot to boot"
I have a stock Pixel 4XL and just tried to upgrade to Android 11 with the latest images from Google.
I tried to patch the extracted boot image with Magisk and when I try to boot, I'm stuck in fastboot mode with "no valid slot to boot"
I then tried to recover to unrooted stock using an edited flash-all.sh script (removed -w flag). Now, I see the "G" logo and the progress bar cycles a couple of times, then I'm back in fastboot mode with "no valid slot to boot"
Is there any way to recover the device?
Click to expand...
Click to collapse
boot into Safe mode then reboot.

Homeboy76 said:
boot into Safe mode then reboot.
Click to expand...
Click to collapse
How do I get into safe mode from fastboot?
If I switch back and forth with `set_active a/b` I can get it to the G logo with the progress bar, but it gets stuck there regardless of which buttons I press or hold down.

J.L.C. said:
How do I get into safe mode from fastboot?
If I switch back and forth with `set_active a/b` I can get it to the G logo with the progress bar, but it gets stuck there regardless of which buttons I press or hold down.
Click to expand...
Click to collapse
ok. Flash the stock boot.img to both slots:
fastboot flash boot --slot all boot.img

Homeboy76 said:
ok. Flash the stock boot.img to both slots:
fastboot flash boot --slot all boot.img
Click to expand...
Click to collapse
Unfortunately, I still end up stuck in fastboot with no valid slot to boot
I just tried to adb sideload an OTA through stock recovery recovery, and now I'm stuck at the G logo.

J.L.C. said:
Unfortunately, I still end up stuck in fastboot with no valid slot to boot
I just tried to adb sideload an OTA through stock recovery recovery, and now I'm stuck at the G logo.
Click to expand...
Click to collapse
@J.L.C. try this:
First, make sure you have the latest:
- Platform-tools r30.0.4 installed on your computer
- The latest Android 11 (R) extracted in the Platform-tools folder
- Make sure you can see these files bootloader.img, radio.img, image....zip and fastboot.exe in the Platform-tools folder
Second, when you connect the phone to your computer make sure you do not plug the USB cable into a charging USB port.
Third, cd to the Platform-tools folder (Mac/Linux) or open a command prompt in the Platform-tools folder (Windows - see OP [Post 1] #1 in the Guide below) and type the following commands and press enter after each command:
Notes:
- If you are using a Mac or Linux computer put this ./ in front of every command.
- Guide
fastboot reboot bootloader
fastboot flash bootloader --slot all <complete name of bootloader.img>
fastboot reboot bootloader
fastboot flash radio --slot all <complete name of radio.img>
fastboot reboot bootloader
fastboot update -w <complete name of image-coral-....zip> --skip-reboot --slot all
(this will wipe your phone data and internal storage)
I suggest you do it this way because something is jacked on your phone this will clear out all the gremlings
fastboot reboot bootloader
fastboot reboot
If it works thank this post: https://forum.xda-developers.com/showpost.php?p=83509975&postcount=9

Homeboy76 said:
@J.L.C. try this:
First, make sure you have the latest:
- Platform-tools r30.0.4 installed on your computer
- The latest Android 11 (R) extracted in the Platform-tools folder
- Make sure you can see these files bootloader.img, radio.img, image....zip and fastboot.exe in the Platform-tools folder
Second, when you connect the phone to your computer make sure you do not plug the USB cable into a charging USB port.
Third, cd to the Platform-tools folder (Mac/Linux) or open a command prompt in the Platform-tools folder (Windows - see OP [Post 1] #1 in the Guide below) and type the following commands and press enter after each command:
Notes:
- If you are using a Mac or Linux computer put this ./ in front of every command.
- Guide
fastboot reboot bootloader
fastboot flash bootloader --slot all <complete name of bootloader.img>
fastboot reboot bootloader
fastboot flash radio --slot all <complete name of radio.img>
fastboot reboot bootloader
fastboot update <complete name of image-coral-....zip> --skip-reboot --slot all
(this will wipe your phone data and internal storage)
I suggest you do it this way because something is jacked on your phone this will clear out all the gremlings
fastboot reboot bootloader
fastboot reboot
If it works thank this post: https://forum.xda-developers.com/showpost.php?p=83509975&postcount=9
Click to expand...
Click to collapse
Is there any way to pull the data from the phone from fastboot or recovery? Like an idiot, I didn't back up before attempting the upgrade.

J.L.C. said:
Is there any way to pull the data from the phone from fastboot or recovery? Like an idiot, I didn't back up before attempting the upgrade.
Click to expand...
Click to collapse
@J.L.C.try this:
I hope you are using a Windows computer, I don't know how to do this on a Mac or Linux computer.
1. Add the path to the Platform-tools folder to Windows environment variables.
2. Create a folder on your computer that you want to copy the files from your Pixel 4 XL to.
3. Open a command prompt in that folder and type:
adb pull "/storage/emulated/0/"
(This should backup your internal storage.)
Note: USB debugging should be enabled on phone

It happened to me, I just flashed stock 10 then ota 11

stevoswifty said:
It happened to me, I just flashed stock 10 then ota 11
Click to expand...
Click to collapse
:good:

I'm back up and running but had to do a full wipe, including userdata (-w flag).
I tried fastboot installs of older 10 and 11 images and always ran into the same issue.
OTA upgrades over adb were failing with status 1.
So, phone recovered, data not so much.

J.L.C. said:
I'm back up and running but had to do a full wipe, including userdata (-w flag).
I tried fastboot installs of older 10 and 11 images and always ran into the same issue.
OTA upgrades over adb were failing with status 1.
So, phone recovered, data not so much.
Click to expand...
Click to collapse
:good:

I had the same problem, ADB was unauthorised, so I was unable to to do anything with that.
When I was in the 'Fastboot Mode', the command:
$ fastboot devices
was unable to find my device, and therefore I was unable to flash the stock boot.img.
I solved it by selecting 'Power Off' in 'Fastboot Mode' and when the screen turned black, I did press and hold the Volume Down button until the device rebooted into 'Fastboot Mode'. Now my device was detected in when calling the command '$ fastboot devices'.
I do not remember if my device was connected via USB to the computer at that time of reboot.
Then I reflashed the stock boot.img (as flashing the magisk_boot.img never succeeded), and my telephone booted succesfully up unrooted. Then I generated a new patched boot image via Magisk, and rerooted the device without any problems.

Hello, I've run into the same/a similar problem. My Pixel 4a is in a bootloop after attempting to unroot.
I've flashed the stock factory image in accordance to these instructions and I'm still met with the bootloader upon a power cycle.
I've tried doing it on both slots to see if anything might help, but it hasn't yet.
My phone tells me "no valid slot to boot" for the reason just like those above, but nothing seems to help.
EDIT: I cannot apply an OTA update, either. Seeing as I can't unlock the device and validate the RSA key, the device is 'unauthorized' for ADB.

use.logic said:
Hello, I've run into the same/a similar problem. My Pixel 4a is in a bootloop after attempting to unroot.
I've flashed the stock factory image in accordance to these instructions and I'm still met with the bootloader upon a power cycle.
I've tried doing it on both slots to see if anything might help, but it hasn't yet.
My phone tells me "no valid slot to boot" for the reason just like those above, but nothing seems to help.
EDIT: I cannot apply an OTA update, either. Seeing as I can't unlock the device and validate the RSA key, the device is 'unauthorized' for ADB.
Click to expand...
Click to collapse
I don't know if this will help you, but hopefully it will help someone else:
I was unable to get my pixel 4a (sunfish) to boot after flashing stock, as well, with an error about no valid boot slot. However, running the flash tool through the browser fixed the problem. You'll need a chromium-based browser like Brave, but it got my phone working again.

I just stumbled across this issue when I flashed the wrong image to my Pixel 4a5G - accidentally downloaded "redfin" instead of "bramble". I'd previously patched the included boot.img using Magisk on my 4a5G and then tried to flash the rooted image using flash-all.bat (with -w removed, of course):
{
"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"
}
As you can see, it flashed a new bootloader and radio, then stopped due to not being able to identify the phone as 'redfin'. The phone then obviously bootlooped - no surprise there. It showed "unknown" as the device type in Fastboot instead of Bramble.
It took me a while to get things working again, as I really didn't want to have to wipe the phone:
1. First of all I tried to just flash a working bootloader - basically deleted everything from flash-all.bat below the line "fastboot flash bootloader ...". That restored the device type "Bramble" in Fastboot, but resulted in the "no valid slot" bootloop.
2. I then found this thread and tried the suggestion of "fastboot flash boot --slot all boot.img", which didn't help. I tried both the stock boot.img from the image I was already running (June 2021) and the stock boot.img from the image I was trying to update to (August 2021) - both appeared to flash successfully but didn't help get rid of the error - after a few boot attempts the phone would always land back on Fastboot showing the "no valid slot" message.
3. I then tried flashing the entire stock June 2021 image using flash-all.bat with -w removed. Process completed successfully but didn't get rid of "no valid slot"
4. I then figured I would have to wipe the phone - but as a last ditch effort, I tried flashing the entire stock August 2021 image using flash-all.bat with -w removed. Process completed successfully and to my surprise, the phone booted! I was able to reinstall Magsik normally, patch a boot.img file and then re-root normally using flash-all.bat.
The two reasons I'm posting this:
1. Don't get discouraged and keep trying different images - maybe it'll work
2. Why did the August image work, but the June one didn't? Is it because the Redfin image I accidentally flashed was from August? Are downgrades with flash-all.bat generally not possible?

I have this same problem.. I've tried to flsah using the android flash tool (the browser one) it goes through and says it completed successfully then when booting the Google logo shows up and the little loading bar underneath then takes me back to the bootloader and its back to square one again from there. I tried flashing manually. but it didnt work either. Any advice?

I had to try multiple different images manually before I got back to a working system. I'm starting to suspect that the trick was using an image with a newer time stamp that the one I was running before. Which images are you using exactly?

bemymonkey said:
I had to try multiple different images manually before I got back to a working system. I'm starting to suspect that the trick was using an image with a newer time stamp that the one I was running before. Which images are you using exactly?
Click to expand...
Click to collapse
i've been trying the most recent ones

OK I managed to get it to work by using the android flash tool but instead of picking the most recent build i picked the beta build of android 12 and voila it worked ... dont know why but thanks for the response

Yes. Even I am also stuck with same issue :
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.053s]
Finished. Total time: 0.061s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash bootloader --slot all
unknown partition 'bootloader'
fastboot: error: cannot determine image filename for 'bootloader'
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash bootloader --slot all bootloader-bramble-b5-0.4-7758094.img
Sending 'bootloader_a' (8762 KB) OKAY [ 0.318s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b5-0.4-7758094
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.388s]
Sending 'bootloader_b' (8762 KB) OKAY [ 0.317s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b5-0.4-7758094
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.432s]
Finished. Total time: 2.100s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.056s
\RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot flash radio --slot all radio-bramble-g7250-00161-211008-b-7807492.img
Sending 'radio_a' (149780 KB) OKAY [ 3.665s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_a
OKAY [ 0.824s]
Sending 'radio_b' (149780 KB) OKAY [ 3.636s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_b
OKAY [ 1.085s]
Finished. Total time: 9.842s
RootDevice_GooglePixel4a\platform-tools_r31.0.3-windows (2)\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.044s]
Finished. Total time: 0.053s
RootDevice_GooglePixel4aplatform-tools_r31.0.3-windows (2)\platform-tools>fastboot update -w image-bramble-sq1a.211205.008.zip --skip-reboot --slot all
Warning: slot set to 'all'. Secondary slots will not be flashed.
--------------------------------------------
Bootloader Version...: b5-0.4-7758094
Baseband Version.....: g7250-00161-211008-B-7807492
Serial Number........: 15191JECB01734
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.075s]
Checking 'version-bootloader' OKAY [ 0.056s]
Checking 'version-baseband' OKAY [ 0.072s]
Setting current slot to 'a' OKAY [ 0.145s]
extracting boot.img (96 MB) to disk... took 0.244s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.440s]
Writing 'boot_a' OKAY [ 0.679s]
archive does not contain 'boot.sig'
terminating with uncaught exception of type std:ut_of_range: basic_string

Unbrick Nairo / xt2075-3 / moto G5G plus after flashing LineageOS

Yesterday I wanted to flash my new Nairo / xt2075-3 / moto G5G plus with LineageOS. But unfortunately it doesn't boot anymore.
Only the EDL boot works. This blankfile works not:
https://mirrors.lolinet.com/firmware/motorola/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
https://mirrors.lolinet.com/firmware/moto/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
I downloaded a full TWRP backup (befor i bricket the device) and the latest stock ROM (using Motorola Rescuetool, but this requires fastboot)
This guide doesn't work either:
https://www.reddit.com/r/MotoG/comments/k73n66
I use the Image-Files from the Stock ROM this are the extrcted files:
27.05.2022 18:57 339968 abl.elf
27.05.2022 18:57 519296 aop.mbn
14.12.2020 02:09 35 blank-flash.bat
14.12.2020 02:09 38 blank-flash.sh
02.03.2022 15:59 13107456 bootloader.img
27.05.2022 18:50 708 default.xml
27.05.2022 18:57 126080 devcfg.mbn
02.03.2022 15:59 211712 gpt.bin
27.05.2022 18:57 519296 hyp.mbn
27.05.2022 18:50 134 index.xml
27.05.2022 18:57 519296 keymaster.mbn
27.05.2022 18:50 80 pkg.xml
27.05.2022 18:44 682968 programmer.elf
27.05.2022 18:57 257152 prov64.mbn
14.12.2020 02:09 181144 qboot
14.12.2020 02:09 229106 qboot.dll
14.12.2020 02:09 134292 qboot.exe
27.05.2022 18:57 76928 qupfw.elf
27.05.2022 19:03 7721216 singleimage.bin
31.10.2019 05:35 93624 star
31.10.2019 05:35 194682 star.exe
27.05.2022 18:57 126080 storsec.mbn
27.05.2022 18:50 4189312 tz.mbn
27.05.2022 18:50 2092160 uefi_sec.mbn
27.05.2022 18:57 4189312 xbl.elf
27.05.2022 18:57 126080 xbl_config.elf
Does somebody has any idea?

No ideas, also i never managed to get the moto downoad mode tool work

Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s

1.692 / 5.000
Hello, I was successful now I have a working phone again. But it didn't work with the Motorola Rescue Tool. I used this to download the latest firmware. Then I flashed this firmware with Fastboot and the script from (https://kfhost.net/flashfile):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -----------------------------------------------------------------------------------------------
echo English - Process concluded!
echo Português - Processo concluído!
echo English - Press any key to restart the phone!
echo Português - Pressione qualquer tecla para reiniciar o celular!
echo -----------------------------------------------------------------------------------------------
pause
fastboot reboot
exit
I hope someone else can use it ;-).

Germanandroidplayer said:
Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s
Click to expand...
Click to collapse
Hey, can I ask you how did you manage to unbrick it? My phone doesn't get recognized via fastboot. It seems dead but when I connect it to the pc, it gets recognized as "Qualcomm HS-USB QDLoader 9008"

Ok I cannot believe it was so stupid, it didn't work because I had to long press power button + volume down while executing the blank flash file, as said in this post (I put the screenshot below)
{
"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"
}

OK, I hope your problem is solved and your phone is working again? It's been some time now. I don't remember having to hold down any keys. My problem with the blank flash file was that the signatures were probably wrong. So I grabbed an empty flash file from the other phone that has the same processor.

I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.

officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
Hi,
Did you read my post from 05/29/2022?

officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
I have the same problem with XT2075-3(GB retail with Android 11), I flashed the radio from the US stock ROM and it bricked the device after a restart... So this may not be caused by Android 12. I flashed US radio cause there's no 5G NR reception in China. 'All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot.' - That makes two of us. Now waiting for a solution, too.

Still cannot access fastboot, any one can provide the firehose file, please?

[email protected] said:
Still cannot access fastboot, any one can provide the firehose file, please?
Click to expand...
Click to collapse
See Post #3 and #4 or if this dont work #6

Here is the link again: https://mirrors.lolinet.com/firmware/motorola/nairo
This didn't work on my Nairo. I'm using this (see below) because Nairo and Racer should contain the same CPU/SOC.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
After loading blankfile you have to create new partitons and flash the stock ROM
you can use the script from here (https://kfhost.net/flashfile). The Stock ROM you can get with the Motorola Rescue Tool.