I have tried to flash back to stock firmware but i am unable to get play store to certify. I have an unlocked bootloader and am able to return to stock and update to the latest firmware but play store will not certify. From my understanding the bootloader being unlocked should not effect the certification so there must be another problem and as i cannot flash the full restore to stock due to unlocked bootloader, i am at a loss to know how to address the problem.
Has anyone been able to return to stock and obtain certified play store status?
Ok it seems I was wrong and unlocked bootloader is the problem. CTS profile mismatch. Whish I knew about this before I unlocked the bootloader.
Root with magisk and use magisk hide and you can have a certified play store again. It works for me.
Yes i have previously done this but now i wish to have a pure stock setup. Biggest Problem with this device is that we are not able to restore a full factory image without a locked bootloader.
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
jusx10i said:
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
Click to expand...
Click to collapse
I'd love any info on this as well.
Unfortunately, I just had to wait the week.
I will say though when you come to install TWRP make sure you follow the instructions. I didn't, then I had to wait another week for the OEM Unlock to re-appear again!
I recently had a stock Pixel 2 die, couldn't access anything to try and fix the problem because the I never allowed OEM unlocking, too bricked to access recovery or anything. To avoid this happening with my Pixel 2 XL, I want to unlock the bootloader just in case I need to flash anything to recover the device if something similar happens again. No interest in flashing anything custom anymore, can't be bothered to attempt to hide apps from root since I've had problems doing that in the past just to get my online banking to work.
My question is, will allowing OEM unlocking on a stock image stop anything like banking apps and Google Pay from working? I know a lot of these apps can detect root and stop themselves from working, but would this do the same with just allowing OEM unlock in the developer settings? I wouldn't unlock the bootloader through ADB until something goes wrong to begin flashing etc.
ridley1000 said:
I recently had a stock Pixel 2 die, couldn't access anything to try and fix the problem because the I never allowed OEM unlocking, too bricked to access recovery or anything. To avoid this happening with my Pixel 2 XL, I want to unlock the bootloader just in case I need to flash anything to recover the device if something similar happens again. No interest in flashing anything custom anymore, can't be bothered to attempt to hide apps from root since I've had problems doing that in the past just to get my online banking to work.
My question is, will allowing OEM unlocking on a stock image stop anything like banking apps and Google Pay from working? I know a lot of these apps can detect root and stop themselves from working, but would this do the same with just allowing OEM unlock in the developer settings? I wouldn't unlock the bootloader through ADB until something goes wrong to begin flashing etc.
Click to expand...
Click to collapse
I don't believe it will stop Google Pay from working, but have not tested it. As for other apps, it depends on whether that app checks for an unlocked bootloader. Some apps do check for unlocked bootloader.