Develop Bugs

Unlocked and rooted security question

Is it ok to pay bills, check bank account etc on a device that's unlocked and rooted? Or once you do that to the device you loose all security?
Thanks
Sent from my Pixel XL using XDA-Developers Legacy app

jblack41510 said:
Is it ok to pay bills, check bank account etc on a device that's unlocked and rooted? Or once you do that to the device you loose all security?
Thanks
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I wouldn't do it, at least not outside my home wifi. Your bank probably has certain protections but your data is exposed if you lose the device or it gets stolen. That being said, I have done it with no untoward effects, but that was before hacking became so prevalent. Be curious to see what others have to say.

So it's only really a threat if I loose my device?
Is there any security issue using while in possession of the device?
Sent from my Pixel XL using XDA-Developers Legacy app

jblack41510 said:
So it's only really a threat if I loose my device?
Is there any security issue using while in possession of the device?
Click to expand...
Click to collapse
Root is not an additional threat if you lose your phone. If you lose your phone to a pro you are toast, root or not. If they are not a pro root makes zero difference. Assuming you have a pin password on the phone. If you don't you are of course toast.
The danger of root is you. If you muck it up by installing unknown software, turning off encryption, stuff like that...that is where you will get in trouble.

Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Sent from my Pixel XL using XDA-Developers Legacy app

jblack41510 said:
Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've always been rooted and I use banking and pay apps on occasion, I mean all this is anecdotal so take it with a grain of salt because we can't predict the future of what exploits bring and no one knows your habits when it comes to mobile devices.
I dont put a lot of stake in to those apps you mentioned, they make money off of fear.
Keep your device up to date, don't download programs you are uncertain of, make sure you have a lock screen and pattern. At this point its a difference of 6 or 7 pad locks on the front door.

V
jblack41510 said:
Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Click to expand...
Click to collapse
I dont consider those apps to be unknown. They come from here, have been around forever and are very popular. Adaway was on the store until Google changed the rules.
Based on what you are doing you are fine..
And I agree with thw poster above, the commercial security programs are next to useless.
And keep your phone up to date. A phone not up to date on security patches scares me far more than a rooted phone.
Do your thing you are fine.

TonikJDK said:
Root is not an additional threat if you lose your phone. If you lose your phone to a pro you are toast, root or not. If they are not a pro root makes zero difference. Assuming you have a pin password on the phone. If you don't you are of course toast.
The danger of root is you. If you muck it up by installing unknown software, turning off encryption, stuff like that...that is where you will get in trouble.
Click to expand...
Click to collapse
How are you toast with a locked bootloader, pin startup? Pro or not. Unlocked bl, flash without data wipe -w, and data is exposed. Most don't use a startup pin. I'm not questioning your knowledge just looking for the explanation.
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
How are you toast with a locked bootloader, pin startup? Pro or not. Unlocked bl, flash without data wipe -w, and data is exposed. Most don't use a startup pin. I'm not questioning your knowledge just looking for the explanation.
Click to expand...
Click to collapse
What do you mean most don't use a start up pin? You set a pin/pattern period and the device is encrypted.
That means even if I flash factory without the -w my device won't let me in without me using my pin or pattern. Maybe I am missing some thing? Of course I flash this thing at least once every 60 days and I have literally had the same pin since my first boot up when it encrypted the file system.
Even of you reset the device unless you have the email for the original owner you can't get in.

I should have been more clear when I said 'pro'. I mean a real pro. Hackers got into a locked iPhone in the San Bernardo shooter case. Those same hackers took a run at Android and found a way to hijack an MDM system and remotely reset the pin. None of us need to worry about those kinds of attacks if we lose our phone, but the bottom line is that if you lose physical control of any device, phone, computer, tablet, your data is toast if the right person takes a run at it.

pcriz said:
What do you mean most don't use a start up pin? You set a pin/pattern period and the device is encrypted.
That means even if I flash factory without the -w my device won't let me in without me using my pin or pattern. Maybe I am missing some thing? Of course I flash this thing at least once every 60 days and I have literally had the same pin since my first boot up when it encrypted the file system.
Even of you reset the device unless you have the email for the original owner you can't get in.
Click to expand...
Click to collapse
I'm not 100% on this so bear with me. I was under the assumption that with an unlocked bootloader FRP (factory reset protection) was non functional. By startup pin I meant there is an option when setting a pin to either have it ask for the pin before anything at all happens and one to get into the device once it boots up. Most people use the latter but not the former because it's a pain. Personally, I set both with a locked bootloader so I'm pretty much in the clear. But with an unlocked bootloader and no startup pin (vs login pin) it's my understanding that you are wide open to data theft if you device is stolen.
---------- Post added at 07:16 AM ---------- Previous post was at 07:11 AM ----------
TonikJDK said:
I should have been more clear when I said 'pro'. I mean a real pro. Hackers got into a locked iPhone in the San Bernardo shooter case. Those same hackers took a run at Android and found a way to hijack an MDM system and remotely reset the pin. None of us need to worry about those kinds of attacks if we lose our phone, but the bottom line is that if you lose physical control of any device, phone, computer, tablet, your data is toast if the right person takes a run at it.
Click to expand...
Click to collapse
That I agree with. Although banking apps will ask for verification from an unknown IP address or device. The hackers that got into a locked iPhone were paid millions by us. (the government) I doubt that if your bootloader is locked and the device is lost those same hackers will be paid that kind of money for your pics of the wife and kids. But once again, I was under the assumption that unlocked the task is much, much easier.

bobby janow said:
I'm not 100% on this so bear with me. I was under the assumption that with an unlocked bootloader FRP (factory reset protection) was non functional. By startup pin I meant there is an option when setting a pin to either have it ask for the pin before anything at all happens and one to get into the device once it boots up. Most people use the latter but not the former because it's a pain. Personally, I set both with a locked bootloader so I'm pretty much in the clear. But with an unlocked bootloader and no startup pin (vs login pin) it's my understanding that you are wide open to data theft if you device is stolen.
Click to expand...
Click to collapse
So when I set up my device out the box there was no options to change frp, it asks if you want to set up a finger print and when you click yes it prompts for either a pin or pattern first.
There is no option for start up pin. Once you have a pin or pattern the device is encrypted. As per Google's policy once that happens, unless I remove the pin every power up requires a pin, if you don't use your device for say like 8 hours it requires a pin, otherwise it's a finger print.
No where can I set the pin not to activate upon boot. You either have a pin/pattern or you don't have one.
You can flash this thing all day but without my pattern you aren't getting in and I have been unlocked and rooted since November.

FRP is currently unbeatable unlocked or not. Other than the aforementioned 'pros' I guess.
There is no boot pin on Android, but there is a 'Sim Lock' that you can turn on. It is in the security settings and keeps your phone from connecting to the internet or doing much of anything until you enter it after a reboot. Alarms and so on will not work either. Even with a fingerprint set, when you reboot you still have to enter the pin.

pcriz said:
So when I set up my device out the box there was no options to change frp, it asks if you want to set up a finger print and when you click yes it prompts for either a pin or pattern first.
There is no option for start up pin. Once you have a pin or pattern the device is encrypted. As per Google's policy once that happens, unless I remove the pin every power up requires a pin, if you don't use your device for say like 8 hours it requires a pin, otherwise it's a finger print.
No where can I set the pin not to activate upon boot. You either have a pin/pattern or you don't have one.
You can flash this thing all day but without my pattern you aren't getting in and I have been unlocked and rooted since November.
Click to expand...
Click to collapse
Ok, I have 2 devices, a 5x and a Pixel and I use them both. On the 5x (Android O, locked bootloader) when I am asked to enter a PIN then the question is, " You can further protect this device by requiring your PIN before it starts up. ... Require PIN to start your device?" That is different than after you startup. I don't think on (7.1.2) the Pixel that question is asked.
Nonetheless, if you unlock the bootloader and have root (obviously I can't test this) can you flash a factory image with the -w and get in without your pin? What if you flash an image without the -w switch? Without FRP protection, as with an unlocked bootloader, don't you feel your device is less secure whether it be copying your data via adb or allowing the device to be used in case of theft or loss? Now perhaps I drank the Koolaid, but I know that if I ever lose either of my devices they are totally useless to the next person. Can you say the same thing?
---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------
TonikJDK said:
FRP is currently unbeatable unlocked or not. Other than the aforementioned 'pros' I guess.
There is no boot pin on Android, but there is a 'Sim Lock' that you can turn on. It is in the security settings and keeps your phone from connecting to the internet or doing much of anything until you enter it after a reboot. Alarms and so on will not work either. Even with a fingerprint set, when you reboot you still have to enter the pin.
Click to expand...
Click to collapse
Are you sure FRP is usable with an unlocked bootloader?
edit: I was referring to this article: http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
I just reread it and they have edited it about midway through the article. It does seem that unlocking the bootloader will not disable FRP although there are conflicting reports. Now what about root? lol

bobby janow said:
Ok, I have 2 devices, a 5x and a Pixel and I use them both. On the 5x (Android O, locked bootloader) when I am asked to enter a PIN then the question is, " You can further protect this device by requiring your PIN before it starts up. ... Require PIN to start your device?" That is different than after you startup. I don't think on (7.1.2) the Pixel that question is asked.
Nonetheless, if you unlock the bootloader and have root (obviously I can't test this) can you flash a factory image with the -w and get in without your pin? What if you flash an image without the -w switch? Without FRP protection, as with an unlocked bootloader, don't you feel your device is less secure whether it be copying your data via adb or allowing the device to be used in case of theft or loss? Now perhaps I drank the Koolaid, but I know that if I ever lose either of my devices they are totally useless to the next person. Can you say the same thing?
---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------
Are you sure FRP is usable with an unlocked bootloader?
edit: I was referring to this article: http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
I just reread it and they have edited it about midway through the article. It does seem that unlocking the bootloader will not disable FRP although there are conflicting reports. Now what about root? lol
Click to expand...
Click to collapse
You have two paths. You flash firmware and get presented with the initial setup screen. You will get to a point where you have to log in with the last email used in the device. Unless you have my email and password you get no further.
Otherwise the device will boot to lock screen requesting your PIN. Please explain to me how you get around this? Adb is setup to only work on my machine and you can't revoke creditentials without being in the OS.
I don't know how many different ways to say it, I guess my question is can you detail a way someone can use my device if I lose it?

pcriz said:
You have two paths. You flash firmware and get presented with the initial setup screen. You will get to a point where you have to log in with the last email used in the device. Unless you have my email and password you get no further.
Otherwise the device will boot to lock screen requesting your PIN. Please explain to me how you get around this? Adb is setup to only work on my machine and you can't revoke creditentials without being in the OS.
I don't know how many different ways to say it, I guess my question is can you detail a way someone can use my device if I lose it?
Click to expand...
Click to collapse
I don't know but I'm not a hacker nor have I researched it. So you are implying that even flashing a custom rom you cannot get into the device without a Google password? I find that intriguing to say the least. No custom roms bypass FRP?
My question to you is do you feel as safe with an unlocked bootloader as you would with it locked?

bobby janow said:
I don't know but I'm not a hacker nor have I researched it. So you are implying that even flashing a custom rom you cannot get into the device without a Google password? I find that intriguing to say the least. No custom roms bypass FRP?
My question to you is do you feel as safe with an unlocked bootloader as you would with it locked?
Click to expand...
Click to collapse
If a custom recovery can't bypass the encryption why would a rom be any different. Not to mention you cannot flash a rom without getting into twrp, twrp cannot decrypt the file system without a pin or pattern. I feel even safer because rooted I can utilize apps that can work to protect me at the system level. I can block ads at the system level.
Its like saying you have a door with 5 padlocks, but wouldnt you feel safer with six?
I'd feel safer not using a mobile phone at all but here we are.

pcriz said:
If a custom recovery can't bypass the encryption why would a rom be any different. Not to mention you cannot flash a rom without getting into twrp, twrp cannot decrypt the file system without a pin or pattern. I feel even safer because rooted I can utilize apps that can work to protect me at the system level. I can block ads at the system level.
Its like saying you have a door with 5 padlocks, but wouldnt you feel safer with six?
I'd feel safer not using a mobile phone at all but here we are.
Click to expand...
Click to collapse
That's another story for another day, but I do agree. I can't test any of this, but from days long ago wasn't there a way to boot twrp, go into file manager and delete some files or copy them? Also on a quick search there are a couple of ways to bypass FRP which I will not describe or link to here. And with an unlocked bootloader you can flash any factory image that has the exploit still unpatched.
I guess I just don't see why an unlocked bootloader is such a plus these days. I know you need it for root, but other than ad blocking (which I still get with dns66 unrooted) why allow a hacker to "possibly" compromise your system? I don't know, perhaps I'm getting old and slightly tired of flashing. Needless to say, this is an interesting conversation and certainly thought provoking.

bobby janow said:
That's another story for another day, but I do agree. I can't test any of this, but from days long ago wasn't there a way to boot twrp, go into file manager and delete some files or copy them? Also on a quick search there are a couple of ways to bypass FRP which I will not describe or link to here. And with an unlocked bootloader you can flash any factory image that has the exploit still unpatched.
I guess I just don't see why an unlocked bootloader is such a plus these days. I know you need it for root, but other than ad blocking (which I still get with dns66 unrooted) why allow a hacker to "possibly" compromise your system? I don't know, perhaps I'm getting old and slightly tired of flashing. Needless to say, this is an interesting conversation and certainly thought provoking.
Click to expand...
Click to collapse
There is also the story where Google paid a group of hackers 50 grand when they ran an exploit on a bootloader locked device that allowed them access to data on it. So even given that scenario with a locked bootloader and them not even having to touch the device, they were able access information on it.
Furthermore this is a doomsday scenario of one someone has to have my device, two they have to have the know how, 3 an image that can bypass the security checks that exist outside of the rom that is still allowed to boot without setting off tamper flags.
Also as far as removing files using twrp, again it cannot decrypt the filesystem without pin pattern so when you view the files in the twrp browser they are a bunch of folders with gibberish names and any attempt to make changes fails.
Not unlocking your bootloader is a choice. But let's not pretend that you open yourself up to a world of stolen data and exploits by unlocking it and rooting. That's the kind of scare tactics apps like AVG use to scare people into downloading them and paying for protection that is only good if you don't get attacked at the system level.
I saw the same links for frp bypass but here is the catcher. Unless fastboot is how they are passing it, they can just as easily do it on any device. Not just the bootloader unlocked ones.

pcriz said:
There is also the story where Google paid a group of hackers 50 grand when they ran an exploit on a bootloader locked device that allowed them access to data on it. So even given that scenario with a locked bootloader and them not even having to touch the device, they were able access information on it.
Furthermore this is a doomsday scenario of one someone has to have my device, two they have to have the know how, 3 an image that can bypass the security checks that exist outside of the rom that is still allowed to boot without setting off tamper flags.
Also as far as removing files using twrp, again it cannot decrypt the filesystem without pin pattern so when you view the files in the twrp browser they are a bunch of folders with gibberish names and any attempt to make changes fails.
Not unlocking your bootloader is a choice. But let's not pretend that you open yourself up to a world of stolen data and exploits by unlocking it and rooting. That's the kind of scare tactics apps like AVG use to scare people into downloading them and paying for protection that is only good if you don't get attacked at the system level.
I saw the same links for frp bypass but here is the catcher. Unless fastboot is how they are passing it, they can just as easily do it on any device. Not just the bootloader unlocked ones.
Click to expand...
Click to collapse
Yes, it was in fastboot (I'm pretty sure) and only on an unlocked bootloader of which I'm sure. If the exploit does indeed work then a locked bootloader would be the protection and an unlocked one would mean those padlocks you have are useless. But that's a big "if" and I'm not about to try it. I'm not of the mindset that my data is protected even locked. Bottom line don't lose the device to a person in the know.
I still feel better having a locked bootloader as no one can do anything with my device no matter their skill levels. I just call, blacklist the IMEI, and scrounge up some money for a replacement with no worries. Besides, I use AP all the time and I'm not about to jump through hoops after each Google server update to get it to work again with hiding root. But that is just a personal preference and not really part of this discussion.
As for TWRP, I do remember that there was a way to delete a couple of .key files in order to remove the need to use a password. But that was some time ago before all this security stuff went into effect I believe. But as to the OP question, I believe there is more danger with an unlocked bootloader and root than without. However, if you need root for some reason just make sure you know what you are doing before you do it.

Password Required After Device Restarts

I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.

rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.

If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.

jhs39 said:
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
Click to expand...
Click to collapse
You don't need root. Just need an unlocked bootloader.

toknitup420 said:
You don't need root. Just need an unlocked bootloader.
Click to expand...
Click to collapse
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.

jhs39 said:
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
Click to expand...
Click to collapse
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.

rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
Did you find the phone somewhere or is it yours legitimately? Are you trying to break into another device to get information off it? If you're honest about your intentions you really should explain accurately.
If it's a startup pin you can't bypass that. I hope for owner's sake the bootloader is locked including you if it's yours.
Sent from my Pixel using XDA-Developers Legacy app

toknitup420 said:
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
Click to expand...
Click to collapse
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.

jhs39 said:
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
Click to expand...
Click to collapse
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.

toknitup420 said:
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
Click to expand...
Click to collapse
I misinterpreted your comment then but a lot of people on XDA obviously like to flash their phones and on the Nexus 6P thread you were told by the person who wrote the flashing guides that the absolute first thing you should do with that phone when you got it was to unlock the bootloader. As for getting TWRP to work on the Pixel a lot of experienced flashers including myself have found it challenging to get TWRP to work on this particular phone. Google didn't make Pixels easy to flash on--particularly compared with their earlier Nexus devices. That said I honestly had no idea unlocking the bootloader made the phone that insecure so I sincerely thank you for the heads up.

huh
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Don't you need the pin to even get into TWRP to delete the file?

Raegoul said:
Don't you need the pin to even get into TWRP to delete the file?
Click to expand...
Click to collapse
Ah yes I forgot about this. This trick only works on decrypted devices. Decrypted devices don't require a password or pattern to enter twrp. Pixel is encrypted by default so yes you would need the password in order to access twrp. GLO. I completely forgot about that.

toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Won't it ask for the password when op starts twrp. And if op doesn't have it it cannot decrypt the file system to delete the file you mentioned.
Edit:
NVM saw someone mentioned it

No offense to the OP, but I'm going to call it and say we probably shouldn't be saying anymore. I have never heard of someone setting up their device and then not knowing what their password is. Not saying it's not possible, but if you're on XDA, with a Pixel device on Android O, that means; a) you flashed it and should know your way around some key things on Android, b) you stole the phone, or c) you're trying to break into your significant other's device, and last but not least d) you bought it on Swappa or Cracklist or wherever and the seller didn't wipe it.

People forget their passwords ALL the time... ask my lady if you want!

Erikbronx said:
People forget their passwords ALL the time... ask my lady if you want!
Click to expand...
Click to collapse
Buy her a pen and a pad. No excuses in this day and age.
Sent from my Pixel using XDA-Developers Legacy app

Can't you just go to google.com/android/devicemanager and log in with your google account and unlock it there?

Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?

Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice

I have the same problem and i cannot fix it.

I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while

CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).

mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation

CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.

You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7

Where did you get the ROM images from. I understand there are no officials?

CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.

umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs

CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.

Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number

umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.

gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.

wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one

Where did you get the correct Rom from? Thanks

I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse

I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?

realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!

CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards

Question Warning message after unlocking bootloader

Is there any tool or option to get rid of that warning message whenever you turn on your pixel 6 pro when your bootloader is unlocked and software integrity message?

nofroyo said:
Is there any tool or option to get rid of that warning message whenever you turn on your pixel 6 pro when your bootloader is unlocked and software integrity message?
Click to expand...
Click to collapse
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)

foobar66 said:
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)
Click to expand...
Click to collapse
+1
IIRC,the only phone mfg that I ever saw where that was possible was HTC.
I don't know if it's been done on other mfgs devices, but, none that I can recall, including Motorola/OnePlus/Huawei/Honor/Samsung & LG.
It was kinda cool to be able to do that on the HTC phones, but, as the cat & mouse game gets more involved as time marches on, I'm just happy w/Root & safety net passing.
Anything much beyond what is currently available/present is gravy.

foobar66 said:
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)
Click to expand...
Click to collapse
I recall this discussion in one of the OnePlys forums 2 or 3 years ago. I actuall found back where this message was on the phone (but don't recall the details now).
But - at least on OnePlus devices - there is a check baked into the boot process which will trip over, even when you would be able to change the message. The images are signed with a key from the manufacturer and the result is somehow baked into the phone. When the phone boots, the signature is checked on the actual images and compared with the result from Google. If different, the phone will not boot. So my understanding is that without the Google key, you will never be able to remove that message.

This would require a modified abl.img (part of the bootloader), but the secure boot chain will fail if you just modify that image and you system will not boot. What would be needed is a way to modify and resign the image and all other related bootloader images to maintain the integrity of the secure boot chain.

craigacgomez said:
This would require a modified abl.img (part of the bootloader), but the secure boot chain will fail if you just modify that image and you system will not boot. What would be needed is a way to modify and resign the image and all other related bootloader images to maintain the integrity of the secure boot chain.
Click to expand...
Click to collapse
Thanks for the input much appreciated

It's pretty much here to stay on most unlocked devices.
Just close your eyes for a few seconds. ..

galaxys said:
It's pretty much here to stay on most unlocked devices.
Just close your eyes for a few seconds. ..
Click to expand...
Click to collapse
Indeed, small price you have to pay for being a naughty boy ;-)

General PSA: DO NOT install the Beta on a locked bootloader.

If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.

V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.

truckerdewd said:
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
Click to expand...
Click to collapse
Not everyone has been so lucky. Glad it worked for you, though.

roirraW edor ehT said:
Not everyone has been so lucky. Glad it worked for you, though.
Click to expand...
Click to collapse
True. I posted the steps I followed in this thread.
Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that...
forum.xda-developers.com

I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.

Lughnasadh said:
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Click to expand...
Click to collapse
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.

Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...

V0latyle said:
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Click to expand...
Click to collapse
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.

gpvecchi said:
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
Click to expand...
Click to collapse
Basically yes, as long as you have an unlockable bootloader, can get into fastboot, etc..
For example, if things go haywire for you and you have OEM unlocking enabled, you can use Android Flash Tool to help recover your device. Or you can use fastboot to manually unlock the bootloader and flash whatever.

Lughnasadh said:
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
Click to expand...
Click to collapse
Yeah I think my brain was somewhere else. Interesting though.

@Lughnasadh Just curious which apps? I've not come across any.

bobby janow said:
@Lughnasadh Just curious which apps? I've not come across any.
Click to expand...
Click to collapse
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.

Lughnasadh said:
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Click to expand...
Click to collapse
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?

bobby janow said:
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
Click to expand...
Click to collapse
Yeah, if you go through the Magisk, SafetyNet and similar threads you'll see people who have come across apps that won't work when USB Debugging is enabled. It's really up to the app developer as to whether it checks for it or not.
I'm not entirely sure why after you switch OEM Unlocking off that it has you reboot as I've never switched it off once switched on. My guess would be that a reboot is needed to set ro.oem_unlock_supported to 0. But that's just a guess.

V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
The way Google implements there otas and installs now is a fail safe, the devices will not be bricked what so ever, if on stock that is