[SOLVED] [Q] oops! soft bricked .....

[SOLVED] [Q] oops! soft bricked ..... - T-Mobile HTC One (M7)

M7 was badly misbehaving. Couldn't install apps from the drawer (to the home page) or from the home page directly. I get the vibration feedback and that's it.
There have been other issues as well.
I'd been on the OTA 4.4.3, but some app must have poisoned the phone.
In any case formatted data and wiped caches.
Have TWRP 2.8.02 installed. Unlocked and rooted.
I can get to TWRP or Fastboot with no issues.
But Sideload, push nor fastboot will take my OTArom.zip.
Tried dropping back to TWRP 2.7.11 after reading about some issues. No difference.
FAILED (remote: 24 parsing android-info fail) was the error from Fastboot flash zip rom.zip
sideload seemed to pass the rom but got "error updating executer binary" a couple secs after the sideload is done.
I'd rather install OEM instead of a TWRP back-up that is loaded with apps that might have caused the issues. But so far ......
When I try to copy a TWRP back up (via MTP), TWRP replies "can't copy - data.ext4.win000"
I'm on a Mac so I can't run .exe.
HELP!!
thanks.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##########
(bootloader) imei: #############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

metropical said:
M7 was badly misbehaving. Couldn't install apps from the drawer (to the home page) or from the home page directly. I get the vibration feedback and that's it.
There have been other issues as well.
I'd been on the OTA 4.4.3, but some app must have poisoned the phone.
In any case formatted data and wiped caches.
Have TWRP 2.8.02 installed. Unlocked and rooted.
I can get to TWRP or Fastboot with no issues.
But Sideload, push nor fastboot will take my OTArom.zip.
FAILED (remote: 24 parsing android-info fail) was the error from Fastboot flash zip rom.zip
sideload seemed to pass the rom but got "error updating executer binary" a couple secs after the sideload is done.
I'd rather install OEM instead of a TWRP back-up that is loaded with apps that might have caused the issues. But so far ......
When I try to copy a TWRP back up (via MTP), TWRP replies "can't copy - data.ext4.win000"
I'm on a Mac so I can't run .exe.
thanks.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##########
(bootloader) imei: #############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since you are S-OFF try this RUU_M7UL_TMOUS_5.14.531.1_With_Partial-decrypted.zip

majmoz said:
Since you are S-OFF try this RUU_M7UL_TMOUS_5.14.531.1_With_Partial-decrypted.zip
Click to expand...
Click to collapse
thanks. from adb I assume?

metropical said:
thanks. from adb I assume?
Click to expand...
Click to collapse
No, you will flash it like firmware in fastboot. Rename your file to RUU.zip or substitute RUU.zip with your file name.
Put the phone in bootloader/FASTBOOT USB
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip RUU.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip RUU.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

majmoz said:
No, you will flash it like firmware in fastboot. Rename your file to RUU.zip or substitute RUU.zip with your file name.
Click to expand...
Click to collapse
Martin:android fritz$ fastboot flash zip RUU.zip
sending 'zip' (1567273 KB)...
FAILED (remote: 02 data length is too large)

metropical said:
Martin:android fritz$ fastboot flash zip RUU.zip
sending 'zip' (1567273 KB)...
FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
Have you tried the method nkk71 discussed in FAQ #3?
I don't use a Mac so I can not help you there.

majmoz said:
Have you tried the method nkk71 discussed in FAQ #3?
I don't use a Mac so I can not help you there.
Click to expand...
Click to collapse
yup. no difference

metropical said:
yup. no difference
Click to expand...
Click to collapse
Here is another zip 6.10.531.9 you can try. It might be closer to your system setup since it is for the version just prior to the latest from TMOUS. I looked for a firmware only package but I could not find one.
Make sure you check the MD5 of the files!!!

majmoz said:
Here is another zip 6.10.531.9 you can try. It might be closer to your system setup since it is for the version just prior to the latest from TMOUS. I looked for a firmware only package but I could not find one.
Make sure you check the MD5 of the files!!!
Click to expand...
Click to collapse
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.

metropical said:
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.
Click to expand...
Click to collapse
Try each of the following steps until successful:
If possible, copy your personal files and data off of the phone.
You can pull the recovery.img from the zip and flash it. It is the stock image.
In bootloader, select factory reset
You might be able to build your own firmware by removing the system.img from the zip. You can rename it firmware and flash like the RUU.

metropical said:
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.
Click to expand...
Click to collapse
Use this and update your fastboot / adb
http://forum.xda-developers.com/showthread.php?t=2588979

clsA said:
Use this and update your fastboot / adb
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
appreciate the input, but that's windows. I'm on a Mac. My adb is 1.0.31

metropical said:
appreciate the input, but that's windows. I'm on a Mac. My adb is 1.0.31
Click to expand...
Click to collapse
their old, find new download the SDK

majmoz said:
Try each of the following steps until successful:
If possible, copy your personal files and data off of the phone.
You can pull the recovery.img from the zip and flash it. It is the stock image.
In bootloader, select factory reset
You might be able to build your own firmware by removing the system.img from the zip. You can rename it firmware and flash like the RUU.
Click to expand...
Click to collapse
I have all my files.
when I unzip, I don't see recovery.img or system.zip.
might be the Mac vs Windows.
The phone has no OS right now.

metropical said:
I have all my files.
when I unzip, I don't see recovery.img or system.zip.
might be the Mac vs Windows.
The phone has no OS right now.
Click to expand...
Click to collapse
https://github.com/corbindavenport/nexus-tools
bin updated adb binary to 1.0.32, Dec 16, 2014
README.md Dec 16, 2014
install.sh Dec 16, 2014
license.txt Dec 10, 2013
Click to expand...
Click to collapse

clsA said:
https://github.com/corbindavenport/nexus-tools
Click to expand...
Click to collapse
cool.! nice tool. thanks. hope this fixes my issues.

metropical said:
cool.! nice tool. thanks. hope this fixes my issues.
Click to expand...
Click to collapse
Yeah I have only seen the FAILED (remote: 02 data length is too large) when fastboot was too old
good luck

clsA said:
Yeah I have only seen the FAILED (remote: 02 data length is too large) when fastboot was too old
good luck
Click to expand...
Click to collapse
Darn the Luck ! ! !
No green progress bar.
I tried the RUU linked on the previous page as well as this OTA of the same vintage.
after the following failure, I formatted data and attempted to wipe Dalvik and cache. I get "unable to mount cache".
Martin:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:~ fritz$ fastboot flash zip OTA_M7.zip
error: cannot load 'OTA_M7.zip'
Martin:~ fritz$ cd downloads/android
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.195s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.222s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.187s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.219s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.559s]
finished. total time: 0.559s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Martin:android fritz$ adb devices
List of devices attached
FA35########### device
Martin:android fritz$ adb reboot recovery
Martin:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.216s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.226s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.212s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.244s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.522s]
finished. total time: 0.522s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s

metropical said:
Darn the Luck ! ! !
No green progress bar.
I tried the RUU linked on the previous page as well as this OTA of the same vintage.
after the following failure, I formatted data and attempted to wipe Dalvik and cache. I get "unable to mount cache".
Martin:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:~ fritz$ fastboot flash zip OTA_M7.zip
error: cannot load 'OTA_M7.zip'
Martin:~ fritz$ cd downloads/android
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.195s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.222s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.187s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.219s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.559s]
finished. total time: 0.559s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Martin:android fritz$ adb devices
List of devices attached
FA35########### device
Martin:android fritz$ adb reboot recovery
Martin:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.216s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.226s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.212s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.244s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.522s]
finished. total time: 0.522s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Click to expand...
Click to collapse
That OTA.zip can only be flashed with stock recovery .. it's not a RUU or Rom.zip
you get unable to mount cache because you formatted it
fastboot erase cache causes this error

clsA said:
That OTA.zip can only be flashed with stock recovery .. it's not a RUU or Rom.zip
you get unable to mount cache because you formatted it
fastboot erase cache causes this error
Click to expand...
Click to collapse
how can I get back to stock recovery? I assume with the soft brick and other tries that haven't worked that is the only choice at this point?
do I need to OEM lock or ..........?
and getvar seems to indicate that there is no firmware version now.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##YW######
(bootloader) imei: ############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4326mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Related

Why am I not getting the final unlock bootloader screen?

I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>

See the guide/flashing notes in my signature. It'll straighten you out. Stuck at step 13right?

Redownload the bin file, if you noticed it cought it being 0kb of size.
Also ensure that the phone is seen correctly under windows.
Sent from my PG86100 using Tapatalk

That happened to me the bootloader unlock option did not want to come .. i am sure your number software ends with 3 . Or higher what i did i ran the 2.17.651.2 ruu shotter and after that i had no problems . If you run the ruu.shotter you will lose all your data.
Sent from my HTC.EVO.3D.Xda Premium

Amy luck
Sent from my HTC.EVO.3D.Xda Premium

Any luck?
Sent from my HTC.EVO.3D.Xda Premium

darkstar765 said:
I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
Click to expand...
Click to collapse
Download and run The 2.08 RUU Then Use the htc Unlock I had the same problem today this works

Help with S-Off

Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy

albernhagen said:
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
Click to expand...
Click to collapse
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.

Thanks
Thanks for your response, BoogaBooga. I tried this out, but it seems that I'm out of luck because I'm relocked as opposed to unlocked. Here's what I saw when attempting FacePalm:
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip dna2.06firmware.zip
< waiting for device >
sending 'zip' (33119 KB)...
OKAY [ 2.411s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,52
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,90
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,51
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,48
(bootloader) [RUU]UZ,recovery,74
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 17.400s]
finished. total time: 19.810s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fasboot flash zip PL8320000-DNA.zip
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.814s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot boot DNA-rescue.img
downloading 'boot.img'...
OKAY [ 0.813s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>^A
BoogaBooga said:
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Click to expand...
Click to collapse

After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.

BoogaBooga said:
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
Click to expand...
Click to collapse
Since I bought the phone already unlocked, I never had the old unlock key. I suppose I can contact the guy I bought it from and see if he still has it. Any other ideas in the meantime?

I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862

BoogaBooga said:
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
Click to expand...
Click to collapse
I received help from Beaups and got things working. It was a problem with my supercid. We did basically what happens in post #5 here:
http://forum.xda-developers.com/showthread.php?t=2407640
Thanks!

(bootloader) slot count not found

I encountered a weird problem today, while i was flashing on my XT1022 stock rom 4.4.4 on unlocked bootloader (previously also having 4.4.4), i faced some weird problems,
though the flashing was successful and moto e booted up, i wanted to ask just in case if this is something to worry about pls tell soon as i will update my phone to 5.1 lollipop using official OTA, just in case if i encounter an error-
This is one component of the flashing stock. Each had this thing- (bootloader) slot......
And this: (bootloader) has-slot: recovery not found (an example)
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 299892736 bytes
sending 'logo' (460 KB)...
OKAY [ 0.099s]
writing 'logo'...
OKAY [ 0.154s]
finished. total time: 0.256s
Pls tell what is this as I'm going to update to 5.1 with OTA and I don't want to end up damaging my phone

ayushg1214 said:
I encountered a weird problem today, while i was flashing on my XT1022 stock rom 4.4.4 on unlocked bootloader (previously also having 4.4.4), i faced some weird problems,
though the flashing was successful and moto e booted up, i wanted to ask just in case if this is something to worry about pls tell soon as i will update my phone to 5.1 lollipop using official OTA, just in case if i encounter an error-
This is one component of the flashing stock. Each had this thing- (bootloader) slot......
And this: (bootloader) has-slot: recovery not found (an example)
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 299892736 bytes
sending 'logo' (460 KB)...
OKAY [ 0.099s]
writing 'logo'...
OKAY [ 0.154s]
finished. total time: 0.256s
Pls tell what is this as I'm going to update to 5.1 with OTA and I don't want to end up damaging my phone
Click to expand...
Click to collapse
Using latest adb fastboot throws these four lines but will flash success no problem with that

Rajendran Rasa said:
Using latest adb fastboot throws these four lines but will flash success no problem with that
Click to expand...
Click to collapse
Which version of minimal adb and fastboot will you recommend me so as to not see them?

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.013s]
finished. total time: 0.013s
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' (2192 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 0.104s]
finished. total time: 0.178s
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.522s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.710s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 10.228s]
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: 22.612s
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' (524260 KB)...
OKAY [ 21.521s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 21.638s
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' (522314 KB)...
OKAY [ 21.167s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 21.191s
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' (522269 KB)...
OKAY [ 23.148s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 23.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
(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' (524204 KB)...
OKAY [ 21.778s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 21.800s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.4
(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' (524139 KB)...
OKAY [ 24.183s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.235s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.5
(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' (435100 KB)...
OKAY [ 19.291s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.320s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
error: cannot load 'system.img_sparsechunk.6': No such file or directory
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.507s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.695s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.006s]
finished. total time: 0.007s
tried both rom dec and feb update with latest adb and moto device manager but bad luck

slot count not found
hi my phone also stuck on same after flashing oreo update and phone stucked in boot loop have tried 3 different roms i am getting same error but firmware has stil been updated and be to flash twrp trying twrp rom now to get signal back and fix this

Hi i have installed a custom rom on my moto x play few mount ago, but have got some bugs so i came back to the stock rom and the bootloader was unlock so i want to lock the bootloader by the adb tool but i couldn't lock the bootloader i was getting this time of error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.029s]
finished. total time: 0.030s
can anyone help me with this

Find the motorola fastboot file called mfastboot and use that instead of normal fastboot.

putting custom rom on moto-z play

I have got an unlock code for my phone. I run the command to unlock it and get the following:
[email protected]:/mnt/hgfs/vmshare# fastboot oem unlock < real code here >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.007s]
finished. total time: 0.007s
[email protected]:/mnt/hgfs/vmshare#
I did unlock it before, but was having problems install twrp:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery /mnt/hgfs/vmshare/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' (23452 KB)...
OKAY [ 1.630s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.635s
[email protected]:/mnt/hgfs/vmshare#
so I went back and tried to unlock it.
any help is appreciated
Y-
Follow-up. When I did a 'fastboot boot twrp-3.1..-addison.img' it booted on the phone. When I did a 'fastboot boot twrp-3.1...griffin.img' it just stuck at the boot screen. So is the moto-z addison or griffin build?
Also is there a way to use 'fastboot boot twrp-3.1...addison.img' to permanently put twrp on the phone?
I tried:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery twrp-3.1.1-1-addison.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' (11396 KB)...
OKAY [ 0.792s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.251s]
finished. total time: 1.043s
[email protected]:/mnt/hgfs/vmshare
and it failed.
Y-

You are wrong here. Z Play is here: https://forum.xda-developers.com/moto-z-play
And Z Play is addison, standard Moto Z is griffin. Than if you have Play, you have addison.

[Help] Bootloop after trying to install LineageOS.

Hi xda-developers, how is it going? For me, not good news...
Ok, let me explain. I tried to install LineageOS on my Moto Z (XT-1650-03) with not the expected results. The phone got stucked on the unlocked bootloader message. Ok, I tried to install the stock rom (obtained from: lolinet.com mirrors, griffin/RETEU) and it didn't work. When I turned on the phone, the classic message "no command" was displayed on the screen. After, I tried to convert flashfile.xml to shell script (using motoflash2sh by dlenski on GitHub), and now my phone is on bootloop.
I tried to blank flash with the tool provided by lolinet, but qboot cannot detect my device (but fastboot can).
// First attempt ("no command" message)
Code:
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
// Second attempt (bootloop)
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
// fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223HPT7F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: BDB29AD600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358180070393267
(bootloader) meid:
(bootloader) date: 08-28-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:29:33 UTC 1970"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.HB.1.3.2-15400-8x96.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.24-perf-g03414fd-0000
(bootloader) kernel.version[1]: 2-g9465f65 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x-google 20140827 (prerelease)
(bootloader) kernel.version[3]: (GCC) ) #1 SMP PREEMPT Fri Jul 22 05:40:
(bootloader) kernel.version[4]: 29 CDT 2016
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=5b45243-dirty
(bootloader) hyp.git: git=5b45243-dirty
(bootloader) devcfg.git: git=5b45243-dirty
(bootloader) keymaster.git: git=5b45243-dirty
(bootloader) cmnlib.git: git=5b45243-dirty
(bootloader) cmnlib64.git: git=5b45243-dirty
(bootloader) prov.git: git=5b45243-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
Finished. Total time: 0.156s
I can reboot into fastboot, also I can boot TWRP with fastboot.
Even I tried to wipe all data (factory reset), but the recovery (stock) cannot wipe /cache because it doesn't exist.
EDIT: When I press Reboot to Recovery or Bootloader on TWRP, a message (in blue) appears: "No OS Installed! Are you sure you wish to reboot?"
Any ideas? Thanks in advance!
Best regards.

rodrigolopez0551 said:
Hi xda-developers, how is it going? For me, not good news...
Ok, let me explain. I tried to install LineageOS on my Moto Z (XT-1650-03) with not the expected results. The phone got stucked on the unlocked bootloader message. Ok, I tried to install the stock rom (obtained from: lolinet.com mirrors, griffin/RETEU) and it didn't work. When I turned on the phone, the classic message "no command" was displayed on the screen. After, I tried to convert flashfile.xml to shell script (using motoflash2sh by dlenski on GitHub), and now my phone is on bootloop.
I tried to blank flash with the tool provided by lolinet, but qboot cannot detect my device (but fastboot can).
// First attempt ("no command" message)
// Second attempt (bootloop)
// fastboot getvar all
I can reboot into fastboot, also I can boot TWRP with fastboot.
Even I tried to wipe all data (factory reset), but the recovery (stock) cannot wipe /cache because it doesn't exist.
EDIT: When I press Reboot to Recovery or Bootloader on TWRP, a message (in blue) appears: "No OS Installed! Are you sure you wish to reboot?"
Any ideas? Thanks in advance!
Best regards.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my perry_f using XDA Labs

sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
I see in the post's comments that Moto Z XT1650 is unsupported. Should I try anyway?
EDIT: It doesn't recognise my device (I think it's because I sideloaded the LineageOS zip).
EDIT2: Output of my attempt to flash.
Code:
max-sparse-size: 268435456
Finished. Total time: 0.004s
OKAY [ 0.001s]
Finished. Total time: 0.005s
(bootloader) has-slot:partition: not found
(bootloader) is-logical:partition: not found
Sending 'partition' (142 KB) OKAY [ 0.053s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
< waiting for any device >
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7076 KB) OKAY [ 0.287s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image rpm failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image pmic failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (80886 KB) OKAY [ 2.426s]
Writing 'modem' OKAY [ 1.076s]
Finished. Total time: 3.613s
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2356 KB) OKAY [ 0.119s]
Writing 'fsg' OKAY [ 0.361s]
Finished. Total time: 0.546s
(bootloader) has-slot:bluetooth: not found
(bootloader) is-logical:bluetooth: not found
Sending 'bluetooth' (4296 KB) OKAY [ 0.174s]
Writing 'bluetooth' OKAY [ 0.418s]
Finished. Total time: 0.660s
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.529s]
Writing 'dsp' OKAY [ 0.450s]
Finished. Total time: 1.044s
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (2933 KB) OKAY [ 0.135s]
Writing 'logo' OKAY [ 0.361s]
Finished. Total time: 0.562s
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (32768 KB) OKAY [ 1.052s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.550s]
Finished. Total time: 1.667s
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (32772 KB) OKAY [ 1.044s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.551s]
Finished. Total time: 1.658s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 7.702s]
Writing 'system' OKAY [ 2.725s]
Finished. Total time: 10.703s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (245512 KB) OKAY [ 7.279s]
Writing 'system' OKAY [ 1.805s]
Finished. Total time: 9.317s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (256002 KB) OKAY [ 7.495s]
Writing 'system' OKAY [ 1.784s]
Finished. Total time: 9.522s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (242073 KB) OKAY [ 7.115s]
Writing 'system' OKAY [ 1.864s]
Finished. Total time: 9.203s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (256909 KB) OKAY [ 7.594s]
Writing 'system' OKAY [ 1.751s]
Finished. Total time: 9.565s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261011 KB) OKAY [ 7.718s]
Writing 'system' OKAY [ 1.840s]
Finished. Total time: 9.788s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 7.797s]
Writing 'system' OKAY [ 2.134s]
Finished. Total time: 10.569s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 7.779s]
Writing 'system' OKAY [ 1.908s]
Finished. Total time: 9.966s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (254656 KB) OKAY [ 7.553s]
Writing 'system' OKAY [ 1.650s]
Finished. Total time: 9.527s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262143 KB) OKAY [ 7.811s]
Writing 'system' OKAY [ 1.866s]
Finished. Total time: 9.967s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261022 KB) OKAY [ 7.914s]
Writing 'system' OKAY [ 2.006s]
Finished. Total time: 10.157s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261217 KB) OKAY [ 7.855s]
Writing 'system' OKAY [ 1.787s]
Finished. Total time: 10.023s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (253734 KB) OKAY [ 7.516s]
Writing 'system' OKAY [ 1.813s]
Finished. Total time: 9.564s
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (63148 KB) OKAY [ 1.912s]
Writing 'system' OKAY [ 0.420s]
Finished. Total time: 2.402s
(bootloader) has-slot:oem: not found
(bootloader) is-logical:oem: not found
Sending 'oem' (70336 KB) OKAY [ 2.115s]
Writing 'oem' OKAY [ 0.820s]
Finished. Total time: 3.008s
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.164s]
Finished. Total time: 0.224s
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.172s]
Finished. Total time: 0.233s
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.354s]
Finished. Total time: 0.416s
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 1.974s]
Finished. Total time: 2.037s
(bootloader) has-slot:customize: not found
Erasing 'customize' OKAY [ 0.335s]
Finished. Total time: 0.398s
(bootloader) has-slot:clogo: not found
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) has-slot:ddr: not found
Erasing 'ddr' OKAY [ 0.283s]
Finished. Total time: 0.342s
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2356 KB) OKAY [ 0.120s]
Writing 'fsg' OKAY [ 0.352s]
Finished. Total time: 0.535s
(bootloader) has-slot:bluetooth: not found
(bootloader) is-logical:bluetooth: not found
Sending 'bluetooth' (4296 KB) OKAY [ 0.175s]
Writing 'bluetooth' OKAY [ 0.411s]
Finished. Total time: 0.650s
OKAY [ 0.001s]
Finished. Total time: 0.004s
EDIT3: Finally managed to get my device working again.
I followed this: https://forum.xda-developers.com/showpost.php?p=76932000&postcount=104
Is there anyway to check the legitimate of that ROM?
EDIT4: I downloaded the original stock rom from LMSA (because my phone now has a valid rom, the LMSA can detect my phone correctly).
Thanks.

Better Mobile App

welcome