Related
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.
There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.
plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.
Hi,
I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.
I chose "lock" in the twrp menu, and I entered an endless loop.
Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.
I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns
Code:
$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s
I also tried to enter recovery mode, but it began to splash initial screen on and off again.
How can I recover from this situation?
Thanks in advance!
edit:
"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.
Code:
$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s
edit2:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Thanks. I'll give it a try. I'm almost abandoning.....
junglism93 said:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Click to expand...
Click to collapse
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
maverick6664 said:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Click to expand...
Click to collapse
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
matusala said:
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
Click to expand...
Click to collapse
I've learned. "Don't root. Don't unlock bootloader."
@matusala you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.
I certainly won't be re locking my bootloader, ever!
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
matusala said:
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
Click to expand...
Click to collapse
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.
That's about as far as my knowledge of it goes mate
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?
The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.
Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
maverick6664 said:
I've learned. "Don't root. Don't unlock bootloader."
Click to expand...
Click to collapse
Hmmm......correction.
I would say:
"Root with caution. Otherwise don't root."
Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.
It seems these pixel phones are garbage compared to nexus line. Those were so much better!
matusala said:
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.!
Click to expand...
Click to collapse
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
TENN3R said:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
Click to expand...
Click to collapse
I followed this guide and it worked. It unlocked my bootloader. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Now option is greyed out again in "off" position but it says "Bootloader already unlocked"
Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
junglism93 said:
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
Click to expand...
Click to collapse
Good luck @matusala from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
maverick6664 said:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
I'm sure that is safe if you're updating from full stock to full stock, with mods on board a relock is almost suicidal and the threads about bricked pixels back that up.
If you don't like the warning screen, do what I do, don't watch your phone reboot
Click to expand...
Click to collapse
HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
dimm0k said:
HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
Click to expand...
Click to collapse
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
K1nsey6 said:
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
Click to expand...
Click to collapse
I can get into the bootloader, however here I'm seeing the message that the bootloader is already locked! tried flashing the November update, but getting the failed message that I need to be unlocked
craigacgomez said:
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
Click to expand...
Click to collapse
when I try to get to recovery mode through the bootloader, it immediately spits me back out to the message that there's no valid operating system and to press the power button to power off
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
dimm0k said:
when I try to get to recovery mode through the bootloader...
Click to expand...
Click to collapse
FYI, the bootloader is one of the functional recovery modes.
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
minidude2012 said:
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
Click to expand...
Click to collapse
NippleSauce said:
FYI, the bootloader is one of the functional recovery modes.
Click to expand...
Click to collapse
Beefheart said:
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
dimm0k said:
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
Click to expand...
Click to collapse
Unlikely. This now needs a logic board swap I suspect. You can't unlock the bootloader as you toggled the OEM switch in developer options then relocked the bootloader before flashing stock, you can't boot to Android to untoggle that switch to allow another fastboot unlock command because you have a non-stock image installed with a locked bootloader, and you can't flash back to stock.
Sorry to say, your phone appears to be bricked.
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Beefheart said:
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Click to expand...
Click to collapse
should I try sending it back for a warranty swap or would sending it into Google for repairs not be a good idea?
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Beefheart said:
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Click to expand...
Click to collapse
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
dimm0k said:
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
Click to expand...
Click to collapse
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Beefheart said:
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Click to expand...
Click to collapse
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
dimm0k said:
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
Click to expand...
Click to collapse
The question is, can you use the GC when you purchase another phone?
schmeggy929 said:
The question is, can you use the GC when you purchase another phone?
Click to expand...
Click to collapse
unfortunately Amazon thought of abuse this way and priced it so that the device was $200 less from the get-go and charging $200 for the GC
Doesn’t matter what they say, if the device is in warranty, just write them that the device is damaged. They must replace it.