Related
Has anyone thought that maybe google has made 2.3 unrootable? Scary thought i know, but its kind of like a cat and mouse game with the developers and google/manufacturers with root patches.
Maybe google finally will put the nail in the coffin here?
WOOT. It's rooted, im happily wrong.
It's a developer phone, so why would Google want to make devs waste time trying to root.
could it be possible that Google enable root access by default, then?
djfoo000 said:
could it be possible that Google enable root access by default, then?
Click to expand...
Click to collapse
Definately not.
Dev phones have always been rootable, i doubt that will change.
The phones that have trouble being rooted are always manufacture customized ones.
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
I'd bet that it will be rooted BEFORE!
The developer build on my Nexus One is already rooted. I don't imagine the release build will be any different from all of the previous OTAs.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
You are correct.
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
fastboot oem unlock
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Your right, as of now I don't think Samsung locked any of their phones, but the only thing Samsung has on this phone is the hardware aspect. All the software aspect is by Google.
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Then how do you explain threads like this (on the samsung galaxy sub forums):
[HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!]
It seems like you have carrier/sim lock and root confused. Just like nearly every phone on the market, they are locked. You will also need root to do anything that says "please root your phone". They do not ship this way...
I'm sure it will be rootable... Google doesn't want to block out developers
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
Very true
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
luckyduck69 said:
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
Click to expand...
Click to collapse
that's unlocked for carriers with gsm...that's not root. Simply meaning it will work with at&t or tmobile by changing the sim card. Root lets you edit system files and a custom recovery to flash roms
Lmao no one so far in this thread should get one of these developer phones as you plainly do not understand what you are doing here when it comes to deciding what the difference is between root permissions and unlocked to all networks.
lets put it this way, if you are one of the above who are having trouble, dream on and steer clear from the prospects of rooting all together
unless that is you fancy yourself a very expensive paperweight?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
This command unlocks your bootloader on the N1/N-S allowing you to flash custom roms, but visibly voids your warranty (bootloader screen shows that it's unlocked)
Peace be upon everybody, and good morning/evening
Last night I remained using my PC for a whopping 9 hours of work to figure out how to unlock my E6633 bootloader - and I finally figured it out.
The whole process was bumpy and the Sony Mobile Developers tutorial didn't wholly work out, but it had some vital info for the process. I had to unlock the boot loader using the Flashtool (thankfully), and I had some lack of luck at the beginning, which involved a journey to find the lost driver for my Z5, and to install it in the Device Manager (took some time). And then I took a "detour", since facing another roadblock, by creating a folder in C:\Users\<User>\.flashTool\registeredDevices named by my devices code (that appears when you enter adb devices in cmd), then inside of that folder I've created a .txt named ulcode.txt which contains the serial code provided by Sony Mobile to unlock your boot loader. And I've gotta tell you, it was all a pain in the bass.
More frustratingly, this whole procedure has resulted in zero luck with rooting the goddamn device (thanks Sony), and now I'm stuck with an unrooted bootloader-unlocked device . I'm sure this requires taking another detour. I've failed in every way I know to flash the modified stock kernel for some reason. I've tried cmd to flash the kernel and it comes back with FAILED <Remote: command not allowed>. I've also tried Flashtool to root it directly, and it turned out to be non-working as well.
Now, I'm not going to complain about this whole situation, even though I'm recalling how easy rooting my good old Galaxy S3 was. I'm now looking for a solution for that last tiny bit of the puzzle, and I'm sure there are other fellow members who are facing the same hitch.
Cheers .
Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk
After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.
Go to developer options and check if oem unlock is ticked
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
Then buy a Samsung...
Sent from my E6653 using XDA Free mobile app
Everything is explained here
celderic said:
Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
It is indeed ticked and I'm positive that the bootloader is unlocked.
Yes I tried the easy way of doing it with cmd but it just didn't work out. Kept returning with FAILED <Remote: command did not succeed> and that's why I resorted to the other way of creating those files in the flashtool folders (as explained in the OP).
gm007 said:
After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.
Click to expand...
Click to collapse
It didn't reset to factory settings. Does that mean it wan't unlocked?
dylanel98 said:
Go to developer options and check if oem unlock is ticked
Click to expand...
Click to collapse
It is ticked along with debugging just in case.
bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
I think maybe the developers at Sony are narrowing down the possibility of modifying their devices.
Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
Checking it out...
Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
I went through the steps in that thread and without any problems until the part with
Code:
fastboot –i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXX
I have checked the recognition of my device by entering fastboot devices and it recognized my device successfully.
The X's above being the code provided by Sony, the cmd window (of minimal adb and fastboot) returned with
Code:
FAILED (remote: Command did not succeed)
Although, the step prior to this one which is to unlock the bootloader using Flashtool has succeeded.
It's really mind-boggling...
As far as i know that unlocking bootloader will reset ur phone to factory settings.
And not sure but i think you need to remove a number from the code sony sent to you.
Take a look here: http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
Bootloader unlock is under # STEP 1 - GENERAL GUIDE
I hope this will help
Also check if you're bootloader is allowed to be unlocked.
Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.
UM, I have E6633 and everything works fine... I used flashtool to unlock bootloader.
langeveld024 said:
Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.
Click to expand...
Click to collapse
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yes you cannot unlock bootloader.
I think you have branded phone,locked by carrier.
mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.
langeveld024 said:
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.
Click to expand...
Click to collapse
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk
mrbubba999 said:
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yeah or next time only buy carrier free Sony
Thank you all, guys! I tried everything you told me but guess what! Nothing worked unfortunately...
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
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've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
live4soccer7 said:
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
Click to expand...
Click to collapse
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
TonikJDK said:
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
Click to expand...
Click to collapse
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
live4soccer7 said:
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
Click to expand...
Click to collapse
It requires a manual command in fastboot. Doubt you'll do that accidently.
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
KittyRgnarok said:
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
Click to expand...
Click to collapse
Thanks everyone, that's exactly what I was looking for. I'm curious, what happens if I toggle the OEM unlock option on/off?
live4soccer7 said:
I'm curious, what happens if I toggle the OEM unlock option on/off?
Click to expand...
Click to collapse
That switch has been grayed out after the Verizon unlock, and it reads "Bootloader is already unlocked", so as far as I know it's not possible to toggle.
Thanks! Much appreciated.
Enjoy your Pixel and happy modding mate