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.

Skipsoft unable to unlock my bootloader? Trying to root

Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks

GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.

v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.

GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.

v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go

GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.

v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.

GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.

xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD

I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"

kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.

v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..

kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:

I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...

Downgrade from Pie to Oreo, locked bootloader?

Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:

Google has implemented a rollback prevention system on their devices. You cannot install an earlier version of Android over a later one. Attempting to do so generates an error message and the device will not boot. I believe this applies regardless of the lock status of the bootloader, but I'm sure someone more knowledgeable will chime in.
Sell your device on Swappa. Then purchase an unlocked model off Swappa, if available. No sane person is going to trade their unlockable device for your Verizon model.

if you unlock the bootloader, and wipe the device, you can downgrade to any version that google has published for the device.
If you do NOT unlock the bootloader, it is not possible.

@uicrnen: He has a Verizon device, so he can't unlock it.

Strephon Alkhalikoi said:
@uicrnen: He has a Verizon device, so he can't unlock it.
Click to expand...
Click to collapse
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.

uicnren said:
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
Click to expand...
Click to collapse
Which is why I gave your post a thumbs up. Rollback protection then is similar to Factory Reset Protection in this regard. So long as OEM Unlocking is enabled in developer options and the bootloader unlocked, neither will kick in.

uicnren said:
if you unlock the bootloader
Click to expand...
Click to collapse
Please can you recommend the safest/most reliable way to accomplish this.
uicnren said:
...and wipe the device, you can downgrade to any version that google has published for the device.
Click to expand...
Click to collapse
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.

IconBoy said:
Please can you recommend the safest/most reliable way to accomplish this.
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
Click to expand...
Click to collapse
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
1. BACKUP. Save anything you deem important, as your device will be erased.
1a. Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts.
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images ***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.

Worth mentioning to him if he's on Verizon, it isn't gonna work.
Upgraded anyway. Handful of issues but not enough to regret it. I do regret buying through Verizon though...

forwardthinking said:
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Click to expand...
Click to collapse
Sell it on swappa ms buy what you want.

uicnren said:
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
Click to expand...
Click to collapse
Unlocked Pixel 2 XL bought from Google Store.
uicnren said:
Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Will 15 Second ADB be sufficient, as I've always had success with that...?
Hopefully the ADB Fastboot file from Android Developer I can unzip and copy the updated contents to 15 Second ADB as their batch file installs system wide which is so helpful.
uicnren said:
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts
Click to expand...
Click to collapse
Done that already. :good:
uicnren said:
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images
Click to expand...
Click to collapse
As my device is unlocked and not specific to any carrier, am I correct in choosing the sixth from bottom from the list:
Taimen 8.1.0 (OPM2.171026.006.H1, Jul 2018)?
uicnren said:
***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
Click to expand...
Click to collapse
Duly noted!
uicnren said:
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
Click to expand...
Click to collapse
Once the device first boots from doing all this, is it okay if I skip all the Google account setup and just enable Developer Options and enable OEM unlock?
uicnren said:
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Click to expand...
Click to collapse
So the file I chose from the Android Developers Images page above, would be 100% stock?...and I can just go ahead and relock bootloader?
Should I factory reset after bootloader is relocked?
Thank you for clarifying the steps.

How To Guide After Update Bootloop Fix

Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.

Dang thank you for the guide, but rippers to people who still have their bootloader locked

CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader

Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects

bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......

I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse

bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')

CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?

bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro

CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.

CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?

bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now

CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.

The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL

CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.

bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.

CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.

bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.

Edit: Mod please remove.

CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.

Question Is there a way to revert back to the stock Moto Android 12 rom?

Wanted to find out if there was a way to revert to the stock rom without hassle.

Yeah, you can use LMSA for that.

arsradu said:
Yeah, you can use LMSA for that.
Click to expand...
Click to collapse
will it lock my bootloader though? Also did you face any issues while using that

rowhen_ said:
will it lock my bootloader though? Also did you face any issues while using that
Click to expand...
Click to collapse
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.

arsradu said:
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
Click to expand...
Click to collapse
yeah, it's turned on by default

rowhen_ said:
yeah, it's turned on by default
Click to expand...
Click to collapse
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.

arsradu said:
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
Click to expand...
Click to collapse
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?

rowhen_ said:
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
Click to expand...
Click to collapse
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.

arsradu said:
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
Click to expand...
Click to collapse
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )

rowhen_ said:
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
Click to expand...
Click to collapse
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.

arsradu said:
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
Click to expand...
Click to collapse
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.

rowhen_ said:
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
Click to expand...
Click to collapse
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?

arsradu said:
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
Click to expand...
Click to collapse
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable

rowhen_ said:
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
Click to expand...
Click to collapse
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.

arsradu said:
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
Click to expand...
Click to collapse
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage

rowhen_ said:
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
Click to expand...
Click to collapse
That's weird... I've got no stuttering, battery is pretty damn good, so is signal, and I've got IMS services, which are pretty important to me. Also, Tap to Pay now works again, after locking the bootloader.
Well, I'm glad Lineage works for your! I also prefer PE. But...there are some issue right now. And I'm waiting for a new update which could potentially fix them.