Related
I sure hope so. I can't have a phone without root. Unfortunately I'm stuck with verizon....
Sent from Tapatalk
I assume it will be exactly the same as G4 in terms of root/BL.
How can we know now though? Too early to know.
Sent from my BLU LIFE ONE X using Tapatalk
tabp0le said:
I assume it will be exactly the same as G4 in terms of root/BL.
Click to expand...
Click to collapse
which was what.. seems like some G4s have root
jaladhjin said:
which was what.. seems like some G4s have root
Click to expand...
Click to collapse
Unfortunately only the intl variants and tmobile have unlocked bootloader which is required for root in android 6.0+
Have you guys heard the Unlocked LG G5 has all Major USA Bands?
http://www.droid-life.com/2016/03/18/unlocked-lg-g5-gsm-cdma/
any update on bootloader
krazie1 said:
Have you guys heard the Unlocked LG G5 has all Major USA Bands?
http://www.droid-life.com/2016/03/18/unlocked-lg-g5-gsm-cdma/
Click to expand...
Click to collapse
The discussion is about an unlocked bootloader, not an unlocked carrier situation.
If an unlocked boot loader version existed, it would be called a developer version and it wouldn't be likely to be picked up in large enough numbers to see much real public development.
Basically, it will most likely be MONTHS before you see a leak or hack to unlock the boot loader if EVER. It will be a long time before you even see root if the G4 and V10 (just got root very recently) are anything to go by.
Since mobile device payments have become all the rage, carriers and device manufactures are extra motivated to lock down their devices. The Galaxy S7 and S7 edge (same processor as the G5) are so locked down (even on T-mobile) using Qualcomms secure boot methods that it does a check to verify the main partition before it loads the contents to memory meaning a root can only be done temporarily (live rooted) if an exploit is ever found and will have to be rerooted every reboot. Android developers are going to have to struggle with qualcomm devices especially to develop into the the future.
manaox2 said:
The discussion is about an unlocked bootloader, not an unlocked carrier situation.
If an unlocked boot loader version existed, it would be called a developer version and it wouldn't be likely to be picked up in large enough numbers to see much real public development.
Click to expand...
Click to collapse
If the G5 is carrier unlocked, then wouldn't we simply be able to purchase a T-Mobile variant, get it unlocked, and then use it with a Verizon Sim?
dtroup64 said:
If the G5 is carrier unlocked, then wouldn't we simply be able to purchase a T-Mobile variant, get it unlocked, and then use it with a Verizon Sim?
Click to expand...
Click to collapse
As long as you don't mind paying full price or carrying a second contract and T-Mobile agrees to unlock it. Hopefully development would still be decent with just the t-mobile variant.
dtroup64 said:
If the G5 is carrier unlocked, then wouldn't we simply be able to purchase a T-Mobile variant, get it unlocked, and then use it with a Verizon Sim?
Click to expand...
Click to collapse
Unfortunately Verizon is very strict on what devices can be activated with one of their SIMs. Most likely they would block a Tmobile or international variant on their network. This is the case with the G4 already.
We got root on the V10, not an unlocked bootloader though (yet). Here's to hoping we can get at least root on the G5 in the same manner...need those magic TOT files!
thedrizzle said:
We got root on the V10, not an unlocked bootloader though (yet). Here's to hoping we can get at least root on the G5 in the same manner...need those magic TOT files!
Click to expand...
Click to collapse
We will need more than the TOT file to root the G5. Starting with Android 6.0, Google made changes so that root requires a modified kernel. Changes to system.img will not be enough. Since this involves tampering with the boot.img, the locked bootloader will prevent the phone from booting at all.
Here's hoping we don't have a repeat of the G4 or V10 when it comes to locked bootloaders.
Should I not update my device to keep it as developer friendly as possible (I am preordering it)
manaox2 said:
As long as you don't mind paying full price or carrying a second contract and T-Mobile agrees to unlock it. Hopefully development would still be decent with just the t-mobile variant.
Click to expand...
Click to collapse
Or not having 3g CDMA where there's no LTE.
Anyone working on a root method yet?
This is bull crap why does tmo get a unlocked bl and not everyone else?
Why are people so afraid of it? Just let us enter our serial and we download a program. We void our warranty but how bout you let us take thst risk!?
Sorry Bad post!!
soundgirl101 said:
:crying::crying:None of LG G5 variants have an unlockable bootloader!! This is due primarily to Google agreements with various credit card providers for Android "Tap and Pay" feature to be used!! Other variants, like T-Mobile, will have an "OEM Unlock" feature in developer options!! This will "carrier unlock" the carrier restriction so the phone can go to different "lesser or smaller" cell providers!! Verizon for example has a strict policy on activation of mobile devices on their network!! A non-Verizon G5 will not activate on their network at this time!! With all the security measures, LG's custom locked bootloader with kernel verify, rooting will be unlikely!!:crying::crying: While a "recovery" is available, without root permissions to flash or push the image, it's just a file on the computer!!
Click to expand...
Click to collapse
There are guys in the T-Mobile forum who have successfully unlocked their bootloader . I just picked up the g5 today. It's working well so far . how good is LG with updates ?
Sent from my VS987 using XDA-Developers mobile app
soundgirl101 said:
:crying::crying:None of LG G5 variants have an unlockable bootloader!! This is due primarily to Google agreements with various credit card providers for Android "Tap and Pay" feature to be used!! Other variants, like T-Mobile, will have an "OEM Unlock" feature in developer options!! This will "carrier unlock" the carrier restriction so the phone can go to different "lesser or smaller" cell providers!! Verizon for example has a strict policy on activation of mobile devices on their network!! A non-Verizon G5 will not activate on their network at this time!! With all the security measures, LG's custom locked bootloader with kernel verify, rooting will be unlikely!!:crying::crying: While a "recovery" is available, without root permissions to flash or push the image, it's just a file on the computer!!
Click to expand...
Click to collapse
That is NOT what the OEM Unlock function does at all.
Sent from my SM-G935V using Tapatalk
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
I just received a warranty replace device with NMF26U preinstalled, now i know i can't unlock the bootloader with this android version. How do i downgrade so i can unlock the device? Any ideas?
Verizon version or Google? If Verizon, you are out of luck. You can't downgrade a locked BL phone.
sliding_billy said:
Verizon version or Google? If Verizon, you are out of luck. You can't downgrade a locked BL phone.
Click to expand...
Click to collapse
verizon
palvarez05 said:
verizon
Click to expand...
Click to collapse
Can't do anything. No downgrading. You're out of luck.
When Verizon issued the patch to prevent unlocking the BL they also blocked the ability to downgrade. As far as finding a new exploit I wouldn't hold my breath. I have never seen a Verizon device that has successfully been exploited twice. Ever.
Did you order the warranty device through Verizon or Google?
My wife has a new Verizon Pixel on the way straight from Google. Despite being BL unlocked and rooted, it automatically updated. For some reason the update broke all audio on the phone. I'm really hoping google has a stockpile of verizon phones that aren't updated.
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
Getting an Unlocked Pixel 2 off EBay.
Once I unlock the bootloader, and put in my Verizon sim.......will Verizon lock my bootloader?
z
I don't think any carrier has control over locking the bootloader. They can however keep you from unlocking it, just not the other way around
zardiw said:
Getting an Unlocked Pixel 2 off EBay.
Once I unlock the bootloader, and put in my Verizon sim.......will Verizon lock my bootloader?
z
Click to expand...
Click to collapse
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Keithn said:
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Click to expand...
Click to collapse
The op is talking about bootloader being unlocked and your talking about the carrier/sim lock... Verizon pixels that were on a certain firmware were able to have their bootloader unlocked, and then it was patched. So pretty much all Verizon pixel 2 are not able to have the bootloader unlocked. Pixels straight from Google are able to have the bootloader unlocked. Now as far as the carrier/sim lock, either version, Verizon or Google, they come unlocked and. I'm pretty sure they can't be relocked. I believe they would just blacklist the device.
ice711 said:
The op is talking about bootloader being unlocked and your talking about the carrier/sim lock... Verizon pixels that were on a certain firmware were able to have their bootloader unlocked, and then it was patched. So pretty much all Verizon pixel 2 are not able to have the bootloader unlocked. Pixels straight from Google are able to have the bootloader unlocked. Now as far as the carrier/sim lock, either version, Verizon or Google, they come unlocked and. I'm pretty sure they can't be relocked. I believe they would just blacklist the device.
Click to expand...
Click to collapse
No, I am talking about both. I only mentioned to be aware that the device may be listed as unlocked due to not having carrier restrictions, but might still be a "Verizon Edition" with a non unlockable bootloader.
Keithn said:
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Click to expand...
Click to collapse
Keithn said:
No, I am talking about both. I only mentioned to be aware that the device may be listed as unlocked due to not having carrier restrictions, but might still be a "Verizon Edition" with a non unlockable bootloader.
Click to expand...
Click to collapse
Ahh gotcha. Sorry didn't get that when I read it the first time. When you put it this way, I now get what you were saying. Good advise! :good: :good: