Related
This morning i finally relented and installed the 4.4 update (kitkat?) on my droid razr maxx hd. now im stuck at the red M motorola splash screen thing. is there any way i can fix this? I went to verizon and they wouldent do anything for me. I need my phone for work every day so help is greatly appreciated. i also tried the power volume down to restore factory settings or whatever but it just goes to the M screen forever. the only thing that DOES come up from those menus is ap fast boot. not sure if thats helpful or not. PS im new to this stuff so noob friendly responses please!
Were you rooted at all? Did you modify your system in any way (froze or uninstalled stock apps)? If so, that's why.
Go here to get yourself back in shape:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
f
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else.
i will try this link and post back in a couple hours i have to go take care of a few things. thank you for the quick response.
KiraTheSavior said:
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else
Click to expand...
Click to collapse
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.
ok
iBolski said:
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.
Click to expand...
Click to collapse
attempting it now. will post results.
it worked!
KiraTheSavior said:
attempting it now. will post results.
Click to expand...
Click to collapse
it worked im on kitkat and everythings great! thank you so much for the help! it was really easy with the step by step you linked. now i think ill try rooting and unlocking, if i mess it up i can always flash it like i just did and fix it right?
could you link me to the root/unlock tutorial for my phone? sorry im noob XD
Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.
no
iBolski said:
Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.
Click to expand...
Click to collapse
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?
KiraTheSavior said:
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?
Click to expand...
Click to collapse
You should have just ignored the update until after you unlocked the phone. The link I sent you to was meant to get you updated to KK before the 183.46.10 update. The previous KK update allowed you to unlock your bootloader. Now, that is no longer possible. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
You can still root the phone, though. Search for towelroot and you can install that and run it to root your device.
One thing you could try is once you've rooted, try running Motopocalypse to see if it will unlock your bootloader. Either it will or it won't. It won't hurt your phone in any way or brick it.
lame...
iBolski said:
It's rootable but it's not unlockable anymore. You have lost the ability to unlock the bootloader. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
Search for towelroot and you can install that and run it to root your device.
Click to expand...
Click to collapse
figures. thats me always a day late and a dollar short.
KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
WHOA! WHOA! WHOA! My bad. You should be okay to unlock!
Please go here and attempt it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Get Towelroot and run it. This should root your phone -> http://www.towelroot.com/
Next, get the motopocalypse apk from here -> http://forum.xda-developers.com/showpost.php?p=53428225&postcount=22
Install and run that on your phone. That should then unlock your bootloader.
So, you are fine. I completely brain farted that the soak test hasn't been sent to everyone. It is available to download and install, but don't do it yet.
PLEASE go and unlock your phone. I'm so sorry for the confusion.
Let me know how it goes!
hotspot
KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way
?
KiraTheSavior said:
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way
Click to expand...
Click to collapse
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?
KiraTheSavior said:
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?
Click to expand...
Click to collapse
No, that is the version you CAN unlock. At first, it was believed it couldn't happen, but someone discovered that Moto had accidentally added the bootloader unlock exploit back in with the KK release. It's the version after that, which hasn't been released yet but will be soon, that patches the exploit back up to no allow it. The zip file for it is available outside of the soak test so it hasn't been sent to you. What you took was the OTA you do want which does allow unlocking.
Please, go unlock your phone now before the OTA is released and then you'll be forever locked.
Go here to unlock it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Do it now before you do anything else. Do NOT apply the soak test OTA (which is available via a media fire link from SamuriHL) until you've unlocked your phone.
done
Rooted and unlocked. Very happy about it. But now what? What can I get with bootloader unlocked besides revert to jb?
I still need to get my WiFi tether app to work. I'm grandfathered into unlimited data so my phone is basically my internet. Are there any cool ROMs where the WiFi just works with no tricks or work a rounds?
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,
I'm due to take delivery of my Pixel from EE. Is it true that the booloader cannot be unlocked via normal fastboot oem unlock? Are there any other EE user that confirm?
thanks
EggZenBeanz said:
hello,
I'm due to take delivery of my Pixel from EE. Is it true that the booloader cannot be unlocked via normal fastboot oem unlock? Are there any other EE user that confirm?
thanks
Click to expand...
Click to collapse
Depends on the software version. See this thread
https://forum.xda-developers.com/pixel/help/google-pixel-7-1-1-ee-model-bootloader-t3548611
vkh2k1 said:
Depends on the software version. See this thread
https://forum.xda-developers.com/pixel/help/google-pixel-7-1-1-ee-model-bootloader-t3548611
Click to expand...
Click to collapse
Interesting, thanks! Let's hope it's one from the back of the warehouse then
EggZenBeanz said:
Interesting, thanks! Let's hope it's one from the back of the warehouse then
Click to expand...
Click to collapse
I've received 2 phones direct from EE (1 replacement arrived last week) , and both were on 7.1 out of the box. So there's hope for you being able to unlock the bootlader. Just make sure you skip Wi-Fi setup during the installation process, or turn off automatic updates within Developer options to avoid updating to 7.1.1.
Then use Depixel8 to unlock the bootlader.
http://theroot.ninja/depixel8.html
Thanks for letting me know. Worst case I'll swap it and go with o2. Coming from a oneplus3 it's disappointing to be back with development unfriendly devices
EggZenBeanz said:
Thanks for letting me know. Worst case I'll swap it and go with o2. Coming from a oneplus3 it's disappointing to be back with development unfriendly devices
Click to expand...
Click to collapse
I pulled my sim out of my Verizon model before I turned it on to stop any updates along with skipping wifi setup before I unlocked the bootloader. Thankfully mine was on 7.1. Unlocking was one of the first things I did. After that you can upgrade without locking it back up.
EggZenBeanz said:
Thanks for letting me know. Worst case I'll swap it and go with o2. Coming from a oneplus3 it's disappointing to be back with development unfriendly devices
Click to expand...
Click to collapse
As mentioned, don't put a sim in it and skip wifi setup until you get it unlocked. They download the update quickly....And it installs in the background and if that happens you are done.
You will be fine.
There is about 3 threads a week asking the same exact question..
After posting this I just saw the same exact one right under this one.
Guess it must be a popular question.
Sent from my ONEPLUS A3003 using Tapatalk
Hi everyone. I just won a Google Pixel. The contest was on a tech site and prize was provided by verizon. The phone package doesn't show verizon on it at all. Is there a way to tell if it is verzion locked? Also what does it mean if it is? Will I not get the updates when they go out? I am currently with T-Mobile and my phone before is a Nexus 6P. I haven't rooted or flashed a phone in years. Doesn't mean I'm not willing. Just thought I'd post and see if I could get some advice on what to do next with my Google Pixel. Any help is greatly appreciated. Thanks!
When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.
uodii said:
When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.
Click to expand...
Click to collapse
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.
TonikJDK said:
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.
Click to expand...
Click to collapse
I forgot about that in the developer settings. It's been a while since I did that. Good catch.
Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?
GeekyWilliam said:
Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?
Click to expand...
Click to collapse
Yep, you will be all set. And updates will come from google.
About phone...what version of N is it on? Dont let it update until you answer that. If it is lower than 7.1.1 you can unlock it still.
http://theroot.ninja/depixel8.html
It is 7.1. Thanks again!
GeekyWilliam said:
It is 7.1. Thanks again!
Click to expand...
Click to collapse
Hit it now. You don't have to full unlock but depixel8 it and get the slider done before it updates.
Ok. I'll do it now. Once I depixel8 then I can get the updates?
GeekyWilliam said:
Ok. I'll do it now. Once I depixel8 then I can get the updates?
Click to expand...
Click to collapse
Yea, you can finish the unlock later after it updates. But be aware the next step in unlocking will wipe your phone. So you may want to get it over with.
Hi,
I have Oreo on Pixel XL, and was wondering if there's any way to unlock the bootloader with dePixel8 or otherwise so I can install TWRP/root?
Thanks!
No
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
H0wdy said:
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
Click to expand...
Click to collapse
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
robocuff said:
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
Click to expand...
Click to collapse
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Thanks. I guess I'll wait to see if something else occurs.
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
jmartin72 said:
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
Click to expand...
Click to collapse
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
AncientDeveloper said:
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
Click to expand...
Click to collapse
I wish someone could figure out how to get it done.
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Edit: OEM unlocking is *not* greyed out even on Wifi
nyisles said:
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Click to expand...
Click to collapse
Yep, Google has messed up on quite a few phones. Hit that slider now. That won't unlock it, you still have to issue the fastboot command. But moving that slider now will future proof you if you want to unlock.
jmartin72 said:
I wish someone could figure out how to get it done.
Click to expand...
Click to collapse
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Pixxlman said:
What if we could overwrite the bootloader and leave the sim out of the phone and activate it with wifi then verizon can't check the imei and can't lock it? i have a verizon pixel XL i can try this with if someone could walk me through overwriting a bootloader
Click to expand...
Click to collapse
There are multiple problems with that theory. First, Verizon does not lock them. They all come locked, when they start up they phone home to Google and get permission to unlock. And two, the SIM has nothing to do with locking.
What is the point of Google shipping the phones with two different bootloaders and unlocked and locked states.
Some hope with the clkscrew exploit? Sounded like the phone needed to be rooted to work, but being able to pull trustzone keys from a Google variant could possibly enable a workable patch for the Verizon variant.
Have no idea, but sure sounds plausible.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Google did not close the exploit. Verizon did with the release of 7.1.2 in November 2016.
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
The package will probably fail to install after modifying because of improper signature. It has been tried before....
AncientDeveloper said:
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Click to expand...
Click to collapse
Probably encrypted, you don't have access to the correct tools, or both.
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
gobi42 said:
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No. You can't downgrade with a locked bootloader.