Related
I bought a Moto Z Play off of Swappa and it's arriving on Tuesday. I wanted to double check that the bootloader's locked to make sure that it wasn't loaded with any kind of keylogging software. The seller had photos of it still in the original packaging, but I'm paranoid, so I just wanted to make sure. If I do the volume down + power button method to go into fastboot, how will I know if the bootloader's unlocked? I've seen a few photos of the fastboot screen, and none of them seemed like they had that info.
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
the easyest way is to see if you getting 5 second warning on boot
Anyone else know where the info would be on the fastboot screen?
Xecu said:
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
Click to expand...
Click to collapse
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
defilip69 said:
the easyest way is to see if you getting 5 second warning on boot
Click to expand...
Click to collapse
Any idea what that warning looks like? Is it just the little unlocked lock icon?
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Xecu said:
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Click to expand...
Click to collapse
So, if the bootloader's locked, then phone should be safe for use, right? Or is there anything else the seller might've done to tamper with it?
Even if the bootloader is unlocked it could be safe.
Jimi Mack said:
Even if the bootloader is unlocked it could be safe.
Click to expand...
Click to collapse
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Bantersaurus said:
Anyone else know where the info would be on the fastboot screen?
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
Any idea what that warning looks like? Is it just the little unlocked lock icon?
Click to expand...
Click to collapse
before boot animation u have boot logo which have moto logo. if you have message like ... warning ... bla bla bla ... your phone is unlocked ... bla bla bla ... ( yellow triangle thing ) bla bla bla then is unlocked
Bantersaurus said:
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Click to expand...
Click to collapse
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
DroneDoom said:
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
Click to expand...
Click to collapse
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Bantersaurus said:
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Click to expand...
Click to collapse
I'd check the indication of an unlocked bootloader as others previously mentioned, look at what's prompted upon booting up the phone. If it was unlocked, the message is as clear as day that tells you it's unlocked. If they tried to cover that up you'd still see part of the message like "N/A" or "bad key" within the logo. That indication right there alone is suspicious. Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device.
If you don't see any indication of an unlocked bootloader, then I'd still wipe it through stock recovery and run an app that checks signature verifications and heuristics of malicious apps (Malwarebytes or some other antivirus app).
I forgot to mention the logos that are SUPPOSED to show on the device depending on what Android version it's on.
For marshmallow, you should see the white logo I've posted in attachments along with the indication I marked where you'll see text from the bootloader telling you that's unlocked if the seller tried to cover it up.
For nougat, the one with the aqua colored background and the indication I marked where the cover up text should be.
If there's nothing and the logo is "natural" looking and you don't see a message before the logo then your bootloader is probably locked.
Edit: sorry the indication for the nougat is slightly lower than where it needs to be. Should be on the same level as the marshmallow one.
DroneDoom said:
Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device..
Click to expand...
Click to collapse
I don't think there'll be anything installed (besides the possibility of malware). It's supposed to be a brand new, unopened phone that's still in the original packaging. It'd be too suspicious if there are apps already installed (besides bloatware that's on most phones).
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
I am asking because I'm interested in rooting this phone... But I am afraid that my phone will be forever stuck with a warning screen (similar to attached pic) that i cannot get rid of.. this would be troublesome if i do want to sell it...
if you have unlocked, and then relocked bootloader (with all stock images etc..) please tell me if any warnings remain,... thanks!
It'll go away once you relock the bootloader
Sent from my Pixel 3 XL using Tapatalk
Yes relocking the bootloader will prevent that warning from showing. Just be certain the device is 100% bone stock before locking the bootloader or you could risk being bricked.
fury683 said:
Yes relocking the bootloader will prevent that warning from showing. Just be certain the device is 100% bone stock before locking the bootloader or you could risk being bricked.
Click to expand...
Click to collapse
Risk? Its a for sure thing. Do NOT lock on any kind of custom ROM or any modifications. You need to be 100% stock before locking again or you will brick and not be able to recover
PhantomSoul said:
I am asking because I'm interested in rooting this phone... But I am afraid that my phone will be forever stuck with a warning screen (similar to attached pic) that i cannot get rid of.. this would be troublesome if i do want to sell it...if you have unlocked, and then relocked bootloader (with all stock images etc..) please tell me if any warnings remain,... thanks!
Click to expand...
Click to collapse
Even if you never root your phone, leaving your bootloader unlocked greatly increases your chances of recovering your phone from a no-boot situation because you can flash a complete factory image, rewriting the bootloader. If/when you ever decide to sell, you're going to want to wipe the entire phone anyway, and you can worry about it then. TBH, I don't even notice the warning anymore.
I do not want to relock my bootloader, but I want to get rid of the nag screen at boot that bootloader is unlocked. Just in case my phone will get into wrong hands that is like an open invitation to hack it.
I remember I used to replace this logo with a neutral black screen on one of my previous devices. Isn't that possible anymore nowdays?
Yes, I understand that is not a perfect security. A perfect security is if my phone will be kept in a safe in a swiss bank with keys lost. Just trying not to give obvious hints.
EDIT:
LOL sorry I don't know how but I missed first 8 words in Your post. Don't read my reply it won't help.
Hi.
I was converting from Tmobile to global. To get rid from that messege I simply locked the bootloader. I'm not sure if u want to lock it or you are looking for some kind of way around it. If you would like to do it remember its very important to do it after taking OTA otherwise you can have some problems with your phone. That was mine steps:
Unlock bootloader.
Flash global.
Do OTA.
Lock bootloader with "fastboot oem lock".
Hope it helps. Regards.
thardy00 said:
EDIT:
LOL sorry I don't know how but I missed first 8 words in Your post. Don't read my reply it won't help.
Hi.
I was converting from Tmobile to global. To get rid from that messege I simply locked the bootloader. I'm not sure if u want to lock it or you are looking for some kind of way around it. If you would like to do it remember its very important to do it after taking OTA otherwise you can have some problems with your phone. That was mine steps:
Unlock bootloader.
Flash global.
Do OTA.
Lock bootloader with "fastboot oem lock".
Hope it helps. Regards.
Click to expand...
Click to collapse
LOL, yeah! This happens
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
rockyrobin said:
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
Click to expand...
Click to collapse
Hi !
The best way is to download the zip of your European ROM from the Xiaomi site and try to install it from the update utility in your phone's settings. If that doesn't work, you'll have to unlock your bootloader, install the ROM you want with the flash utility, and choose the relock option before the install starts. Then you will be on an official Xiaomi ROM, with your bootloader locked and you will have updates from Xiaomi and no longer from your operator.
Bill
Hi,
I confirm that manually flashing the European ROM does not work (in my case at least), so I am stuck on MIUI 12.5.6 with RKOEUSF ROM.
If anyone finds a way to upgrade to the official version without unlocking the bootloader, and therefore not breaking the warranty, I would be grateful if you could share it.
Thanks
Hi !
From the moment you want to install a new ROM, you have no choice but to unlock your bootloader. You can then reblock it. Afterwards, I don't know if the warranty is impacted because you go through the official unlocking from Xiaomi.
Bill
Thanks Bill,
I've just tried flashing the zip of my ROM and the phone just quits the update after a long pause, saying that it cannot verify update.
Guess I'll have to unlock the bootloader. There's plenty of info about how to do this, but I've noticed a number of people complaining about the flash process.
When they apply the update, at the end they get an error message. The only way they get round this is with an edit of the settings of miflash.
Is this something I need to worry about?
Just been reading about these errors and it appears that they are caused by the path to the ROM file having too many characters.
Placing the ROM file in your C: folder solves this.