Develop Bugs

Endless bootloop. Can't get into recovery even with fastboot commands

Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.

kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.

When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.

TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.

kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?

TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s

kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?

Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere

kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.

TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.

Download stock firmware with Lenovo Moto Smart Assistant

Hi all. Many people are asking for latest stock firmware for their devices. For those of you who don't know, there is a tool called Lenovo Moto Smart Assitant, which allows you to download and install latest stock firmware. I'm not sure if latest oreo firmwares are also available, but I have downloaded 137-93-14 stock firmware for my reteu XT1685. Other devices are also supported under Flash->Rescue option.
This tool has other simple utilities which may be helpful for less advanced users.
Regards.

Holy smokes this actually works! The time of waiting for leaked firmwares is finally over. Lemotonovo doing things right lately.
Besides the firmware part, this app has some useful tools too.

Does it format internal storage?
UPDATE: Actually, it does and before installation it informs you about the wipe. So it is a no go for me at the moment. However, as long as installing Oreo is possible through an official application, I guess that OTA update on reteu is on its way.

lm_1970 said:
Hi all. Many people are asking for latest stock firmware for their devices. For those of you who don't know, there is a tool called Lenovo Moto Smart Assitant, which allows you to download and install latest stock firmware.
Click to expand...
Click to collapse
talking about this tool? https://support.lenovo.com/nl/nl/downloads/ds101291

​
Jimisballjohn said:
Does it format internal storage?
UPDATE: Actually, it does and before installation it informs you about the wipe. So it is a no go for me at the moment. However, as long as installing Oreo is possible through an official application, I guess that OTA update on reteu is on its way.
Click to expand...
Click to collapse
There are two features in this tool: one is rescue (which formats internal storage) and the other one is upgrade (which I haven't tested but I guess it doesn't format it). Both options are available in the flash menu.
As I understand, in order to be able to upgrade to Oreo with this tool and without losing information, you have to be in stock Nougat, and the upgrade OTA to Oreo should be available for your software channel (as of today it is not the case for most channels).
Regards.

Can i use this while currently on custom 8.1 rom?

ashu.mkb said:
Can i use this while currently on custom 8.1 rom?
Click to expand...
Click to collapse
I believe you need to be on stock recovery.

rjherms said:
I believe you need to be on stock recovery.
Click to expand...
Click to collapse
The "recover" option for a clean flash uses fastboot. That one should remain functional, and this might be the best/easiest way to go back to stock atm.

bazinga137 said:
The "recover" option for a clean flash uses fastboot. That one should remain functional, and this might be the best/easiest way to go back to stock atm.
Click to expand...
Click to collapse
As long as the recover option chooses an Oreo firmware. If it chooses a nougat firmware, then most likely they'll end up with IMEI 0, as the persist fix would need to be applied separately.

Will using rescue return the phone back to stock with locked bootloader??

I had given this a try a few day's ago. It went through the process but the fastboot (boot loop) was still in effect. I doubt anyone offhand would know why it didn't take the rescue? I'm not at home w/ details but everything Ive tried gives me the "downgrade failure" upon flashing. My phone is Amazon XT1687 on 137-93-16 (which is the one the tool downloads and rescues with even the AMZ.137-93-16.img) but its still stuck in fastboot I will probably have to wait for the official 8.1 flashboot file or the 137-93-18 to get out of this jam? I have tried everything, phone has everything intact i.e. IMEI just wont take the flash even at same version so hopefully something 'higher' might work. I'm glad it worked for some of you who might have been waiting longer then me. I managed to bootloop two of these phones in a week ....If anyone thinks they can help I will deff have more details when I'm at my computer =)

oops Im on the .14 not the .16... Lenovo app gives me 137.93.16 but still wont take it. Im looking for anyone who can take a look below and maybe tell me why? I did flash the oreo w/ fastboot method which started all of this, but apparently that didnt take...just soft bricked me =(
thanks guys;
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224TWP8T
(bootloader) cid: 0x0012
(bootloader) channelid: 0x93
(bootloader) uid: 63B7C3BD00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 351856047122180
(bootloader) meid:
(bootloader) date: 03-02-2018
(bootloader) sku: XT1687
(bootloader) battid: SNN5982A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 12:12:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_amz/potter:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-93-14/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.341.14.potter_amz
(bootloader) ro.build.version.full[1]: .amz.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47.01R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gf055b2e-0010
(bootloader) kernel.version[1]: 7-gdc6d2c1 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 30 14:17:37 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC1.07-0-g3b15bb0
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=283f623
(bootloader) devcfg.git: git=283f623
(bootloader) keymaster.git: git=283f623
(bootloader) cmnlib.git: git=283f623
(bootloader) cmnlib64.git: git=283f623
(bootloader) prov.git: git=283f623
(bootloader) aboot.git: git=MBM-NG-VC1.07-0-g9d7f987
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: amz
all: listed above
finished. total time: 0.062s

volcomguyaz said:
I had given this a try a few day's ago. It went through the process but the fastboot (boot loop) was still in effect. I doubt anyone offhand would know why it didn't take the rescue? I'm not at home w/ details but everything Ive tried gives me the "downgrade failure" upon flashing. My phone is Amazon XT1687 on 137-93-16 (which is the one the tool downloads and rescues with even the AMZ.137-93-16.img) but its still stuck in fastboot I will probably have to wait for the official 8.1 flashboot file or the 137-93-18 to get out of this jam? I have tried everything, phone has everything intact i.e. IMEI just wont take the flash even at same version so hopefully something 'higher' might work. I'm glad it worked for some of you who might have been waiting longer then me. I managed to bootloop two of these phones in a week ....If anyone thinks they can help I will deff have more details when I'm at my computer =)
Click to expand...
Click to collapse
Sounds like you need to enter command
fastboot oem fb_mode_clear
To get it to boot normally.

Deff appreciate you taking the time =) honestly I tried probably 99/100 things and I don't have the brain power to figure what the ONE combination is I haven't tried. Bought two of these this past week luckily off offerup- that are more then likely shot. I get complacent with and in between make\models too easily - each phone has its own specific process - my own fault! (the second one really sting's cause I mistakenly forgot to switch it off the cable and fast booted that bad boy like the first one) not something I like to admit from one senior member to another but hey let it be an example for anyone else- it can go sideways real quick with that FB.exe
Maybe if anyone else stops by, is it because they are the Amazon Prime (unlocking bootloader was never an option which means no TWRP which meansss I should have never attempted to flash these devices? ) Is there any hope with an official flash at some point that would bring them back?

It says unsupported device on mine. I'm using an XT1685 retapac, which got the OPS28.85-13 just a few days ago.

ansarips said:
It says unsupported device on mine. I'm using an XT1685 retapac, which got the OPS28.85-13 just a few days ago.
Click to expand...
Click to collapse
Mine is also XT1685. It was supported by the tool while I was on Nougat (137-93-14). Since I upgraded to oreo (leaked OTA install) it is no longer supported. It seems that newer firmware versions are not supported until they are publicly available.
Regards.

Does this work on Rooted device?

goodjuju said:
Does this work on Rooted device?
Click to expand...
Click to collapse
You will never be able to update a rooted device.
You have to be on full and untouched stock, bootloader state doesn't matter.
Sent from my Moto G5 Plus using XDA Labs

goodjuju said:
Does this work on Rooted device?
Click to expand...
Click to collapse
Only if you have no other choices to go back to stock Nougat, and you haven't been playing with oreo non-stock firmwares, I would give a try to the rescue option. This option erases all user data.

I have retus x1787, also says unsupported device was on April security patch, said unsupported. Then I went to June and August security patch and still getting unsupported. I have unlocked bootloader but stock. I wanted to relocked to see if it can be supported, but I can't relock it. Because I can't find the whole stock rom for August which is 137-93-18. Did it work with unlocked bootloader?
Sent from my Pixel 2 XL using Tapatalk

Help with factory resetting Moto g5

I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.

shAen123 said:
I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.
Click to expand...
Click to collapse
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP https://androidfilehost.com/?fid=673956719939821589, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip: https://androidfilehost.com/?fid=3700668719832240875

Andrej_SK said:
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip:
Click to expand...
Click to collapse
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
EDIT#1: Never mind, i got into adb, i just forgot that you had to do the command window thing.
EDIT#2: I did the command and it sits at waiting for device. It wont go past that, I think i should install moto drivers because i reset my pc which got rid of them. Ill update once done.

shAen123 said:
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
Click to expand...
Click to collapse
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
EDIT: Remember that while the phone is in the bootloader menu, the main word of the each command is "fastboot" (e.g. "fastboot flash...", "fastboot boot..."), not "adb".

Andrej_SK said:
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
Click to expand...
Click to collapse
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)

shAen123 said:
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)
Click to expand...
Click to collapse
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Btw, sorry for my mistake, but even the correct command is "fastboot reboot-bootloader" (missing dash between "reboot" and "bootloader" words), I don't think it's gonna help.

Andrej_SK said:
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Click to expand...
Click to collapse
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Oops, I didnt see the edit in time Ill do that
I think it worked, screen went black, then back into bootloader, adb said okay. Ill try and boot into twrp

shAen123 said:
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Click to expand...
Click to collapse
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), boot into the OS, install TWRP, flash 2 zips (links below) and boot into the OS again.
https://androidfilehost.com/?fid=3700668719832240875 fixes ownership of some persist files and brings IMEI back
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ use the 6.0 version, avoids bootloop on stock ROM

Andrej_SK said:
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), install TWRP and flash 2 zips (links below):
fixes ownership of some persist files and brings IMEI back
use the 6.0 version, avoids bootloop on stock ROM
Click to expand...
Click to collapse
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
(I know how to do things, its just terms I'm not good at)

shAen123 said:
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
Click to expand...
Click to collapse
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now here, in the Slovakia) and send you link for an appropriate version of stock ROM which won't brick your phone.

Andrej_SK said:
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now) and send you link for an appropriate version of stock ROM which won't brick your phone.
Click to expand...
Click to collapse
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help

shAen123 said:
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help
Click to expand...
Click to collapse
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.

Andrej_SK said:
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.
Click to expand...
Click to collapse
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.

Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol

shAen123 said:
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.
Click to expand...
Click to collapse
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
shAen123 said:
Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol
Click to expand...
Click to collapse
So is your problem fully fixed now?

Andrej_SK said:
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
So is your problem fully fixed now?
Click to expand...
Click to collapse
Yes it is, I was able to boot and go through an update to give me the lastest security patch. After some downloading/backup retrieving my phone is working normally and I have my iemi and stuff. I might go and root it again at a later date but for now its going to be completely stock. Sorry for the long wait

Stuck in a kind of bootloops with all stock roms I've tried. help needed

So, long story short, a friend of mine endend up buying a new smartphone because his Moto G5 (XT1676, country: Italy) didn't startup anymore. He gave it to me.
There was a black screen with "Your device has failed verification and may not work properly.".
I've done some research and find out it happened a lot on many moto devices, and a common cause was an android crash or failure during an OTA update.
So, the smartphone was never rooted, nor had the usb debugging enabled nor was bootloader unlocked.
I somehow managed to flash a stock ROM(CEDRIC_RETAIL_8.1.0_OPPS28.85-13-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. I picked this one becuase it was the one it was already installed, altough it was corrupted) from the fastboot using a PC.
It loaded up and everything was working fine on first startup.
I then decided to unlock the bootloader, just in case, and tried to install TWRP + Magisk.
Before doing that, I actually never tried to reboot more than 1 time.
Now, I can't tell if the smartphone was already unstable, but at this point it started to reboot itself very randomly:
freezing during boot animation and then reboot itself;
arrriving at android setup with language selection etc. and then reboot itself;
never even arrive at boot animation, just to the logo, and the reboot itself.
But just most of the times. Sometimes I can actually get into the phone and use it normally, until I reboot or power off and startup again. Sometimes it reboots like 6 times and finally get to works. So, very unstable.
I tried of course to remove Magisk and TWRP reflashing the same ROM, but also other stock ROMs like:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1676_CEDRIC_RETEU_DS_8.1.0_OPPS28.85-13-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1676_CEDRIC_TEFES_8.1.0_OPPS28.85-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And always got the same strange behaviour.
So, now I got no TWRP, no Magisk. Just trying to get the stock rom to be stable and I ran out of ideas.
Bonus facts:
It's the first time I try to do something like this. I already rooted my personal Moto G3 and flashed TWRP but never flashed any ROM. So please excuse me if I may say of have done something really wrong.
I followed the procedure descripted by @TheFixItMan : https://forum.xda-developers.com/g5/help/moto-g5-stuck-bootloop-t3915569 , no errors during the flash.
The battery of the smartphone may not be in its best health, because sometimes give the system wrong info about the charge status.(For example, power off at 93%,reboot and get 80%). I have been thinking that maybe the failure happened during the update that broke everything was due to battery failure.
Any help would be really appreciated. The smartphone would be already in trash because my friend is not that of a nerd. I would like to save it and maybe use it myself in replace of my Moto G3. I would also like to use it with root, but for know it would be enough to get it to work properly on non rooted stock rom.
Thank you in advance!
Video proof of the behaviour right after flashing a stock rom: https://streamable.com/tgu9o
fastboot getvar all:
Code:
Microsoft Windows [Versione 10.0.18362.418]
(c) 2019 Microsoft Corporation. Tutti i diritti sono riservati.
C:\Users\***>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3222JCMF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3E7D58F000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: *
(bootloader) meid:
(bootloader) date: 02-22-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 0: 8:17 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.062s

GrizzlyBear45 said:
So, long story short, a friend of mine endend up buying a new smartphone because his Moto G5 (XT1676, country: Italy) didn't startup anymore. He gave it to me.
There was a black screen with "Your device has failed verification and may not work properly.".
I've done some research and find out it happened a lot on many moto devices, and a common cause was an android crash or failure during an OTA update.
So, the smartphone was never rooted, nor had the usb debugging enabled nor was bootloader unlocked.
I somehow managed to flash a stock ROM(CEDRIC_RETAIL_8.1.0_OPPS28.85-13-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. I picked this one becuase it was the one it was already installed, altough it was corrupted) from the fastboot using a PC.
It loaded up and everything was working fine on first startup.
I then decided to unlock the bootloader, just in case, and tried to install TWRP + Magisk.
Before doing that, I actually never tried to reboot more than 1 time.
Now, I can't tell if the smartphone was already unstable, but at this point it started to reboot itself very randomly:
freezing during boot animation and then reboot itself;
arrriving at android setup with language selection etc. and then reboot itself;
never even arrive at boot animation, just to the logo, and the reboot itself.
But just most of the times. Sometimes I can actually get into the phone and use it normally, until I reboot or power off and startup again. Sometimes it reboots like 6 times and finally get to works. So, very unstable.
I tried of course to remove Magisk and TWRP reflashing the same ROM, but also other stock ROMs like:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1676_CEDRIC_RETEU_DS_8.1.0_OPPS28.85-13-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1676_CEDRIC_TEFES_8.1.0_OPPS28.85-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And always got the same strange behaviour.
So, now I got no TWRP, no Magisk. Just trying to get the stock rom to be stable and I ran out of ideas.
Bonus facts:
It's the first time I try to do something like this. I already rooted my personal Moto G3 and flashed TWRP but never flashed any ROM. So please excuse me if I may say of have done something really wrong.
I followed the procedure descripted by @TheFixItMan : https://forum.xda-developers.com/g5/help/moto-g5-stuck-bootloop-t3915569 , no errors during the flash.
The battery of the smartphone may not be in its best health, because sometimes give the system wrong info about the charge status.(For example, power off at 93%,reboot and get 80%). I have been thinking that maybe the failure happened during the update that broke everything was due to battery failure.
Any help would be really appreciated. The smartphone would be already in trash because my friend is not that of a nerd. I would like to save it and maybe use it myself in replace of my Moto G3. I would also like to use it with root, but for know it would be enough to get it to work properly on non rooted stock rom.
Thank you in advance!
Video proof of the behaviour right after flashing a stock rom: https://streamable.com/tgu9o
fastboot getvar all:
Click to expand...
Click to collapse
First remove you imei from getvar.
Solution:-
1) install twrp then format everything ( advance select dalvik, system,data,catch,internal storage and remove the sd card) then format again right one format yes, then install the stock Oreo by using twrp flashable zip.

riyan65 said:
First remove you imei from getvar.
Solution:-
1) install twrp then format everything ( advance select dalvik, system,data,catch,internal storage and remove the sd card) then format again right one format yes, then install the stock Oreo by using twrp flashable zip.
Click to expand...
Click to collapse
Thank you for the answer.
Apparently I cannot edit the post anymore. May I ask why/how is IMEI sensible data? Could a mod edit it for me? I googled it, I was stupid and naive, thank you.
I'll try to do as you described, are the roms on https://mirrors.lolinet.com/firmware/moto/cedric/official/ "flashable" by TWRP or am I looking for something different?
You are referring to the one I can find here https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913, right?
Edit:
Ok by refreshing the page the "Edit" button reappeared and I removed the imei.

Update:
I've done everything(backuped up everything with unofficial TWRP (efs + persist) before doing this) :
TWRP(without microsd) -> Advanced -> selected everything -> Wipe -> Back -> Format -> "yes" -> Wipe -> flash stock oreo (from here https://androidfilehost.com/?w=files&flid=280562 ) -> Aroma installer -> installation ok.
Everything seemed to work, setup ok, starting using it (opening random apps) -> randomly rebooted 2 times.
Then tried various combinations: others stock roms from the same link, others TWRP versions, but everytime endend up with the same situation of random reboots. Totally unstable.
I'm giving up on this device, it is a bit frustrating because when it boots up it works well, smooth and fast: it potentially could be still usable if not for this unstable behavior, so I hate having to dispose it.
At this point I think it may be a strange kind of hardware failure that triggers the random reboots. I don't see anymore how could be system/software-related.
Thank you @riyan65 for helping, if there is something I haven't tried yet that you or somebody else can think of, I am here, but I'm ready to give up

GrizzlyBear45 said:
Update:
I've done everything(backuped up everything with unofficial TWRP (efs + persist) before doing this) :
TWRP(without microsd) -> Advanced -> selected everything -> Wipe -> Back -> Format -> "yes" -> Wipe -> flash stock oreo (from here https://androidfilehost.com/?w=files&flid=280562 ) -> Aroma installer -> installation ok.
Everything seemed to work, setup ok, starting using it (opening random apps) -> randomly rebooted 2 times.
Then tried various combinations: others stock roms from the same link, others TWRP versions, but everytime endend up with the same situation of random reboots. Totally unstable.
I'm giving up on this device, it is a bit frustrating because when it boots up it works well, smooth and fast: it potentially could be still usable if not for this unstable behavior, so I hate having to dispose it.
At this point I think it may be a strange kind of hardware failure that triggers the random reboots. I don't see anymore how could be system/software-related.
Thank you @riyan65 for helping, if there is something I haven't tried yet that you or somebody else can think of, I am here, but I'm ready to give up
Click to expand...
Click to collapse
Did you try safe mode, if it work in safe mode then it not a hardware problem only software (due to some app)
If it won't work in safe mode top then it hardware. Did you check if battery is okay???

riyan65 said:
Did you try safe mode, if it work in safe mode then it not a hardware problem only software (due to some app)
If it won't work in safe mode top then it hardware. Did you check if battery is okay???
Click to expand...
Click to collapse
No, I didn't try safe mode because I thought that with a full wipe and clean installation there wouldn't be any app that could cause this issue. But I'm trying right now and will provide feedback soon.
The battery, as mentioned in first post, is not perfect, but can keep enough charge for like a day of medium use.
Plus, I have another Moto G5 (not mine, but used by another person I know), with an healthy battery: I tried to use that battery in this moto g5(the one with random reboots), and had the same exact issue, so I excluded anything battery-related.
Edit:
Same even with safe reboot ( video proof of the behaviour: https://streamable.com/m41cc ) :/
Bonus fact:
Now that it rebooted itself (normally, no safe mode), I'm using if for several minutes, no reboots for now, but I'm pretty sure that they will return as soon as i reboot manually or power off and restart.
But these are the cases that surprise me, with an hardware failure it shouldn't be possible that randomly it works normally for minutes. Also, why no random reboots while in bootloader or twrp?

Help to know my original stock ROM - Not as easy as it looks

Hi everyone.
I know that when reading the title of my thread they can say "pfff just type the USSD code and look for the baseband in the configuration", but if it were that easy we will not be here.
I have this phone (Motorola Z2 Force) which at the time I changed the original ROM (do not ask why, please), at that time I installed a stock ROM that worked but has always generated the message "verity mode set to disable" at startup, that's because the ROM doesn't match the same version of ROM that was on the phone.
So now I want to go back to the original ROM, but I never wrote down what that firmware was, so I have no clue which ROM to look for. I tried installing several ROMs because I know the model of the phone and its variation, but even so there are many ROMs, some worked, some did not, some I did not even try because they are too many, but all that worked for me showed me the same message "verity mode set to disable".
I have tried to find out the exact ROM I had through data that is still true, such as the phone's serial number or IMEI code, but I can't find information on how to interpret those numbers, I can't find a "translator" to find out what Help me find out what my original stock ROM was.
Any ideas?

Loperaco said:
Hi everyone.
I know that when reading the title of my thread they can say "pfff just type the USSD code and look for the baseband in the configuration", but if it were that easy we will not be here.
I have this phone (Motorola Z2 Force) which at the time I changed the original ROM (do not ask why, please), at that time I installed a stock ROM that worked but has always generated the message "verity mode set to disable" at startup, that's because the ROM doesn't match the same version of ROM that was on the phone.
So now I want to go back to the original ROM, but I never wrote down what that firmware was, so I have no clue which ROM to look for. I tried installing several ROMs because I know the model of the phone and its variation, but even so there are many ROMs, some worked, some did not, some I did not even try because they are too many, but all that worked for me showed me the same message "verity mode set to disable".
I have tried to find out the exact ROM I had through data that is still true, such as the phone's serial number or IMEI code, but I can't find information on how to interpret those numbers, I can't find a "translator" to find out what Help me find out what my original stock ROM was.
Any ideas?
Click to expand...
Click to collapse
Go to fastboot and use the command "fastboot getvar all" minus the quotations. Post the report here with your IMEI blacked out and we can help you
There are a few posts here to help you get fastboot setup if you don't have it

Starkiller2 said:
Go to fastboot and use the command "fastboot getvar all" minus the quotations. Post the report here with your IMEI blacked out and we can help you
There are a few posts here to help you get fastboot setup if you don't have it
Click to expand...
Click to collapse
Hi Starkiller.
This what the command returns:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SKHYNIX LP4x DIE=12Gb M5=06 M6=04 M7=00 M8=0D
(bootloader) cpu: MSM8998 2.1 (4)
(bootloader) serialno: ZY224WPP9T
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 3E3684D8
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-26-2018
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4346
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-24/
(bootloader) ro.build.fingerprint[1]: e78f1:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.24.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Fri Sep 20 09:23:35 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190920
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190920
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190920
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?

npjohnson said:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?
Click to expand...
Click to collapse
Hi npjohnson
I'm afraid you fell into the trap. Although you see that the firmware is correct, it really is not true. As I said before, I have a working ROM installed, and the "getvar" command shows exactly that, that is, what I have installed, so you are immersed in a loop. You see that I have a proper installation, but that is not the original ROM, and apparently it matches because I did indeed look for a firmware that matches my cell phone model, but I know that this is not exactly correct, because I keep getting the message " verity mode set to disable ".
Now, about the variations that you propose to me, I have this:
RETLA: There I found two versions, "XT1789-05_NASH_RETLA_SS" and "XT1789-05_NASH_RETLA_DS". With the first one the cell phone goes blank when it starts, with the second one it shows me the message that I have installed a different firmware.
RETBR: I never tried, because I bought the cell phone in Colombia at the time. Should I try this?
RETAIL: This is actually the one I currently have, but as I said, I have the message "verity mode set to disable".
This is why I need to know, through things that have not had modification such as the serial number or the IMEI, what ROM originally had.
I am very grateful for your help, so I will keep trying my best guys.

Loperaco said:
Hi npjohnson
I'm afraid you fell into the trap. Although you see that the firmware is correct, it really is not true. As I said before, I have a working ROM installed, and the "getvar" command shows exactly that, that is, what I have installed, so you are immersed in a loop. You see that I have a proper installation, but that is not the original ROM, and apparently it matches because I did indeed look for a firmware that matches my cell phone model, but I know that this is not exactly correct, because I keep getting the message " verity mode set to disable ".
Now, about the variations that you propose to me, I have this:
RETLA: There I found two versions, "XT1789-05_NASH_RETLA_SS" and "XT1789-05_NASH_RETLA_DS". With the first one the cell phone goes blank when it starts, with the second one it shows me the message that I have installed a different firmware.
RETBR: I never tried, because I bought the cell phone in Colombia at the time. Should I try this?
RETAIL: This is actually the one I currently have, but as I said, I have the message "verity mode set to disable".
This is why I need to know, through things that have not had modification such as the serial number or the IMEI, what ROM originally had.
I am very grateful for your help, so I will keep trying my best guys.
Click to expand...
Click to collapse
You are confused, the verity mode set to disabled notice is not because you have a firmware for a different device... It's because verity is disabled.
If you relock the bootloader that may go away, but I wouldn't worry about it.
RETLA appears to be correct for your device.

npjohnson said:
You are confused, the verity mode set to disabled notice is not because you have a firmware for a different device... It's because verity is disabled.
If you relock the bootloader that may go away, but I wouldn't worry about it.
RETLA appears to be correct for your device.
Click to expand...
Click to collapse
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?

Loperaco said:
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?
Click to expand...
Click to collapse
Never heard of SS, use whichever boots for you.

Loperaco said:
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?
Click to expand...
Click to collapse
SS is "Single Sim" and DS is "Dual Sim".

Loperaco said:
Hi Starkiller.
This what the command returns:
...
(bootloader) ro.carrier: retla
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
Click to expand...
Click to collapse
It's unusual for a Moto device to be running in slot b
But that shouldn't affect your issue.
If you have a Windows PC LMSA'S Flash rescue option works good for downloading and flashing stock firmware.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs

Loperaco said:
Any ideas?
Click to expand...
Click to collapse
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled

ph03n!x said:
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled
Click to expand...
Click to collapse
You problem with RSD Lite is likely USB 3 ports, also most PC's that shipped with Windows 10, will not work with RSD Lite.
You need a PC that shipped with Windows 7 or XP, and USB 2 ports.
Sent from my ali using XDA Labs

ph03n!x said:
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled
Click to expand...
Click to collapse
Hahahaha LOL
ok, clearly that could be an effective solution, unfortunately not the most suitable

sd_shadow said:
You problem with RSD Lite is likely USB 3 ports, also most PC's that shipped with Windows 10, will not work with RSD Lite.
You need a PC that shipped with Windows 7 or XP, and USB 2 ports.
Click to expand...
Click to collapse
After realising that Moto has abandoned this device, I've abandoned Moto firmware too... Experimenting with Lineage now :laugh:
Loperaco said:
ok, clearly that could be an effective solution, unfortunately not the most suitable
Click to expand...
Click to collapse
For me, it was more of an OCD to not see that ugly screen once in a while when I restart. I'm rooted with Magisk, have EdXposed too - while Safety Net passes (for now at least), I do not use banking or Google Pay apps on this device - have a stock, unlocked P30 Pro only for that. So no sweat :highfive:

XT1789-01 engineering bootloader
npjohnson said:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?
Click to expand...
Click to collapse
Dear I've a Z2 force with XT1789-01 model number which is Verizon but "ENGINEERING BOOTLOADER" so my phone doesn't flash any firmware and says failed to start bootloader mode.
What's compatible firmware for engineering bootloader?
If I flash by commands it shows hardware malfunction

AlahmadPR said:
Dear I've a Z2 force with XT1789-01 model number which is Verizon but "ENGINEERING BOOTLOADER" so my phone doesn't flash any firmware and says failed to start bootloader mode.
What's compatible firmware for engineering bootloader?
If I flash by commands it shows hardware malfunction
Click to expand...
Click to collapse
You have a prototype device, return it to whomever you bought it from and get a new one.

I'm responsible for it
npjohnson said:
You have a prototype device, return it to whomever you bought it from and get a new one.
Click to expand...
Click to collapse
Is there a way to recover? Because I was using it b4