If I want to take the phone back to stock, what do I have to do to get the OTA? The phone said unlocked even before we started rooting it. Do these phones come unlocked (sprint 4g)?
loveubuntu said:
If I want to take the phone back to stock, what do I have to do to get the OTA? The phone said unlocked even before we started rooting it. Do these phones come unlocked (sprint 4g)?
Click to expand...
Click to collapse
What I did was install a stock nandroid through recovery, then relocked my bootloader. Your phone must have been previously rooted, because the phone's do not ship in that state. To re lock your boot loader just boot your phone into the bootloader, start the command prompt on your pc, and then type fastboot oem lock.
Thanks. to go factory condition though, I have to unroot first and then fastboot oem unlock, correct?
You maybe right, if that is how easy to unlock-lock, I may have unlocked it by fastboot oem locked and not remembered (it was late). This is a friends phone and I'm not used to having phones unlocked this easily.
You can leave the boot loader unlocked and still receive ota updates.
Sent from my Galaxy Nexus using XDA App
loveubuntu said:
If I want to take the phone back to stock, what do I have to do to get the OTA? The phone said unlocked even before we started rooting it. Do these phones come unlocked (sprint 4g)?
Click to expand...
Click to collapse
Yeah, OTA updating should have nothing do with whether your bootloader is locked or not
Rooting and unlocking the bootloader will not affect the ota, what will is custom system apps like non stock gmail, or a changed build prop (common from market enabler)
Sent from my Nexus S
I am thinking of getting an S6 and i wanted a rootable phone. i see a root method available but no bootloader unlock and yet i see ROMs available. how does this work. i thought bootloader needed to be unlocked in order to do custom ROMs. Or is htere a verizon bootloader unlock available i could not find?
johnbravado said:
I am thinking of getting an S6 and i wanted a rootable phone. i see a root method available but no bootloader unlock and yet i see ROMs available. how does this work. i thought bootloader needed to be unlocked in order to do custom ROMs. Or is htere a verizon bootloader unlock available i could not find?
Click to expand...
Click to collapse
There is not and 99% chance there will never be a bootloader unlock. Root method no longer works in later versions of android. The bootloader does not need to be unlocked with a custom recovery.
I apologize for not diligently searching as I should, I came across this asking the same more or less as I was.... I have one sitting on lrx22g.g920vvru1a0c3 which if I read the root method correctly I can root... At that point you say that the boot loader doesn't need to be unlocked so I can ( mfastboot flash recover xxxx.IMG ) on a locked boot loader? Or use rashr ? And after which we can ROM it?... Could I then theme it as well? I am coming for Motorola's all I've ever had/used/touched ever.... Running stock do I need to deodex it to be able to theme it? Do we have firmware out there n a tool (like Moto's rsd lite/ house of moto) to flash it with? With unlimited data is there a mobile hotspot mod/hack use utilize the baked I hotspot app? Can I still pull system apps theme um zip um and flash up.... Not having the Sim card yet I can really play with it as I wish to ... I just powered it on and its asking for an update... So I figured it'd try to root it now as there's no unlock for it..... Thank you kindly for your time and information
OE2 is the latest firmware that is rootable. Once rooted, you can flash a custom recovery and load roms through that.
There is a rooted S6 available for sale on swappa right now, just so you know
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
Doubled checked and noticed that three variants of Factory Images exist. Factory, Telus, and Verizon. Since I have a Verizon locked BL and have unlocked. Is this a backdoor to "correct" the problem. Just like what happened with Pixel 2 Verizon before 8.1 when that exploit existed. Reason why I ask, I had a Pixel 2 factory unlocked and after a (4) refurbish channel replacement with NO UNLOCK ability don't want to see if this is a end around to Lock up Pixels.
If you have a Verizon phone, you should only flash the Verizon ROM (or OTA update). If your phone is already bootloader unlocked, updates should not relock the bootloader, unless you specifically go through the process to relock it. If the bootloader is locked and you flash an update, the update may potentially nullify the method used to unlock the bootloader. In that case, it is best to wait and see what others report.
I have flashed the September Verizon variant (factory image and not OTA) on a Pixel and Pixel XL (both unlocked with dePixel at the very beginning). Nothing happened to the already locked devices. I have little doubt that it would have patched the exploit on a still locked device.
Thank You sliding_billy that was the answer I needed. Not that I will relock, but the fact that others might thought would be good to get verification. Waiting for more drop in price on Verizon locked ones with Pixel 3 release. I want to pick up more used ones. This device has become my #1 after all my Nexus 5X's suffered blod.
Spent all day scraping this forum for some guidance on getting TWRP on the TMO variant.
I have followed several methods that have been posted here. The last I tried was flashing international -> Q Preview 3 to unlock the bootloader. I was able to get the bootloader unlocked, but this didnt change the fact that TMO has disabled the common fastboot commands like boot, making it impossible to boot to TWRP directly from the bootloader. No idea how this worked for anybody.
Attempting to flash recovery with the twrp image doesnt work since fastboot tries to flash recovery_b and reports that the partition doesnt exist. The set_active command has also been removed.
I managed to find one thread that provided instructions for flashing a patched boot image. However, there are no patched boot images I can find. I am willing to patch it myself if nobody else has tried this yet.
If there are any other people out there making monthly payments on the phone, you can bypass the bootloader unlock using the international to Q preview method, but i do not think you can permanently carrier unlock until you pay off the phone.
Many of the guides out there for TMO were made back in June/July. Looks like some updates have been issued to prevent them from working anymore. If there is anyone that frequents this forum that can help me out, I'd be happy to offer some ongoing assistance myself once i get this thing rooted.
There's a few threads on here that tell people to PM certain users to have their phone SIM unlocked. I was one of them, T-Mobile, only had the phone for 5 months now, still paying on it. Unlocked and converted. Also, just use MSM Download Tool to convert to international, you'll find a guide on here somewhere. After that, re-unlock your bootloader, fastboot boot TWRP, flash the TWRP installer zip, flash desired version of OOS, then you'll be good to go. Simple as that.