Database Users

[Q] Definitely [Bricked] Maybe

Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks

scari said:
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
Click to expand...
Click to collapse
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.

foxob said:
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
Click to expand...
Click to collapse
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you

scari said:
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
Click to expand...
Click to collapse
so this doesn't work? too bad. that has helped me save my zte open a few times.

foxob said:
so this doesn't work? too bad. that has helped me save my zte open a few times.
Click to expand...
Click to collapse
no, that method doesn't work definitely...
:crying:

are you able to get into fastboot?

hecatae said:
are you able to get into fastboot?
Click to expand...
Click to collapse
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).

scari said:
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
Click to expand...
Click to collapse
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.

Arrowblue said:
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Click to expand...
Click to collapse
when I flash the phone with windows this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
and when I try to flash with ADB under Mac Os this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
and I try to flash the original boot image and the modified one,
but without success...

[HOW TO] Unbrick XT1031 if Brazilian 5.0 OTA fails

So I had an awful experience of bricking my XT1031 when following the guide to flash the Brazilian Lollipop 5.0 OTA. I tried everything I could think of to fix it, and just about gave up. However, there is hope
If you tried to flash the Brazilian 5.0 OTA on your XT1031 and now have a phone that won't turn on after applying the OTA, but get a sound when you plug it into your PC like it connected or get a message that it's installing a bulkusb driver, this is for you. If you have a XT1031 that doesn't turn on due to other circumstances, I'm not sure this will work, but you can try.
Big thanks to Boss422 for creating the MotoFlasher Bootloader Tool and davidp799 for providing me the steps to unbrick the XT1031. Without these two, I wouldn't of been able to do any of this, so if you want to thank anyone, thank them.
Tools you will need
Fastboot - Link
MotoFlasher Bootloader Tool - Link
Boost Mobile 4.4.4 stock Image - Link
STEPS
1. Plug phone into your computer and make sure you hear the computer make the sound like it has connected to your XT031.
2. Start MotoFlasher Bootlader Tool. Select Moto G as your phone and 4.4.4 as your last android version. Detect your device, then flash the bootloader. The bootloader should pop up on your screen
3.Take the Boost factory image and extract it to your fastboot folder (this is just how I do it. You just need to be able to fastboot files from the zip you downloaded.)
4. Find the batch file "falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat" and run it. It will now start flashing the necessary files and most of it will fail, reboot your phone.
5. Your phone should now be booting up like normal. The bootscreen may be glitchy though and there could be bugs, so to solve this, turn off your phone before it boots all the way up and return to the bootloader. Once back in the bootloader, run the "falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat" batch file once more and this time it will take longer and everything should say "okay".
6. Your phone has now been brough back from the dead. :good:

on device manager it says Quallcomm Bootloader HS 9008
here the log
**** BASIC INFORMATION ****
SYSTEM: Aplication Started at: 06/12/14 09:52
SYSTEM: OS: Microsoft Windows NT 6.1.7601 Service Pack 1
ASSEMBLY: MotoFlasher Version: 1.6.1.1
WARNING: No Python 2.7.x detected on "C:\Python27", Moto X flashing Disabled
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM15
OUTPUT*: OKAY [ 0.045s]
OUTPUT*: greeting device for command mode
OUTPUT*: OKAY [ 0.004s]
OUTPUT*: identifying device
OUTPUT*: ...serial = 0x306CBE3
OUTPUT*: ...chip-id = 0x800 (MSM8226)
OUTPUT*: ...chip-rev = 0x0
OUTPUT*: ...sv-sbl = 0x0
OUTPUT*: OKAY [ 0.039s]
OUTPUT*: finding files
OUTPUT*: ...programmer = programmer.mbn
OUTPUT*: ...singleimage = singleimage.bin
OUTPUT*: OKAY [ 0.015s]
OUTPUT*: validating files
OUTPUT*: OKAY [ 0.144s]
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.023s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.027s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.103s]
OUTPUT*: flashing singleimage
OUTPUT:
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT*:
**** END OF PROGRAM ****

Sandivisi said:
on device manager it says Quallcomm Bootloader HS 9008
here the log
**** BASIC INFORMATION ****
SYSTEM: Aplication Started at: 06/12/14 09:52
SYSTEM: OS: Microsoft Windows NT 6.1.7601 Service Pack 1
ASSEMBLY: MotoFlasher Version: 1.6.1.1
WARNING: No Python 2.7.x detected on "C:\Python27", Moto X flashing Disabled
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM15
OUTPUT*: OKAY [ 0.045s]
OUTPUT*: greeting device for command mode
OUTPUT*: OKAY [ 0.004s]
OUTPUT*: identifying device
OUTPUT*: ...serial = 0x306CBE3
OUTPUT*: ...chip-id = 0x800 (MSM8226)
OUTPUT*: ...chip-rev = 0x0
OUTPUT*: ...sv-sbl = 0x0
OUTPUT*: OKAY [ 0.039s]
OUTPUT*: finding files
OUTPUT*: ...programmer = programmer.mbn
OUTPUT*: ...singleimage = singleimage.bin
OUTPUT*: OKAY [ 0.015s]
OUTPUT*: validating files
OUTPUT*: OKAY [ 0.144s]
OUTPUT*: switching to download mode
OUTPUT*: OKAY [ 0.023s]
OUTPUT*: greeting device for image downloading
OUTPUT*: OKAY [ 0.027s]
OUTPUT*: sending programmer
OUTPUT*: OKAY [ 0.103s]
OUTPUT*: flashing singleimage
OUTPUT:
OUTPUT*: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT*:
**** END OF PROGRAM ****
Click to expand...
Click to collapse
I used this to fix my issues with that earlier today. --> http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Just follow everything this says to do. It may be slightly confusing at first, but take your time and you'll get it. It took me a little while to do it right. I wasn't really focusing though. Lol best of luck to you and anyone else with this issue!

davidp799 said:
I'm pretty sure to fix that, I used riffraff. If I can find the guide on how to use riffraff I'll link it for you
Click to expand...
Click to collapse
thank you, iam really need somebody help me iam here waiting good news from you

HELP
i upgrade to 5.0 brazil done. i flash custom recovery TWRP 2.8.1. But after i backup (data, boot, system, and pds) and reboot, it stuck at boot logo and black screen :crying: after that, i can go to bootloader but cant go to recovery and stuck at logo TWRP :crying:
sorry for my poor english

t-ara said:
i upgrade to 5.0 brazil done. i flash custom recovery TWRP 2.8.1. But after i backup (data, boot, system, and pds) and reboot, it stuck at boot logo and black screen :crying: after that, i can go to bootloader but cant go to recovery and stuck at logo TWRP :crying:
sorry for my poor english
Click to expand...
Click to collapse
get the stock recovery and kernel (boot.img) from here
http://forum.xda-developers.com/showpost.php?p=57316705&postcount=368

itslels said:
So I had an awful experience of bricking my XT1031 when following the guide to flash the Brazilian Lollipop 5.0 OTA. I tried everything I could think of to fix it, and just about gave up. However, there is hope
If you tried to flash the Brazilian 5.0 OTA on your XT1031 and now have a phone that won't turn on after applying the OTA, but get a sound when you plug it into your PC like it connected or get a message that it's installing a bulkusb driver, this is for you. If you have a XT1031 that doesn't turn on due to other circumstances, I'm not sure this will work, but you can try.
Big thanks to Boss422 for creating the MotoFlasher Bootloader Tool and davidp799 for providing me the steps to unbrick the XT1031. Without these two, I wouldn't of been able to do any of this, so if you want to thank anyone, thank them.
Tools you will need
Fastboot - Link
MotoFlasher Bootloader Tool - Link
Boost Mobile 4.4.4 stock Image - Link
STEPS
1. Plug phone into your computer and make sure you hear the computer make the sound like it has connected to your XT031.
2. Start MotoFlasher Bootlader Tool. Select Moto G as your phone and 4.4.4 as your last android version. Detect your device, then flash the bootloader. The bootloader should pop up on your screen
3.Take the Boost factory image and extract it to your fastboot folder (this is just how I do it. You just need to be able to fastboot files from the zip you downloaded.)
4. Find the batch file "falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat" and run it. It will now start flashing the necessary files and most of it will fail, reboot your phone.
5. Your phone should now be booting up like normal. The bootscreen may be glitchy though and there could be bugs, so to solve this, turn off your phone before it boots all the way up and return to the bootloader. Once back in the bootloader, run the "falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat" batch file once more and this time it will take longer and everything should say "okay".
6. Your phone has now been brough back from the dead. :good:
Click to expand...
Click to collapse
it' say ****DETECTION STARTED:****
OUTPUT:
OUTPUT:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: < waiting for device >
it only been saying that

Wow this is exactly what happened to me just about 2 hours ago. Phone didnt turn on, no bootloader etc. The only thing is that my model is xt1034 so can i flash an stock 4.4.4 rom instead of your boost mobile rom?

Eduardogv said:
Wow this is exactly what happened to me just about 2 hours ago. Phone didnt turn on, no bootloader etc. The only thing is that my model is xt1034 so can i flash an stock 4.4.4 rom instead of your boost mobile rom?
Click to expand...
Click to collapse
you managed to solve ?, I also have the same problem in the xt1045

hi,
Do you have a copy of the motoflasher bootloader tool? It seems their site is not available. Thank you

Phone is dead

Hey!
My Moto g5 plus is dead and not even starting....only led is blinking near speaker.
Help me to resolve this issue.

What happened to your device before this? Did you take an OTA update, or flash something?

Try connecting it to a computer.

The blinking led refers to low battery, so maybe your charging circuit got fried and the charger is unable to charge your phone if its in warranty, visit moto service center or any local shop.

echo92 said:
What happened to your device before this? Did you take an OTA update, or flash something?
Click to expand...
Click to collapse
i just unlock boot loader and flash ota update and it stucks. please help

Yeah same here
Niel_ujle said:
Hey!
My Moto g5 plus is dead and not even starting....only led is blinking near speaker.
Help me to resolve this issue.
Click to expand...
Click to collapse
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:14 PM ----------
DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
Click to expand...
Click to collapse
any one help....
---------- Post added at 02:32 PM ---------- Previous post was at 02:14 PM ----------
jaysamani said:
i just unlock boot loader and flash OTA update and it stucks. please help
Click to expand...
Click to collapse
I also tried the same
unlocked the bootloader and after I flashed stock ROM and then updated through OTA
now the device is not responding

DEV JC said:
I recently installed an update,
after that phone is not responding, even the power and volume buttons are also not working(for fast boot mode)
only LED is glowing while charging..
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
any one help....
---------- Post added at 02:14 PM ---------- Previous post was at 02:14 PM ----------
any one help....
---------- Post added at 02:32 PM ---------- Previous post was at 02:14 PM ----------
I also tried the same
unlocked the bootloader and after I flashed stock ROM and then updated through OTA
now the device is not responding
Click to expand...
Click to collapse
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?

echo92 said:
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?
Click to expand...
Click to collapse
i do not remember which firmware i had before
but i installed the "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware,
after that i got a ota update after installing the phone was dead...

DEV JC said:
i do not remember which firmware i had before
but i installed the "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware,
after that i got a ota update after installing the phone was dead...
Click to expand...
Click to collapse
Ah, from the sounds of it you downgraded your stock firmware and then attempted to take an OTA update. You've likely corrupted your bootloader and thus hard bricked your device. This is why downgrading stock firmware is a bad idea...
All I can suggest is to try to use the albus (Moto Z2 Play) blankflash and Moto Z Play GPT/bootloader from this post https://forum.xda-developers.com/showpost.php?p=73062532&postcount=15 and use a TWRP flashable of a stock ROM. I do not know, and suspect you cannot, flash stock G5+ ROMs onto your device (possibly due to having a Moto Z Play bootloader), so hopefully there's a TWRP flashable of the Oreo stock ROM when that arrives.
If that blankflash does not work, then you may have to wait for a newer blankflash to be leaked (Motorola does not release these blankflash files, they are leaked, sometimes alongside firmware), perhaps when the Oreo factory image is leaked. We generally cannot build them from scratch as they require cryptographic signing by Motorola. The only other alternative is to send the device to a service centre and an expensive motherboard replacement.

Thanks
echo92 said:
Ah, from the sounds of it you downgraded your stock firmware and then attempted to take an OTA update. You've likely corrupted your bootloader and thus hard bricked your device. This is why downgrading stock firmware is a bad idea...
All I can suggest is to try to use the albus (Moto Z2 Play) blankflash and Moto Z Play GPT/bootloader from this post https://forum.xda-developers.com/showpost.php?p=73062532&postcount=15 and use a TWRP flashable of a stock ROM. I do not know, and suspect you cannot, flash stock G5+ ROMs onto your device (possibly due to having a Moto Z Play bootloader), so hopefully there's a TWRP flashable of the Oreo stock ROM when that arrives.
If that blankflash does not work, then you may have to wait for a newer blankflash to be leaked (Motorola does not release these blankflash files, they are leaked, sometimes alongside firmware), perhaps when the Oreo factory image is leaked. We generally cannot build them from scratch as they require cryptographic signing by Motorola. The only other alternative is to send the device to a service centre and an expensive motherboard replacement.
Click to expand...
Click to collapse
Thanks buddy for the solution...
it works man....
i need some more help....
where can i find the latest firmware...
my model is "XT1686" moto g5 plus

Hey...
I just recovered the dead Moto g5 plus...
Now I'm on pixel experience 8.1 ROM
I live in India....
I have a Jio 4G sim...
Which works perfectly but..Volte is not working....
I tried Aex 5.1 Volte issue is still there....
Any help pls....

DEV JC said:
Thanks buddy for the solution...
it works man....
i need some more help....
where can i find the latest firmware...
my model is "XT1686" moto g5 plus
Click to expand...
Click to collapse
did your phone start working? my one is not starting it stuck in bootloop i think.please answer asap

After that I flashed pixel experience ROM....
It works for me...
But LTE is now working.....
I think I should go for the service centre

echo92 said:
These forums are not real time, so please be patient for a reply.
1)Which stock firmware did you have before unlocking your bootloader?
2)Which firmware did you flash and can you remember what the OTA was that you installed?
Click to expand...
Click to collapse
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
here is the output: :crying:
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\jaysa\Desktop\motog5plus>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.126s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2164 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.174s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.402s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.327s]
finished. total time: 0.740s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.495s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.443s]
finished. total time: 0.945s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.361s]
writing 'dsp'...
OKAY [ 0.200s]
finished. total time: 0.570s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75642 KB)...
OKAY [ 1.671s]
writing 'oem'...
OKAY [ 0.653s]
finished. total time: 2.333s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (517327 KB)...
OKAY [ 11.275s]
writing 'system'...
OKAY [ 4.289s]
finished. total time: 15.589s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (502109 KB)...
OKAY [ 11.001s]
writing 'system'...
OKAY [ 4.078s]
finished. total time: 15.087s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522558 KB)...
OKAY [ 11.413s]
writing 'system'...
OKAY [ 4.002s]
finished. total time: 15.423s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (500901 KB)...
OKAY [ 10.948s]
writing 'system'...
OKAY [ 3.933s]
finished. total time: 14.888s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (432777 KB)...
OKAY [ 9.473s]
writing 'system'...
OKAY [ 3.512s]
finished. total time: 12.996s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
C:\Users\jaysa\Desktop\motog5plus>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (74872 KB)...
OKAY [ 1.661s]
writing 'modem'...
OKAY [ 0.696s]
finished. total time: 2.366s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.038s]
finished. total time: 0.041s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.025s]
finished. total time: 0.027s
C:\Users\jaysa\Desktop\motog5plus>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2528 KB)...
OKAY [ 0.076s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.178s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase cache
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.032s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.075s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.025s
C:\Users\jaysa\Desktop\motog5plus>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.036s
C:\Users\jaysa\Desktop\motog5plus>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.022s]
finished. total time: 0.023s
C:\Users\jaysa\Desktop\motog5plus>fastboot reboot
rebooting...
finished. total time: 0.007s
C:\Users\jaysa\Desktop\motog5plus>
any help? what the **** is going with me?

jaysamani said:
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
here is the output: :crying:
<snip>
any help? what the **** is going with me?
Click to expand...
Click to collapse
1)So you had the latest NPN25.137-92 firmware (November 2017) for XT1686 devices?
I'm not sure why you downgraded to the Jan 2017 NPN25.137-15 firmware (though it's deployed to Indian devices, the firmware is very old compared to what you had). By doing so, you set your device up for a hard brick - you effectively had a Nov 2017 bootloader, but a Jan 2017 system. As you cannot downgrade bootloaders, taking an OTA would likely have corrupted your bootloader and thus caused your device to hard brick.
2)I'm not sure which blankflash you used to rescue your device, hopefully it's the right one for G5 Plus devices (I asked you in the other thread you posted in).
I did say in the other thread as well that you will likely want to flash the NPN25.137-92 firmware using the procedure outlined in that guide, I do not understand why you're trying to flash the European/US NPN25.137-33 firmware, which might damage your device further. The pre-flash validation errors are from attempting to flash a stock ROM older than what was on your device (which would have been the November firmware, so thus you need to flash the Nov 2017 firmware). I understand you're desperate to get your device running again, please take a moment to properly read up on which firmware you need.
If the firmware flashes don't work, you may either have to wait for someone else to suggest other tips or submit your device for an expensive motherboard repair, and use this as a lesson to be careful if you downgrade.

jaysamani said:
i had latest Nov firmware before unlocking boot loader,
after that i flash "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" <-- this stock rom.
everything was good till i got ota update (which one i don't know but it was around 250 MB)
during this update phone died.
Now i am unable to boot my device in any mode
and i think i can flash "POTTER_NPN25.137-33_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" <-- this rom.
any help? what the **** is going with me?
Click to expand...
Click to collapse
You shouldn't have downgraded the bootloader, that causes an instant hard brick. Now that you've downgraded and got a hard brick, I'd suggest you wait for an update and use that full fastboot update to get it fixed or use the blankflash for 139-92 (if exists). Although I saw someone running 137-93 which could be a county-specific update or just some minor update as the guy just had his motherboard repaired and was running 137-93 instead of the 137-92 update which I believe everyone else is on or about to get.
Always remember not to downgrade Moto device's gpt and bootloader. And only take OTAs when you're either completely stock (locked bootloader with no system modifications) or unlocked bootloader with no system modifications.
Fellow members, please correct me if I missed something and do recommend suggestions.

psychopac said:
You shouldn't have downgraded the bootloader, that causes an instant hard brick. Now that you've downgraded and got a hard brick, I'd suggest you wait for an update and use that full fastboot update to get it fixed or use the blankflash for 139-92 (if exists). Although I saw someone running 137-93 which could be a county-specific update or just some minor update as the guy just had his motherboard repaired and was running 137-93 instead of the 137-92 update which I believe everyone else is on or about to get.
Always remember not to downgrade Moto device's gpt and bootloader. And only take OTAs when you're either completely stock (locked bootloader with no system modifications) or unlocked bootloader with no system modifications.
Fellow members, please correct me if I missed something and do recommend suggestions.
Click to expand...
Click to collapse
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus is different in this regard), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA seemingly having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...

echo92 said:
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...
Click to expand...
Click to collapse
Good to know that he had access to fastboot. He now has a chance to flash the 137-92 in order to get his phone up and running. And thanks for the info.

Done But still one Issue!
echo92 said:
Just a couple of things to add on
1)It's not usually the act of downgrading which causes the hard brick, which appears to deceive users into believing it's okay to downgrade. As far as I know, it's installing an OTA whilst downgraded which causes the issue of a hard brick.
With bootloaders (at least on the G4 Plus, and I have no reason to think the G5 Plus is different in this regard), you cannot downgrade a bootloader, it'll block you with a security downgrade error. However, you could still downgrade your firmware. In this case, the user still had the Nov 2017 bootloader but likely the Jan 2017 system. In taking an OTA, the OTA update appears to have no checks regarding the bootloader - it appears to assume that your bootloader is the same patch level as your system (i.e. in this case it'd assume you'd have the Jan 2017 bootloader too). Normally, with a locked bootloader or a device with the same firmware patch level, this would apply. With a downgrade, that's an incorrect and dangerous assumption, with the OTA seemingly having authorisation to overwrite the newer bootloader and causing a hard brick with a corrupted bootloader (corrupting the newer Nov 2017 bootloader, from what I understand).
Granted, Motorola's naming system for firmware builds is not very helpful, with different builds for different regions, though I imagine they'd argue that unlocking the bootloader means flashing the correct firmware and finding said firmware is now our responsibility.
2)I'm not sure if there is a NPN25.137-92 compatible blankflash (and I'm not sure if the albus blankflash still works), if not then we'd have to wait for a leaked blankflash from Motorola, either from a friendly contact within the engineering teams or a major OS update (e.g. the Oreo factory ROM). Somehow, the above user has managed to get back to fastboot despite appearing to hard brick their device... I've suggested to them to try flashing the NPN25.137-92 firmware if they are booting to fastboot reliably.
I do agree with the general message in your post though that downgrading is very risky and OTA updates should only be taken on particular firmware setups - namely, a device all on the same firmware patch level and no modifications, and not on the mixed firmware level that a downgrade would cause. Having a £200+ (or your regional equivalent) fancy paperweight is not fun to see...
Click to expand...
Click to collapse
thank you all for all your support
just i flash "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" ROM
and now it shows that oem_locked and software status is official
but still it is in boot loop(now it shows Motorola logo and it restarts)
Can i give it to service it is under warranty?
Once again thank you thank you
now at locked boot loader what can i do?

jaysamani said:
thank you all for all your support
just i flash "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" ROM
and now it shows that oem_locked and software status is official
but still it is in boot loop(now it shows Motorola logo and it restarts)
Can i give it to service it is under warranty?
Once again thank you thank you
now at locked boot loader what can i do?
Click to expand...
Click to collapse
If you've got a locked bootloader, and it's bootlooping, there's not much we can do.
Did you fully wipe your device (wipe cache, and factory reset), to verify that there's nothing on your device that might be causing an issue?
It might be due to the blankflash you used, again, can you please show which blankflash you used to rescue your device?
Can you get us your getvar info to have a look please?
1)Boot your device to the bootloader. Connect your device to the computer.
2)In the ADB terminal, type 'fastboot getvar all' (without quotes) and press Enter.
3)Copy the output to a post here, you may wish to remove your IMEI. This output is a list of your device variables and should tell us if the firmware flashed okay.
Unfortunately, because your bootloader was unlocked, Motorola has a record of the unlock key being requested against your IMEI and thus your remaining Motorola warranty is void. Regardless of your device showing oem_locked and no bootloader unlocked warning, your IMEI would indicate that void warranty. There are instances where service centres have looked at the paperwork and simply repaired your device, however, I do not know if in this instance the service centre would do this. You may have to pay for an expensive motherboard replacement (about 70 % of the device cost, from what I understand). It's up to you if you want to get your device repaired or put the money towards a new device.
As an aside, this is one of the reasons why downgrading can be very risky...

[Help] Downgrade h873

Hello
I curiously updated my h873 to 8.0 via lgup and now am not happy with that too much battery drain random reboots so i want to back to my 7.0 i read that it can harm the device and when i chek anti rollback it shows "anti rolback disabled" is this means i can safe downgrade to 7.0 ? if yes tell me how pls.

does anyone know how to fix this am stuck in fastboot mode but can't flash any .img
>fastboot boot twrp-3.1.1-0-h870.img
downloading 'boot.img'...
OKAY [ 0.546s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.566s

Pixel 2XL - Android 11 Dev Preview install issue: Not enough space

Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex

Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data

I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.

Edmontonchef said:
Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data
Click to expand...
Click to collapse
Thanks, that worked! I didn't even knew there are OTA files for the 11 preview.
The announcement stated image flashing only, so I assumed only full factory images are available.
I flashed the stock boot image back as well, so no twrp anymore, no reason, just like to run stock if possible.
Thanks a lot again, such a simple thing.

pantallica420 said:
I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.
Click to expand...
Click to collapse
Thanks, I have redownloaded all images multiple times, no luck, but the 11 previre OTA worked, so it is sorted, even though the underlying issue still persists.

MiLeX84 said:
Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex
Click to expand...
Click to collapse
You have a spare Pixel 2 XL? ? I am still using duct tape to keep mine together. Lmao.