I saw a lot of people in the bootloader unlock thread talking about this. By flashing the stock factory image from Google, you haven't completely converted it to a Google phone. OTAs will still come from Verizon. There is almost no way to stop this: PLEASE be careful before taking OTAs in case Verizon does something shady with unlocked devices.
Lightn1ng said:
I saw a lot of people in the bootloader unlock thread talking about this. By flashing the stock factory image from Google, you haven't completely converted it to a Google phone. OTAs will still come from Verizon. There is almost no way to stop this: PLEASE be careful before taking OTAs in case Verizon does something shady with unlocked devices.
Click to expand...
Click to collapse
Ota's come from Google. Not Verizon. Your sim dictates what other BS happens with your phone. As long as you have a Verizon sim in a Verizon pixel you'll have a Verizon pixel. I'm pretty sure they pool the cid of Verizon pixels so they know which ones to allow bootloader unlocking and which ones to flag as ineligible.
mikeyinid said:
Ota's come from Google. Not Verizon. Your sim dictates what other BS happens with your phone. As long as you have a Verizon sim in a Verizon pixel you'll have a Verizon pixel. I'm pretty sure they pool the cid of Verizon pixels so they know which ones to allow bootloader unlocking and which ones to flag as ineligible.
Click to expand...
Click to collapse
It's based on the IMEI number. Verizon OTAs differ from Google ones, even if they come from google
So, if I have a Google firmware installed on an unlocked Verizon device using a T-Mobile SIM, will I get OTA's at all?
PuffDaddy_d said:
So, if I have a Google firmware installed on an unlocked Verizon device using a T-Mobile SIM, will I get OTA's at all?
Click to expand...
Click to collapse
Probably still Verizon OTAs.
Lightn1ng said:
Probably still Verizon OTAs.
Click to expand...
Click to collapse
How can I get a Verizon OTA with a T-Mobile SIM? I'm assuming I won't get an OTA at all and will need to side load. Just looking for confirmation...
PuffDaddy_d said:
How can I get a Verizon OTA with a T-Mobile SIM? I'm assuming I won't get an OTA at all and will need to side load. Just looking for confirmation...
Click to expand...
Click to collapse
It uses the IMEI number to verify which OTAs to download. That doesn't change, it's tied to your specific phone
Why even bother with OTAs at all?
If you took the time to unlock the bootloader and get root, why would you not flash the stock images when they show up on googles developers page?
If you've loaded TWRP at all or mounted system rw; OTAs will not work.
I unchecked OTAs in developer options.
When new ones come out, I'll update when I feel like it.
PuffDaddy_d said:
How can I get a Verizon OTA with a T-Mobile SIM? I'm assuming I won't get an OTA at all and will need to side load. Just looking for confirmation...
Click to expand...
Click to collapse
For clarification, OTAs all come from Google, but Google occasionally has different OTAs for phone variants depending on your carrier associated IMEI (If you go to Google's OTA download page, you can see these in the description - there will be multiple OTAs for a date with different carriers).
Hey just came across this thread and not sure if the general consensus is accurate as far as it updating to the IMEI or not. I am currious though since I do have a Nexus 6 that has the VZW IMEI (starting with 99) but want to say once I switched to the FI sim card and away with VZW and flashed the FI software for the Nexus 6 it did in fact update to only the FI software from that point on. I could be wrong but I do not recall ever having to flash the FI software after updates due to it being VZW relased software. And in case anyone care I did notice that the unlockable Google software does in fact have VZW programs in it they are frozen by default in Titanium Backup. But like I said just 2 cents worth and not able to confim it 100%.
What about EE uk, can it be unlocked aswell?
I mean, Pixel 2 and 2 XL's are SIM unlocked. So really it depends who you pay money to for service.
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
joloxx9joloxx9 said:
What about EE uk, can it be unlocked aswell?
Click to expand...
Click to collapse
Unfortunately, we're still not sure man. You can always tryyyyy
joloxx9joloxx9 said:
What about EE uk, can it be unlocked aswell?
Click to expand...
Click to collapse
No, I have unlocked the bootloader on my wife's pixel 2 from EE, I can now load custom software, so reloaded Google's factory image, but the phone is still sim locked to EE. It's definately an IMEI thing, not software.
danlat1415 said:
No, I have unlocked the bootloader on my wife's pixel 2 from EE, I can now load custom software, so reloaded Google's factory image, but the phone is still sim locked to EE. It's definately an IMEI thing, not software.
Click to expand...
Click to collapse
EE bootloader can be Unlocked, I was reffering to that.
Yes the EE bootloader can be unlocked. Just use the same method as on Verizon.
Related
4.4.4 appeared on my Verizon Prepaid Moto G this morning. Soak test is over.
Reckoning said:
4.4.4 appeared on my Verizon Prepaid Moto G this morning. Soak test is over.
Click to expand...
Click to collapse
So what are the changes? I know there is more than just camera quality and pausing videos. they lock down anything? 4.3 to 4.4 took away my tethering and a few other things. what did they lock this time
redking117 said:
So what are the changes? I know there is more than just camera quality and pausing videos. they lock down anything? 4.3 to 4.4 took away my tethering and a few other things. what did they lock this time
Click to expand...
Click to collapse
Haven't had a chance to check yet. At first glance the only thing I've noticed is it seems a little quicker.
Does this re-lock the bootloader if you paid for the unlock code?
Reckoning said:
Haven't had a chance to check yet. At first glance the only thing I've noticed is it seems a little quicker.
Click to expand...
Click to collapse
Dat Windows Phone Dialer
Dadud said:
Does this re-lock the bootloader if you paid for the unlock code?
Click to expand...
Click to collapse
My phone's not unlocked, I have no idea.
Reckoning said:
My phone's not unlocked, I have no idea.
Click to expand...
Click to collapse
wasnt able to install it, even after reverting to stock firmware through fastboot flash files.
Edit: tried it one last time, got it to sucessfully install, running 4.4.4 now
Dadud said:
Does this re-lock the bootloader if you paid for the unlock code?
Click to expand...
Click to collapse
I'm also interested in this. Though, I may just wait, and use this opportunity to flash a stable 4.4.4 based ROM instead. Don't want to lose root or bootloader unlock.
RedCrow101 said:
I'm also interested in this. Though, I may just wait, and use this opportunity to flash a stable 4.4.4 based ROM instead. Don't want to lose root or bootloader unlock.
Click to expand...
Click to collapse
It's safe. Rooted on 4.4.4 with a custom recovery again.
Added Hotspot
Dadud said:
It's safe. Rooted on 4.4.4 with a custom recovery again.
Click to expand...
Click to collapse
What is safe? You mean it is safe to revert back to stock (and take the xt1028 4.4.4 update) and still not lose root or have bootloader locked again?
classic757 said:
What is safe? You mean it is safe to revert back to stock (and take the xt1028 4.4.4 update) and still not lose root or have bootloader locked again?
Click to expand...
Click to collapse
I've looked everywhere to try to find how to unlock and root. Can you show me where you found out how to do this and does it still stay prepaid if you do?
Sent from my LG-D850
roughneckboren said:
I've looked everywhere to try to find how to unlock and root. Can you show me where you found out how to do this and does it still stay prepaid if you do?
Sent from my LG-D850
Click to expand...
Click to collapse
See my post (#923) on this thread: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/post54076489
And yes, it is still prepaid after unlocking.
Hope this helps.
Unlocked xt1028
classic757 said:
See my post (#923) on this thread: http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/post54076489
And yes, it is still prepaid after unlocking.
Hope this helps.
Unlocked xt1028
Click to expand...
Click to collapse
When the new cell unlock law goes into effect Motorola should have to give out unlock codes for the XT1028..
I Doubt it. Seeing as the Moto G was manufactured before the law went into effect.
classic757 said:
What is safe? You mean it is safe to revert back to stock (and take the xt1028 4.4.4 update) and still not lose root or have bootloader locked again?
Click to expand...
Click to collapse
you'll lose root but its not hard to get it back.
Takenover83 said:
I Doubt it. Seeing as the Moto G was manufactured before the law went into effect.
Click to expand...
Click to collapse
I read nothing in the bill that prohibits the unlocking of any device manufactured prior to the enactment date of the legislation. Specifically, the bill allows unlocking at the direction of the owner of the device:
(c) Unlocking at Direction of Owner.--Circumvention of a
technological measure that restricts wireless telephone handsets or
other wireless devices from connecting to a wireless telecommunications
network--
(1)(A) as authorized by paragraph (3) of section 201.40(b)
of title 37, Code of Federal Regulations, as made effective by
subsection (a); and
(B) as may be extended to other wireless devices pursuant
to a determination in the rulemaking conducted under subsection
(b); or
(2) as authorized by an exemption adopted by the Librarian
of Congress pursuant to a determination made on or after the
date of enactment of this Act under section 1201(a)(1)(C) of
title 17, United States Code,
may be initiated by the owner of any such handset or other device, by
another person at the direction of the owner, or by a provider of a
commercial mobile radio service or a commercial mobile data service at
the direction of such owner or other person, solely in order to enable
such owner or a family member of such owner to connect to a wireless
telecommunications network, when such connection is authorized by the
operator of such network.
Dadud said:
you'll lose root but its not hard to get it back.
Click to expand...
Click to collapse
Thanks.
I flashed stock Verizon 4.4.2 firmware and then took 4.4.4 update via ota.
Tired of flashing nightlies and custom roms with all their bugs and issues.
Glad to be back on stock and re-rooted with TWRP installed.
---------- Post added at 08:36 PM ---------- Previous post was at 08:31 PM ----------
Reckoning said:
When the new cell unlock law goes into effect Motorola should have to give out unlock codes for the XT1028..
Click to expand...
Click to collapse
That would be great if they were to do that.
classic757 said:
Thanks.
I flashed stock Verizon 4.4.2 firmware and then took 4.4.4 update via ota.
Tired of flashing nightlies and custom roms with all their bugs and issues.
Glad to be back on stock and re-rooted with TWRP installed.
Click to expand...
Click to collapse
Yeah, kept getting systemui force closes after installing a few things, and usually while listening to my podcasts. i'll probably venture back into roms once they hammer out that issue
Dadud said:
Yeah, kept getting systemui force closes after installing a few things, and usually while listening to my podcasts. i'll probably venture back into roms once they hammer out that issue
Click to expand...
Click to collapse
I hear you. The only reason I used custom roms was because Verizon had not yet pushed the 4.4.4 ota and now that they have and I have it I have no need for customs roms. Actually I find the 4.4.4 update to be quite a surprise. The camera is much improved imo and the rom seems to be a bit more quicker than before. All-in-all I am glad I reverted back to stock rom and I plan on staying with stock.
P.S. To my understanding Android L is coming later this year to the moto G.
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...
fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.
JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse
superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
it leaves a copy of the fxz on your computer.
sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.
Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.
Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
The guys who brought us sunshine for HTC devices just released their bootloader unlock tool for those of us with Verizon Pixels. YAY!
Check it out here http://theroot.ninja/depixel8.html
Sweet, will do it in the morning for sure.
Works perfectly first try. Wonderful news.
Few questions.
Does this do a wipe on the phone?
Will this allow you to flash stock images from google with no issues and remain unlocked?
If you unlock it and then relock it(without flashing the stock image from google), does it stay unlockable without exploit?
qwer777 said:
If you unlock it and then relock it(without flashing the stock image from google), does it stay unlockable without exploit?
Click to expand...
Click to collapse
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.
Is there a way to do this without wiping user data?
SophieTurner said:
Is there a way to do this without wiping user data?
Click to expand...
Click to collapse
Unfortunately no. Unlocking or locking the bootloader wipes user data. Its a security feature. This is how all Pixel / Nexus phones have been for a while now.
DELETED
dbrohrer said:
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.
Click to expand...
Click to collapse
Alright. Thanks so much for the info! I'm guessing they're tying the lock to the IMEI then.
Could one unlock the bootloader on the Verizon variant, flash the stock Google firmware and receive OTA updates from Google? In other words, converting the phone to the unlocked version software wise.
darabo said:
Could one unlock the bootloader on the Verizon variant, flash the stock Google firmware and receive OTA updates from Google? In other words, converting the phone to the unlocked version software wise.
Click to expand...
Click to collapse
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?
deesugar said:
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?
Click to expand...
Click to collapse
They have never done this for other devices that have had their bootloaders unlocked, so I doubt it.
deesugar said:
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?
Click to expand...
Click to collapse
I highly doubt they'd go as far as shutting down one's service. Jailbreaking and modifying one's device has been deemed legal by the US Supreme Court IIRC, it's your own property to do what you wish after all.
Now if you were to hack Verizon's servers directly for some reason then that'd be a completely different story...
darabo said:
I highly doubt they'd go as far as shutting down one's service. Jailbreaking and modifying one's device has been deemed legal by the US Supreme Court IIRC, it's your own property to do what you wish after all.
Now if you were to hack Verizon's servers directly for some reason then that'd be a completely different story...
Click to expand...
Click to collapse
Alright so I guess the remaining question is can you flash the stock Google firmware and receive OTA updates from Google? Thereby turning your Verizon phone into a Google Store version with no issues?
dbrohrer said:
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.
Click to expand...
Click to collapse
They are backorder for me until the 12/9 wonder what version they will ship with.
JustusIV said:
They are backorder for me until the 12/9 wonder what version they will ship with.
Click to expand...
Click to collapse
It will almost certainly ship with the October security patch. The kicker is the phone will check for updates as soon as you sign in and connect to the internet. I don't know if it will force the update or if it will just notify you that there is one.... And I don't think you can boot the phone up without a sim on the first boot to get around this. I think it requires and internet connection to get through the setup.
---------- Post added at 02:57 PM ---------- Previous post was at 02:48 PM ----------
deesugar said:
Alright so I guess the remaining question is can you flash the stock Google firmware and receive OTA updates from Google? Thereby turning your Verizon phone into a Google Store version with no issues?
Click to expand...
Click to collapse
Negative. You cannot turn a Verizon phone into a Google phone.
They are the same phone. The difference is a server side switch that is being made. Maybe there is an IMEI database with all of the Verizon phones or something similar. As soon as your phone connects to the internet, it will check and confirm that its in that database and the "OEM unlocking" toggle will be grayed out, no matter what Google factory image you are on.
The beginning and the end is the OEM unlock toggle. dePixel8 is just forcing the switch so that you can unlock the bootloader. If you flash a new image or just reboot you will see that the toggle will be flipped, but it was still be grayed out.
If you want an unlocked bootloader, unlock it and leave it unlocked. If you don't care or want to stay stock, leave it alone.
DELETED
dbrohrer said:
It will almost certainly ship with the October security patch. The kicker is the phone will check for updates as soon as you sign in and connect to the internet. I don't know if it will force the update or if it will just notify you that there is one.... And I don't think you can boot the phone up without a sim on the first boot to get around this. I think it requires and internet connection to get through the setup.
---------- Post added at 02:57 PM ---------- Previous post was at 02:48 PM ----------
Negative. You cannot turn a Verizon phone into a Google phone.
They are the same phone. The difference is a server side switch that is being made. Maybe there is an IMEI database with all of the Verizon phones or something similar. As soon as your phone connects to the internet, it will check and confirm that its in that database and the "OEM unlocking" toggle will be grayed out, no matter what Google factory image you are on.
The beginning and the end is the OEM unlock toggle. dePixel8 is just forcing the switch so that you can unlock the bootloader. If you flash a new image or just reboot you will see that the toggle will be flipped, but it was still be grayed out.
If you want an unlocked bootloader, unlock it and leave it unlocked. If you don't care or want to stay stock, leave it alone.
Click to expand...
Click to collapse
Where are you getting this information?
cambunch said:
Where are you getting this information?
Click to expand...
Click to collapse
Jcase comments on the Pixel XL forum, other Pixel XL forum comments, my own device / experience. I have a Pixel 128gb from Verizon.
Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding
Can you provide more detailed instructions please
Im serious thats all there is to it.
What parts are you having problems with?
Didn't work for me, unfortunately. Phone promptly asked for SIM Pin.
zerocover said:
Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding
Click to expand...
Click to collapse
Just out of curiosity, will this be possible to do on a Verizon model? Obviously not flashing the ones above but making a VZ version?
Sent from my Nexus 6 using XDA-Developers Legacy app
illitero said:
Didn't work for me, unfortunately. Phone promptly asked for SIM Pin.
Click to expand...
Click to collapse
This does not unlock your phone, this is an unlocked rom with no carrier bloatware.
You must already have an unlocked phone. If your phone is paid off call your carrier and ask for the pin.
ozzmanj1 said:
Just out of curiosity, will this be possible to do on a Verizon model? Obviously not flashing the ones above but making a VZ version?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be
zerocover said:
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be
Click to expand...
Click to collapse
I haven't bought a priv yet. But i came across a killer deal for a VZ model that's I'd be using on tmo. I'm going to be snagging it. But will test for sure and let you know. I am just trying to read up on the phone before ordering it on how to get rid of bloat and whatnot without root. Thank you very much for making the file.
Sent from my Nexus 6 using XDA-Developers Legacy app
zerocover said:
This does not unlock your phone, this is an unlocked rom with no carrier bloatware.
You must already have an unlocked phone. If your phone is paid off call your carrier and ask for the pin.
Click to expand...
Click to collapse
Haha, duh. I'm sorry. Very distracted, late night for me when I found this thread. plz4giv
zerocover said:
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be
Click to expand...
Click to collapse
I tried it and it worked. However, once it boots it will install a software update which takes you back to the bloated VZW version. Perhaps there's a way to block that update?
dakota_96 said:
I tried it and it worked. However, once it boots it will install a software update which takes you back to the bloated VZW version. Perhaps there's a way to block that update?
Click to expand...
Click to collapse
Totally possible. If we had root just modify the host file and set the verizon server update ip to localhost. You should be able to install DNS66 and do something similar. This will take digging on your end to figure out what the update IP is though.
I have an ATT Priv, so if I flash this I'll get next time OTA from BlackBerry instead of ATT? Saw the one above with the Verizon update and went back to bloated version.
Reporting back in to verify that it worked flawlessly on both at&t and t-mobile variants I have. Now if only we could get root lol
Thank you so much for your effort
I have an ATT branded Priv which got unlocked from ATT directly and has successfully installed this ROM. It works perfectly without any ATT bloatwares, but this built is old and when I check for system update it shows my system is up to date. However the most recent built for unlocked factory image is AAL202 according to the blackberry official reload software website.
So does this ROM OTA updates via ATT server or directly from Blackberry server?
zerocover said:
Im serious thats all there is to it.
What parts are you having problems with?
Click to expand...
Click to collapse
dude what about the firmware version? and update status?
is there one available for the AAL230 update? and is the at&t version provided here applicable on my priv with AAL230 update installed?
zerocover said:
Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding
Click to expand...
Click to collapse
Is this possible for the Verizon moto z play???
calistoz said:
is there one available for the AAL230 update? and is the at&t version provided here applicable on my priv with AAL230 update installed?
Click to expand...
Click to collapse
AT&T runs a newer version of android then the international. If you want stockish android with no carrier bloat go international.
jzamalot said:
Is this possible for the Verizon moto z play???
Click to expand...
Click to collapse
Send me a moto z play and we shall see. Otherwise sorry I can't test it.
With the very recent Verizon Priv update can the de-bloated image be updated?
Option is greyed out on mine ... it's a Google Store phone. purchased from Google specifically so I would be able to unlock.
And I can't. I'm p*ssed. Very unhappy.
Are you saying you can't check on the OEM unlocking option under Developer Options?
I just checked and I was able to do it.
Yes, that's exactly what I'm saying. It's greyed/disabled.
and per Google, I have a VZW branded phone.
So now it's going back. $900 wasted.
_litz said:
and per Google, I have a VZW branded phone.
So now it's going back. $900 wasted.
Click to expand...
Click to collapse
Did you buy from Verizon or Google store?
dubt17 said:
Did you buy from Verizon or Google store?
Click to expand...
Click to collapse
Google Store. They are selling 3 models of Pixel 4 : unlocked, VZW locked, and Google Fi.
They sent me a VZW one.
I was able to unlock mine no problem. I bought the unlocked version from Google even though I'm on Verizon. I put my Verizon sim in, skipped all the setup, ticked to allow oem unlocking, rebooted to bootloader and unlocked no problem.
That's a bummer yo.
_litz said:
Google Store. They are selling 3 models of Pixel 4 : unlocked, VZW locked, and Google Fi.
They sent me a VZW one.
Click to expand...
Click to collapse
Are you just going to return and cancel or are they exchanging it for you?
That sucks..
For those who unlock. Do you use something for Google Pay? (That magisk thing?)
Also...do you know if device theft protection still works if stolen?
I recently tried to root my Pixel 2 but then I rolled back because I wasn't sure of these two things.
Sent from my Pixel 4 using Tapatalk
does this mean we can flash magisk root if we unlock the bootloader?
thesebastian said:
That sucks..
For those who unlock. Do you use something for Google Pay? (That magisk thing?)
Also...do you know if device theft protection still works if stolen?
I recently tried to root my Pixel 2 but then I rolled back because I wasn't sure of these two things.
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
I haven't unlocked in years but I do read about it. I think you only need Magisk if you're going to root. Bootloader unlock only needs a kernel to bypass the unlock check. But since there are no kernels yet you can't use GP if you unlock the P4.
Until Google releases the factory images for the P4, it may be hard to install Magisk. Without TWRP, we need to use the boot image modification method. Unless you are competent enough to find and extract the boot.img from your phone, you will have to wait until the factory images are released to get your hands on it.
So while it is probably technically possible to root right now, the ave person that isn't an Android OS expert probably won't have the technical skills to do it.
To those asking ... yes, I bought from google store. They sent me the verizon variant instead of the unlocked variant.
re: google pay/etc (anything requiring safetynet), Magisk can provide root, and its Magiskhide component can hide that root from SafetyNet. Installing Xposed inside Magisk, however, cannot be hidden.
re: installing magisk if you unlock the bootloader - that's a yes.
Anyone in here extracted the boot.img from the factory image yet?
I'm on a mac right now so I was hoping to just download someone elses.
My OEM unlock is available. I'm waiting for root. The only thing I want right now is hotspot. I was hoping that since it's an unlocked phone that it would work straight out of the box. I've been with LG since the G4 and I've always bought mine unlocked and the hotspot works without having to go through Verizon and pay for the subscription. I'm on the old grandfathered unlimited data plan. I'd hate to have to return this phone and go with the G8 but I don't have internet where I live and I have to have hotspot.
Spookymyo said:
My OEM unlock is available. I'm waiting for root. The only thing I want right now is hotspot. I was hoping that since it's an unlocked phone that it would work straight out of the box. I've been with LG send the G4 and I've always bought mine unlocked and the hotspot works without having to go through Verizon and pay for the subscription. I'm on the old grandfathered unlimited data plan. I'd have to have to return this phone and go with the G8 but I don't have internet where I live and I have to have hotspot.
Click to expand...
Click to collapse
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
cntryby429 said:
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
Click to expand...
Click to collapse
?? ...I did not... I'll do a search
cntryby429 said:
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
Click to expand...
Click to collapse
Would you mind sharing your unpatched boot.img?
Shponglized said:
Would you mind sharing your unpatched boot.img?
Click to expand...
Click to collapse
You can get it with the system images that are available from Google. It'd be hesitant to give you the one I downloaded in case you have one of the other 2 variants of the October release (this assumes that the boot.img's are even different which in not sure).
I got a tester device so it was already unlocked. I'm just waiting for TWRP before I start messing with it.