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?
Related
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?
you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA
JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?
discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?
crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly
Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.
Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though
How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.
discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps
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.
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs
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...