Develop Bugs

Download stock firmware with Lenovo Moto Smart Assistant

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

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

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

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

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

Can i use this while currently on custom 8.1 rom?

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

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

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

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

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

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

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

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

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

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

Does this work on Rooted device?

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

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

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

[Unlock / Relock] Bootloader

If you want to unlock bootloader, just follow the motorola guide.
For trouble shooting or more info about how to get your "cid" and see if it's unlockable , have a look here.
If you want to relock it:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.080s]
finished. total time: 0.080s
Code:
fastboot oem lock
...
(bootloader) warranty bit blown
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.943s]
finished. total time: 0.944s

So, um, is it unlockable? (Given the article linked is generic across all Moto phones, and the list of unlockable phones does not actually list the Moto One Vision.) Apparently you can run
Code:
fastboot getvar all
with the phone in bootloader mode to get the cid, and if it is one of: 0x0000, 0x0003, 0x0007, 0x0009, 0x000B, 0x000C, 0x000D, 0x000E, 0x0014, 0x00DE or 0x0032; but no others, its bootloader can be unlocked.
Asking because there's an Amazon UK Prime Day deal on today and tomorrow for this phone where it's 25% off its regular price, and I'd rather only buy it if, once its warranty runs out as do the Android One security updates, there's a chance for me to unlock the bootloader and put on, say, Lineage OS. My LG G5 is on its last legs and I do need a new phone, and it'll be a long while before this phone regularly sells used for £199.99 here in the UK. Especially with Brexit, and therefore an impending Sterling devaluation, closing fast.
(I gather the "Amazon Prime phones" mentioned as non-unlockable in the article are US Amazon Prime exclusive phones such as the Moto G6 and X4 that were for a time offered only to Amazon Prime customers in the US.)

obs3rv said:
So, um, is it unlockable?
(I gather the "Amazon Prime phones" mentioned as non-unlockable in the article are US Amazon Prime exclusive phones such as the Moto G6 and X4 that were for a time offered only to Amazon Prime customers in the US.)
Click to expand...
Click to collapse
Yes. Developer Mode has an option to unlock the bootloader.
£199 quid is a hell of a deal ; considering I shelled out £269 last month for mine.

Would you (or anyone with an EU version of this handset really) be kind enough to get the cid in bootloader mode using fastboot per my earlier post? I gather that the cid is the ultimate arbiter of whether the bootloader is unlockable, and that even permanently-locked bootloader handsets have similar firmware that has the Enable OEM unlock option in Developer Mode. (I'm happy to be corrected on this point.)

Answering my own question, the cid of a Motorola One Vision bought off Amazon Italy turned out to be 0x0032, indicating that its bootloader may be unlockable:
Code:
(bootloader) cid: 0x0032
You can boot into the bootloader from a powered-off, cable disconnected state by:
holding down the volume-down key
plugging in the USB cable whose other end is already connected to a computer with the Motorola Device Manager drivers installed
Then fastboot works.
(Why did I buy it from Amazon Italy rather than Amazon UK, taking advantage of the Prime Day deal? Despite the fact that Amazon UK showed the Prime Day deal was meant to run for 48 hours, at midnight, Amazon UK pulled its own merchant listing, leaving only third-party sellers, and so the Prime Day deal became unavailable. Amazon Italy had a lightning deal the following day on the phone for €249.99, which was a better price than I could find anywhere else. So I bought it, having missed out on the Prime Day deal the previous day. Thanks, Amazon. Thamazon.)
Almost full fastboot getvar all output for those who are curious (with serial number, IMEI and battery serial number redacted):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190605
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 000003D60F1C577A0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 05-20-2019
(bootloader) sku: XT1970-3
(bootloader) carrier_sku: XT1970-3
(bootloader) battid: [redacted]
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 23 6:59: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/kane_reteu/kane_sprout:9/
(bootloader) ro.build.fingerprint[1]: PSA29.137-17/6875e:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.18.kane_reteu.
(bootloader) ro.build.version.full[1]: retail.en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld66) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Wed Jun 5 08:01:45 CDT 2019
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190605
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.611s
FYI Amazon Spain seem to have had this handset at a decent price since Prime Day, and the price hasn't gone back up yet -- the price is down €40 from its usual €299.99 price to €259.99 since last week. Not quite as good as the €249.99 Lightning Deal on Amazon Italy from a week ago, and nowhere near as good as the £199.99 Amazon UK Prime Day deal, but still a good deal. (On Amazon Italy it's €269.99 starting today, but on the other Amazon Eurozone websites it's still €299.99, and in the UK the Amazon usual offer of £269.99 is back.)

obs3rv said:
Answering my own question, the cid of a Motorola One Vision bought off Amazon Italy turned out to be 0x0032, indicating that its bootloader may be unlockable:
Code:
(bootloader) cid: 0x0032
You can boot into the bootloader from a powered-off, cable disconnected state by:
holding down the volume-down key
plugging in the USB cable whose other end is already connected to a computer with the Motorola Device Manager drivers installed
Then fastboot works.
(Why did I buy it from Amazon Italy rather than Amazon UK, taking advantage of the Prime Day deal? Despite the fact that Amazon UK showed the Prime Day deal was meant to run for 48 hours, at midnight, Amazon UK pulled its own merchant listing, leaving only third-party sellers, and so the Prime Day deal became unavailable. Amazon Italy had a lightning deal the following day on the phone for €249.99, which was a better price than I could find anywhere else. So I bought it, having missed out on the Prime Day deal the previous day. Thanks, Amazon. Thamazon.)
Almost full fastboot getvar all output for those who are curious (with serial number, IMEI and battery serial number redacted):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190605
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 000003D60F1C577A0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 05-20-2019
(bootloader) sku: XT1970-3
(bootloader) carrier_sku: XT1970-3
(bootloader) battid: [redacted]
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 23 6:59: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/kane_reteu/kane_sprout:9/
(bootloader) ro.build.fingerprint[1]: PSA29.137-17/6875e:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.18.kane_reteu.
(bootloader) ro.build.version.full[1]: retail.en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld66) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Wed Jun 5 08:01:45 CDT 2019
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190605
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.611s
FYI Amazon Spain seem to have had this handset at a decent price since Prime Day, and the price hasn't gone back up yet -- the price is down €40 from its usual €299.99 price to €259.99 since last week. Not quite as good as the €249.99 Lightning Deal on Amazon Italy from a week ago, and nowhere near as good as the £199.99 Amazon UK Prime Day deal, but still a good deal. (On Amazon Italy it's €269.99 starting today, but on the other Amazon Eurozone websites it's still €299.99, and in the UK the Amazon usual offer of £269.99 is back.)
Click to expand...
Click to collapse
Yea it's sold by amazon.it at 299 euro, I was near to gets an galaxy a70 but seems they have troubles to run gsi roms. I'll order Moto's phone pretty soon, but I'd like to compile his kernel first so if done well I'll get it.

My phone is a RETBR with cid: 0x0032. Motorola sent me an unlock code that seemingly works, however I'm unable to activate OEM unlock under developer options, as it's greyed out. Any ideas?

Activate internet, switch back and open developer again

Karanso said:
Activate internet, switch back and open developer again
Click to expand...
Click to collapse
I've tried even factory resetting with LTE and WiFi during the setup process.
edit: something random happened and I've succeeded, lol.

Impossible to relock the bootloader
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards

gonzo1963 said:
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards
Click to expand...
Click to collapse
Hi. I have relocked my bootloader twice but never seen anything like that.
A quick google suggests that a factory reset before relock should work. Other says that rooting with magisk made the oem toggle usable again so that they could relock. You'll have to reflash firmware before ofc, cause you don't wanna get it locked with non signed code flashed to it
Let me know if you get it solved.

tys0n said:
Hi. I have relocked my bootloader twice but never seen anything like that.
A quick google suggests that a factory reset before relock should work. Other says that rooting with magisk made the oem toggle usable again so that they could relock. You'll have to reflash firmware before ofc, cause you don't wanna get it locked with non signed code flashed to it
Let me know if you get it solved.
Click to expand...
Click to collapse
Good Morning,
I don't know if I understood you well, I'm sorry, my English is not perfect.
First inform you, it is not essential to relock the bootloader. I just want to do it, to update via OTA.
If I can update it manually with the bootloader unlocked, I would not need to relock it.
Can I do it as you indicate in this post: https://forum.xda-developers.com/showpost.php?p=80903809&postcount=23?
I have not rooted the smartphone yet, I will do so soon as explained in this thread: TWRP 3.3.1 & Root for Moto 1 Vision
It occurs to me...
Do you think it would be fixed by reflashing the latest firmware again manually as you explain in this thread: [XT1970-X] Stock firmware share thread. [TOOL] fastboot flash / info
Regards

gonzo1963 said:
It occurs to me...
Do you think it would be fixed by reflashing the latest firmware again manually as you explain in this thread: [XT1970-X] Stock firmware share thread. [TOOL] fastboot flash / info
Regards
Click to expand...
Click to collapse
Good again
I've tried it, but it's still the same.
The same problem, still locked.
Regards

gonzo1963 said:
Good again
I've tried it, but it's still the same.
The same problem, still locked.
Regards
Click to expand...
Click to collapse
I really don't know as I don't have this problem.
View attachment 4907879
Have you tried full reflash with wipe, and then boot it and go through the setup so that it connects online?
Have you tried with root to see if the toggle gets enabled?

tys0n said:
I really don't know as I don't have this problem.
View attachment 4907879
Have you tried full reflash with wipe, and then boot it and go through the setup so that it connects online?
Have you tried with root to see if the toggle gets enabled?
Click to expand...
Click to collapse
Good morning,
I've only done a "factory setting", I don't know how to do a wipe and everything you tell me.
I hope to root the smartphone in the next few days! Another challenge!, hehe.
I hope I don't keep a brick.
I'll tell you how it goes
Regards and thanks
Enviado desde mi unknown mediante Tapatalk

Good afternoon,
I don't know how to do it: "full reflash with wipe, and then boot it and go through the setup so that it connects online?", maybe I've done it without knowing it.
Anyway something strange is happening, it is updated via OTA (PSAS29.160-55-7-1) although it has the bootloader locked.
Rooting is delayed due to a doubt: https://forum.xda-developers.com/showthread.php?p=81281003 until I solve it, I will not do it for fear of the brick.
Regards
Enviado desde mi unknown mediante Tapatalk

Good afternoon,
After rooting it, it seems that everything has been fixed.
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards
Click to expand...
Click to collapse
Did anyone find the solution to this problem?
I've tried everything, completely reflashing retail rom, retbr rom, installed magisk on an encrypted phone, on an unencrypted phone, erased the phone data, unerased... Every f*CK*NG thing and the switch is still grayed out...
I want to relock my bootloader but I just can't.... I don't know what to do anymore...
Can anyone help me?
Thanks a lot

Preceptor said:
Did anyone find the solution to this problem?
I've tried everything, completely reflashing retail rom, retbr rom, installed magisk on an encrypted phone, on an unencrypted phone, erased the phone data, unerased... Every f*CK*NG thing and the switch is still grayed out...
I want to relock my bootloader but I just can't.... I don't know what to do anymore...
Can anyone help me?
Thanks a lot
Click to expand...
Click to collapse
No idea why that is.
While rooted, I have no problems with the oem unlock toggle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my moto one vision.

tys0n said:
No idea why that is.
While rooted, I have no problems with the oem unlock toggle.View attachment 5047225
Sent from my moto one vision.
Click to expand...
Click to collapse
Not only that, I've rooted using different methods. Encrypted phone, not encrypted, old magisk, new magisk, and the list goes on. The oem unlock Is always grey...

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

Unlock E5 Play

Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.

vindy1099 said:
Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Most people with this device, just post in
https://forum.xda-developers.com/moto-e5
Unlocking the bootloader is fairly straightforward, and does not cause any of the issues you described.
Rooting can cause problems.
I suggest looking at the E5 section for current tooting method.
Did you buy the device new?
What do you get with fastboot getvar all ?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Most people with this device, just post in
https://forum.xda-developers.com/moto-e5
Unlocking the bootloader is fairly straightforward, and does not cause any of the issues you described.
Rooting can cause problems.
I suggest looking at the E5 section for current tooting method.
Did you buy the device new?
What do you get with fastboot getvar all ?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Thank for replying shadow. The phone is renewed (which I take to mean it was factory reset). You are right in that it may not have been the unlocking of the previous phone that caused me problems but what I did afterwards when trying to root it, and likely flashing the wrong ROM to it. The command "fastboot getvar all" when executed on the phone I am now using yields the following:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(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.396s
Any advice you may have would be good. I don't want to make another attempt at rooting until I am confident I have instructions I can follow to the letter and that I am highly confident are correct for my model phone (carrier issues considered). I will try to get this thread where you pointed me to in the xda fourms. I know reposting questions is frowned upon and I have never moved a thread before, but I should be able to figure it out. Thank you for your suggestions.