Related
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
FernBch said:
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
Click to expand...
Click to collapse
Yes sprint and bought directly from play store.
Guess I'll start with this tool eH?
forum.xda-developers.com/pixel/development/tool-skipsoft-android--google-t3482761
Problem is, I already updated via OTA to latest version. Am I screwed?
Screwed?? If you mean BL locked, no. I have the Verizon branded variant but unlocked, rooted, and flashed SU. When I saw NMF26Q was available from Google I downloaded it, installed via flash-all from fastboot, then rerooted and flashed SU again no problem.
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
Please look at OP install instructions in this thread.
Please look at OP install instruction in TWRP thread.
I guess you aren't on Telus in Canada or your hotspot would work. When you give no information, too hard to help. But I read this forum so even though I don't have Sprint or Verizon as my provider, I know there are many threads about turning hotspot on for unlimited data plans. Guidance: read those threads too!
Then ask for specific guidance. I don't want to reread for 25 min to find and copy and paste to spoonfeed when you should read. Much nicer to fill in a few missing spots than hold your hand not having a clue of your technical knowledge and skills.
Happy holidays.
Specific guidance: update SDK tools before you start!
Sent from my sailfish using XDA Labs
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing to worry about. I just ignore it.
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That's Verizon's equivalence of "Sorry sucka, you're on your own!"
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
Click to expand...
Click to collapse
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
joetheshmo said:
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
robocuff said:
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
Click to expand...
Click to collapse
Which tether hack? This one? http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
If so, I have not done any tether hack yet....still reading since there are multiple ways to do it. (sprint variant/google play store)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
No, having SuperSU means you are no longer stock. You need all stock images to lock bootloader.
If you need a locked bootloader for Android Pay or some other apps. Install one of the customer kernels, they hide it. You still need to remove SuperSU though. From what I've seen its a bit harder to hide that for now. So you can root, make change for hotspot and remove root.
Otherwise nothing hurts to have your bootloader unlocked. It gives you more options if anything ever goes wrong. You need unlocked bootloader to even load Google factory images.
PS. I'd recommend Franco kernel as it imporoves battery life.
Sent from my Pixel using Tapatalk
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in “wireless & networks” and you are ready to go:laugh:
eos9d said:
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in �wireless & networks� and you are ready to go[emoji23]
Click to expand...
Click to collapse
Depending on his plan, he may not have that option. Many do not, hence still need the tether hack.
I received the 7.0 update yesterday (NRD90M.N920VVRUC3QB9).
I'm Developer Options, I can turn on OEM Unlock, which says "Allow Phone to be OEM Unlocked."
Any chance this means anything as far as root or unlock?
*Giving my hopes up.*
It was there before the update.
tifford said:
I received the 7.0 update yesterday (NRD90M.N920VVRUC3QB9).
I'm Developer Options, I can turn on OEM Unlock, which says "Allow Phone to be OEM Unlocked."
Any chance this means anything as far as root or unlock?
*Giving my hopes up.*
Click to expand...
Click to collapse
Which unlock are you referring to? Verizon comes sim unlocked for 4g sims
jazzdglass said:
Which unlock are you referring to? Verizon comes sim unlocked for 4g sims
Click to expand...
Click to collapse
In developer options. There's a switch for oem unlock. However it doesn't work like everyone thinks it does
tylerlawhon said:
In developer options. There's a switch for oem unlock. However it doesn't work like everyone thinks it does
Click to expand...
Click to collapse
I know that toggle. But nothing happens when it's flipped o or off. So what you mean it doesn't work like everyone thinks?
jazzdglass said:
I know that toggle. But nothing happens when it's flipped o or off. So what you mean it doesn't work like everyone thinks?
Click to expand...
Click to collapse
Everyone wants to think it will do like it does in stock Android where you enable that and then fastboot oem unlock to unlock the bootloader
jazzdglass said:
I know that toggle. But nothing happens when it's flipped o or off. So what you mean it doesn't work like everyone thinks?
Click to expand...
Click to collapse
On Verizon that doesn't unlock the bootloader all it does is prevent the FRP problems when you do a factory reset.. If you factory reset with oem unlock off then you'll need the original Google account to get the phone running again after factory resetting but with oem unlock on you don't need the original Google account it's basically for security against theft and what @tylerlawhon said is also true.
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.
According to this thread( https://slickdeals.net/f/14948867-google-pixel-3-phone-64-gb-pink-169-99?page=16#commentsBox ), one could unlock the bootloader of a Verizon 3 with the following method. I have already installed this month's update, so I cannot test it for now. If you have a Verizon Pixel 3 and have not installed this month's update, can you test this?
"
remove sim (!!!) if you ran it before with the sim inside - remove sim and do factory reset TWICE
connect to wifi
let it download the update
DONT INSTALL UPDATE
go to About Phone -> Build Version. Click it 10 times until it tells you're the Developer now
go to Developer menu
wait until the OEM unlock option becomes clickable (happens after system update is downloaded, but NOT installed)
toggle OEM unlock (result: should be enabled)
Enable USB debug on the phone (also Developer menu)
connect the device to your win/mac/linux machine with adb installed with USB cable with data pins. Phone will ask if you authorize your PC to USB debug it
from your PC run : "adb reboot bootloader". That will reboot your phone to bootloader with message and status "locked"
from your PC while your phone is in fastboot mode: "fastboot flashing unlock" (that should respond with
OKAY [ 0.356s]
Finished. Total time: 0.368s)
You're good now. It's bootloader unlocked. you can install any updates. It will not lock itself and can install any other 3rd party firmware (on your risk, sure)"
No replies... So, the method does not work?
yourrealking said:
No replies... So, the method does not work?
Click to expand...
Click to collapse
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
dcarvil said:
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Click to expand...
Click to collapse
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?
yourrealking said:
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?
Click to expand...
Click to collapse
That is the way I understand it.
dcarvil said:
That is the way I understand it.
Click to expand...
Click to collapse
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
It shouldn't hurt to try, but if it is a Verizon phone it is unlikely to work.
Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.
yourrealking said:
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.
Click to expand...
Click to collapse
Even for Verizon version?
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
- Hit settings
- about phone
- software information
- build number 5 times
- profit
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
RedHatter271 said:
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
Click to expand...
Click to collapse
Have you tried through fastboot? (fastboot oem unlock)
Oh, got you. Sorry!
As far as I'm aware samsung devices don't support fastboot. I did attempt to connect it in case I was wrong but was not able to get fastboot to recognize the device.
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
darkidz555 said:
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
Click to expand...
Click to collapse
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
Did your Developer Options come already unlocked after setting it up?
twistedumbrella said:
Did your Developer Options come already unlocked after setting it up?
Click to expand...
Click to collapse
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
luigi90210 said:
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
Click to expand...
Click to collapse
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
twistedumbrella said:
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
Click to expand...
Click to collapse
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
Click to expand...
Click to collapse
They support it.
RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
If you can boot into download mode there is an instruction just press vol up button and it will prompt do you want to unlock bootloader mine is like that. Im not sure yours since mine is korea version.
luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader .
Click to expand...
Click to collapse
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
if you're in North America, Canada etc Qualcomm chips there do not support bootloader unlocking, at least the Samsung one's don't, not sure about other OEMs.
darkidz555 said:
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
Click to expand...
Click to collapse
They used to, so there was always a possibility it returned.
I recently read this article on XDA about unlocking the boot loader on the Fold 3 which results in Samsung disabling the camera (WTH?), Is this a thing on the Flip3 too?
My device is rooted. I have always been able to find the OEM unlock option under developer options without any constraints.
My camera is NOT affected. I can still use it without any issues.
I have an European device (SM-F711B).
Hope this helps some of you to track down whether this is a location or carrier based problem.
Hey Redhatter,
Out of topic question, but are you getting Tmobile 5G just fine?
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse