Related
Is there then an easy way to relock the bootloader and wipe any trace of it ever being unlocked?
I know I sound a bit paranoid, but what if I need to send it in for a warranty-related problem?
I got my phone today and was actually a tad disappointed over it being "Samsung-branded" with the yakjuxw-build. One would think it would be entirely managed by Google with it being a Google phone and all.
use the gnex toolkit to flash to google version, then use it to relock bootloader. 10 min thing
Sent from my Galaxy Nexus using XDA Premium HD app
If you care about voiding the warranty, then I would recommend that you do the following BEFORE unlocking your bootloader:
Plug it into USB, reboot into bootloader.
Type "fastboot getvar all".
You'll probably see a variable called "unlocked" which would be set to "no" or "0". See if there are any variables listed there that talk about warranty. If there are, then I wouldn't recommend unlocking because even if you re-lock the bootloader, they'll know it was unlocked at some point.
I know that this was not an issue on the Nexus S (also made by Samsung). You could re-lock the bootloader and nobody would be any the wiser.
The reason I suggested you try it was because of the Motorola Xoom (which of course is another Google Experience device with an unlockable bootloader). On all Xoom bootloaders, there's the standard "unlocked" bootloader variable, but also an additional one called "IsWarrantyVoid". From the factory, both bootloader variables are set to "no". As soon as you unlock the bootloader for the first time, both variables are set to "yes". If you then go and lock it again, "Unlocked" gets set to "no", but "IsWarrantyVoid" remains "yes" and there's nothing you can do to change it.
So I think you're OK because this is a Samsung device, but just double check it before you unlock the bootloader. If you don't see any kind of bootloader variable pertaining to warranty, I say go for it. I did a quick check of bootloader variables on my LTE Gnex and didn't see anything suspicious, but it sounds like you have a GSM version, so you should check yourself just to be absolutely sure.
< waiting for device >
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.006s
I dared to unlock the bootloader and flash yakju 4.0.2. I mainly flashed 4.0.2 too see if OTA's work and they seem to. Got a small 8mb update but no .3 or .4 as of yet. Gonna check tomorrow morning, though. It's 10.40 pm here.
When on 4.0.4, I'll root.
I couldn't even stay from tampering with my 7 hours old phone, lol. Let's just hope I won't need any repairs. ^^
Sent from my Galaxy Nexus using Tapatalk 2
JaiaV said:
< waiting for device >
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.006s
Click to expand...
Click to collapse
Hmm..."secure" worries me. I'm sure this is a stupid question to ask at a place like XDA, but does anyone have a GSM Gnex that has NOT been unlocked yet? Can you tell us the value of "secure"? I went back and checked on my LTE Gnex and it's there and also set to "no". I missed that one the first time around.
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.007s
Secure flag doesn't reset when re-locked.
Theshawty said:
Is there then an easy way to relock the bootloader and wipe any trace of it ever being unlocked?
I know I sound a bit paranoid, but what if I need to send it in for a warranty-related problem?
I got my phone today and was actually a tad disappointed over it being "Samsung-branded" with the yakjuxw-build. One would think it would be entirely managed by Google with it being a Google phone and all.
Click to expand...
Click to collapse
Unlock, flash temp Clockwork, make backup, done.
Just restore that backup and you'll be back to yakjuxw. Reboot after restore to remove temp Clockwork, then relock bootloader. Good as new.
P.S. might be a good idea to note the radio your phone came with, in case you flash a different one. Clockwork does not backup radio, so you'll just need to flash the radio before restoring to stock.
Sent from my Galaxy Nexus
JaiaV said:
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.007s
Secure flag doesn't reset when re-locked.
Click to expand...
Click to collapse
Yes, which makes me wonder if it's set to "yes" out of the factory, then set to no upon first unlock. "Secure" reeks of being Samsung's version of Motorola's "IsWarrantyVoid".
I'm sure most of us here at XDA unlocked our bootloader the day we got the phone even if we ended up re-locking it a day later. I'm hoping that someone has a girlfriend or parents or somebody that has a Galaxy Nexus that's never been unlocked in order to check the value of that "secure" variable.
secure is basically another way of telling if the bootloader is secure, it's nothing to get scared over
So does it come from the factory set to no?
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Yes, which makes me wonder if it's set to "yes" out of the factory, then set to no upon first unlock. "Secure" reeks of being Samsung's version of Motorola's "IsWarrantyVoid".
Click to expand...
Click to collapse
On HTC devices, the secu_flag (or secure flag) is what dictates if the bootloader is re-lockable. If the flag is set to 1, you cannot re-lock the bootloader; if it is set to 0, you can. I'm just speculating here, but it may be similar on a Samsung device. Confirmation would be needed of course.
That's great info to know. Thanks!
Sent from my Galaxy Nexus using Tapatalk 2
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
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(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: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s
wtf xda turned some of it into emojis
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options
41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.
vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work
vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options
vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs
vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2
41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow
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
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