I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Nick_Gl said:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Click to expand...
Click to collapse
Nothing it will work just fine. From what I understand just a slight difference for Europe. It will be fine.
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
You probably wouldn't get any updates. The trigger for that version probably wouldn't get to you. But I am not certain on that. Might be able to pull it via wifi with no SIM in it.
Do NOT relock your bootloader unless it is just before you are going to put it in a box to send back for warranty.
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
bobby janow said:
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
Click to expand...
Click to collapse
He made it sound like his pixel is from Verizon. In that case he can't lock and unlock the bootloader whenever he wants.
To the OP. What are you trying to do? It doesn't matter if you are on V. If it makes you feel better just flash U then. As long as you don't have twrp or root you will still get OTAs. Why would you want to lock your bootloader? You can have an unlocked bootloader and still take normal OTAs just fine . it its a Verizon sold pixel you won't be able to unlock once you lock.
fritzgerald said:
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Click to expand...
Click to collapse
Thanks wasn't sure. I'll just remember to side load the correct one in February.
aholeinthewor1d said:
He made it sound like his pixel is from Verizon. <snip>
Click to expand...
Click to collapse
It was certainly a little bit confusing, however, the last part of his post it said.. (device from Google) so I figured it was a GPixel activated on Verizon.
Related
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
Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks
I'm pretty sure all phones manufactured after a certain year(think it was 2014) were made so they can be used anywhere. As long as it has the necessary bands. You will not be able to flash other firmware, unless the bootloader gets unlocked and root becomes available...
Sent from my Pixel 2 XL using Tapatalk
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
It's not quite the same. It is unlocked, but the bootloader cannot be unlocked.
Erik1805 said:
Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks
Click to expand...
Click to collapse
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.
IDroidThere4Iam said:
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.
Click to expand...
Click to collapse
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.
mikeyinid said:
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.
Click to expand...
Click to collapse
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.
Erik1805 said:
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.
Click to expand...
Click to collapse
How do you adb sideload with a locked bootloader?
mikeyinid said:
How do you adb sideload with a locked bootloader?
Click to expand...
Click to collapse
Used this. Went great.
https://developers.google.com/android/ota
Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yea, we're talking about two different things.
mikeyinid said:
Yea, we're talking about two different things.
Click to expand...
Click to collapse
Yes thought so. No custom rom flashing for me, thats what you ment
Erik1805 said:
Yes thought so. No custom rom flashing for me, thats what you ment
Click to expand...
Click to collapse
But, I just learned something because I had no idea Google posted the OTA files like that
Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
this is an old post but im trying to see if anyone can help me with this adb sidload. I get an error that footer is wrong and cant get the android P beta to flash. any thoughts?
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
live4soccer7 said:
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
Click to expand...
Click to collapse
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
TonikJDK said:
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
Click to expand...
Click to collapse
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
live4soccer7 said:
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
Click to expand...
Click to collapse
It requires a manual command in fastboot. Doubt you'll do that accidently.
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
KittyRgnarok said:
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
Click to expand...
Click to collapse
Thanks everyone, that's exactly what I was looking for. I'm curious, what happens if I toggle the OEM unlock option on/off?
live4soccer7 said:
I'm curious, what happens if I toggle the OEM unlock option on/off?
Click to expand...
Click to collapse
That switch has been grayed out after the Verizon unlock, and it reads "Bootloader is already unlocked", so as far as I know it's not possible to toggle.
Thanks! Much appreciated.
Enjoy your Pixel and happy modding mate
I have a new XT2113-2 (TM) that is yet to be boot loader unlocked/rooted/etc. I don't want to do that until I am sure. I got this variant of the phone so I could unlock the bootloader, root, TWRP, etc and was afraid the "global" variant -3 might not work with USA 5G. The phone came with Android 11 installed (and has since auto-installed at least one security update). It shows the build as RZKS31.Q3-45-16-3-11 and the baseband ends with Kiev_TMO_CUST. I am using it on ATT (via Red Pocket) since TM service just sucks where I live. And I do get the 5G icon on it now.
But ideally, I want to get this to the original TM Android 10, which I think is shown here as the file XT2113-2_KIEV_TMO_10_QZKS30.Q4-40-95-6_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip as I hope it will undo some of the "security" crap Google has added to Android with each successive release.
So I need to be sure of the following:
1. Can I downgrade from 11 to 10?
2. Is there some reason to NOT use the firmware mentioned above? Should I use retail US (RETUS) instead? I am not sure the differences (it would be great if that would permit me to use this phone on Red Pocket Verizon but the IMEI now shows as incompatible on Verizon).
3. Must I unlock the boot loader to downgrade? I know I must to do other stuff and I have the unlock code on hand and ready to put it if needed. If I must unlock the boot loader to downgrade, will I have to re-unlock it afterwards? And, if so, will I have to go through the same process of getting a code or will the code I have now work?
4. How do I flash to do the downgrade? I have the Lenovo Rescue/Smart Assistant installed on my PC and was able to download the stock firmware (I assume it matches what is on there now) and stashed it aside. But is there some other tool needed?
5. Once I achieve downgrade, what is the best way to avoid having the thing auto-update to Android 11?
Thanks for your help with these questions.
If you are going to take this phone to AT&T, you will not get 5G if you unlock the bootloader. The NR band will be restricted. Downgrading from 11 to 10 generally doesn't work either.
I can't answer the rest of your questions.
RETIEF said:
If you are going to take this phone to AT&T, you will not get 5G if you unlock the bootloader. The NR band will be restricted. Downgrading from 11 to 10 generally doesn't work either.
I can't answer the rest of your questions.
Click to expand...
Click to collapse
Thanks for this response. I do have it on ATT (via Red Pocket) now and it does appear to get 5G now. I have not yet unlocked the bootloader, was thinking to do it, but considering that it would cause loss of 5G I think I will not and will just return the phone. Wow!
RETIEF said:
If you are going to take this phone to AT&T, you will not get 5G if you unlock the bootloader. The NR band will be restricted. Downgrading from 11 to 10 generally doesn't work either.
I can't answer the rest of your questions.
Click to expand...
Click to collapse
BTW - have you any references on this behavior? I am wondering if this is something that would affect ALL phones with unlocked boot loaders (like Pixel, OnePlus, etc). Thanks for the heads-up.
WARNING: ONLY DO THAT IF YOU ARE REALLY SURE AND DO BE CAREFULLY. I recommend you: do it not.
By downgrading to an older software, the bootloader in many cases can be destroyed, so your phone is completly bricked!
I write this from EXPERIENCE. My amazon fire is completed bricked, when i have flash a older SYSTEM. It can't turn on, no fastboot, no recovery!
whitedavidp said:
BTW - have you any references on this behavior? I am wondering if this is something that would affect ALL phones with unlocked boot loaders (like Pixel, OnePlus, etc). Thanks for the heads-up.
Click to expand...
Click to collapse
I suspect, but don't know, that all phones with unlocked bootloaders are blocked from 5g from AT&T. I know my kiev (RETUS) is.
RETIEF said:
I suspect, but don't know, that all phones with unlocked bootloaders are blocked from 5g from AT&T. I know my kiev (RETUS) is.
Click to expand...
Click to collapse
Thanks. Yet another reason to dislike ATT, I guess. Sadly, in my area TM coverage stinks. And this phone will not work on Verizon (unclear why but they reject the IMEI). And getting the Verizon variant will preclude ever rooting the thing. So I really feel trapped!
Likewise
RETIEF said:
I suspect, but don't know, that all phones with unlocked bootloaders are blocked from 5g from AT&T. I know my kiev (RETUS) is.
Click to expand...
Click to collapse
I always figured it was this
English Community-Lenovo Community
as my IMEI SV on the Metro/TMO variant is 05 rather than 07. Never tested with a locked bootloader though.
whitedavidp said:
BTW - have you any references on this behavior? I am wondering if this is something that would affect ALL phones with unlocked boot loaders (like Pixel, OnePlus, etc). Thanks for the heads-up.
Click to expand...
Click to collapse
Bootloader unlocked Pixels work fine on ATT 5G, don't know about OnePlus.