Database Info

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:

[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

A true brick? Nooo... deleted OS

I have apparently bricked my phone and trying to have some hope that I can still do something.
It's an older 2018 phone which I happily had root running the stock Android 8 OS. Then decided to put LineageOS 20.1 on it. It was a perfect fit. Following instructions I got online, I wiped all the partitions before flash the LOS zip. But of course that wiped my zip away. So now I'm stuck in TWRP after wiping everything, and can't choose my OS to flash. I couldn't reboot to slot A for certain, so I chose B. Bad mistake, especially since the API level was quite lower than the 33 on the Lineage.
So now now matter what buttons I press/hold, it simply doesn't make a peep. Eternally powered down??

treysky54 said:
Following instructions I got online, I wiped all the partitions before flash the LOS zip.
Click to expand...
Click to collapse
No, don't wipe *all* partitions of course. Can you share these instructions please? What device model? buildno?

aIecxs said:
No, don't wipe *all* partitions of course. Can you share these instructions please? What device model? buildno?
Click to expand...
Click to collapse
It was a video on youtube, but I see my mistake. I did delete internal storage, and he doesn't show that (see screenshot). Great, how dumb was that. I messed up big time. I also deleted two other partitions I've never seen before, OEM and DPU (or something close to that, don't recall exactly). I'm not a newbie overall, but I straight up made a good ol' fashioned mistake.
Motorola Z3 Play. I was in a temporary TWRP boot when it happened. The Z3 Play (Beckham) was on the stock OS before the boot, 8.1.0 May 2018, Build OPW28.70-31, Kernel 4.4.78
This sucks. I can't figure out a way to get it powered on in order to connect it to adb/fastboot. If only I could force it to power on to any screen.
{
"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"
}

see what VID/PID is connected in windows device manager.
this may give you starting point
https://forum.xda-developers.com/t/how-to-restore-a-bricked-z3-play.3986061

aIecxs said:
see what VID/PID is connected in windows device manager.
this may give you starting point
https://forum.xda-developers.com/t/how-to-restore-a-bricked-z3-play.3986061
Click to expand...
Click to collapse
Damn, something shows up! I'm amazed. First off, thank you greatly for that link. Even though I've been researching around, I didn't know about that potential blankflash option. I'm about to boot into MX as I type. Crossing fingers.
This forum is full of the most outstanding group of people, I tell you what.
edited: the correct VID/PID is
USB\VID_22B8&PID_2E80\ZY226B9BF7

22b8:2e80 Motorola PCS is fastboot mode, click on -> Properties -> Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> android_winusb.inf -> Android Bootloader Interface (may require windows driver signature enforcement disabled beforehand)
then check fastboot devices from cmd.exe

Awesome idea, I'll try that back in Windows. I'm in Linux currently, and it shows up in QDL mode, so that's good. I still get permission denied when trying to run blank-flash.sh. But the REAL issue is fastboot nor adb have yet to see the phone. It says "waiting for any device" when fastboot devices. Something is stopping me. I had only the swipe lock screen (no pin etc) before, but that concern should be moot anyway since I've wiped literally everything there is to wipe. Yes the bootloader was unlocked and root prior. Is verity my problem i wonder?

QPST doesn't show an ESN. Wtf? So it seems EDL is activated, but it's not showing as an actual phone. which is why fastboot isn't seeing it. Sigh... still trying here.

right, 05c6:9008 is EDL mode, therefore no fastboot commands work. if you're on linux you can use this python edl script. usage is similar to fastboot.
Code:
python3 edl w partition gpt.bin --loader=path/to/programmer.elf
python3 edl w bootloader bootloader.img --loader=path/to/programmer.elf
python3 edl w modem_a NON-HLOS.bin --loader=path/to/programmer.elf
python3 edl w fsg_a fsg.mbn --loader=path/to/programmer.elf
python3 edl w bluetooth_a BTFM.bin --loader=path/to/programmer.elf
python3 edl w dsp_a dspso.bin --loader=path/to/programmer.elf
python3 edl w logo_a logo.bin --loader=path/to/programmer.elf
python3 edl w boot_a boot.img --loader=path/to/programmer.elf
python3 edl w system_a system.img --loader=path/to/programmer.elf
python3 edl w system_b system_other.img --loader=path/to/programmer.elf
python3 edl w vendor_a vendor.img --loader=path/to/programmer.elf
python3 edl w oem_a oem.img --loader=path/to/programmer.elf
python3 edl w oem_b oem_other.img --loader=path/to/programmer.elf
system.img and vendor.img needs to created first.
Code:
sudo apt install android-tools-fsutils
simg2img system.img_sparsechunk.* system.img
simg2img vendor.img_sparsechunk.* vendor.img
if you don't find prog_emmc_firehose_sdm636_ddr_moto.mbn (this file is also required for QPST/QFIL) then use the blankflash in EDL mode, that should repair fastboot so you can flash everything from fastboot.
Code:
fastboot flash partition gpt.bin
fastboot flash booloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
some partitions maybe need to wiped
Code:
fastboot --set-active a
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase ddr
fastboot format:ext4 cache
fastboot format:ext4 userdata
https://mirrors-obs-2.lolinet.com/firmware/motorola/2018/beckham/blankflash
https://mirrors-obs-2.lolinet.com/firmware/motorola/2018/beckham/official/RETAIL

Wonderful data, thanks. I have two issues.
1. I can't find any QTSP-flashable files for my phone in order to use your python scripts. I wish though.
2. Since there's no fastboot connection, I can't find a way to get the blank-flash to take, or to wipe.
I do have a full update of the stock OS that I pulled using TWRP, but there's nothing there I can use for QTSP sadly.

I have linked BECKHAM_RETAIL_8.1.0_OPWS28.70-56-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and blankflash_from_OPW28.70-56.zip
qboot.exe works in EDL mode, but you need to install Qualcomm HS-USB QDLoader 9008 Driver first.

aIecxs said:
I have linked BECKHAM_RETAIL_8.1.0_OPWS28.70-56-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and blankflash_from_OPW28.70-56.zip
Click to expand...
Click to collapse
I saw that, and had those already downloaded. Maybe I'm missing something here, but in order to flash regular OS files (like the one you mentioned), I first need blank-flash to fix it, which needs fastboot, which isn't working of course. And to use QTSP or QFIL, I need the special firehose files (which I can't find). Seems I need to either get fastboot to connect, or get the special qtsp files.
If only I could get back into TWRP, I could restore my backup. But I only did temporary boots of TWRP.

read again my post of today, I have updated with more information.

aIecxs said:
read again my post of today, I have updated with more information.
Click to expand...
Click to collapse
Here's my results from qboot. Seemed promising at first, but it still won't make a connection in order to allow a flash.

The qboot log:
**** Log buffer [000001] 2023-02-11_03:07:22 ****
[ -0.000] Opening device: \\.\COM9
[ 0.001] Detecting device
[ 34.547] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.547] Check qboot_log.txt for more details
[ 34.548] Total time: 34.550s
[ 34.549]
[ 34.549] qboot version 3.86
[ 34.549]
[ 34.549] DEVICE {
[ 34.549] name = "\\.\COM9",
[ 34.549] flags = "0x64",
[ 34.549] addr = "0x62FD54",
[ 34.549] api.bnr = "0xF42DC0",
[ 34.549] }
[ 34.549]
[ 34.549]
[ 34.549] Backup & Restore {
[ 34.549] num_entries = 0,
[ 34.549] restoring = "false",
[ 34.549] backup_error = "not started",
[ 34.549] restore_error = "not started",
[ 34.549] }
[ 34.549]
BTW this seems intriguing:
Unbrick Qualcomm Mobiles with Step-by-step Guide
Phones are generally bricked when we flash any non-compatible ROM or delete any partition. Refer to our guide on Unbrick Qualcomm Mobiles.
www.droidsavvy.com

EDL mode has a timeout of 30 sek or so, disconnect, reboot the phone in EDL mode and try again.

Well I have a black screen etc, but will keep trying. Didn't know about the timeout. Been watching it in device manager to see if it connect/disconnects, but seems stable. Was checking for boot looping.
update: dammit it's still not connecting. I need to figure out what possible reasons could be blocking the communication.

just press and keep holding volume + power buttons to reboot the phone

I really appreciate your tenacity staying with me on this. After even more button pushes, I did get this far. First time it's said anything except detecting device. Gives hope. But.. it had an issue with the file. Not sure yet why. I'm afraid the blankflash file may not be compatible because my last stock OS was OPW28.70-31, and the blankflash I found is OPW28.70-56. Pretty minor I know, but I'm considering everything.
*** Log buffer [000001] 2023-02-11_03:49:09 ****
[ -0.000] Opening device: \\.\COM16
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 204 (0xcc)
[ 0.005] ...cpu.sn = 1641220384 (0x61d30920)
[ 0.005] Opening singleimage
[ 0.007] ERROR: error opening singleimage
[ 0.007] Check qboot_log.txt for more details
[ 0.008] Total time: 0.009s
[ 0.008]
[ 0.008] qboot version 3.86
[ 0.008]
[ 0.008] DEVICE {
[ 0.008] name = "\\.\COM16",
[ 0.008] flags = "0x64",
[ 0.008] addr = "0x62FD54",
[ 0.008] sahara.current_mode = "3",
[ 0.008] api.buffer = "0x2D1D020",
[ 0.008] cpu.serial = "1641220384",
[ 0.008] cpu.id = "204",
[ 0.008] cpu.sv_sbl = "0",
[ 0.008] api.bnr = "0x742FE8",
[ 0.008] }
[ 0.008]
[ 0.008]
[ 0.008] Backup & Restore {
[ 0.008] num_entries = 0,
[ 0.008] restoring = "false",
[ 0.008] backup_error = "not started",
[ 0.008] restore_error = "not started",
[ 0.008] }

what says logfile? try to rename singleimage -> singleimage.bin
btw only execute .\blankflash.bat or .\qboot.exe blank-flash no other arguments given.

How To Guide GUIDE FOR FLASHING A-TEAM GSI for moto g stylus 2022 5g family, moto 2021 family , moto G8 family, ECT with links to gsi roms and custom sock rom

EDIT : THIS ERROR ONLY HAPPENS ON WINDOWS. GO TO THE TELEGRAM GROUP IN THE BOTTOM LINK AND INSTALL PIZZAG'S MINT LINUX. AS IT HAS ADB AND FASTBOOT DRIVERS BAKED IN. ROMS FLASH FLAWLESSLY ON LINUX. IF YOU HAVE ANY PROBLEMS CONTACT THE DEVS VIA TELEGRAM.
C\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
1031shadow said:
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM
(ON WINDOWS AND LINUX IF NOT ALREADY INSTALLED)
TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb
The new telegram account has several moto devices unified in one group they also have a chat room where other users and the actual devs will respond to your inquiries or you can message them directly on telegram.
Another thing is windows is trash if you want the best compatibility with the ROM flasher he provides you can install his mint Linux with adb and fastboot installed also has dump and build tool for those who like his ROMs .
the above error only happens in Windows I've tested on Linux and it works without having to edit the script
all credit goes to
A-Team @pizzaG
https://t.me/A_Team_Digital_Solutions

Thank you. !
Much appreciated on the links and detailed info.

1031shadow said:
FOR ANYONE WHO HAS THIS ERROR GO TO THE BOTTOM OF THE PAGE FOR FIX
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
i contacted the developer for a fix but no reply so i fixed it myself i love these roms but very little help from the comunity so i did it myself ive been rooting for 12 years now so not a noob but not a dev
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb​
i also wanted to add i really appreciate the developers for this rom for even taking time to develop roms and root for this device i will be posting the links for their telegram to download custom gsi and custom stock roms it was almost impossible to find as of writing
all credit goes to
A-Team @pizzaG​ https://t.me/ATeamReleases
Click to expand...
Click to collapse
ATeamReleases is not found on Telegram right now.

Your right I'ma edit with new links

403 forbidden
https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/