Develop Bugs

Newly bought Lenovo P2C72 issues.

I have bought a Lenovo P2C72 4GB/64GB..
Opened it then it prompted for an update (no sim yet).
Build Number: V3.5_1652_5.1342.1_ST_P2c72
After update I plugged in Sim card..
Some say If I plugged in Sim card it will auto configure to P2a42. It didnt for me.
I found out that there is no google play.
There were numerouse Chinese Play stores and bloatwares. I want to get rid of it.
How can I transfer to P2A42? I cant unlock bootloader.. I think it needs Chinese number.
-What are my options to get to a Global Rom?
I have downloaded a ZIP file for P2a42 Nougat Update (1.9GB). Can I just use this for update?
[Update]
Please correct me if what I'm planning to do wrong and I'll raise some questions about my plans aswell.
1. I downloading the fastboot files for P2a42. Q> Can I fastboot even if my bootloader is locked?
2. I'll flash all execpt the bootloader.img (because of modem issues). Q> Is bootloader.img different from boot.img?
3. After flashing via fastboot (if I get to this part without issues) Can I go to Nougat Update through OTA zip file?
3.1 If not How can I update to Nougat?
[Update2]
1. Flashed via Fastboot (https://www.getdroidtips.com/install-official-stock-rom-for-lenovo-p2-p2a42/) Skipped bootloader.img
Problem.. Im stuck at Lenovo Opening White Screen already performed fastboot erase userdata
Process Log
C:\Program Files (x86)\Minimal ADB and Fastboot>TTT
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt_both0.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (33 KB)...
OKAY [ 0.031s]
writing 'partition'...
OKAY [ 0.031s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (1907 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.156s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (21677 KB)...
OKAY [ 0.485s]
writing 'boot'...
OKAY [ 0.358s]
finished. total time: 0.858s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (25265 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 0.409s]
finished. total time: 0.971s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.375s]
writing 'dsp'...
OKAY [ 0.175s]
finished. total time: 0.552s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk0.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 5.648s]
writing 'system'...
OKAY [ 4.499s]
finished. total time: 10.147s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk1.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (258079 KB)...
OKAY [ 5.612s]
writing 'system'...
OKAY [ 4.081s]
finished. total time: 9.693s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk2.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (258077 KB)...
OKAY [ 5.599s]
writing 'system'...
OKAY [ 3.854s]
finished. total time: 9.453s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk3.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261716 KB)...
OKAY [ 5.704s]
writing 'system'...
OKAY [ 4.251s]
finished. total time: 9.970s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk4.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262033 KB)...
OKAY [ 5.736s]
writing 'system'...
OKAY [ 4.434s]
finished. total time: 10.171s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk5.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (251510 KB)...
OKAY [ 5.471s]
writing 'system'...
OKAY [ 3.897s]
finished. total time: 9.369s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk6.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (259097 KB)...
OKAY [ 5.617s]
writing 'system'...
OKAY [ 3.835s]
finished. total time: 9.467s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk7.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (259098 KB)...
OKAY [ 5.626s]
writing 'system'...
OKAY [ 3.946s]
finished. total time: 9.571s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk8.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (259098 KB)...
OKAY [ 5.645s]
writing 'system'...
OKAY [ 3.984s]
finished. total time: 9.642s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk9.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (259100 KB)...
OKAY [ 5.622s]
writing 'system'...
OKAY [ 4.191s]
finished. total time: 9.813s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk10.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250251 KB)...
OKAY [ 5.469s]
writing 'system'...
OKAY [ 4.381s]
finished. total time: 9.850s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk11.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261655 KB)...
OKAY [ 5.681s]
writing 'system'...
OKAY [ 4.668s]
finished. total time: 10.349s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system systemchunk12.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (64584 KB)...
OKAY [ 1.422s]
writing 'system'...
OKAY [ 0.994s]
finished. total time: 2.416s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (131072 KB)...
OKAY [ 2.871s]
writing 'modem'...
OKAY [ 1.941s]
finished. total time: 4.812s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (300 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.031s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.891s]
finished. total time: 0.891s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>pause
Press any key to continue . . .
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223MSGQC fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>
[Update3]
Nothing seems to work. Stuck in White screen booting. PLEASE HELP!
[UPDATE 4: Its Working Now with P2a42]
Using this guide. (https://www.getdroidtips.com/install-official-stock-rom-for-lenovo-p2-p2a42/)
Flashed this via Fastboot (https://mega.nz/#!3hhhhRYC!bDbs1VGHA7s0n-uH-B30fVDsulFRVw-ZbYTvheS9m8I/)
Note:
I excluded/removed (bootloader.img) from fastboot folder
then used the existing flashall.bat file included in the zip file
Code:
C:\Program Files (x86)\Minimal ADB Tool>flashall
I got bootlooped probably because I used the answer by Undesirable. Made my own bat file.
(Dont get me wrong though, its good answer just not for me atm)
https://forum.xda-developers.com/lenovo-p2/how-to/stock-rom-t3552973/page2

joemar53 said:
I have bought a Lenovo P2C72 4GB/64GB..
Opened it then it prompted for an update (no sim yet).
After update I plugged in Simcard..
However i found out that there is no google play.
There were numerouse Chinese Play stores and bloatwares. I want to get rid of it.
How can I transfer to P2A42? I cant unlock bootloader.. I think it needs Chinese number.
Click to expand...
Click to collapse
it's a diffrent device, you can't just "change to p2a42"

You should be able to put the row rom on it but it'll still be a p2c72 hardware wise (They don't have some 4g bands etc.)

BravoOscarKilo said:
You should be able to put the row rom on it but it'll still be a p2c72 hardware wise (They don't have some 4g bands etc.)
Click to expand...
Click to collapse
idc about the hardware bands its fine.. the Chinese software stinks..
can I just download a zip a ROW rom? what can I do with it next?
[Update]
just tried it using the software update app.
brings me to the chinese bootloader but failed update of somesort.

Bump Please help me.

joemar53 said:
Bump Please help me.
Click to expand...
Click to collapse
Have you tried sideloading playstore?

Siva Mk said:
Have you tried sideloading playstore?
Click to expand...
Click to collapse
I know I can side load Playstore. However I would want the updates from P2a42.. English stuffs
chinese security apps.. so annoying AF

joemar53 said:
I know I can side load Playstore. However I would want the updates from P2a42.. English stuffs
chinese security apps.. so annoying AF
Click to expand...
Click to collapse
In that case try the method suggested in the previous thread. I believe the question is the same.

Siva Mk said:
In that case try the method suggested in the previous thread. I believe the question is the same.
Click to expand...
Click to collapse
im stuck at White Screen Booting.. Bootloop

joemar53 said:
im stuck at White Screen Booting.. Bootloop
Click to expand...
Click to collapse
Can you get to recovery?

Siva Mk said:
Can you get to recovery?
Click to expand...
Click to collapse
Hmm that is weird, i have a P2c72 and before updating to the Nougat build.. it didn't have any chinese bloatware or any problems before or after 6.0.1

Got it working now Look at 1st post - [UPDATE 4]

Good job mate!

Great job!
C:\Program Files (x86)\Minimal ADB and Fastboot>
[/HIDE]
[Update3]
Nothing seems to work. Stuck in White screen booting. PLEASE HELP!
[UPDATE 4: Its Working Now with P2a42]
Using this guide. (https://www.getdroidtips.com/install-official-stock-rom-for-lenovo-p2-p2a42/)
Flashed this via Fastboot (https://mega.nz/#!3hhhhRYC!bDbs1VGHA7s0n-uH-B30fVDsulFRVw-ZbYTvheS9m8I/)
Note:
I excluded/removed (bootloader.img) from fastboot folder
then used the existing flashall.bat file included in the zip file
Code:
C:\Program Files (x86)\Minimal ADB Tool>flashall
I got bootlooped probably because I used the answer by Undesirable. Made my own bat file.
(Dont get me wrong though, its good answer just not for me atm)
https://forum.xda-developers.com/lenovo-p2/how-to/stock-rom-t3552973/page2[/QUOTE]
I have a P2C72 as well, tried your method and it is working 100% first time, no boot loop!

Can someone please provide me a link to download the P2C72 Nougat Rom Chinese Version?
Thanks in Advance

Phone got bricked after accidental update on rooted phone, help?

Hi
I have had my Z2 Play for half a year, and soon after I got it I unlocked the bootloader with Motorola's official method, installed TWRP, rooted it with Magisk and installed Xposed Framework. I was on Nougat all the time and used it happily. A few months ago it started repeatedly asking me to OTA update, but I just ignored the messages. Then one day, I must have accidentally pressed something, because I think it tried to update. I got a message that the update failed or something like that.
The phone gradually got worse after that, randomly rebooting into TWRP. I could somehow get it to boot Android by going to the bootloader and chosing "factory mode" but mostly the modem would not work at all and the phone would not be usable.
Trying to solve it, I decided to flash a whole ROM, hoping to remove all of the damage done by the botchered update. Since I already had unlocked my bootloader and TWRP, I decided to just flash a custom ROM, since I did not know if flashing stock would work with TWRP. I found some of the custom ROMs here on XDA, and tried to flash them with TWRP. However, flashing would not work. I got some error code 255. I am attaching a screenshot of the error.
{
"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"
}
I tried both flashing via the adb sideload method via my Mac and via USB OTG (flash drive) but I got the same result for both.
Having seen this, I decided to try to relock the bootloader and restore stock firmware. I tried following this tutorial. However, that did not seem to work. Here is my fastboot output:
Code:
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot devices
ZY224BLVMC fastboot
Pals-MacBook-Air:platform-tools Fiksdal$ ./fasboot oem lock begin
-bash: ./fasboot: No such file or directory
Pals-MacBook-Air:platform-tools Fiksdal$ fastboot oem lock begin
-bash: fastboot: command not found
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock begin
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.003s]
Finished. Total time: 0.005s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock begin
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.018s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.008s]
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.264s
Pals-MacBook-Air:platform-tools Fiksdal$ sudo fastboot flash partition gpt.bin
Password:
sudo: fastboot: command not found
Pals-MacBook-Air:platform-tools Fiksdal$ sudo ./fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.005s]
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.259s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.209s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.548s]
Finished. Total time: 0.943s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.093s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.344s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.838s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.234s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.729s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.125s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.667s]
Writing 'dsp' OKAY [ 0.132s]
Finished. Total time: 0.984s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash oem oem.img
(bootloader) has-slot:oem: not found
Sending 'oem' (232923 KB) OKAY [ 10.302s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 10.554s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
Sending 'system' (517135 KB) OKAY [ 20.549s]
Writing 'system' (bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
Sending 'system' (522979 KB) OKAY [ 20.458s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 20.674s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
Sending 'system' (524215 KB) OKAY [ 20.487s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 20.704s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
Sending 'system' (521087 KB) OKAY [ 19.126s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 19.330s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
Sending 'system' (518083 KB) OKAY [ 19.082s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 19.295s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
Sending 'system' (515569 KB) OKAY [ 18.974s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 19.192s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
Sending 'system' (250209 KB) OKAY [ 9.380s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 9.579s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (75092 KB) OKAY [ 2.888s]
Writing 'modem' OKAY [ 1.878s]
Finished. Total time: 4.954s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.020s]
Finished. Total time: 0.210s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.020s]
Finished. Total time: 0.210s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.114s]
Writing 'fsg' OKAY [ 0.065s]
Finished. Total time: 0.364s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.206s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 2.252s]
Finished. Total time: 2.442s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase customize
(bootloader) has-slot:customize: not found
Erasing 'customize' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.194s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase customize
(bootloader) has-slot:customize: not found
Erasing 'customize' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.194s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase clogo
(bootloader) has-slot:clogo: not found
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.192s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
Finished. Total time: 0.003s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot reboot
Rebooting
Finished. Total time: 0.005s[/HTML]
This seemed to do nothing to my device. I wondered if maybe the bootloader was in some sort of locked/unlocked limbo, so I tried to unlock the bootloader again using the key I got from Moto by email. That did not work either.
Code:
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem unlock THECODEFORMYDEVICE
(bootloader) invalid boot state
OKAY [ 0.005s]
Finished. Total time: 0.008s
So I seem to be getting nowhere. There has to be some way to totally wipe everything, to get a fresh start? I do not care if I have to restore stock firmware, stock bootloader, whatever. I just want to be able to at least use my phone somehow. Is my device totally bricked? Is there nothing I can do?
I used adb and fastboot on macOS High Sierra.

1) What custom ROM are you trying to flash? That TWRP error 255 suggests you're trying to flash a 64 bit custom ROM onto your device whilst you have a 32 bit TWRP. I'd try finding a 32 bit custom ROM and flash that, or try to update your TWRP to 64 bit and try again with the custom ROM you've downloaded.
2) Looking at your fastboot flash log, your bootloader appears to be 'locked' from the initial OEM lock command, but as you've tried to flash a stock ROM older than the firmware you had on your device, your device bootloader rejected the flash (security version downgrade and pre-flash validation errors point to using a much older firmware than what you had on your device).
Can I ask why you wanted to re-lock your bootloader? As far as I understand, you don't have to lock the bootloader to revert back to stock in most cases...
I'm not familiar with Z2 Play firmwares, though rahulsnair has uploaded the Oreo June 2018 security patch firmware here: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 If you can confirm that this firmware has been released to your device variant/software channel, I'd suggest downloading that firmware, and delete the old firmware you have. Extract the newer firmware to your ADB directory and try to flash again.
If that doesn't work, you may have to consider submitting your device to a service centre (unless someone else has suggestions?).

echo92 said:
1) What custom ROM are you trying to flash? That TWRP error 255 suggests you're trying to flash a 64 bit custom ROM onto your device whilst you have a 32 bit TWRP. I'd try finding a 32 bit custom ROM and flash that, or try to update your TWRP to 64 bit and try again with the custom ROM you've downloaded.
2) Looking at your fastboot flash log, your bootloader appears to be 'locked' from the initial OEM lock command, but as you've tried to flash a stock ROM older than the firmware you had on your device, your device bootloader rejected the flash (security version downgrade and pre-flash validation errors point to using a much older firmware than what you had on your device).
Can I ask why you wanted to re-lock your bootloader? As far as I understand, you don't have to lock the bootloader to revert back to stock in most cases...
I'm not familiar with Z2 Play firmwares, though rahulsnair has uploaded the Oreo June 2018 security patch firmware here: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 If you can confirm that this firmware has been released to your device variant/software channel, I'd suggest downloading that firmware, and delete the old firmware you have. Extract the newer firmware to your ADB directory and try to flash again.
If that doesn't work, you may have to consider submitting your device to a service centre (unless someone else has suggestions?).
Click to expand...
Click to collapse
Whoah, thank you! I got it to boot!
I flashed the Oreo firmware that you linked me to using the method the post supplied. (I also ran
Code:
./fastboot oem unlock
first).
After that, when I tried rebooting the phone, I saw (for less than one second) some icon with an Android laying down., then the screen went totally black without any further progress.
I then held down power and volume down to boot into bootloader, then I chose "FACTORY MODE". It then booted Oreo! There was some "encrypting your device message", and then it continued booting Oreo.
However, I still could connect to no cellular networks. It could have something to do with the fact that I am in "FACTORY MODE"? I put my two sims in there, but they both do not connect to anything at all. Although the phone can read the name of their operator. I seem to recall that I could indeed connect to cellular networks in "FACTORY MODE" before, so I am not sure.
I tried rebooting the phone again and it now got stuck in this screen with the Android laying down. It says "No command." This time the image persisted for longer before the screen got stuck. Then it went black for a while, while the "device is unlocked" warning screen came back, and now the Android laying down again. It seems to loop like this. I can only get it to boot Android "normally" by going through the bootloader and chosing factory mode. That would be fine, except I do not have cellular connectivity, only WiFi. Seems strange to me, as I did restore the whole firmware, which should include the modem driver, right? Maybe I flashed the wrong region firmware or something? However, this exact problem was there even before I flashed any firmware at all. It was in the beginning, after the accidental update. The phone would not boot properly, and I had to use factory mode. Then also, the phone woud boot, but had no cellular connectivity, exactly like this now.
In case it helps, I am posting my fastboot output
Code:
Pals-MacBook-Air:~ Fiksdal$ cd Downloads/platform-tools
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot devices
ZY224BLVMC fastboot
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.008s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.008s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.160s]
Finished. Total time: 0.189s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.248s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.578s]
Finished. Total time: 0.847s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (71565 KB) OKAY [ 3.333s]
Writing 'modem' OKAY [ 0.474s]
Finished. Total time: 3.824s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
Sending 'fsg' (4020 KB) OKAY [ 0.200s]
Writing 'fsg' OKAY [ 0.069s]
Finished. Total time: 0.287s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.020s]
Finished. Total time: 0.042s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.020s]
Finished. Total time: 0.043s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.825s]
Writing 'dsp' OKAY [ 0.138s]
Finished. Total time: 0.981s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.111s]
Writing 'logo' OKAY [ 0.065s]
Finished. Total time: 0.193s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.810s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.280s]
Finished. Total time: 1.107s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 1.036s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.342s]
Finished. Total time: 1.396s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
Sending 'system' (262141 KB) OKAY [ 12.459s]
Writing 'system' OKAY [ 1.390s]
Finished. Total time: 13.866s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
Sending 'system' (255693 KB) OKAY [ 12.038s]
Writing 'system' OKAY [ 1.319s]
Finished. Total time: 13.375s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
Sending 'system' (243069 KB) OKAY [ 11.486s]
Writing 'system' OKAY [ 1.386s]
Finished. Total time: 12.891s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
Sending 'system' (260338 KB) OKAY [ 12.294s]
Writing 'system' OKAY [ 1.982s]
Finished. Total time: 14.294s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
Sending 'system' (260451 KB) OKAY [ 12.350s]
Writing 'system' OKAY [ 1.436s]
Finished. Total time: 13.804s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
Sending 'system' (242833 KB) OKAY [ 11.667s]
Writing 'system' OKAY [ 1.249s]
Finished. Total time: 12.934s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
Sending 'system' (262140 KB) OKAY [ 12.659s]
Writing 'system' OKAY [ 1.301s]
Finished. Total time: 13.978s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
Sending 'system' (262141 KB) OKAY [ 12.531s]
Writing 'system' OKAY [ 1.479s]
Finished. Total time: 14.027s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.8
(bootloader) has-slot:system: not found
Sending 'system' (262142 KB) OKAY [ 12.492s]
Writing 'system' OKAY [ 1.586s]
Finished. Total time: 14.096s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.9
(bootloader) has-slot:system: not found
Sending 'system' (262141 KB) OKAY [ 12.641s]
Writing 'system' OKAY [ 1.326s]
Finished. Total time: 13.985s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.10
(bootloader) has-slot:system: not found
Sending 'system' (239064 KB) OKAY [ 11.553s]
Writing 'system' OKAY [ 1.200s]
Finished. Total time: 12.771s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.11
(bootloader) has-slot:system: not found
Sending 'system' (45248 KB) OKAY [ 2.014s]
Writing 'system' OKAY [ 0.265s]
Finished. Total time: 2.297s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash oem oem.img
(bootloader) has-slot:oem: not found
Sending 'oem' (155105 KB) OKAY [ 7.322s]
Writing 'oem' OKAY [ 0.869s]
Finished. Total time: 8.207s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase carrier
(bootloader) has-slot:carrier: not found
Erasing 'carrier' OKAY [ 0.041s]
Finished. Total time: 0.063s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase DDR
(bootloader) has-slot:DDR: not found
Erasing 'DDR' OKAY [ 0.007s]
Finished. Total time: 0.028s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.073s]
Finished. Total time: 0.096s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.015s]
Finished. Total time: 0.037s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem fb_mode_clear
OKAY [ 0.005s]
Finished. Total time: 0.005s
Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot reboot
Rebooting
Finished. Total time: 0.005s

Fiksdal said:
Hi
I have had my Z2 Play for half a year, and soon after I got it I unlocked the bootloader with Motorola's official method, installed TWRP, rooted it with Magisk and installed Xposed Framework. I was on Nougat all the time and used it happily. A few months ago it started repeatedly asking me to OTA update, but I just ignored the messages. Then one day, I must have accidentally pressed something, because I think it tried to update. I got a message that the update failed or something like that.
The phone gradually got worse after that, randomly rebooting into TWRP. I could somehow get it to boot Android by going to the bootloader and chosing "factory mode" but mostly the modem would not work at all and the phone would not be usable.
Trying to solve it, I decided to flash a whole ROM, hoping to remove all of the damage done by the botchered update. Since I already had unlocked my bootloader and TWRP, I decided to just flash a custom ROM, since I did not know if flashing stock would work with TWRP. I found some of the custom ROMs here on XDA, and tried to flash them with TWRP. However, flashing would not work. I got some error code 255. I am attaching a screenshot of the error.
I tried both flashing via the adb sideload method via my Mac and via USB OTG (flash drive) but I got the same result for both.
Having seen this, I decided to try to relock the bootloader and restore stock firmware. I tried following this tutorial. However, that did not seem to work. Here is my fastboot output:
This seemed to do nothing to my device. I wondered if maybe the bootloader was in some sort of locked/unlocked limbo, so I tried to unlock the bootloader again using the key I got from Moto by email. That did not work either.
So I seem to be getting nowhere. There has to be some way to totally wipe everything, to get a fresh start? I do not care if I have to restore stock firmware, stock bootloader, whatever. I just want to be able to at least use my phone somehow. Is my device totally bricked? Is there nothing I can do?
I used adb and fastboot on macOS High Sierra.
Click to expand...
Click to collapse
I can't unlock the bootloader of my z2 play:crying:....... please tell me the process:crying:........

unbrick moto g6 play

Hello guyz, my moto g6 play has a softbrick i think. i tried to unbrick it but allway faill.
on fastboot it says that:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
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.094s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.245s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.429s]
finished. total time: 0.674s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (68654 KB)...
OKAY [ 2.421s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.437s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (5908 KB)...
OKAY [ 0.184s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.199s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.534s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.534s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (512617 KB)...
OKAY [ 18.021s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 18.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (522892 KB)...
OKAY [ 18.358s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 96.946s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (521140 KB)...
OKAY [ 18.077s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 18.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (482035 KB)...
OKAY [ 17.477s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 17.482s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (168392 KB)...
OKAY [ 6.413s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.413s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (146510 KB)...
OKAY [ 5.388s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 5.392s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 535822336 bytes
sending 'vendor' (247519 KB)...
OKAY [ 8.819s]
writing 'vendor'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 8.829s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
I can install a gsi and boot it, but there's no way to reflash the stock rom. th bootloader says "Flashing_locked"
can someone help to come out from this brick?

It sounds like your bootloader is locked then. And you need firmware the same as, or newer than the one currently on the device. You can't downgrade.

Help! I disconnected the cable at the time he was flashing the rom 9.0

Help! I disconnected the cable at the time he was flashing the rom 9.0 ai my (moto G6 Play 1922-5) stayed so whenever I flash a rom.
{
"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"
}
When I flash the rom on the device.
C:\9>mfastboot oem lock begin
...
(bootloader) Not in unlocked state
OKAY [ 0.002s]
finished. total time: 0.003s
C:\9>mfastboot oem lock begin
...
(bootloader) Not in unlocked state
OKAY [ 0.002s]
finished. total time: 0.005s
C:\9>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.045s
C:\9>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (7483 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.363s
C:\9>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1423 KB)...
OKAY [ 0.050s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.057s
C:\9>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.550s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.568s
C:\9>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (18532 KB)...
OKAY [ 0.617s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.636s
C:\9>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.534s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.538s
C:\9>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (188470 KB)...
OKAY [ 6.197s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 6.213s
C:\9>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 8.994s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 8.998s
C:\9>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (235853 KB)...
OKAY [ 8.075s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 8.087s
C:\9>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262141 KB)...
OKAY [ 8.936s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 8.954s
C:\9>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262143 KB)...
OKAY [ 9.041s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 9.059s
C:\9>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (251061 KB)...
OKAY [ 8.919s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 8.927s
C:\9>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.5': No error
C:\9>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.6': No error
C:\9>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.7': No error
C:\9>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (59664 KB)...
OKAY [ 1.939s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 1.946s
C:\9>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.067s
C:\9>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.100s
C:\9>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (5984 KB)...
OKAY [ 0.210s]
writing 'fsg'...
(bootloader) Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.228s
C:\9>mfastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s
C:\9>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.102s
C:\9>mfastboot oem lock
...
(bootloader) Not in unlocked state
OKAY [ 0.105s]
finished. total time: 0.118s
C:\9>pause
Pressione qualquer tecla para continuar. . .
Deseja finalizar o arquivo em lotes (S/N)?
Click to expand...
Click to collapse

Don't try to lock the bootloader. Open the flashfile XML in the zip. The commands are there. Or use Moto smart assistant to rescue.

It looks like you need to unlock your bootloader OP. Here's a video guide https://www.youtube.com/watch?v=92xb9VvxYMA

madbat99 said:
Don't try to lock the bootloader. Open the flashfile XML in the zip. The commands are there. Or use Moto smart assistant to rescue.
Click to expand...
Click to collapse
does not work

Motorocker said:
It looks like you need to unlock your bootloader OP. Here's a video guide https://www.youtube.com/watch?v=92xb9VvxYMA
Click to expand...
Click to collapse
C:\9>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.004s]
finished. total time: 0.004s
always remain of the error

Diego Davi said:
C:\9>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.004s]
finished. total time: 0.004s
always remain of the error
Click to expand...
Click to collapse
Can you post the output you get from fastboot getvar all
I don't know if that will help folk work out a fix for you but I reckon it'll be worth seeing if it works.

Yeah he's locked

fastboot getvar all
Motorocker said:
Can you post the output you get from fastboot getvar all
I don't know if that will help folk work out a fix for you but I reckon it'll be worth seeing if it works.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 98ca827
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
sample this is my device that I bought here in Brazil

Diego Davi said:
Help! I disconnected the cable at the time he was flashing the rom 9.0 ai my (moto G6 Play 1922-5) stayed so whenever I flash a rom.
When I flash the rom on the device.
Click to expand...
Click to collapse
I'm almost positive that you're flashing the wrong firmware. As far as I know, no firmware for the G6 Play has 7 sparse chunk files. I could be wrong, but I had to a lot of digging through aljeter and Jeter firmware to get twrp working, and at best I saw 5 sparse chunks in every firmware that I handled. Can you tell me the name of the firmware zip you're trying to flash, or point me to it?

Spaceminer said:
I'm almost positive that you're flashing the wrong firmware. As far as I know, no firmware for the G6 Play has 7 sparse chunk files. I could be wrong, but I had to a lot of digging through aljeter and Jeter firmware to get twrp working, and at best I saw 4 sparse chunks in every firmware that I handled. Can you tell me the name of the firmware zip you're trying to flash, or point me to it?
Click to expand...
Click to collapse
My friend also warned about this but I used the .bat file
so that it has until the 7, the last rom that ultilive was the
XT1922-5_ALJETER_9.0_PPPS29.55-25-4_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml

Diego Davi said:
My friend also warned about this but I used the .bat file
so that it has until the 7, the last rom that ultilive was the
XT1922-5_ALJETER_9.0_PPPS29.55-25-4_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml
Click to expand...
Click to collapse
Download minimal adb & fastboot if you don't have it already. Here's a link to the thread. I use the portable version. Then check the firmware you have right now. Make sure the sparse chunks go from 0-4. There should be 5 total. If there are less, or more sparse chunks than that, redownload your firmware from here. Then follow these steps.
1. Unzip the firmware into the same folder as minimal adb & fastboot.
2. Right click the cmd-here.exe shortcut inside the folder and run it as administrator.
3. Open the flashfile.xml with a text editor.
4. Run the following commands in order.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
5. Use your volume buttons, select reboot bootloader and hit the power button. You should loop back into fastboot.
6. Run the command; fastboot oem fb_mode_set
7. Read the flash file, then flash everything in it manually, and in order. If something refuses to flash, skip it and go to the next item in line. Do NOT use a bat file for ANY of this!
8. Once finished, issue the command fastboot oem fb_mode_clear then fastboot reboot and your device should start working again.
If there are any errors please let me know exactly what they say.

Spaceminer said:
Download minimal adb & fastboot if you don't have it already. Here's a link to the thread. I use the portable version. Then check the firmware you have right now. Make sure the sparse chunks go from 0-4. There should be 5 total. If there are less, or more sparse chunks than that, redownload your firmware from here. Then follow these steps.
1. Unzip the firmware into the same folder as minimal adb & fastboot.
2. Right click the cmd-here.exe shortcut inside the folder and run it as administrator.
3. Open the flashfile.xml with a text editor.
4. Run the following commands in order.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
5. Use your volume buttons, select reboot bootloader and hit the power button. You should loop back into fastboot.
6. Run the command; fastboot oem fb_mode_set
7. Read the flash file, then flash everything in it manually, and in order. If something refuses to flash, skip it and go to the next item in line. Do NOT use a bat file for ANY of this!
8. Once finished, issue the command fastboot oem fb_mode_clear then fastboot reboot and your device should start working again.
If there are any errors please let me know exactly what they say.
Click to expand...
Click to collapse
I'll download it here and test it now.
here is the photo of how the bootloader stayed when it solved the problem.
https://imgur.com/a/Ns8afvU

Diego Davi said:
I'll download it here and test it now.
here is the photo of how the bootloader stayed when it solved the problem.
https://imgur.com/a/Ns8afvU
Click to expand...
Click to collapse
Please let me know if it works!

Spaceminer said:
Please let me know if it works!
Click to expand...
Click to collapse
I do not start the system
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.003s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.076s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash bootloader bootload
er.img
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.401s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.019s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.019s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.019s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.010s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.003s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.003s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.056s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash bootloader bootload
er.img
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.257s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.389s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (59664 KB)...
OKAY [ 1.941s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 1.953s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (5984 KB)...
OKAY [ 0.193s]
writing 'fsg'...
(bootloader) Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.210s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.534s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.545s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (1423 KB)...
OKAY [ 0.048s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.058s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.546s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.560s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash recovery recovery.i
mg
target reported max download size of 535822336 bytes
sending 'recovery' (18532 KB)...
OKAY [ 0.603s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.614s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash system system.img_s
parsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (488837 KB)...
OKAY [ 15.851s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 15.858s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash system system.img_s
parsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (498726 KB)...
OKAY [ 15.974s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 15.980s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash system system.img_s
parsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (523261 KB)...
OKAY [ 17.052s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 17.060s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash system system.img_s
parsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (486861 KB)...
OKAY [ 15.826s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 15.832s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash system system.img_s
parsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (198692 KB)...
OKAY [ 6.452s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.458s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash vendor vendor.img
target reported max download size of 535822336 bytes
sending 'vendor' (252383 KB)...
OKAY [ 8.169s]
writing 'vendor'...
(bootloader) Invalid partition name vendor
FAILED (remote failure)
finished. total time: 8.176s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (188474 KB)...
OKAY [ 6.105s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 6.114s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.003s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>

Diego Davi said:
C:\rom\XT1922-5_ALJETER_RETBR_9.0_PPP29.55-25>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
I hate to say it, but that's very bad. Unless you have JTAG equipment on hand, you won't be able to fix this device without sending it Motorola. Your emmc is locked to read only. You're effectively bricked.

Diego Davi said:
My friend also warned about this but I used the .bat file
so that it has until the 7, the last rom that ultilive was the
XT1922-5_ALJETER_9.0_PPPS29.55-25-4_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml
Click to expand...
Click to collapse
Don't use .bat to flash. Type the commands manually. They are in the flashfile.xml in the firmware.

Spaceminer said:
I hate to say it, but that's very bad. Unless you have JTAG equipment on hand, you won't be able to fix this device without sending it Motorola. Your emmc is locked to read only. You're effectively bricked.
Click to expand...
Click to collapse
Okay, thanks a lot for the help !. I'm very grateful

madbat99 said:
Don't use .bat to flash. Type the commands manually. They are in the flashfile.xml in the firmware.
Click to expand...
Click to collapse
Okay, I did not know that detail next time. I already know how to do the procedure, thank you!

Spaceminer said:
Please let me know if it works!
Click to expand...
Click to collapse
Good night, would I have to do the same unbrick of the moto g5 that uses memory card?

Moto G5 Plus totally dead, stuck on AP Fastboot Flash Mode (Secure)

Hello friends,
Plz help my Moto G5 Plus xt686 is totally dead. I tried flashing stock rom via fastboot. But it's not working, phone still in fastboot stuck condition. Also tried RSD lite tool and Lenovo repair assistant both are not reading my device. Tried unlocking bootloader but getting read datablock error. Tried flashing naugat and oreo roms. Plz spare your valuable time to help me out. Regards.

Kumarvicky12 said:
Hello friends,
Plz help my Moto G5 Plus xt686 is totally dead. I tried flashing stock rom via fastboot. But it's not working, phone still in fastboot stuck condition. Also tried RSD lite tool and Lenovo repair assistant both are not reading my device. Tried unlocking bootloader but getting read datablock error. Tried flashing naugat and oreo roms. Plz spare your valuable time to help me out. Regards.
Click to expand...
Click to collapse
Did you Try flashing latest stock firmware, and did bootloader and gpt got flashed successful?

Nothing got flashed, bootloader, gpt everything failed.

Kumarvicky12 said:
Nothing got flashed, bootloader, gpt everything failed.
Click to expand...
Click to collapse
What error it give?

riyan65 said:
What error it give?
Click to expand...
Click to collapse
plz go through logs
C:\Minimal ADB and Fastboot>echo off
max-sparse-size: 268435456
finished. total time: 0.000s
...
FAILED (remote failure)
finished. total time: 0.016s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.328s
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 1.578s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.594s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.369s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.377s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.047s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 5.670s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.718s
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 5.660s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.676s
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 5.473s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.489s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.770s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.785s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.771s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.786s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.779s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.795s
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 5.542s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.558s
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 5.802s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.833s
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 5.614s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.629s
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.315s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.362s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'DDR'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.000s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
...
FAILED (remote failure)
finished. total time: 0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .

I believe you have a problem with your phone internal memory.
Enviado de meu Moto G (5) Plus usando o Tapatalk

You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html

Kumarvicky12 said:
plz go through logs
C:\Minimal ADB and Fastboot>echo off
max-sparse-size: 268435456
finished. total time: 0.000s
...
FAILED (remote failure)
finished. total time: 0.016s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.086s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.328s
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 1.578s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.594s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.369s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.377s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.047s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 5.670s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.718s
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 5.660s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.676s
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 5.473s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.489s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.770s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.785s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.771s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.786s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.779s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.795s
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 5.542s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.558s
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 5.802s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.833s
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 5.614s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.629s
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.315s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.362s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'DDR'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.000s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
...
FAILED (remote failure)
finished. total time: 0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
Click to expand...
Click to collapse
Mostly you device gpt table got corrupted or your emmc storage is failing. I suggest you to flash gpt table of different firmware ,Maybe it will help.

Ok will give a try

roundaway said:
You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html
Click to expand...
Click to collapse
i never tried any custom ro on this mobile. it was neither unlocked. it automatically got in this condition. i didn't done anything with it.

cybernetus said:
I believe you have a problem with your phone internal memory.
Enviado de meu Moto G (5) Plus usando o Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 6839d8c1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 4FA26E6C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.156s

riyan65 said:
Mostly you device gpt table got corrupted or your emmc storage is failing. I suggest you to flash gpt table of different firmware ,Maybe it will help.
Click to expand...
Click to collapse
Different firmware means from other moto devices....??

roundaway said:
You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html
Click to expand...
Click to collapse
my device is not getting recognised as adb device, but only fastboot device, i am unable to get unlock data. plz check below
C:\Minimal ADB and Fastboot>adb device
adb: usage: unknown command device
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot devices
6839d8c1 fastboot
C:\Minimal ADB and Fastboot>

How about the gpt table? You try to flash t this?
Enviado de meu Moto G (5) Plus usando o Tapatalk
---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------
Kumarvicky12 said:
Different firmware means from other moto devices....??
Click to expand...
Click to collapse
From another rom. Lineage etc. I believe.
Enviado de meu Moto G (5) Plus usando o Tapatalk

Kumarvicky12 said:
my device is not getting recognised as adb device, but only fastboot device, i am unable to get unlock data. plz check below
C:\Minimal ADB and Fastboot>adb device
adb: usage: unknown command device
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot devices
6839d8c1 fastboot
C:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Here's what I recommend. Download the official Motorola G5 Plus (Potter) Oreo firmware, POTTER_RETAIL_8.1.0_OPSS28.85-17-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from whatever site you can find it (https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/). Extract the zip file in the same folder as fastboot.exe.
With the phone in fastboot mode execute each of the following commands one at a time:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If the phone reboots and starts up then great. After it starts go to Settings and enable Developer Options. In Developer Options enable ADB and OEM Unlock.
If the phone doesn't boot properly then sorry. You will have tried to install the official retail version.

Kumarvicky12 said:
Different firmware means from other moto devices....??
Click to expand...
Click to collapse
Different firmware= different region firmware like retain

same phone same error
I have the same phone and got these results with roundaway suggestion
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.018s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.048s
the phone shows no IMEI "0000000" no baseband "blank space" and no product/variant "potter 0000000000000000" i belive it is a hardware malfunction at this point I have tried everything I could find in the forums

MaxPowell2 said:
I have the same phone and got these results with roundaway suggestion
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.018s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.048s
the phone shows no IMEI "0000000" no baseband "blank space" and no product/variant "potter 0000000000000000" i belive it is a hardware malfunction at this point I have tried everything I could find in the forums
Click to expand...
Click to collapse
Confirm the ROM you tried to install is the correct one for your phone:
Moto G5 Plus = potter
Moto G5 = cedric
Also, the files to be flashed should be in the same folder as the fastboot.exe files.
There are multiple problems with the phones. One is it won't accept a fastboot flash of factory firmware. Second problem might show up after/if the phone reboots and that is the infamous IMEI = 0.
The OP's getvar all command didn't reveal the (bootloader) ro.build.fingerprint information which would tell us the firmware version installed. However, the bootloader number appears to be the current Oreo version. That was one reason for flashing the latest version of the Oreo firmware.
The only other thing to try would be to download the latest version of TWRP into the same folder as fastboot.exe and try:
fastboot boot twrp.img (where twrp.img is the filename of the latest twrp)
If the phone boots into twrp then download the latest twrp flashable Oreo and copy and paste to the phone. Try and Install it. Big longshot because the bootloader is probably locked..

Dont worry dude, I have been there and came out of it.
First of all sorry for being late.
What you have to do is
1. connect your phone to your pc with with a pc or laptop.
L2. Download Lenovo Moto Smart Assistant lll from the Official website. Just search on google.
3. Make sure you install it on the C: Drive only, with administrative rights.
4. Run it, it will ask for your Lenovo login id. Now you need to go to Lenovos website from the browser, register a new one.
And after 5-10 mins login with the same id.
5. Well, if you are unable to login due to un responsive page, use a vpn .
6. After you login go for "Rescue".
7. Choose the option which says, Phone not able to boot or start.
8. It would automatically detect your device if it's connected to a pc with a cable and is in fastboot mode.
9. It fails to detect sometimes, so you can try manually enter your device.
10.Now it would download the latest stock rom, there would be a small download text which is hyperlinked.
11. Once completed it might ask to "Rescue".
It will start working, it might look like it's stuck, but it not, it can take from 5 mins to 30 mins or even more.
12. After the process is complete, just boot your phone normally, or it might boot automatically.
13. Enjoy.
If there's something wrong any problem or error,
Let me know.

Akahat27 said:
Dont worry dude, I have been there and came out of it.
First of all sorry for being late.
What you have to do is
1. connect your phone to your pc with with a pc or laptop.
L2. Download Lenovo Moto Smart Assistant lll from the Official website. Just search on google.
3. Make sure you install it on the C: Drive only, with administrative rights.
4. Run it, it will ask for your Lenovo login id. Now you need to go to Lenovos website from the browser, register a new one.
And after 5-10 mins login with the same id.
5. Well, if you are unable to login due to un responsive page, use a vpn .
6. After you login go for "Rescue".
7. Choose the option which says, Phone not able to boot or start.
8. It would automatically detect your device if it's connected to a pc with a cable and is in fastboot mode.
9. It fails to detect sometimes, so you can try manually enter your device.
10.Now it would download the latest stock rom, there would be a small download text which is hyperlinked.
11. Once completed it might ask to "Rescue".
It will start working, it might look like it's stuck, but it not, it can take from 5 mins to 30 mins or even more.
12. After the process is complete, just boot your phone normally, or it might boot automatically.
13. Enjoy.
If there's something wrong any problem or error,
Let me know.
Click to expand...
Click to collapse
This didn't work. Smart Assistant couldn't detect the device I am trying to Rescue. Can you suggest something else?