please help urgently - Moto Z Play Questions & Answers

install by fastboot oreo and at the end of the phone no longer start, just enter fastboot. minimal adb gives me all error, attached capture, I hope someone can help me :crying::crying:
ON THE PHONE IT SAYS THE FOLLOWING FASTBOOT REASON: FALL-THROUGH FROM NORMAL BOOT MODE
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
???????????? fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target didn't report max-download-size
sending 'partition' (45 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target didn't report max-download-size
sending 'bootloader' (5115 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target didn't report max-download-size
sending 'modem' (73864 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target didn't report max-download-size
sending 'fsg' (2612 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target didn't report max-download-size
sending 'dsp' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target didn't report max-download-size
sending 'logo' (2187 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (16484 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target didn't report max-download-size
sending 'oem' (110454 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target didn't report max-download-size
sending 'system' (254735 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target didn't report max-download-size
sending 'system' (258156 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target didn't report max-download-size
sending 'system' (248454 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target didn't report max-download-size
sending 'system' (242885 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target didn't report max-download-size
sending 'system' (259562 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target didn't report max-download-size
sending 'system' (262031 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target didn't report max-download-size
sending 'system' (260168 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target didn't report max-download-size
sending 'system' (258453 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target didn't report max-download-size
sending 'system' (260863 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.9
target didn't report max-download-size
sending 'system' (262078 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.10
target didn't report max-download-size
sending 'system' (262141 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.11
target didn't report max-download-size
sending 'system' (257454 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.895s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.000s

try
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120
Alternative to RSDlite section.

KrisM22 said:
try
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120
Alternative to RSDlite section.
Click to expand...
Click to collapse
Hi, it did not work, and the rds lite does not recognize the phone. I'm going back to download the firmware to vlver to try, do you know any other solution?
Attached photo of how the bootloander looks

RSDlite itself will not work for you but fastboot might.
I hoped fastboot devices might
You can boot to fastboot logs - nice - can you switch to fastboot screen and take a pic of it?
I am heading out but will be back in a bit. hang on!

KrisM22 said:
RSDlite itself will not work for you but fastboot might.
I hoped fastboot devices might
You can boot to fastboot logs - nice - can you switch to fastboot screen and take a pic of it?
I am heading out but will be back in a bit. hang on!
Click to expand...
Click to collapse
I can go into all the fatboot manes, start, restart bootloander, recovery mode (here there is no recovery) etc

joshua764 said:
I can go into all the fatboot manes, start, restart bootloander, recovery mode (here there is no recovery) etc
Click to expand...
Click to collapse
If you have stock recovery, you will see a dead Android. Hold pwr and tap volup
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
KrisM22 said:
If you have stock recovery, you will see a dead Android. Hold pwr and tap volup
Click to expand...
Click to collapse
Then tap voldn once and tap pwr. Take a picture.

KrisM22 said:
If you have stock recovery, you will see a dead Android. Hold pwr and tap volup
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Then tap voldn once and tap pwr. Take a picture.
Click to expand...
Click to collapse
whenever I try to enter recovery stock I get this screen that I attach ... I appreciate your time in helping me

you attached bootloader logs
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
if you plug your phone to your computer,
and press and hold pwr & vol-up (5-20 secs)
does your computer chirp as if recognizing the phone I don't care about files.

KrisM22 said:
you attached bootloader logs
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
if you plug your phone to your computer,
and press and hold pwr & vol-up
does your computer chirp as if recognizing the phone I don't care about files.
Click to expand...
Click to collapse
if it sounds, it recognizes it

joshua764 said:
if it sounds, it recognizes it
Click to expand...
Click to collapse
Are you saying "YES, it sounds"?

KrisM22 said:
Are you saying "YES, it sounds"?
Click to expand...
Click to collapse
yes. sorry my bad english

Is the screen showing that bootloader log thing or something else?

KrisM22 said:
Is the screen showing that bootloader log thing or something else?
Click to expand...
Click to collapse
It shows me what you see on the attached screen,
where do you enter the error of the screens that I sent you

joshua764 said:
It shows me what you see on the attached screen,
where do you enter the error of the screens that I sent you
Click to expand...
Click to collapse
Not understanding sorry please type in spanish and then use google translate and paste english translation.
BOTH spanish and english.
picture is bad, please attach again. I need that. Sorry and thanks!
---------- Post added at 04:33 PM ---------- Previous post was at 04:20 PM ----------
please answer. I will try to help.

KrisM22 said:
Not understanding sorry please type in spanish and then use google translate and paste english translation.
BOTH spanish and english.
picture is bad, please attach again. I need that. Sorry and thanks!
---------- Post added at 04:33 PM ---------- Previous post was at 04:20 PM ----------
please answer. I will try to help.
Click to expand...
Click to collapse
What you see in the image is what allows me to see the bootloader, if I want to enter with the power button some other side sends me the error that I have previously sent
Lo que ves en la imagen es lo que me permite ver el bootloader, si quiero entrar con el boton power algun otro lado me manda el error que te he enviado anteriormente

joshua764 said:
What you see in the image is what allows me to see the bootloader, if I want to enter with the power button some other side sends me the error that I have previously sent
Lo que ves en la imagen es lo que me permite ver el bootloader, si quiero entrar con el boton power algun otro lado me manda el error que te he enviado anteriormente
Click to expand...
Click to collapse
The image in your last post doesn't appear to load properly - for me, the image loads as a 404 (not found).
When you flashed the Oreo stock ROM, did you lock your bootloader?
What ADB version are you using? Are you using the latest minimal ADB tools (v1.4.3) https://forum.xda-developers.com/showthread.php?t=2317790 or the Google fastboot tools? https://developer.android.com/studio/releases/platform-tools
EDIT - if you can, can you provide your getvar info please?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste or upload the output here, you may wish to omit your IMEI.

echo92 said:
The image in your last post doesn't appear to load properly - for me, the image loads as a 404 (not found).
When you flashed the Oreo stock ROM, did you lock your bootloader?
What ADB version are you using? Are you using the latest minimal ADB tools (v1.4.3) https://forum.xda-developers.com/showthread.php?t=2317790 or the Google fastboot tools? https://developer.android.com/studio/releases/platform-tools
EDIT - if you can, can you provide your getvar info please?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste or upload the output here, you may wish to omit your IMEI.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY223LCGC3
(bootloader) cid: 0x0000
(bootloader) channelid: 0x23
(bootloader) uid: 9C2DFF1200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 08-29-2017
(bootloader) sku: XT1635-02-SS
(bootloader) battid: SNN5975A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jan 5 2:39: 1 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/addison/addison:8.0.0/OPN
(bootloader) ro.build.fingerprint[1]: 27.76-12-22/24:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.24.addison.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g174984b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Mar 26 08:27:14 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=fbd9875-dirty
(bootloader) devcfg.git: git=fbd9875-dirty
(bootloader) keymaster.git: git=fbd9875-dirty
(bootloader) cmnlib.git: git=fbd9875-dirty
(bootloader) cmnlib64.git: git=fbd9875-dirty
(bootloader) prov.git: git=fbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: attmx
all: listed above
finished. total time: 0.517s

echo92 said:
The image in your last post doesn't appear to load properly - for me, the image loads as a 404 (not found).
When you flashed the Oreo stock ROM, did you lock your bootloader?
What ADB version are you using? Are you using the latest minimal ADB tools (v1.4.3) https://forum.xda-developers.com/showthread.php?t=2317790 or the Google fastboot tools? https://developer.android.com/studio/releases/platform-tools
EDIT - if you can, can you provide your getvar info please?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Paste or upload the output here, you may wish to omit your IMEI.
Click to expand...
Click to collapse
hi, download another firmware stock and flash it fastboot and just start the phone, thank you very much for your time, something is wrong with the firmware

joshua764 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY223LCGC3
(bootloader) cid: 0x0000
(bootloader) channelid: 0x23
(bootloader) uid: 9C2DFF1200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 08-29-2017
(bootloader) sku: XT1635-02-SS
(bootloader) battid: SNN5975A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jan 5 2:39: 1 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/addison/addison:8.0.0/OPN
(bootloader) ro.build.fingerprint[1]: 27.76-12-22/24:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.24.addison.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g174984b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Mar 26 08:27:14 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=fbd9875-dirty
(bootloader) devcfg.git: git=fbd9875-dirty
(bootloader) keymaster.git: git=fbd9875-dirty
(bootloader) cmnlib.git: git=fbd9875-dirty
(bootloader) cmnlib64.git: git=fbd9875-dirty
(bootloader) prov.git: git=fbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: attmx
all: listed above
finished. total time: 0.517s
Click to expand...
Click to collapse
Thanks for the output. It does look like your bootloader was re-locked during the last flash. As such, those fallthrough errors suggest your bootloader cannot verify your device partitions (e.g. kernel, system, recovery, etc) and thus is blocking boot https://source.android.com/security/verifiedboot/ That could point to, for example, a bad flash or failing flash memory (so your bootloader cannot read the partitions).
With your original flash of the Oreo stock ROM, did you note any errors in the flash, or is the flash log you provided from the original flash? Looking at your output it does suggest the flash worked as the values (bootloader version C1:82, baseband and kernel) seem to match the stock Oreo update.
I'd try a different computer and/or different USB ports, update your ADB tools and see if you can re-flash your device again. I'd also try to unlock your device bootloader if possible (though if your OEM unlocking is off, that's not possible until you can boot). If your device is still unable to boot and you cannot flash your device or cannot get a flash to work, there may be a more serious hardware/flash memory error on your device.
EDIT - glad to hear you got it fixed, which firmware did you download in the first place?

joshua764 said:
hi, download another firmware stock and flash it fastboot and just start the phone, thank you very much for your time, something is wrong with the firmware
Click to expand...
Click to collapse
great - is your bootloader unlocked?
Thanks @echo92 !!!

Related

Security Warning status fastboot with low battery don't change

Hello everyone !
I have the phone in security warning status, i want to flash the RUU but i have the low battery and it's can't change...
the download mode and the recovery are not work, it's just work the bootloader, i tried the follow batch file in fastboot for 10 hours but nothing:
 @ECHO off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
this compare:
battery-voltage:
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
battery-voltage:
finished. total time: 0.009s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
my phone is UNLOCKED and S-ON, it work only on fastboot (adb is not find my device) this is the detail:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54PYJ03254
all:
finished. total time: 0.133s
any solutions?

Please help phone stuck in fast boot.

LONG STORY SHORT ROOTED MY PHONE HAD A CUSTOM ROM I WANTED A DIFFERENT ROM THE ROM I HAD REPLACED MY TWRP WITH THEIR RECOVERY AND I COULDNT INSTALL THE NEW ROM USING THEIRS SO I FACTORY RESET THE PHONE NOW I I CANT GET OUT OF FAST BOOT EVERYTHING I CLICK JUST SAYS N/A AND PUTS ME IN BOOTLOADER LOGS
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.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' (23420 KB)...
OKAY [ 0.505s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.515s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
cannot load 'recovery.img': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.504s]
booting...
FAILED (remote failure)
finished. total time: 1.251s
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.129s]
finished. total time: 0.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
Formatting is not supported for file system with type 'raw'.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:data: not found
erasing 'data'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
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.016s]
finished. total time: 0.018s
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.140s]
finished. total time: 0.141s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase partition
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
erasing 'partition'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format partition
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
Formatting is not supported for file system with type ''.
C:\Program Files (x86)\Minimal ADB and Fastboot>
IS WHAT I HAVE SO FAR NOTHING WORKS. I SPENT 600 ON THIS PHONE PLEASE SOMEONE HELP!!!!!!!!
First of all, the rom had it's OWN recovery? That is a rom that should not be flashed. It looks like the rom or recovery completely wiped the partitions on your phone. Have you tried getting into download mode?
Your mistake was factory resetting the phone on a custom rom. Don't EVER factory reset unless it is a STOCK based rom and you're doing it through the phones settings or you are doing it through recovery to flash a new rom.
Maybe try using Google's Android SDK? Maybe there is an issue with Minimal ADB.
I'm just trying to list some options.
Download the stock Firmware for your device, extract the files in your adb/fastboot folder.
Download that file https://drive.google.com/open?id=0B134drJ4-Ed0MHQ5aE1wUmp5eFk
and place it in your adb/fastboot folder. Run the batch fail and wait for complete. If that don't work, your partition table is broken.
yea it has its own recovery like it wasn't twrp when I booted in to recovery it just said recovery on top and said apply update and advanced and that's it. it wasn't twrp at all and ill try the listed options obove and update thread thanks you guys I'm a noobie to this
when I click your link it says url invalid
what is that file u linked in because it will not let me go to that url
Do u need stock firmware for US Addison? I had a tough time finding it but have it in my Dropbox if you need it. Along with fastboot TWRP etc. https://www.dropbox.com/sh/ndo7qz1h41rsv8i/AABeNwCnJojSGQuF4REAOCd3a?dl=0
https://drive.google.com/open?id=0B134drJ4-Ed0MHQ5aE1wUmp5eFk
Sorry copied the wrong link. Now it should work.
bro you are a life saver this twrp was exactly what I needed so I could flash twrp and get stock nougat it still tells me just n/a on the boot up but after 5-10 it boots like normal thanks man
That's a batch file to flash a complete stock firmware file. For me works the Link fine.

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

Z play wont charge :(

someone please help me !!! my z play stopped loading after updating to oreo.
bootloader unlocked, twrp, all right. already tried several custom roms, and the ones that charge are the roms 6.0 ... I'm going crazy behind the solution.
Sorry my bad English
xXLuKyXx said:
someone please help me !!! my z play stopped loading after updating to oreo.
bootloader unlocked, twrp, all right. already tried several custom roms, and the ones that charge are the roms 6.0 ... I'm going crazy behind the solution.
Sorry my bad English
Click to expand...
Click to collapse
Look at https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530
You could try to flash rafikowy's oreo stock signed with RSDlite, but if that throws an error, use the "alternative" method with either that rom or a 7.x stock rom, depending on whether your target is 8 or 7.
Do not go back to a 6.x rom!!!!!!!!!!!
Already try, adb gives me an error, but in rsd lite i instal any Stock ROM, but the z play wont charge.... Only charge when i turn off...
xXLuKyXx said:
Already try, adb gives me an error, but in rsd lite i instal any Stock ROM, but the z play wont charge.... Only charge when i turn off...
Click to expand...
Click to collapse
did you follow the instructions of "alternative" exactly - what error did adb give?
what rom did you use?
I use NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Adb give me a error in "write OEM"
And stop in sparsechunk 10
xXLuKyXx said:
I use NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Adb give me a error in "write OEM"
And stop in sparsechunk 10
Click to expand...
Click to collapse
Post the log and I,ll look at it when I get home
Fastboot>fastboot getvar max-sparse-size
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
max-sparse-size: 268435456
finished. total time: 0.172s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.187s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.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' (45 KB)...
OKAY [ 0.062s]
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.172s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootlo
ader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.296s]
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.563s]
finished. total time: 0.875s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
(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' (73864 KB)...
OKAY [ 3.018s]
writing 'modem'...
OKAY [ 0.641s]
finished. total time: 3.674s
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' (2612 KB)...
OKAY [ 0.187s]
writing 'fsg'...
OKAY [ 0.078s]
finished. total time: 0.265s
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 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.721s]
writing 'dsp'...
OKAY [ 0.187s]
finished. total time: 0.908s
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' (2187 KB)...
OKAY [ 0.156s]
writing 'logo'...
OKAY [ 0.079s]
finished. total time: 0.251s
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' (16384 KB)...
OKAY [ 0.813s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.330s]
finished. total time: 1.143s
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' (16484 KB)...
OKAY [ 0.689s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.359s]
finished. total time: 1.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
(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' (254735 KB)...
OKAY [ 10.083s]
writing 'system'...
OKAY [ 1.908s]
finished. total time: 11.991s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
(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' (258160 KB)...
OKAY [ 10.486s]
writing 'system'...
OKAY [ 2.157s]
finished. total time: 12.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
(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' (248442 KB)...
OKAY [ 10.060s]
writing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 11.654s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target didn't report max-download-size
sending 'system' (242885 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.4
target didn't report max-download-size
sending 'system' (259562 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.5
target didn't report max-download-size
sending 'system' (262038 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.6
target didn't report max-download-size
sending 'system' (245956 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.7
target didn't report max-download-size
sending 'system' (262091 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.8
target didn't report max-download-size
sending 'system' (260076 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.9
target didn't report max-download-size
sending 'system' (262142 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.10
target didn't report max-download-size
sending 'system' (261896 KB)...
FAILED (command write failed (No error))
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.11
target didn't report max-download-size
sending 'system' (261778 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.12
target didn't report max-download-size
sending 'system' (257319 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target didn't report max-download-size
sending 'oem' (110454 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
FAILED (command write failed (No error))
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
FAILED (command write failed (No error))
finished. total time: -0.000s
Try a different ROM like the one from here
https://forum.xda-developers.com/mo...m-official-fastboot-stock-oreo-image-t3786537
I try, but my z play still not charge...
But with this ROM, everything sayd okay in adb...
xXLuKyXx said:
I try, but my z play still not charge...
But with this ROM, everything sayd okay in adb...
Click to expand...
Click to collapse
I thought you just gave me a log of where it didn't???
in the link rom that you passed me all the adb commands passed ... everything ok .... when I plugged the cell phone into the charger, it does not show the ray design on the battery indicating that it is charging, but the charge goes up slowly, and It also does not stay off, it keeps restarting ...
I am running rafikowy's stock signed upgraded to June.
power phone off.
Either with wall wart, or plugged in to computer, I get
flash symbol for a few seconds, circle showing (84%) battery status for 10-20 secs - at about 23 seconds it goes to blank..
check your cables/wall warts.

De-Bricking Support and Questions for my XT1789-06

Hi,
I am stuck, and figured I need to ask you guys some questions.
As I have done previously with other phones, I bought a used Moto Z2 Force to fix up. I bought a bricked phone with no hardware problems. The previous user said he updated it in Stock to Android Pie, and after the update the phone wouldnt boot anymore, so he sold it. I figured I would just debrick it and use it with LineageOS.
But I didnt succeed, and dont know what else to try, so Im asking you.
It is a XT-1789-06 bought in Germany.
So: When I start the phone up, it says: "Your device is corrupt. it cant be trusted and will not boot." and that I should turn to the official Motorola unlocking portal.
I did that, followed the instructions, was able to boot into fastboot mode, and got the Code, and with that the one from motorola, but when I try the
Code:
fastboot oem unlock XXXXXXXXXXXXXX
I get the following:
Code:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.008s]
finished. total time: 0.008s
Obviously I cant do that, because the phone wont boot up. But event though it says OKAY, there is no change to the variable: securestate: flashing_locked, and i still cant flash anything, and the startup error remains the same. When I try "fastboot flashing unlock" I get the same message.
So, the next thing I tried was the LMSA software. It did the Flash-> rescue-> choose model XT1789-06 -> and flash, and it downloaded the NASH_PPX29.159_23_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip ROM, and apparently did something to the phone, but it didnt change the outcome, still the phone shows the same error on bootup.
Then I did a fastboot -w, after which the phone didnt show anything anymore on bootup, just blank screen, and the tried both steps described above again, stil no change.
Then I tried to boot into the newest Twrp image with "fastboot boot twrp.....img" but it fails with the error: too many links.
Then I tried all of the above in Ubuntu, then on windows with the fastboot files given in the guide in this forum, and then with the mfastboot, that I found somewhere else. Same outcome.
Then I tried just flashing the Stockrom that LMSA downloaded with the flashall method from the same guide, but flashing fails with: Permission denied.
So, do you have any ideas what more I can try to unbrick this phone? I will be happy to give you any further information. I will append fastboot getvar all as soon as I reboot my PC in 2 min.
Edit:
Code:
F:\motoz2force>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4120
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NE
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 1
all: listed above
finished. total time: 0.177s
Edit 2: While I can boot into fastboot mode, when I try to start recovery mode from there, I get the same "Your device is corrupt", so no adb for me.
Edit3:
"fastboot -w" results in:
Code:
F:\motoz2force>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s
It's odd that it says 'a' is unbootable, most updates and roms usually go to 'b' so if there was trouble I'd expect it to be on 'b' slot.. Anyways, it's possible that the chain of trust is corrupt and you can try to blankflash to remedy that and hopefully be able to flash (even with a locked bootloader). You can follow this guide to try and blankflash, if successful then you can try to flash your firmware again. *Note - with a locked bootloader you can only flash the same firmware or newer, that means you should try the one that was downloaded by lmsa. Also, look by your charger port to verify that it is indeed an -06 variant and not just saying -06 because that was what was flashed.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
If no success all around, you can try switching slots and making 'a' the active slot. Once it is active, try to boot it and see if it will, if not, try flashing the firmware you have on that slot.
Thank you for your help. Unfortunatley it didnt get me very far. I installed the drivers on my Vista-PC. When I executed the blank-flash.bat It just said <waiting for device>. Then I removed Motorola and te qualcomm drivers, rebooted, installed the qualcomm-drivers again, rebooted, but then in the device manager the phone just showed up as "Fastboot nash S" without proper drivers. I couldnt get the qualcomm drivers to recognize the device. blank-flash.bat still showed the same thing.
Other ports, same behaviour.
Then I reinstalled moto drivers to test the other commands.
When I tried "fastboot oem blankflash" I got:
Code:
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Then I tried
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.008s
I checked next to the charging port, it is really a XT1789-06.
Stuck again. Any other pointers? that would be so great. thanks in advance. I am still learning a lot here, even without progress.
I'm in the same situation, but with an xt1789-05, but it turns on normal, but I don't have Wi-Fi and no data network, and I've tried everything to remove the OEM lock, but without success, and whenever I try a ROM new, it gives me bootloader failure or error.
I'm sure your command to set the other slot is wrong fastboot --set-active=a
As for the blankflash, you need to be in edl mode which isn't always the easiest to get into manually and it's even harder when your system is jumbled. (You think it would be easier since that's when you need it). Either way, that's why blankflash isn't running.
When I wanted to get into edl mode I was holding volume up+power while connecting USB to PC.
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
You should try running the lmsa tool again. Were you ever successful in switching slots? If you're unsure of the syntax, type fastboot --help that should show you the proper way. Blankflash should be your last option.
wolzotan said:
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
Click to expand...
Click to collapse
Hi There I have same situation as you, did you fix your phone?
and how you fixed your phone?
I have XT1789-05, please help me, thanks a lot
hi AHMN48, i saw your posts around and figured you have the same problem. I have not yet found a solution unfortunately.
I have tried some more suggestions made here:
Code:
F:\motoz2force>fastboot --set_active=_a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot reboot emergency
rebooting into emergency download (EDL) mode...
OKAY [ 0.000s]
finished. total time: 0.000s
I got really excited when that happened, but it just came up in fastboot mode again.
this is my screen, if it helps anything
and I tried those commands on all of my usb ports, and most of the ports on my docking station. Its a Lenovo W520, and I have windows 7 and Ubuntu 18.04 available.
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
wolzotan said:
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
Click to expand...
Click to collapse
RSD is a bit antiquated and we use a flashall.bat in the command prompt to do the same thing. In your OP you posted your getvar output and it looks like it still has oreo on it. Whether lmsa has actually done anything and flashed pie, it would appear not according to you. Run fastboot getvar all again and look at your build fingerprint, if it is still oreo 8.0 then lets try flashing the last oreo version instead of trying to jump to pie.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ok. Thanks so much 41rw4lk, for walking me through this. Still no luck unfortunately.
I ran the following commands on a new laptop, new windows 10, that I hadnt tried before. However the outcome was identical, as far as i see.
I did download the firmware you linked. I ran the preparation.bat, and then the flashfile.bat. this is the log. It shows the same error messages, that I got with the Pie firmware.
Code:
max-sparse-size: 268435456
finished. total time: 0.000s
...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.234s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.656s
target reported max download size of 536870912 bytes
sending 'modem_a' (97411 KB)...
OKAY [ 6.896s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.896s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.297s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.312s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.219s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.828s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.844s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.172s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.187s
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB)...
OKAY [ 1.172s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.172s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 30.593s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 30.608s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 26.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 26.233s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 25.927s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 25.927s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 126.811s
target didn't report max-download-size
sending 'system' (523200 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'system' (413555 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (515182 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (319593 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'oem' (163061 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'ddr'...
FAILED (command write failed (No error))
finished. total time: 0.000s
target didn't report max-download-size
sending 'fsg' (5600 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.270s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.290s
...
OKAY [ -0.000s]
finished. total time: -0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
And then a current flashboot getvar all:
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3922
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.147s
It seems at some point some command was successful in switching the slots. Strange... I am really fishing in the dark here.
Still the Phone says: Device corrupted, and to unlock the bootloader, and when I try t unlock the bootloader in fastboot, it still tells me to check "OEM Unlocking" in the developer options.
You won't be able to unlock the bootloader until you're able to boot, sign in, and enable oem unlocking in dev options. Since it changed a few things around, try running the lmsa tool again.
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
wolzotan said:
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
Click to expand...
Click to collapse
Make sure you're running lmsa and such as an admin, some users depending on their pc have had to pay attention to this, while most don't.
Yeah I did that.

Categories

Resources