Develop Bugs

Moto Z Play won't update help needed?

I apologise if I'm posting in wrong place. I really hope some one can help me. Last week I bought a Moto Z Play direct from Amazon UK.
I have taken it out of box and set it up but I'm having problems, firstly phone will not update it is stuck on android 6.0.1 when click system updates it says up to date no system updates available.
Secondly no Moto mods will work. When connect a mod to phone it says phone needs updating but can't update.
Thirdly android pay won't work. When try to set up it say android pay can not be used as device might be rooted, has a unlocked bootloader or custom ROM.
Here is some more information on phone
Model no - XT1635-02
Software Channel - retgb
Android Version - 6.0.1
Baseband Version is _ M8953_10208.08.04.48R ADDISON_ROW_CUST
Kernel Version [email protected]#1Mon Nov 7 04:18:00 CST 2016
Build No- MPNS24.104-49-4
I have asked on Lenovo forum and they say it sounds like phone has been flashed.
Looking at information above would you agree, does it look and sound like phone has been flashed.
Does any one know how I can update phone and get Moto mods working. Not so concerned about android pay although would be nice if worked.
I love phone and don't want to return if don't have too. But can't keep a phone if can't update and use mods designed for phone.
Any advice or help would be much appreciated
Thanks in advance

So you bought a brand new phone and haven't modded it at all, and it's saying it may be rooted? Download a root checked on play store to verify. But if you haven't modded the system at all then I'd return it and get another sent to you. You could try to bring it all back to stock but since you bought it recently the easiest option is to get yourself another.

andy55 said:
So you bought a brand new phone and haven't modded it at all, and it's saying it may be rooted? Download a root checked on play store to verify. But if you haven't modded the system at all then I'd return it and get another sent to you. You could try to bring it all back to stock but since you bought it recently the easiest option is to get yourself another.
Click to expand...
Click to collapse
I have downloaded and tried several root checkers from play store and they both say phone is not rooted so I'm confused.
Why would phone not be able to update, why would I get error message when try android pay saying can't use as phone might have been flashed etc. If phone is not rooted.
Any suggestions on how to fix

PinkBear154 said:
I have downloaded and tried several root checkers from play store and they both say phone is not rooted so I'm confused.
Why would phone not be able to update, why would I get error message when try android pay saying can't use as phone might have been flashed etc. If phone is not rooted.
Any suggestions on how to fix
Click to expand...
Click to collapse
The bootloader is probably unlocked, that's why Android Pay will not work. Does your WiFi work?, does the phone recognize the SIM card?

Guapo613 said:
The bootloader is probably unlocked, that's why Android Pay will not work. Does your WiFi work?, does the phone recognize the SIM card?
Click to expand...
Click to collapse
WiFi works fine and it recognises SIM card fine. Currently using a giffgaff SIM if it helps.
Just won't update and android pay won't work
Thanks

Okay, if your bootloader is unlocked, you will see a warning message when you boot up your phone,
I have a guide how to relock bootloader, and get ota updates. You could follow that one, if you dont wanna get a new phone.
Here is the link,
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Probably you need to unlock the bootloader.. (if its closed..)
Than flash twrp and a custom rom, after that. Follow my guide.
(You can pm me)
But! Your warranty will break if you unlock the bootloader,
So its maybe better to get a new moto z play.....

I'm hoping someone else can confirm this - the only information I can find for that build version is reports from US devices, suggesting that build was normally deployed in the US. https://forums.republicwireless.com/t/moto-z-play-system-update/336 https://www.reddit.com/r/Moto_Z/comments/5m1mps/us_unlocked_z_updates/
I'm having trouble finding references to this update being deployed in the UK on the retgb channel, so it may be that the device was somehow misflashed with a US firmware, hence the lack of updates. Do you see a bootloader unlocked screen by the way when you turn the device on? I'm surprised this would have come from Amazon UK though, unless it was a return (but then they surely would have mentioned that).
I was wondering, if you'd be able to grab the getvar all data from your device please?
1)Install the minimal ADB tools if you don't have them: https://forum.xda-developers.com/showthread.php?t=2317790
Also would be worth installing the Motorola device tools https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27,
2)Boot your device to the bootloader (power off your device, then hold down the volume down and power key until your device boots). Connect your device to your computer via USB.
3)Open your ADB terminal, and verify your device is communicating via fastboot by typing 'fastboot devices' without quotes into the terminal. You should see your device respond with its serial number.
3a)If you see a response, then type 'fastboot getvar all' without quotes and you should see an output of your device variables. Please copy and paste that output here in a post, you may wish to omit your IMEI numbers.
If you see 'waiting for device' in ADB, check if you have driver signature enforcement disabled in Windows 8.1/10 or that the fastboot drivers are correctly installed.
Hopefully the Motorola staff in the Motorola forums can help you too.

Thank you all for your advice. It is not showing bootloader error when powering on phone. Phone boots and loads just fine no errors. I don't have a usb able at moment to connect it to computer but have just ordered one to come tomorrow. So will try and connect phone to computer and get the getvar data tomorrow and will update you.

PinkBear154 said:
Thank you all for your advice. It is not showing bootloader error when powering on phone. Phone boots and loads just fine no errors. I don't have a usb able at moment to connect it to computer but have just ordered one to come tomorrow. So will try and connect phone to computer and get the getvar data tomorrow and will update you.
Click to expand...
Click to collapse
Cool!

getvar all data
I have just connected phone to computer and can confirm that it is communicating via fastboot. Here is getvar all data. Please advice me on what to do next.
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 2DBC2AB700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **********
(bootloader) meid:
(bootloader) date: 09-10-2016
(bootloader) sku: XT1635-02
(bootloader) battid: SNN5975A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 4:52:52 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/addison/addison:6.0.1/MPN
(bootloader) ro.build.fingerprint[1]: S24.104-49-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.addison.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.3-04710-89xx.0
(bootloader) version-baseband: M8953_10208.08.04.48R ADDISON_ROW_CUST
(bootloader) kernel.version[0]: Linux version 3.18.24-perf-g649f0b1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Mon Nov 7 04:18:00 CST 2016
(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 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb

I says it unlocked
(I'm not sure)

PinkBear154 said:
I have just connected phone to computer and can confirm that it is communicating via fastboot. Here is getvar all data. Please advice me on what to do next.
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 2DBC2AB700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **********
(bootloader) meid:
(bootloader) date: 09-10-2016
(bootloader) sku: XT1635-02
(bootloader) battid: SNN5975A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 4:52:52 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/addison/addison:6.0.1/MPN
(bootloader) ro.build.fingerprint[1]: S24.104-49-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.addison.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.3-04710-89xx.0
(bootloader) version-baseband: M8953_10208.08.04.48R ADDISON_ROW_CUST
(bootloader) kernel.version[0]: Linux version 3.18.24-perf-g649f0b1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Mon Nov 7 04:18:00 CST 2016
(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 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
Click to expand...
Click to collapse
Thanks for the getvar info, it's useful info.
1)Despite receiving the device as new from Amazon UK, the bootloader is reporting that the device has an unlocked bootloader: (bootloader) securestate: flashing_unlocked . Normally, on a new device straight from Motorola or Amazon, you'd see OEM_locked and not flashing_unlocked. This is likely why you don't have Android Pay. Unless Amazon or someone unlocked the bootloader, this appears to be as a result of (a previous owner?) the unlock key being requested against the device. I honestly don't know if there's a way to unlock a bootloader without requesting an unlock key from Motorola...
2)With the bootloader unlocked, the warranty associated with this device is voided, as reflected by the (bootloader) iswarrantyvoid: yes flag (which is a shame, as if this was a properly brand new device, it'd have 2 years warranty with Motorola as is now standard with UK and EU devices - https://help.motorola.com/hc/apps/settings/legal/global/en-gb/index.html?t=T1507061106 ) . It's possible any repairs would require the device IMEI being checked, and it may show up in Motorola's database that this device has a voided warranty.
3)As mentioned before, looks like you have the US retail firmware on your UK device. Furthermore, your bootloader version and stock ROM version do not appear to match. Your bootloader C1:07 appears to correspond with the April 2017 Nougat NPNS25.137-24-1-9 yet you have a Marshmallow system which appears to be the November 2016 security update. Attempting to take an OTA update with a mismatched bootloader and system (especially a newer bootloader than the system) is likely going to result in a nasty hard brick, where your device fails to boot and function at all. This normally requires a blankflash to resolve.
EDIT - one more thing, do the IMEI numbers on your device match the IMEI number written on the box?
Overall, this device doesn't seem to be in a good state for being supposedly new. Though this is conjecture, the evidence suggests that the previous owner unlocked the bootloader, then flashed a Moto Z Play firmware (e.g. from here https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/ ), perhaps in an attempt to get US radio bands? As there's no bootloader unlocked screen - possibly from a custom logo flash - they may have been able to return the device to Amazon UK without questions. I still am confused how this device was sold as new, despite the getvar all info indicating this device is anything but new. I'm sorry, I don't like to be the breaker of bad news.
Off the top of my head, you have a few options:
a)Return the device to Amazon, exchange it for a new device. When you receive the device, check the fastboot getvar all info again. If this is genuinely new, you should see OEM_locked under (bootloader)securestate and of course your warranty should be intact. Your Moto Mods and Android Pay should also start working.
b)Keep the device and attempt to flash the Nougat stock fastboot ROM. I'm not familiar with Moto Z Play firmware (no thanks to Motorola's naming convention), but the NPNS26.118-22-1 Android 7.1.1 stock ROM should suffice. I'm hoping someone else can confirm that this firmware was deployed to retGB (I've seen it on retEU), as Motorola seems to have a habit of deploying different firmwares to different retail channels - I do not know if this applies to Moto Z Play devices recently, or if Motorola has unified its firmware builds.
By flashing this, you should bring your device up to the same patch level (rather than having a new bootloader/old system), and also if the build is deployed for retGB/retEU, you should start getting OTA updates. This process of flashing should also wipe your device clean, for a fresh start. Depending on the source of the stock ROM (as these stock firmwares are leaked), if they have been signed with the correct cryptographic keys, you could also lock your bootloader, which should also give you Android Pay and Safetynet passing (if Safetynet does not pass, some apps from the Play Store may not work). Alternatively, you could keep your bootloader unlocked and root with magisk, which may let you pass Safetynet and use Android Pay. Either way, you'd also be updated to a newer stock ROM than you had and should be able to use Moto Mods.
If you choose to flash, you'll likely want the NPN26.118.22-1 August 2017 stock firmware - here's a download repository here: https://firmware.center/firmware/Motorola/Moto Z Play/Stock/ As I'm not fully familar with Z Play flashing, you could use the firmware flashing instructions here to flash this stock ROM https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190 The fastboot flash should occur as you're flashing stock ROM firmware, regardless of whether you had a custom ROM or stock ROM previously. The first set of commands should flash the stock firmware onto your device, the second set should lock your bootloader (though locking if you're already on stock firmware seems to require enabling OEM unlocking under Settings>Developer Options). The major point to not flash stock firmware older than the stock firmware on your device.
Bear in mind, if you do decide to keep the device, you may not have a warranty, as the warranty may have been with the original owner, who voided the Motorola warranty. I'm not sure if Amazon UK will still honour the warranty despite selling the device as reportedly new, especially now the device bootloader is unlocked (through no fault of your own), so any issues you may encounter later on with the device might be troublesome to resolve. I'm hoping UK distance selling/consumer laws will cover you for at least 2 years, but might be worth getting clarification from Amazon and Motorola, in case you have to pay for repairs. Just a thought, Motorola may be able to check when the bootloader unlock key was requested against your device's IMEI, and thus you could have that as evidence that you did not unlock the device bootloader (if you've got the paperwork that says you got the device long after the unlock key was requested). Again, I'd seek advice from Amazon UK. If you're concerned about repairs/warranty, then the easiest thing would be to exchange the device for a brand new one.
Good luck whatever you decide.

If you choose to keep the phone! I know how to get him locked again. You will get ota's again
Your own choice
Pm me if you need help

Hi every one,
I tried to return phone but, amazon are refusing to take it back accusing me of tampering with phone which I had not. So as it looked like I was stuck with phone I decided to follow instructions above, and reflashed phone and locked boot loader..
This worked really well and have been able to get ota updates, got my moto mods working and even android pay was working.
I was really pleased and thought I had put this nightmare behind me. But after 2 days of working fine phone has started to play up. It started with error messages that certain apps had stopped working. Then in the middle of watching a YouTube video phone crashed and phone restarted. It rebooted but then started showing more error messages, first play services keeps stopping, the play store topped responding, NFC keeps stopping, gboard keepes stopping. The error messages were constantly popping up so could not do any thing.
Tried restarting phone and it got stuck in a boot loop and would not load. Did a factory reset and am able to boot phone but phone still is having these error messages and phone frequently crashes and restarts. The strange thing is if I start phone in safe mode it seems to work fine, no error messages, no crashing. So I don't understand what is causing phone to be so unstable. I have not installed any apps since factory reset. So only apps are the pre installed ones..
Any one got any idea what's going on. It there any way to fix it. I'm pulling my hair out here. I only bought phone as need a reliable phone with good battery life for when my youngest son goes in to hospital to keep in touch with people. I feel like I've wasted my money.
Please some one help

PinkBear154 said:
Hi every one,
I tried to return phone but, amazon are refusing to take it back accusing me of tampering with phone which I had not. So as it looked like I was stuck with phone I decided to follow instructions above, and reflashed phone and locked boot loader..
This worked really well and have been able to get ota updates, got my moto mods working and even android pay was working.
I was really pleased and thought I had put this nightmare behind me. But after 2 days of working fine phone has started to play up. It started with error messages that certain apps had stopped working. Then in the middle of watching a YouTube video phone crashed and phone restarted. It rebooted but then started showing more error messages, first play services keeps stopping, the play store topped responding, NFC keeps stopping, gboard keepes stopping. The error messages were constantly popping up so could not do any thing.
Tried restarting phone and it got stuck in a boot loop and would not load. Did a factory reset and am able to boot phone but phone still is having these error messages and phone frequently crashes and restarts. The strange thing is if I start phone in safe mode it seems to work fine, no error messages, no crashing. So I don't understand what is causing phone to be so unstable. I have not installed any apps since factory reset. So only apps are the pre installed ones..
Any one got any idea what's going on. It there any way to fix it. I'm pulling my hair out here. I only bought phone as need a reliable phone with good battery life for when my youngest son goes in to hospital to keep in touch with people. I feel like I've wasted my money.
Please some one help
Click to expand...
Click to collapse
Wow thats weird... What is your software channel?

Software channel is retgb

PinkBear154 said:
Software channel is retgb
Click to expand...
Click to collapse
Hmm, can you try a full reflash of the stock firmware, please? If you post your build number here (when the device isn't crashing on you) we can try to provide the same build if you've since updated.
Is this crashing occurring with no SIM and no SD cards in place?
I'm concerned that Amazon regard this as not their issue, though - how are they determining the device was modified, any ideas?
If a reflash doesn't fix the issues, you may have to submit your device for a service/hardware repair. At least in the UK/EU, even though the Motorola warranty is void, you could argue to Amazon - under the Consumer Rights Act - that the device was not as described (described as new, but getvar info suggests previously unlocked bootloader, though you may have to present proof either way), and that the device is not of satisfactory quality (you don't expect a new device to exhibit this behaviour), and seek a repair or replacement: http://www.legislation.gov.uk/ukpga/2015/15/contents/enacted This may work as you have a contract with Amazon when you bought the device.
EDIT - Citizen's Advice on the matter: https://www.citizensadvice.org.uk/c...ne-wrong-with-a-purchase/return-faulty-goods/

Hi sorry have been out all day so have not been able to reply before now.
Build NO is
NPNS26.118-22-2-12
I have not tried taking SIM card out but will try in a minute and see how phone behaves and will let you know. I don't currently have a memory card for phone so have been using without a memory card.
Thanks again

Download stock firmware with Lenovo Moto Smart Assistant

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

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

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

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

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

Can i use this while currently on custom 8.1 rom?

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

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

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

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

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

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

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

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

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

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

Does this work on Rooted device?

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

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

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

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.

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

Firmware for XT1789-05 / M29E1

Hi all,
I recently bought an XT1789 from the US planning to use it in Germany.
The SKU is XT1789-04.
Next to the USB C port, however, it says "Model: XT1789-05, Type: M29E1"
Software variant: tmo
Software channel: tmo
Baseband: M8998TMO_20207.117.02.41.04R NUS
Build-Number: OCXS27.1.4
I wanted to get rid the T-Mobile branding and also update it to Android 9 (Pie).
So as a first step I unlocked the bootloader which gave me the well-known "Your device software can't be checked for corruption..." message on startup.
Then I installed the latest official RETEU SW.
As you can imagine, the mobile connection couldn't be established anymore after that. WiFi kept on working.
I also tried RETEU with NON-HLOS.bin from the latest TMO (Oreo) which also didn't work.
Flashing the latest RETAIL (Pie) with and without NON-HLOS.bin from the latest TMO (Preo) didn't work as well.
I also considered flashing the complete TMO SW but wasn't sure whether this would brick my phone completely.
I couldn't find any other threads dealing with my combination of SW/HW or maybe I wasn't able to completely follow.
Now I would like to understand what I need to do in order to make the phone work again.
Any hint is appreciated.
----
Update: I installed XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip and the baseband info is back.
However, now the SIM card I inserted before updating the device, will not connect to the network anymore.
It seems the device is network locked, at least it is not able to connect to any of the listed networks when invoking a manual search.
Since it used to work with that SIM I guess it used to be unlocked and is now locked again due to the flashing procedure.
Any ideas what else to do?

RaminJ said:
Hi all,
I recently bought an XT1789 from the US planning to use it in Germany.
The SKU is XT1789-04.
Next to the USB C port, however, it says "Model: XT1789-05, Type: M29E1"
Software variant: tmo
Software channel: tmo
Baseband: M8998TMO_20207.117.02.41.04R NUS
Build-Number: OCXS27.1.4
I wanted to get rid the T-Mobile branding and also update it to Android 9 (Pie).
So as a first step I unlocked the bootloader which gave me the well-known "Your device software can't be checked for corruption..." message on startup.
Then I installed the latest official RETEU SW.
As you can imagine, the mobile connection couldn't be established anymore after that. WiFi kept on working.
I also tried RETEU with NON-HLOS.bin from the latest TMO (Oreo) which also didn't work.
Flashing the latest RETAIL (Pie) with and without NON-HLOS.bin from the latest TMO (Preo) didn't work as well.
I also considered flashing the complete TMO SW but wasn't sure whether this would brick my phone completely.
I couldn't find any other threads dealing with my combination of SW/HW or maybe I wasn't able to completely follow.
Now I would like to understand what I need to do in order to make the phone work again.
Any hint is appreciated.
----
Update: I installed XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip and the baseband info is back.
However, now the SIM card I inserted before updating the device, will not connect to the network anymore.
It seems the device is network locked, at least it is not able to connect to any of the listed networks when invoking a manual search.
Since it used to work with that SIM I guess it used to be unlocked and is now locked again due to the flashing procedure.
Any ideas what else to do?
Click to expand...
Click to collapse
I think you ruined the baseband...
The best bet is to flash the blankflash...
Sent from my moto g(7) supra using Tapatalk

You have a lot of conflicting info. TMO isn't on the -05 variant, it's on the -04
A quick search for XT1789-05 / M29E1 suggests it may be a RETIN device, so you might try flashing RETIN pie firmware since reteu and retail didn't work.

First of all I want to thank both of you for taking the time to answer.
cgigate said:
I think you ruined the baseband...
The best bet is to flash the blankflash...
Sent from my moto g(7) supra using Tapatalk
Click to expand...
Click to collapse
Are you sure about that?
After flashing XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU to both slots the WiFi works and networks are found. However, it cannot register to any network.
Of course I tried different SIMs.
I have the impression that the device is provider locked again.
At least this would explain why it detects the SIM, prompts for the PIN but is not able to register.
I guess it is impossible to unlock unless the device is connected to the T-Mobile network in the US.
41rw4lk said:
You have a lot of conflicting info. TMO isn't on the -05 variant, it's on the -04
A quick search for XT1789-05 / M29E1 suggests it may be a RETIN device, so you might try flashing RETIN pie firmware since reteu and retail didn't work.
Click to expand...
Click to collapse
I am confused as well. While XT1780-05 / M29E1 is written next to the USB port, the label on the packaging says XT1789-04(,RETAIL,LIC).
Are you suggesting to try a flashall with RETIN fw including modem (NON-HLOS)?

You've flashed pie, so there is no going back to oreo. I have a TMO and it is an xt1789-04 (ATT is -04 too). Since it says -05 on the phone itself it's international, meaning it is used in a few different countries so finding the correct firmware will be a challenge since you have no way of knowing what the original software channel was. India and Brazil use the -05 I believe and their firmware is almost identical except the modems. A quick search brought up India, so I would start with a RETIN pie firmware.

41rw4lk said:
You've flashed pie, so there is no going back to oreo. I have a TMO and it is an xt1789-04 (ATT is -04 too). Since it says -05 on the phone itself it's international, meaning it is used in a few different countries so finding the correct firmware will be a challenge since you have no way of knowing what the original software channel was. India and Brazil use the -05 I believe and their firmware is almost identical except the modems. A quick search brought up India, so I would start with a RETIN pie firmware.
Click to expand...
Click to collapse
Are you referring to the software channel the device was shipped with?
If so, it used to be tmo as can be seen in the following screenshot I took before starting flashing the device:
link to the screenshot (G Drive)
The phone itself was shipped from Toronto, Canada (at least according to the details on ebay).
Do you recommend flashing all files from RETIN, including the modem?

RaminJ said:
Are you referring to the software channel the device was shipped with?
If so, it used to be tmo as can be seen in the following screenshot I took before starting flashing the device:
link to the screenshot (G Drive)
The phone itself was shipped from Toronto, Canada (at least according to the details on ebay).
Do you recommend flashing all files from RETIN, including the modem?
Click to expand...
Click to collapse
You may have gotten it with TMO software, but that isn't a TMO variant. My best guess is RETIN, though it could be RETBR or something else. Not to mention whatever carrier you plan on using, it might not jive with whatever firmware is supposed to be on there. Your first goal however should be to find the correct firmware and make sure wifi, mobile, and all that works. I would try to avoid the latest version of whatever firmware you flash since you don't want an nv value you can't overwrite.

41rw4lk said:
You may have gotten it with TMO software, but that isn't a TMO variant. My best guess is RETIN, though it could be RETBR or something else. Not to mention whatever carrier you plan on using, it might not jive with whatever firmware is supposed to be on there. Your first goal however should be to find the correct firmware and make sure wifi, mobile, and all that works. I would try to avoid the latest version of whatever firmware you flash since you don't want an nv value you can't overwrite.
Click to expand...
Click to collapse
Well, in that case someone has made a big effort flashing TMO software and sealing the package perfectly afterwards
Since the device came along with a US type power plug I'll go with XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC first I guess.

Update:
No WiFi, SIM not detected with both,
XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC and
XT1789-05_NASH_RETBR_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Flashed both slots back to XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU --> WiFi works again, SIM is detected (but not registered to any network)

@cgigate I am not able to enter EDL mode otherwise I would have tried it.
Doesn't matter if I try it via adb or via twrp it will always reboot without entering EDL mode.
I even tried building an EDL cable but this also doesn't help.
@41rw4lk I found another post where you stated that having flashed a pie modem on a variant that never received pie (TMO) would finally make the phone unusable for mobile networks. It is still not comprehensible for me why with the latest TMO software flashed mobile networks are found. I also never paid attention to the writing on the screen protector saying "4G LTE SIM pre-installed". When trying to manually select a provider the phone will reply that the SIM cannot be registered to that network. It's as if there was an internal SIM that is being registered to the network instead of the inserted one.

The long and short of it is, you have a mutt and nothing going for you. You say it has XT1789-05 stamped by the charging port, then it is definitely not a TMO variant. It may have TMO firmware flashed on it, but who knows what the user before you did. Another thing, what provider are you trying to use? I noticed you tried RETBR, but not RETIN, why? Honestly there are a few different providers for the 05 variant, which one is correct? I don't know. That's a common problem around here, people flash things off the cuff and have no idea what they're flashing nor do they ever know what was original. Then they do dumb things like lock the bootloader thinking that it's some magic fix, it's not. DO NOT relock your bootloader for any reason.
Go to fastboot and post the output of this command.
fastboot getvar all

@41rw4lk, thanks for taking the time, I really appreciate that!
I really wonder why the label on the package says XT1789-04. The IMEI on said label is identical to the one read out in the device. However, XT1789-05 is stamped by the charging port.
From what I can tell (having checked all available variants on lolinet) the following ones have "XT1789-05*" in their names:
AMXBR
AMXCO
AMXLA
AMXMX
OPENMX
RETBR
RETLA
TEFBR
TIMBR
Versions I tried so far without luck:
XT1789-06_NASH_RETIN_8.0.0_OPXS27.109-49-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC
--> no WiFi
--> Bluetooth OK
--> SIM not detected
--> fb: baseband not found
XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
--> WiFi OK
--> SIM detected, not registered to network
--> fb: baseband M998_50.71.02.95M NUS
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU
--> WiFi OK
--> SIM detected, not registered to network
--> fb: M8998TMO_2027.117.02.41.08R NUS
XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC
--> no WiFi
--> SIM not detected
--> Bluetooth OK
--> fb: baseband not found
XT1789-05_NASH_RETBR_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC
--> boot loop
--> SIM detected --> bootloop
--> reflash
--> WiFi OK
--> SIM detected
--> BT OK
--> fb: M8998_50.71.02.95M NUS
NASH_RETAIL_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CF
--> WiFi OK
--> SIM detected
--> no networks found
--> fb: baseband not found
XT1789-05_NASH_RETLA_DS_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC
XT1789-05_NASH_RETLA_SS_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC
--> with both the system will come up as Dual SIM device
--> dual SIM config: SIM detected but not registered
--> manually patched to single SIM --> same behavior
--> WiFi OK
--> BT OK
--> fb: M998_52.74.02.96M NCD
Whatever version I try, flashing XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU afterwards at least allows me for listing available networks again.
'fastboot getvar all' output:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: CHINA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224TK6CL
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 4308BFDA
(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: *************** (same as on package but hidden here)
(bootloader) meid:
(bootloader) date: 02-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4381
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-23/
(bootloader) ro.build.fingerprint[1]: 113ea:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.23.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: M8998_52.74.02.96M NCD
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Jul 5 09:27:21 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.190s
By the way, in a few days I will get another one of these devices. Chances are that the same SW is installed.
Would it be helpful to read out said device's config/software?

You've got a mess. Your output looks like 3 different firmwares jumbled together. You're flashing 06 firmware for some odd reason, and despite it all you still have TMO pieces in there. Flashall.bat files are not universal, while one might flash TMO, it won't flash everyone firmware completely.
Everything about this phone is suspect. You say you bought from US, but it shipped from CA, you're in Germany and it has TMO on a non US variant 05. You should try plain old RETAIL and make sure the flashall you have is for retail firmware. That phone reminds me of the coolicool phones they always shipped with the wrong firmware and the solution was typically to flash the correct firmware (RETAIL).

I actually do generate the flashfiles for each firmware using FlashAll utility as described in this post.
Is there another FlashAll out there I am not aware of?

RaminJ said:
I actually do generate the flashfiles for each firmware using FlashAll utility as described in this post.
Is there another FlashAll out there I am not aware of?
Click to expand...
Click to collapse
There is a flash file in each firmware package
Sent from my LG-LS997 using Tapatalk

41rw4lk said:
The long and short of it is, you have a mutt and nothing going for you. You say it has XT1789-05 stamped by the charging port, then it is definitely not a TMO variant. It may have TMO firmware flashed on it, but who knows what the user before you did. Another thing, what provider are you trying to use? I noticed you tried RETBR, but not RETIN, why? Honestly there are a few different providers for the 05 variant, which one is correct? I don't know. That's a common problem around here, people flash things off the cuff and have no idea what they're flashing nor do they ever know what was original. Then they do dumb things like lock the bootloader thinking that it's some magic fix, it's not. DO NOT relock your bootloader for any reason.
Go to fastboot and post the output of this command.
fastboot getvar all
Click to expand...
Click to collapse
If relock bootloader there's nothing else to do?

@cgigate In my understanding there is a flashfile.xml that has to be converted into a batch file for fastboot usage. Please let me know if there is another method. I checked available flashall batch files. I couldn't find real differences to the generated ones. Please correct me if I'm wrong.

RaminJ said:
@cgigate In my understanding there is a flashfile.xml that has to be converted into a batch file for fastboot usage. Please let me know if there is another method. I checked available flashall batch files. I couldn't find real differences to the generated ones. Please correct me if I'm wrong.
Click to expand...
Click to collapse
Rootjunkys tool is good, as long as you are creating the bat file from the firmware you are using, and not reusing bat from old firmware.
You could try
Code:
fastboot erase all
Before flashing
Sent from my ali using XDA Labs

sd_shadow said:
Rootjunkys tool is good, as long as you are creating the bat file from the firmware you are using, and not reusing bat from old firmware.
You could try
Code:
fastboot erase all
Before flashing
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thanks but had no luck with erase all command on Retail or TMO Firmware.
I will soon get access to a working TMO device. Is it possible to get any information out of it that could help reviving my phone again?

Hey, sorry if it's unrelated to this, but can someone teach me how to flash this Firmware?
I actually require the same version he is looking for.
PM me if you are willing to do so, please... I just need it back functional again instead of it showing a "corrupt" notice.
Thank you!