Develop Bugs

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

Need help with very weird soft brick

Hey everybody, here's my story: I bought earlier today a second-hand G5, it was already soft bricked when I purchased it. It was already unlocked (had the warning message when turned on), so I first proceeded to install TWRP, try and flash a custom ROM.
Everything was working fine on bootloader mode, phone was snappy (more on that in a bit) and not lagging.
Then the issues started: on TWRP, it took ages to do anything. The phone's boot logo lasted almost a minute, then TWRP's splash screen stood there for over another minute, and each action I made in it (like touching options on menus and stuff like that) needed a good 10+ seconds to be processed. Tried formatting data, changing FS to from F2FS to EXT4, and other stuff like that, nothing solved the tremendous lag. I also faced some random reboots and many USB disconnecting/reconnecting episodes (like one per second, sometimes) at TWRP as well. Getting the phone to boot TWRP is also a pain, because it keeps switching between a bootlogo with "N/A" (as if there is a custom ROM/recovery installed) and a bootlogo with "bad key" (as if bootloader is unlocked, but ROM and recovery are stock), remains a few minutes in each, and eventually it decides to boot up on TWRP.
Eventually I just gave up and flashed a stock firmware using both RSDLite and fastboot. Flashing times were just about alright, as was everything done via bootloader mode, no stuttering here. Stock recovery (which is operated via volume/power keys, not touch) seemed to work without speed issues as well.
At some point (after many failed efforts, reboots that went straight to recovery, wiping everything multiple times using both TWRP and stock recovery, and so on) I managed to start booting it and... It was sluggish as hell. The boot animation took around 10 minutes to complete (not looping through the animation multiple times, it was just really slow, and it actually just showed about 2 or 3 frames from different moments of the animation and stuck in these frames for several minutes each), the "Hello Moto" tone also played very slowly (as if I were streaming it in 1080p using a 256kbps modem), and when it reached the Lenovo logo (which I presume is the last stage in the boot animation), it bootlooped back to the first frame (Motorola's logo, same as the splash screen but without the "bad key" or "N/A" warning - I had changed from that annoying "bootloader unlocked, device can't be trusted" screen by flashing a modified logo.bin, thus the only difference between splash screen and bootanimation's first frame was the abscence of the text), did so a few times (I think I let it run that way for about 40 minutes) before battery got depleted. Never got into OS.
I did run into a few secondary issues (tried to relock bootloader then unlock again just to find that I couldn't get an unlock code from Motorola's site; had it booting straight into recovery; couldn't wipe data and cache, had TWRP ask for encryption key; etc), but managed to solve all of them.
The point is that right now I have a phone that I can boot either TWRP or stock recovery, or go into bootloader (or sometimes bootloop whilst taking 10 minutes to display the boot animation), but TWRP is slower than a Celeron rendering GTA V, barely usable. Flashing custom (through TWRP) or stock (through fastboot or RSDLite) ROMs seem to complete successfully, but they never get to boot.
If there's any difference, I don't know which version the phone was when I purchased it, but right now bootloader is B8.31, and I tried flashing both 16-2 then 16-4 Oreo versions. Phone model is 1672.
Any help is appreciated, I bought this phone as a gift to my girlfriend and it's specially frustrating I didn't manage to fix it for her.

K3n H1mur4 said:
Hey everybody, here's my story
Click to expand...
Click to collapse
Bro Try To Flash No verity opt zip
it might help you boot

Sonisudhanshu said:
Bro Try To Flash No verity opt zip
it might help you boot
Click to expand...
Click to collapse
Device seems to be unable to get into recovery, now. Just goes into a bootloop with "bad key" (even though TWRP has been flashed). When I try to boot TWRP straight from fastboot (like boot twrp.img instead of flash recovery twrp.img), it shows the usual splash screen (also with neither "bad key" nor "N/A"), but then bootloops into "bad key" again. Will try flashing a different firmware (tried with a random RETBR Nougat and the latest, 16-4, RETBR Oreo) to see if I get any luck.

this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?

Exanneon said:
this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?
Click to expand...
Click to collapse
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?

K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
there isn't one yet, but that seems to be your only option atm

Exanneon said:
there isn't one yet, but that seems to be your only option atm
Click to expand...
Click to collapse
K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Why would he need a blank flash? There's nothing wrong with his bootloader
Also we can already revive hard bricked devices with mmcblk0 image but that's not the issue here
Also you obviously won't get another unlock code from Motorola - your device is already unlocked - just because you locked it again doesn't actually lock it the same way
You can just unlock it via fastboot with an unlock command
Anyway moving on
Goto https://mirrors.lolinet.com/firmware/moto/cedric/official/
And downloaded the latest firmware for your device
Flash it via fastboot - note that the firmware must be the same or later version than what is already there
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5 (only oreo firmware)
fastboot flash system system.img_sparsechunk.6 (only oreo firmware)
fastboot flash system system.img_sparsechunk.7 (only oreo firmware)
fastboot flash system system.img_sparsechunk.8 (only oreo firmware)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Make sure gpt and Bootloader flash successfully - a pre flash validation error means that the firmware is too old
Post the output if you get errors

K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Did you try a clean flash or a dirty flash, sometimes dirty flash can result this so I prefer you to clean the data inside first by using twrp advance wipe select all and the format yes and again do a advance wipe after boot into bootloader and flash the latest firmware with bootloader and gpt codes also so bootloader also can reflash. Once you are clean without any other software in Device. the device will work like a champ, and please post the flashing command you get in fastboot as well as getvar also by removing the IMEI and serial number.
Here is the link for latest firmware:-
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
-
Click to expand...
Click to collapse
Hey pal, I appreciate your advice and understand you're a very helpful member in the G5 forums, but I have around 10 years on the modding community (even before Android), and am pretty familiar with flashing via recovery, fastboot or vendors' flashing tools. I've already tried, so, the steps you suggested, to no result either.
Just as a sideline, I've actually managed to get an unlock code from Motorola's online support, but that doesn't make a difference anyway.
I gave a shot on three of the RETBR versions (Oreo 16-2 and 16-4, and Nougat 93-8, this last one obviously without flashing bootloader and gpt). In all of the attempts I got either one of two results: it gets to recovery (TWRP runs slow as hell, stock recovery seems fine) or it keeps bootlooping when I try to get to recovery.
Just tried a RETAIL 16-4 firmware (with gpt and bootloader from RETBR being flashed instead of RETAIL's files), the only error messages I got in fastboot were the expected "Image signed with key bad key when flashing boot and recovery .imgs, but they both flashed just as expected. Same result as before: bootlogo with unlocked warning (showing bad key), then a "boot animation" that was really just the first frame from each part (Motorola logo same as boot logo, the first frame of the animation that plays with the "Hello Moto" sound - also, only some parts of the tone played, like it was lagging too much; then Lenovo Logo; then Motorola logo with "Motorola, a Lenovo company" below; then Lenovo logo again - I really suspect that, if one pulls a bootanimation.zip from a stock firmware, each of the "0", "1", "2" etc parts will have as their first frame exeactly the frames I just described, as if the phone was unable to properly display the animation) displaying for a few minutes each, then it jumps back to bootlogo. It's definitely in bootloop even though I just flashed just per instructions, and also with this issue of being veeeeeeeryyyyyy sloooooooooowwww... After that, it just keeps going into bootlogo for several minutes, than screen off for a few seconds, then bootlogo again for several minutes.
riyan65 said:
-
Click to expand...
Click to collapse
There's no dirty flashing via fastboot AFAIK. When I managed to get into TWRP, I had an issue with /data being encrypted and in F2FS, and some issue with /cache, too (but /cache was in EXT4), both of them were showing as 0B in size at that "repair or change file system" screen.
I read somewhere that F2FS can make TWRP very slow, so I though it could be that, but I formatted /data to EXT4 as well and the phone was still very slow. I also was having issues with TWRP not being able to mount /data and /cache, formatting solved that as well.
After formatting, I managed to flash Bootleggers. It took a good 30-40 minutes to flash, and TWRP restarted right after that so I couldn't flash GApps. It went again into a bootlogo-only bootloop (no frames from boot animation appeared before it restarted into bootlogo again). Then I just gave up on TWRP and tried finding some stock firmware that could boot, but, as stated on the answer above, I still didn't manage to do so.
Right now I'm suspecting either a hardware fault or something very messed with GPT (but I can't really tell for the second one since I've already flashed both RETBR's GPTs and both of them gave me the same result).
What I'd like to try now before just giving up are both very unlikely options to find: first, a custom ROM that's fastboot flashable (Iif I remember well some files in fastboot must be signed by Motorola else they won't flash, so there's no way to create a fastboot-flashable custom firmware, am I right?); second, to find out if the bootloader is stored in the same NAND/eMMC as the other partitions, or if it is a separate chip. If it's the same chip, I could easily rule out a hardware fault and try to find other possible solutions. If it's stored separately, than it explains why bootloader works without stuttering and the other modes (except for stock recovery, but that's kinda slow by itself so I could simply be unable to tell the difference) like TWRP and normal booting are so slow and failing everytime.

New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?

K3n H1mur4 said:
New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?
Click to expand...
Click to collapse
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.

riyan65 said:
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.
Click to expand...
Click to collapse
I have tried it as well, no success whatsoever
I managed to flash Bootleggers again last night, took a couple hours to complete but at least TWRP didn't reboot during the process. Differently from stock ROM, however, phone didn't even get to the sluggish boot animation. It just stays in bootlogo, then eventually reboots (again to bootlogo).
Later tonight I'll try your suggestion again, I plan to do a Format Data, then changing it to ext4 again (if I remember well, Format Data puts the partition into f2fs), perhaps reflashing the no-verity zip and then Bootleggers again. I'm not hoping to get it working anymore, though.

Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC? @TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(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: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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

K3n H1mur4 said:
Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC?
@TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(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: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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
Click to expand...
Click to collapse
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard

TheFixItMan said:
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
Click to expand...
Click to collapse
Well, if the phone gets no signal it'll sure be an issue. But first I need to get it to boot before I can worry with that.
TheFixItMan said:
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard
Click to expand...
Click to collapse
Already tried RETBR and RETAIL, neither worked (they flashed just fine via either via fastboot or RSD, but got on bootloop with sluggish bootanimation and/or just bootlogo bootlooping). I'm trying with TIMBR right now, but I doubt it will make any difference. Device is a 1672, since I bought it second-hand and already bricked can't tell if the previous owner flashed anything wrong on it. If it did so, I think the device would be hardbricked, not with this weird slowness on TWRP and boot animation, and bootloops would be solved by reflashing stuff on fastboot.

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

How To Guide HOW TO UNLOCK BOOTLOADER

First Download Motorola USB Driver and Tiny Fastboot
Then make sure you have enabled "OEM UNLOCK" / "Allow OEM to be unlocked" in Developer Options ( to turn on Developer Options, just go to the "About" Section in your Settings and click on the build number 7 times )
After you've made sure that its all enabled, power off your phone and once its off, press and hold the Power Button + Volume Down Button and it should boot to a screen with an image of an Android with its stomach open.
Once you've reached there, connect your phone to the PC and extract the Tiny Fastboot .zip file and run the flash.bat
Now a cmd windows will upon and you will be asked to choose a fastboot verision, just type "1" and click Enter.
Now choose the 8th option i.e Bootloader Unlock Menu by typing "8" and pressing Enter
Now type in the 3rd option and the unlock code will be automatically copied.
Open Unlock My Device Portal and paste the unlock code in the 6th step's input box and agree to the agreement and click on the "REQUEST UNLOCK KEY" button at the bottom of the page below the agreement
Now you should have recieved a mail in your email account with which you linked to Motorola.
Now again type the 3rd option in your cmd so that you can return to the "Bootloader Unlock Menu" and now press 2nd option and paste the unique unlock code you received in your registered email and voila, a message shall appear on your phone asking whether you wanna unlock your bootloader or not, just use volume buttons to switch between the 2 options and press home button to enter your choice
Now click on the home button if the message shown on the right middle side near the two triangles is "START", if something else is shown then use your volume buttons to navigate back to the "START" option and press enter.
Your Device will be reset in this process and you will be greeted with an Android Welcome Screen with a language choice and a "START" button
To confirm whether your device is unlocked or not, just repeat step 2 and when you go to the specific option in Developer Options, it should show something like "Bootloader is already unlocked" and the option will be greyed out.
GOOD LUCK ! AND I HAVE ATTACHED THE FILES BELOW TOO !

If you're willing to use normal ADB Tool rather than this Tiny Fastboot, feel free to do so..
From the 4th to 7th step, instead of Tiny Fastboot use open ADB in cmd and type fastboot oem get_unlock_data then copy the unlock code you get from there, it should be something like (bootloader) 3A35315903679773#3498G234K23 to remove those bootloader from every line just open Data Scrub Tool and paste your code there and click on "Format My Data" and it will remove all unwanted text like "(bootloader)" from the code and you can copy it and then follow step 8 & 9 and come back to adb and type " fastboot oem unlock <unlock code> " where <unlock code> is the unlock code sent to your mail. enter the command and a message shall appear on your phone asking whether you wanna unlock your bootloader or not, just use volume buttons to switch between the 2 options and press home button to enter your choice, then proceed to follow step 11-13.
GOOD LUCK ! AND I HAVE ATTACHED AN ADB ZIP BELOW INCASE ANYONE NEEDS IT.

Thank very much! Data scrub tool was also very useful

Thank you very much for sharing.

HOLA COMO ESTAN?, LEI TODOS SUS ARTICULOS UNO POR UNO Y HE PROBADO CADA COSA Y SIGO TENIENDO EL MISMO ERROR QUE TU TENIAS AL INICIO, LEI QUE ACTUALIZASTE EL PARCHE DE SEGURIDAD Y FUNCIONO PERO NO SE COMO ACTUALIZARLO MI DISPOSITIVO ES UN MOTO G9 PLAY MODELO (guamp XT2083 - 1) SI PUDIERA AYUDARE CON ESTE MODELO SE LOS AGRADECERIA

WILSON_LMS said:
HOLA COMO ESTAN?, LEI TODOS SUS ARTICULOS UNO POR UNO Y HE PROBADO CADA COSA Y SIGO TENIENDO EL MISMO ERROR QUE TU TENIAS AL INICIO, LEI QUE ACTUALIZASTE EL PARCHE DE SEGURIDAD Y FUNCIONO PERO NO SE COMO ACTUALIZARLO MI DISPOSITIVO ES UN MOTO G9 PLAY MODELO (guamp XT2083 - 1) SI PUDIERA AYUDARE CON ESTE MODELO SE LOS AGRADECERIA
Click to expand...
Click to collapse
English on XDA Please
Google translation
HELLO, HOW ARE YOU? I READ ALL YOUR ARTICLES ONE BY ONE AND I HAVE TRIED EVERYTHING AND I STILL HAVE THE SAME ERROR AS YOU HAD AT THE BEGINNING, I READ THAT YOU UPDATED THE SECURITY PATCH AND IT WORKED BUT I DON'T KNOW HOW TO UPDATE IT MY DEVICE IS A MOTO G9 PLAY MODEL (guamp XT2083 - 1) IF I COULD HELP WITH
Click to expand...
Click to collapse

HELLO HOW ARE YOU?, I READ ALL YOUR ARTICLES ONE BY ONE AND I HAVE TRIED EVERY THING AND I KEEP HAVING THE SAME ERROR THAT YOU HAD AT THE BEGINNING, I READ THAT YOU UPDATED THE SECURITY PATCH AND IT WORKED BUT I DON'T KNOW HOW TO UPDATE IT MY DEVICE IS A MOTO G9 PLAY MODEL (guamp XT2083 - 1) IF YOU COULD HELP WITH THIS MODEL I WOULD APPRECIATE IT

C:\Users\SO\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamp_retail-252ee94a782-211027
(bootloader) product: guamp
(bootloader) board: guamp
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX hC9aP3 RV=08 PV=01 FV=0000000031303030
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5-M8=06 05 00 11
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY327KMT5P
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 9147803F
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 804464640
(bootloader) reason: Volume down key pressed
(bootloader) imei: 867685059931725
(bootloader) imei2: 355530110667141
(bootloader) meid:
(bootloader) date: 07-17-2020
(bootloader) sku: XT2083-1
(bootloader) carrier_sku: XT2083-1
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 3944
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:11/RPX
(bootloader) ro.build.fingerprint[1]: S31.Q2-58-17-4-1/9f01c:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_29.11.02.88R GUAMP_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed O
(bootloader) kernel.version[4]: ct 27 05:16:38 CDT 2021
(bootloader) git:xbl: MBM-3.0-guamp_retail-0ed29cb2f-211027
(bootloader) git:xbl_config: MBM-3.0-guamp_retail-0ed29cb2f-211027
(bootloader) git:abl: MBM-3.0-guamp_retail-252ee94a782-211027
(bootloader) git:rpm: MBM-3.0-guamp_retail-834e250d-211027
(bootloader) git:tz: MBM-3.0-guamp_retail-13b6e616-211027
(bootloader) git:hyp: MBM-3.0-guamp_retail-13b6e616-211027
(bootloader) git:devcfg: MBM-3.0-guamp_retail-13b6e616-211027
(bootloader) git:keymaster: MBM-3.0-guamp_retail-4b088521-211027
(bootloader) git:storsec: MBM-3.0-guamp_retail-4b088521-211027
(bootloader) git:uefisecapp: MBM-3.0-guamp_retail-4b088521-211027
(bootloader) gitrov: MBM-3.0-guamp_retail-13b6e616-211027
(bootloader) git:qupfw: MBM-3.0-guamp_retail-2e25c72-211027
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 5
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6P9SN
(bootloader) primary-display: hlt_hx83102d_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.348s

Thank you for the guide.
One thing I'd like to add, in case anyone else encounters this issue.
Try to use Gmail as your account email for Motorola, since that's what's gonna be used to send you the unlock code. I've got issues using other email providers.
So...just so you know. In case you don't receive the unlock code (which should come in about a minute or so), try to change your account email address and request the code again.

after several trying i cant unlock my my boot loader...moto g60 running android 12. using laptop windows 11.. pls help me. i want to unlock bl and feel the taste of custom roms badly. @lofi2op @arsradu @WILSON_LMS @sd_shadow .
this is my new acount. i was a senior member in xda for several years since micromax ninja times somehow i lost that acount thatswhy i made this new acount...i will be very grateful if you guys help me out...dont know fastboot dont recognise my device somehow..i changed usb cable also...used vivo cable,samsunge cable..but no use....any other way to unlock bootloader from getting that code through email, like we do do previously in other moto phones earler? pls guide me...im confused and irritated.help me pls...waiting for u reply.

reejuu said:
after several trying i cant unlock my my boot loader...moto g60 running android 12. using laptop windows 11.. pls help me. i want to unlock bl and feel the taste of custom roms badly. @lofi2op @arsradu @WILSON_LMS @sd_shadow .
this is my new acount. i was a senior member in xda for several years since micromax ninja times somehow i lost that acount thatswhy i made this new acount...i will be very grateful if you guys help me out...dont know fastboot dont recognise my device somehow..i changed usb cable also...used vivo cable,samsunge cable..but no use....any other way to unlock bootloader from getting that code through email, like we do do previously in other moto phones earler? pls guide me...im confused and irritated.help me pls...waiting for u reply.
Click to expand...
Click to collapse
Well, you need to make sure the device is recognised in fastboot mode (maybe adb, too).
Try to use platform tools from here: https://developer.android.com/studio/releases/platform-tools
Also, did you get the unlock code via email?
Personally don't know another way to unlock the bootloader without fastboot and a data cable.

arsradu said:
Well, you need to make sure the device is recognised in fastboot mode (maybe adb, too).
Try to use platform tools from here: https://developer.android.com/studio/releases/platform-tools
Also, did you get the unlock code via email?
Personally don't know another way to unlock the bootloader without fastboot and a data cable.
Click to expand...
Click to collapse
No didnt get the unlock code via email...can u pls help...in a elaborated way...i cant work out i tried many times

reejuu said:
No didnt get the unlock code via email...can u pls help...in a elaborated way...i cant work out i tried many times
Click to expand...
Click to collapse
Well, pretty much everything is described on the Motorola site here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Except for the SDK part.
Ok, let's see if we can make a better tutorial than Motorola did. Unlikely, but we can try.
Get the Android Platform Tools. You can download it here.
I see no point in downloading the whole SDK for this.
Install the latest Motorola USB Drivers. Get them here.
Next, you will need to get your device ID.
1. Device in Fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable)
2. open up CMD prompt inside the platform tools folder
then type:
fastboot devices
3, make sure device is connected (you should see your serial number displayed if everything ok)
then type
fastboot oem get_unlock_data
you should get something like this:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
4. Now copy the "code" part off of each line (basically exclude the (bootloader) part and remove all spaces) and make it a single string.
Should look something like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
5. Now copy the resulting line (your line, not the one in my example) in the text input field on that page, and click "Can my device be unlocked?"
IF it can be unlocked, you will get a Request Unlock Key button.
Agree to the terms and get click Request Unlock Key.
Please, note that NOT ALL MODELS CAN BE UNLOCKED!
If anything unclear, please, let me know. Add screenshots or details so we can understand what the problem is.
Make sure you use a Gmail email address for your account. You can change it from your account in case it's not. There seem to be some issues with other email providers.

arsradu said:
Well, pretty much everything is described on the Motorola site here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Except for the SDK part.
Ok, let's see if we can make a better tutorial than Motorola did. Unlikely, but we can try.
Get the Android Platform Tools. You can download it here.
I see no point in downloading the whole SDK for this.
Install the latest Motorola USB Drivers. Get them here.
Next, you will need to get your device ID.
1. Device in Fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable)
2. open up CMD prompt inside the platform tools folder
then type:
fastboot devices
3, make sure device is connected (you should see your serial number displayed if everything ok)
then type
fastboot oem get_unlock_data
you should get something like this:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
4. Now copy the "code" part off of each line (basically exclude the (bootloader) part and remove all spaces) and make it a single string.
Should look something like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
5. Now copy the resulting line (your line, not the one in my example) in the text input field on that page, and click "Can my device be unlocked?"
IF it can be unlocked, you will get a Request Unlock Key button.
Agree to the terms and get click Request Unlock Key.
Please, note that NOT ALL MODELS CAN BE UNLOCKED!
If anything unclear, please, let me know. Add screenshots or details so we can understand what the problem is.
Make sure you use a Gmail email address for your account. You can change it from your account in case it's not. There seem to be some issues with other email providers.
Click to expand...
Click to collapse
Okay i will try it now and reply you shortly what will happen!

reejuu said:
Okay i will try it now and reply you shortly what will happen!
Click to expand...
Click to collapse
The links in the original tutorial (the one from Motorola) seem to be either outdated. So I've replaced them with hopefully the right ones.
Anyway, in short, the flow should look like this:
1. install driver
2. download and unpack the platform tools
3. enter the platform tools folder
4. connect your device
5. open a cmd prompt inside the platform tools folder (or navigate to it from CMD prompt; as you wish)
6. do a "fastboot devices" to make sure the device is detected
5. do a "fastboot oem get_unlock_data"
This should give you the request string. But it's in multiple parts so we need to make it a single one in the next step.
6. put the request string in a single part (remove "(bootloader)" and spaces, if there are any).
7. copy-paste the string in the field
8. try to see if the device is unlockable.
9. if it is, you should get an unlock key via email in a few minutes maximum. Just make sure your account uses a Gmail email address.
That's it.

arsradu said:
The links in the original tutorial (the one from Motorola) seem to be either outdated. So I've replaced them with hopefully the right ones.
Anyway, in short, the flow should look like this:
1. install driver
2. download and unpack the platform tools
3. enter the platform tools folder
4. connect your device
5. open a cmd prompt inside the platform tools folder (or navigate to it from CMD prompt; as you wish)
6. do a "fastboot devices" to make sure the device is detected
5. do a "fastboot oem get_unlock_data"
This should give you the request string. But it's in multiple parts so we need to make it a single one in the next step.
6. put the request string in a single part (remove "(bootloader)" and spaces, if there are any).
7. copy-paste the string in the field
8. try to see if the device is unlockable.
9. if it is, you should get an unlock key via email in a few minutes maximum. Just make sure your account uses a Gmail email address.
That's it.
Click to expand...
Click to collapse
How to make sure that that unlock key in received in gmail acount? How will it linked to fastboot?

reejuu said:
How to make sure that that unlock key in received in gmail acount? How will it linked to fastboot?
Click to expand...
Click to collapse
The key will be sent to your email if your device is unlockable and you follow the steps above.
I'm not sure I understand the second question...
Did you try the steps? Did you get stuck? If so, where?

arsradu said:
The key will be sent to your email if your device is unlockable and you follow the steps above.
I'm not sure I understand the second question...
Did you try the steps? Did you get stuck? If so, where?
Click to expand...
Click to collapse
done successfully thanks a lot..now will install twrp...

reejuu said:
done successfully thanks a lot..now will install twrp...
Click to expand...
Click to collapse
Awesome!
You actually don't need to install TWRP. And...it might be better if you don't.
Some ROMs usually come with their own Recovery. PixelExperience for example will have its own recovery. So you don't need to flash TWRP. Just to boot into it, long enough to flash the actual ROM (with its own recovery).
The difference?
fastboot flash boot twrp.zip
this is for flashing TWRP.
vs
fastboot boot twrp.img
this is for booting TWRP.
Also, you can actually install TWRP from within itself. I think the option is called "install into ramdisk" or something like that.
But again...You usually don't need to install TWRP. Just to boot into it, so you can flash whatever ROM you want.
One thing to remember: if you ever want to go back to stock ROM, please, first try to boot into it, and see if the OEM Unlocking option is still ON! If it's not, better NOT lock back the bootloader! Careful with that. You can easily brick your phone!

arsradu said:
Awesome!
You actually don't need to install TWRP. And...it might be better if you don't.
Some ROMs usually come with their own Recovery. PixelExperience for example will have its own recovery. So you don't need to flash TWRP. Just to boot into it, long enough to flash the actual ROM (with its own recovery).
The difference?
fastboot flash boot twrp.zip
this is for flashing TWRP.
vs
fastboot boot twrp.img
this is for booting TWRP.
Also, you can actually install TWRP from within itself. I think the option is called "install into ramdisk" or something like that.
But again...You usually don't need to install TWRP. Just to boot into it, so you can flash whatever ROM you want.
One thing to remember: if you eve want to go back to stock ROM, please, first try to boot into it, and see if the OEM Unlocking option is still checked! If it's not, better NOT lock back the bootloader! Careful with that. You can easily brick your phone!
Click to expand...
Click to collapse
how to flash rom? and which rom is god for me first time?