Related
Has anyone thought that maybe google has made 2.3 unrootable? Scary thought i know, but its kind of like a cat and mouse game with the developers and google/manufacturers with root patches.
Maybe google finally will put the nail in the coffin here?
WOOT. It's rooted, im happily wrong.
It's a developer phone, so why would Google want to make devs waste time trying to root.
could it be possible that Google enable root access by default, then?
djfoo000 said:
could it be possible that Google enable root access by default, then?
Click to expand...
Click to collapse
Definately not.
Dev phones have always been rootable, i doubt that will change.
The phones that have trouble being rooted are always manufacture customized ones.
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
I'd bet that it will be rooted BEFORE!
The developer build on my Nexus One is already rooted. I don't imagine the release build will be any different from all of the previous OTAs.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
You are correct.
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
fastboot oem unlock
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Your right, as of now I don't think Samsung locked any of their phones, but the only thing Samsung has on this phone is the hardware aspect. All the software aspect is by Google.
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Then how do you explain threads like this (on the samsung galaxy sub forums):
[HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!]
It seems like you have carrier/sim lock and root confused. Just like nearly every phone on the market, they are locked. You will also need root to do anything that says "please root your phone". They do not ship this way...
I'm sure it will be rootable... Google doesn't want to block out developers
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
Very true
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
luckyduck69 said:
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
Click to expand...
Click to collapse
that's unlocked for carriers with gsm...that's not root. Simply meaning it will work with at&t or tmobile by changing the sim card. Root lets you edit system files and a custom recovery to flash roms
Lmao no one so far in this thread should get one of these developer phones as you plainly do not understand what you are doing here when it comes to deciding what the difference is between root permissions and unlocked to all networks.
lets put it this way, if you are one of the above who are having trouble, dream on and steer clear from the prospects of rooting all together
unless that is you fancy yourself a very expensive paperweight?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
This command unlocks your bootloader on the N1/N-S allowing you to flash custom roms, but visibly voids your warranty (bootloader screen shows that it's unlocked)
http://www.htcdev.com/
Not sure if anyone has posted this yet but HTC's site to unlock the bootloader is live. It doesn't really matter much anymore but in the event someone is interested in trying it out the link is above.
Make sure you follow the instructions and, more importantly, understand the ramifications of what you are doing before you do it.
From what I understand, the Thunderbolt isn't supported
Only the UK sensation.
Sent from my ADR6350 using XDA Premium App
Copy and pasted
Supported Devices for the Bootloader
The following 2011 models (Launched prior to September, 2011) will be supported on this web site. Devices in green are currently unlockable, check back often for updates on the unlock status of additional devices:
HTC Sensation (EU)
FOTA 1.45.401.2
HTC EVO 3D (Sprint)
HTC Sensation 4G (T-Mobile USA)
Jcase says the leak he just received gives the thunderbolt the ability to be unlocked via htc's tool, so they will probably add it when GB is released.
And just to clear this up, I've been reading around and some people think this tool is going root your device. This is not true. All t will do is unlock your bootloader. You will still have to either run an exploit to gain root, or flash a rooted ruu via hboot once the bootloader is unlocked.
DO NOT DOUBT YOUR WARRANTY WILL BE VOID AFTER USING THE TOOL. There is no doubt in my mind HTC will flag your device, and that they will share this information with Verizon. We already have an unlocked bootloader, so there is no need to use this tool.
I've said my peace.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
orkillakilla said:
DO NOT DOUBT YOUR WARRANTY WILL BE VOID AFTER USING THE TOOL. There is no doubt in my mind HTC will flag your device, and that they will share this information with Verizon. We already have an unlocked bootloader, so there is no need to use this tool.
Click to expand...
Click to collapse
No doubt that he is completely correct in saying this, Verizon will not be taking the hit to the wallet by letting this people who dont attempt to fix their phone and the first sign their phone may be bricked. Explore all options when it comes to your troubles before calling Verizon for a replacement phone.
Grnlantern79 said:
No doubt that he is completely correct in saying this, Verizon will not be taking the hit to the wallet by letting this people who dont attempt to fix their phone and the first sign their phone may be bricked. Explore all options when it comes to your troubles before calling Verizon for a replacement phone.
Click to expand...
Click to collapse
Better yet, if you rooted and you mess up your phone, don't call Verizon at all. It's not their fault, they shouldn't have to fix it.
If it's a hardware problem, call them. If it's software and your not rooted, call them.
If you screwed up, suck it up and fix it yourself...
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
And unless you paid for the kick ass insurance or got it through say Best Buy you may end up getting a replacement phone that is in the same boat anyways. Dam how do insurance company's and Verizon get away with sending these "like new replacments" out.
I have had my phone rooted just over a week, and I have been doing nothing but reading and just missing around with ADB and what works for a majority of other users. Keep reading, keep learning, and dont give up.
orkillakilla said:
Better yet, if you rooted and you mess up your phone, don't call Verizon at all. It's not their fault, they shouldn't have to fix it.
If it's a hardware problem, call them. If it's software and your not rooted, call them.
If you screwed up, suck it up and fix it yourself...
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Click to expand...
Click to collapse
orkillakilla said:
Jcase says the leak he just received gives the thunderbolt the ability to be unlocked via htc's tool, so they will probably add it when GB is released.
And just to clear this up, I've been reading around and some people think this tool is going root your device. This is not true. All t will do is unlock your bootloader. You will still have to either run an exploit to gain root, or flash a rooted ruu via hboot once the bootloader is unlocked.
DO NOT DOUBT YOUR WARRANTY WILL BE VOID AFTER USING THE TOOL. There is no doubt in my mind HTC will flag your device, and that they will share this information with Verizon. We already have an unlocked bootloader, so there is no need to use this tool.
I've said my peace.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Click to expand...
Click to collapse
An unlocked bootloader allows you to flash unsigned images. Root becomes as easy as recovery in a PG05IMG.zip, then flashing the package in recovery. No exploit needed.
Also, along with the do not doubt it voids your warranty, HTC adding support does not mean Verizon will allow it. If Verizon says no, HTC will not add support to the web tool.
Grnlantern79 said:
Dam how do insurance company's and Verizon get away with sending these "like new replacments" out.
Click to expand...
Click to collapse
You aren't giving them a new phone. You are giving a broken one. They in turn are giving you a refurbished used one to put you back AT LEAST in the same position as owning your used phone.
That, and they get away with it because you signed a contract allowing it.
adrynalyne said:
An unlocked bootloader allows you to flash unsigned images. Root becomes as easy as recovery in a PG05IMG.zip, then flashing the package in recovery. No exploit needed.
Also, along with the do not doubt it voids your warranty, HTC adding support does not mean Verizon will allow it. If Verizon says no, HTC will not add support to the web tool.
Click to expand...
Click to collapse
You have a point about Verizon allowing it. I did mention the ability to flash a rooted RUU via hboot.
I guess we will just have to wait and see what Verizon does.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Yes you mentioned it, but it is not correct.
A PG05IMG.zip is merely a file format for flashing via hboot. Each HTC devce has its own naming scheme. An RUU is a rom update utility and is in executable format. However, what most people do is extract the rom.zip in it, which has images that flash the phone from top to bottom.
With the bootloader unlocked, there is no need to go to such extremes. You can flash JUST a recovery and then use it to install super user and be done.
I think since Phones in the future will be shipping with unlocked bootloaders the site will not be needed for those devices for reasons I just wrote, but the site would be past phones that still shipped with the bootloaders locked and those are going to be the one that will be tracked for voided warranty. In the future it will be as easy and the Droid Charge (shipped with unlocked bootloader) Root method (easy and cake) I did one for a friend and was like "thats it" so painless. There will be no reason to show HTC or Verizon that you did anything to future phones it will be so easy to gain SU on the next phone from HTC on America's Favorite Network.
adrynalyne said:
Yes you mentioned it, but it is not correct.
A PG05IMG.zip is merely a file format for flashing via hboot. Each HTC devce has its own naming scheme. An RUU is a rom update utility and is in executable format. However, what most people do is extract the rom.zip in it, which has images that flash the phone from top to bottom.
With the bootloader unlocked, there is no need to go to such extremes. You can flash JUST a recovery and then use it to install super user and be done.
Click to expand...
Click to collapse
adrynalyne said:
Yes you mentioned it, but it is not correct.
A PG05IMG.zip is merely a file format for flashing via hboot. Each HTC devce has its own naming scheme. An RUU is a rom update utility and is in executable format. However, what most people do is extract the rom.zip in it, which has images that flash the phone from top to bottom.
With the bootloader unlocked, there is no need to go to such extremes. You can flash JUST a recovery and then use it to install super user and be done.
Click to expand...
Click to collapse
I see. Thank you for explaining. I'm no dev, but do enjoy learning new things. That makes sense
To grnlantern79, HTC will not be shipping any devices with unlocked bootloaders, which is the reason for the website tool. I don't think they will be supporting legacy devices with this tool. Only newer and future devices.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
I want to blame the news or lack of LOL this was the last post I read.
Peter Chou, CEO of HTC said, "Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience."
and now that you brought up your point this is what I found,
HTC will continue to ship all their phones with locked bootloaders, but will be offering a web-based tool for those who wish to have full control over their handsets.
Dam HTC make up your mind LOL.
orkillakilla said:
I see. Thank you for explaining. I'm no dev, but do enjoy learning new things. That makes sense
To grnlantern79, HTC will not be shipping any devices with unlocked bootloaders, which is the reason for the website tool. I don't think they will be supporting legacy devices with this tool. Only newer and future devices.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Click to expand...
Click to collapse
Grnlantern79 said:
I want to blame the news or lack of LOL this was the last post I read.
Peter Chou, CEO of HTC said, "Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience."
and now that you brought up your point this is what I found,
HTC will continue to ship all their phones with locked bootloaders, but will be offering a web-based tool for those who wish to have full control over their handsets.
Dam HTC make up your mind LOL.
Click to expand...
Click to collapse
I 100% expected it to be this way when I first heard they will unlock bootloaders. I think its at least a step in the right direction.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
orkillakilla said:
I 100% expected it to be this way when I first heard they will unlock bootloaders. I think its at least a step in the right direction.
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Click to expand...
Click to collapse
Yes step in the right direction it is but correct me if I am wrong, didnt the Droid Charge ship with an unlocked bootloader?
Grnlantern79 said:
Yes step in the right direction it is but correct me if I am wrong, didnt the Droid Charge ship with an unlocked bootloader?
Click to expand...
Click to collapse
Samsung phones are always unlocked and easiest to root. HTC ones are generally all locked by the OEM (well until now), but the community finds a way to unlock them.
yareally said:
Samsung phones are always unlocked and easiest to root. HTC ones are generally all locked, but the community finds a way to unlock them (well until now).
Click to expand...
Click to collapse
You wonder if the reason they unlock them is because they know they will never send any updates to the phones LOL.
Grnlantern79 said:
You wonder if the reason they unlock them is because they know they will never send any updates to the phones LOL.
Click to expand...
Click to collapse
Possibly, lol. Though I just think they're trying to not go the path moto tried and failed with on phones such as the Droid X.
Those that think they really care about you unlocking it on their site can't really explain how their future phones will come unlocked by default without any tools. Still unknown for sure, but I believe they said they would not be locking any new releases from now on as well.
Hey all. My early upgrade is this weekend so I'm going to but a gs3 but I must be able to root and unlock boot loader.
Was looking at the unlock app
https://play.google.com/store/apps/details?id=com.mmmeff.ez.unlock
And see that the recent reviews saying they are having issues unlocking boot loader since update from Verizon.
Is the app broken now And or did they patch the phone so u cant unlock the boot loader?
I don't amt to buy this phone then end up not being able to unlock the bootloader (I can't stand anything other than aosp)
Lmk. Also how would I go about unlocking the boot loader without using that app or is that the only way to do so?
This is posted all over this forum. However, all you need to do is search for version 1.2 and it will unlock the bootloader, after you root, of course.
Sent from my SCH-I535 using xda premium
the guide posted at the top of the dev forum should be your new best friend
HHF2 said:
This is posted all over this forum. However, all you need to do is search for version 1.2 and it will unlock the bootloader, after you root, of course.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Here is my copy http://db.tt/TtOVCI1W . Just make sure you root first .
Sent from my SCH-I535 using xda app-developers app
Valkyrie743 said:
Hey all. My early upgrade is this weekend so I'm going to but a gs3 but I must be able to root and unlock boot loader.
Was looking at the unlock app
https://play.google.com/store/apps/details?id=com.mmmeff.ez.unlock
And see that the recent reviews saying they are having issues unlocking boot loader since update from Verizon.
Is the app broken now And or did they patch the phone so u cant unlock the boot loader?
I don't amt to buy this phone then end up not being able to unlock the bootloader (I can't stand anything other than aosp)
Lmk. Also how would I go about unlocking the boot loader without using that app or is that the only way to do so?
Click to expand...
Click to collapse
The developer recommends version 1.2 and you can get that from here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
There is a way to unlock the bootloader manually, but that takes a bit more effort and some terminal coding. I would definitely recommend just downloading EZ-Unlock v1.2 and using that. It's just a push of a button! That's what I did.
At the risk of being reprimanded.....
My phone is rooted and I have unlocked the boot-loader with One click "ez bootloader unlock." I have flashed numerous ROM's and continue to flash various ROM's... After flashing each new ROM and getting through the initial setup, I download ClockWorkMod from the play store, if not already part of the ROM, and then "One click ez bootloader unlock." I then run the "One click ez bootloader unlock" and then the ClockWorkMod for my model phone. I do this each time I flash a new ROM.
My question is whether this is unnecessary or not? I see that the later versions of "One click ez bootloader unlock" have a re-lock option, but I am unclear as whether or not it is unnecessary to unlock the boot-loader each and every time a person flashes a new ROM? Or under what circumstances would a person need to unlock their boot-loader after successfully unlocking it the first time?
It seems to me that once the boot-loader is successfully unlocked that a person would not have to unlock it again unless they ODIN back to Stock OEM, but I have not been able to google or search these forums successfully to find an answer, and for that I apologize, because I'm sure it's here somewhere, and some "Senior Member" will be quick to jump at the opportunity to point that out to me.... After a healthy dose of liquid courage, I am reluctantly asking the question here.... And if someone is so kinda as to answer my question, who knows, maybe it will help some other person who has the same question, but is afraid to ask, because of the harshness and lack of patience of some "Senior Members?"
A sincere thank you in advance to anyone who might answer my question. :fingers-crossed:
The only time you need to re-unlock the bootloader is if you Odin back to stock.
Sent from my SCH-I535 using Tapatalk 2
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 guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np