now that the boot loader is unlocked, it would be safe to flash a rom from any other US variant correct? or do we still have to wait for verizon only roms?
also, how would one root before or after the unlock?
If the underlying hardware isn't different, from what I've read, it should be fine.
Folks are already flashing sprint and att kernels to the unlocked vzw gs3, so yea it should work! Although I prefer to stick with software developed specifically for this device.
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
gretting and salutations,
I recently traded my iphone 6 plus with a busted screen to a store for a galaxy s7, which is still under warrenty so im hella stoked. Anyway, love the phoone. Would like to root and flash something vanilla. or as vanilla as i can get.
I have an att model g930A, unlocked and on t-mobile.
I've been looking in the forums and im not seeing alot of roms for the att model, which i guess is different than the international version.
any insight??
As i said, id like the be as vanilla as i can get.
wifi calling is not required and neither is VOLTE.
-As long as tethering works, im fine.
Yes the US models are using a Qualcom CPU instead of exynos and have a locked bootloader which makes custom ROMs near impossible.
I believe you can flash stock ROMs with Odin, that's about it.
Beanvee7 said:
Yes the US models are using a Qualcom CPU instead of exynos and have a locked bootloader which makes custom ROMs near impossible.
I believe you can flash stock ROMs with Odin, that's about it.
Click to expand...
Click to collapse
there is an option under developer options for oem unlock and i read that unlocks the bootloader.
i dont mind the phone as it is but id like to debloat or just flash straight android. no bloat.
You can find a thread here https://forum.xda-developers.com/ga...covery-official-twrp-galaxy-s7-t3458579/page3 discussing the unlocking of bootloader.
According to a post in early May it still hasn't been done for US models.
Really thinking about flashing the U firmware but I'm worried about my unlock.
I couldn't go thru att but I did pay for a code, if that matters. Reading on the forum it should be fine if you got it thru att but IDK what my process is classified as.
I had to trade my S6 in 2016 because I couldnt stand not being able to flash custom roms via recovery, and at the time it was deemed nearly impossible to bootloader unlock an S6, especially since dev's were losing interest working around Exynos chip vs Qualcomm. But what about today? I see some threads talking about roms and TWRP and stuff which makes me think this phone was finally cracked? Is that so? Or is it only very particular variants? I remember there was like 1 model S6 that you could properly root if it had a very specific version of Android on it at the time, but if it was ever upgraded it was locked.
So which phones are bootloader/recovery installable? And what do I need to know version wise before buying one? (like are some versions blacklisted, to stay away from)
Bootloader is not locked on S6 except AT&T variant.
forumber2 said:
Bootloader is not locked on S6 except AT&T variant.
Click to expand...
Click to collapse
but it used to be right? I had a verizon S6 and it was basically impossible to unlock as I recall. Is this a new development?
Hello All,
Ok so first off you guys at XDA are the ****! I swear I can find anything I need to know on this site with a little research, much respect. So as the title suggests I wanted to know if it's possible to flash a SM-G970U (US) with SM-G970F (UK) firmware? I am basically looking for a slightly less complicated way of enabling "OEM Unlock" to Unlock the bootloader. And yes I realize that more than likely I will not be able to use any US sim cards with that firmware but if it is possible and I could unlock the bootloader I could basically load anything I wanted onto it right?
......actually seems like the SM-G9700 would be a better candidate for the firmware to load on the SM-G970U.
.....be gentle, I'm a N00B...kind of =\
Hello All,
xlivexevilx said:
Ok so first off you guys at XDA are the ****! I swear I can find anything I need to know on this site with a little research, much respect. So as the title suggests I wanted to know if it's possible to flash a SM-G970U (US) with SM-G970F (UK) firmware? I am basically looking for a slightly less complicated way of enabling "OEM Unlock" to Unlock the bootloader. And yes I realize that more than likely I will not be able to use any US sim cards with that firmware but if it is possible and I could unlock the bootloader I could basically load anything I wanted onto it right?
......actually seems like the SM-G9700 would be a better candidate for the firmware to load on the SM-G970U.
.....be gentle, I'm a N00B...kind of =\
Click to expand...
Click to collapse
Actually i want to know as well because i read somewhere where someone said its possible because they are all the same models........did it work for you?
yea no...don't do that it won't work
Lol i already tried it flashed succesfully according to odin but when the device rebooted it came with the same firmware before and nothing changed Lmao
how did it flashed ,please specify
I was told this is not possible. Unless you can find original overstock (i.e. that has NOT been updated) in which case you can pay to unlock the bootloader.
Otherwise, I believe any bootloader beyond v1 cannot be bootloader unlocked. Only hope is Sammie does us a solid when this goes EOL and unlocks the bootloader. Question is whether VZW and AT&T will prevent them from doing that.
My S10e is still going great, and if I could root and flash a custom rom I'd probably replace the battery and roll with it another 3-4 years because I have no interest in the larger phones that dominate the Android market now.