Related
I have a general question for my note 2 possibly moving to a note 4. Can someone tell me the difference between unlocking a phone ans rooting. My note 2 is att and rooted and have it on the straight talk Sim. I picked up a new note 4 for 300 bucks can rooting it do the same as unlocking it.
I'm not in USA but believe I can help clarify. Unlocking relates to the ability to use your phone
on a different network than what it's locked to.
Rooting is completely different, it gives you total control over your device. However be aware that ATT version of N4 is locked up tight and cannot be rooted at the moment. May I spontaneously combust if my facts are wrong.
Hahaha OK well thank you I'll get it unlocked for starters. Straight talk runs on the ATT network so I'll get it unlocked to safe
What is the best way to unlock a phone? Is it a similar to do like flashing via Odin?
You purchase a code, then you put in a different carrier sim card, then type in the code, and the phone is carrier unlocked. No flashing necessary.
Rooting means gaining access to the file system of your phone to install apps, delete files, etc.
If you have no warranty on your phone, you may be able to downgrade to 4.1.1, unlock, and run OTA updates to get back to KK.
I have the Canadian version (sgh-i317m) of the Note 2 that was running the latest 4.4.2. I used Odin to flash back to stock 4.1.1 which tripped the knox counter, unlocked, and flashed back to stock 4.4.2.
I purchased a G4 h815 with hopes of unlocking the bootloader. It turned out to the the giveaway USA variant so LG will not allow bootloader unlock. Since it was still on 5.1 I was able to put a rooted 5.1 stock build on it using Low Effort Root thanks to this thread http://forum.xda-developers.com/g4/...zw-intl-variants-soon-root-lg-t3164765/page64. My question is where do I go from here? If I put a non-rooted MM ROM on it will I be able to continue upgrading the ROM or will that be a dead end? Should I put a stock ROM on it that will be able to receive OTAs from LG? If so which one do I need in order to guarantee that I can get OTAs? If it is not possible to retain root, how can I insure that I can at least have tethering available? I am not new to rooting and ROMing but I am new to locked bootloaders and new MM security issues. I am a net10 user (AT&T network) since that is the only good signal in my area. I bought this phone for the superior camera, micro sd slot and general good value in a used phone but I fear that it is at a development dead end. Any insights, suggestions or resources that anyone can point me toward. I have searched extensively in these LG4 forums and elsewhere without seeing these issues directly addressed. My next step would be to give up on LG and go with a phone that allows development like an HTC One M9.
Thanks in advance!
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
tuxdreamerx said:
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
Click to expand...
Click to collapse
Verizon model is fine for what the phone is.
You shouldn't have any issues using it on T-Mobile USA . Verizon phones are sim unlocked . The only thing with the Verizon version is that if it had the update where they don't let the bootloader unlock then you can't unlock it and root. Besides that you can use it on TMobile as a regular Google phone.
Sent from my Pixel XL using Tapatalk
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
This is partially false, I'm using a Verizon pixel XL on TMO and when I dropped out of beta, Google rolled out the TMO branch to my phone.
If you can depixl8 it and unlock the bootloader, you can flash custom Roms or the factory images to your heart's desire with no issues. Just never relock the bootloader, since it won't be able to be unlocked again(if it truly is a Verizon pixel XL)
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
You can sideload updates to a locked device so OP could sideload a current ota from tmobile. It can in fact beneficial to run the tmobile software on tmo because of optimizations for network connectivity
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
STraver said:
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
Click to expand...
Click to collapse
Should be able to just pop in the ATT sim
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I guess that'll be the big question. If the phone was only a display model since it was released. I wonder if the display models get the updates pushed automatically... I will find out tomorrow.
Well the phone came with 7.1.2 so no fun for me. Thanks for the info from everyone.
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Grubling said:
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Click to expand...
Click to collapse
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
tuxdreamerx said:
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
Click to expand...
Click to collapse
Google points to that being a Verizon SKU. But with the build number being non-Verizon, you might be able to unlock it.
There may be some relevant information here: https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
Count your blessings, most of us with Verizon models are still locked on other carriers.
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
zfk110 said:
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
Click to expand...
Click to collapse
You can unlock the bootloader on Verizon.
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
I literally just did this 2 months ago. Got a pixel xl and it was a verizon phone but I have Tmobile. The phone can be unlocked, it can be rooted, it can be rommed, yes it can! Mine came with 711 or 712 cant remember but whatever doesnt matter. Just follow the guide in the other thread by @Homeboy76, it's a GREAT read and tutorial. It will put you from stock nougat to stock pie, but afterwards you can go to nougat, oreo, or pie. I know because after I did it, i went to an custom rom, then to a custom oreo rom, back to stock pie, back to custom pie lol. I would put a link up to the thread but idk how to do hyperlinks lmao, i skipped that day of school.
Hi all, I wonder if anyone knowledgeable out there could assist?
I am in the UK and have bought a manufacturer-refurbished unlocked Xperia XA2 phone.
A friend of mine is in rural USA and can only use the Verizon network.
I am aware that Verizon only allow certain phones for use on their network and I discovered that the XA2 was now on their list of officially acceptable phones
So here is my question. I intend to install lineageos on this phone which of course will require unlocking the bootloader.
If I go ahead and put lineage on having unlocked the bootloader, will this phone still work on Verizon? I will be posting the phone to my friend and the last thing I want is for the phone to refuse to play with Verizon once he switches it on.
Can anyone advise of anything I need to be aware of before proceeding, or is my plan good?
Thanks!!
pingers5 said:
Hi all, I wonder if anyone knowledgeable out there could assist?
I am in the UK and have bought a manufacturer-refurbished unlocked Xperia XA2 phone.
A friend of mine is in rural USA and can only use the Verizon network.
I am aware that Verizon only allow certain phones for use on their network and I discovered that the XA2 was now on their list of officially acceptable phones
So here is my question. I intend to install lineageos on this phone which of course will require unlocking the bootloader.
If I go ahead and put lineage on having unlocked the bootloader, will this phone still work on Verizon? I will be posting the phone to my friend and the last thing I want is for the phone to refuse to play with Verizon once he switches it on.
Can anyone advise of anything I need to be aware of before proceeding, or is my plan good?
Thanks!!
Click to expand...
Click to collapse
Hi
If you just want to make it usable with Verizon, you don't need to put lineage, you just need to download flashtool and flash US's firmware, in order to make it 99% compatible.
If u want to put lineage, knowing that it isn't an official firmware, be aware that it may work as it may not work. 90% it will work, because lineage is made in order to remove brand limits, but...
Do what you want, but be aware that there are some things that may not work.
Here in Italy even if a phone is brandized (like Vodafone, etc.) you are still able to use it with other operators, and if you want to debrand it, it is just in order to remove operator's apps or animations (e.g. Vodafone boot animation), to get stock Sony ones. I don't know what changes in the US or in the UK.
Regards,
F.
Hi, thanks for the reply - just for clarity, my enquiry is on a network level - ie, will verizon block a phone simply because it has lineage on it. I am very familiar with modding and how lineage affects the phone so that is not what I need to know.. Since verizon are finicky about which models are usable with their network in the USA, my question is really an extension of that - do they block phones (which work fine with stock) running a non-stock rom (eg based on the fact they detect an unlocked bootloader). Want to put lineage on for all the good reasons to put lineage on - notably bloatware removal etc etc. Is there anyone out there running lineage on verizon in the USA?
faby GT said:
Hi
If you just want to make it usable with Verizon, you don't need to put lineage, you just need to download flashtool and flash US's firmware, in order to make it 99% compatible.
If u want to put lineage, knowing that it isn't an official firmware, be aware that it may work as it may not work. 90% it will work, because lineage is made in order to remove brand limits, but...
Do what you want, but be aware that there are some things that may not work.
Here in Italy even if a phone is brandized (like Vodafone, etc.) you are still able to use it with other operators, and if you want to debrand it, it is just in order to remove operator's apps or animations (e.g. Vodafone boot animation), to get stock Sony ones. I don't know what changes in the US or in the UK.
Regards,
F.
Click to expand...
Click to collapse
I have the 6 pro unlocked bought from Google. I use it on Verizon. I found out that when I got the phone and put the Sim in that the November update was not downloaded and installed. I factory reset the device and did not insert the SIM and I got the update. I now have SD1A.210817.036 installed. I this the correct version? I understand there is a November update 037 now but I don't see that. Now I am concerned that when the December update comes out that I wont get that either. Does anyone here know if Google and Verizon have fixed this issue?
Thanks
We don't know because it's just too early to tell. Word is they stopped pushing the .037 OTA at all, although I don't know that from personal experience. I've got the unlocked P6P running on AT&T and I got all the OTAs almost immediately. The next OTA should be out next Monday, but I believe Verizon variants have often lagged at least a little when though the OTA is available directly from Google for all variants at the same time.
Also commonly, after several updates the Verizon version of the firmware gets merged into a single universal firmware.
Regardless of any of this, you can flash either the Verizon version of the OTA manually, getting it directly from Google's site. You may even be able to flash the non-Verizon OTA manually, but there's no reason to avoid the Verizon version since you're using it with Verizon.
With the Pixel 5, unlocked but using Verizon as my service provider: there was a 50-50 shot on some sort of delay on updates. I think it has to do with their mmWave 5G and other providers (US and international) either do not use mmWave; or aren't as proprietary as Verizon.
Is there any benefit to running the Verizon version on an unlocked pixel 6 pro?
RVO27 said:
Is there any benefit to running the Verizon version on an unlocked pixel 6 pro?
Click to expand...
Click to collapse
The best answer is "maybe", leaning towards "probably".
For example, and probably a bad example but the only one I got. When I got my unlocked HTC 10 before I got the Pixel 1 in 2016, and I was still with Verizon at the time, I had no idea that I was going to have to jump through hoops to get Verizon's radio.img on my HTC 10, which was rooted so no big deal. Now maybe there was a whole Verizon firmware I could flash, but if I just wanted to use the regular unlocked HTC 10 firmware, I had to put the Verizon radio.img on there to even work on the network.
On the Pixels, I don't think it's ever been quite like that. I think you can use the regular firmware just fine on Verizon, but maybe, just maybe, it will work better with their proprietary bits that come with the Verizon version of the firmware.
Also, I know sometimes in the past that if you had the unlocked firmware on a device but used a Verizon SIM (or in other cases with some phones, an AT&T SIM, and probably applied to T-Mobile too), that you would then receive an OTA automatically to put you on their particular variant of the most recent firmware. So unless you disabled updates in Developer Options, you'd get the "proper" firmware for your usage anyway, and of course, being rooted is the ultimate method to avoid the proprietary variant of the firmware since OTAs will most likely refuse to even update a rooted device, although you should still turn automatic updates off since there's a chance it could instead soft-brick your device.
jjbender said:
I have the 6 pro unlocked bought from Google. I use it on Verizon. I found out that when I got the phone and put the Sim in that the November update was not downloaded and installed. I factory reset the device and did not insert the SIM and I got the update. I now have SD1A.210817.036 installed. I this the correct version? I understand there is a November update 037 now but I don't see that. Now I am concerned that when the December update comes out that I wont get that either. Does anyone here know if Google and Verizon have fixed this issue?
Thanks
Click to expand...
Click to collapse
I have an unlocked p6 (not pro) that I got from Amazon which I am using on Verizon. When I first set it up without a sim card it got the 36 update OTA without a problem. I put in the sim card and didn't receive the 37 update long after it was released. Finally I tried an inactive Mint sim (t-mobile network) and got the update when I checked for a system update using the settings menu. It probably would have worked without a sim also.
Rumors are that there will be a December update so I will be checking then. If I don't get it I will try without a sim or with an inactive sim. But that will mean that automatic updates don't work for unlocked p6s on verizon.
I did finally sideload the .037.A1 which is the Verizon version so I will see if I start getting the OTA updates.
Thanks all
sdbe said:
Rumors are that there will be a December update so I will be checking then.
Click to expand...
Click to collapse
For clarification, if you didn't know (forgive me if you did), the Pixel 6/Pro will receive an update every single month from the time it came out until five years later (so ~ October 2026). Especially some of the later years they might only be security updates - not Android version updates, but they will come like clockwork I believe the first Monday of every month.
Personally i wouldn't use the vzw firmware as there are hardware differences between the two especially radio