Bootloader Unlocking and Rooting on the Pixel XL - Google Pixel XL Questions & Answers

Hello, I have a pixel xl that was purchased from the Google store and is currently on 7.1.1. In developer options their is a option for oem unlocking. Does turning on this option simply unlock the bootloader? Also, if that is the case, is there a step by step guide to rooting the phone? I am considering rooting but haven't done it in many years so just want to be extra cautious so i don't screen up the phone. I have poked around a little in these forums but have been confused and just want to make sure i get the correct procedure for my pixel and circumstances. Now, is it my understanding that with rooting i can no longer take ota updates, right? What if i just turned on the oem option, could i take ota updates then? Just trying to understand all my options. Also, if that is the case where i can no longer take ota updates, are the ota updates filtered and pushed out timely by the xda community? The developers do a awesome job especially the fact that the pixel is so different but I'm just trying to weigh all my options.
If i do end up rooting, i have used the Google support a few times already, would you advise if i have any issues and need to contact them, telling them that my phone is rooted or no?
Also, i would like to see the volume louder, is there a mod or anything that can be done for this?
Thank you for any and all feedback regarding my questions.
Sent from my Pixel XL using Tapatalk

jreink01 said:
Hello, I have a pixel xl that was purchased from the Google store and is currently on 7.1.1. In developer options their is a option for oem unlocking. Does turning on this option simply unlock the bootloader? Also, if that is the case, is there a step by step guide to rooting the phone? I am considering rooting but haven't done it in many years so just want to be extra cautious so i don't screen up the phone. I have poked around a little in these forums but have been confused and just want to make sure i get the correct procedure for my pixel and circumstances. Now, is it my understanding that with rooting i can no longer take ota updates, right? What if i just turned on the oem option, could i take ota updates then? Just trying to understand all my options. Also, if that is the case where i can no longer take ota updates, are the ota updates filtered and pushed out timely by the xda community? The developers do a awesome job especially the fact that the pixel is so different but I'm just trying to weigh all my options.
If i do end up rooting, i have used the Google support a few times already, would you advise if i have any issues and need to contact them, telling them that my phone is rooted or no?
Also, i would like to see the volume louder, is there a mod or anything that can be done for this?
Thank you for any and all feedback regarding my questions.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No, extra steps are required. Read up on the guides in this forum including ones for ADB and fastboot. Also mskip's toolkit. Be sure you understand what you are doing before embarking on your exciting journey.
Sent from my Pixel XL using Tapatalk

Related

[Q] Question Purpose of Root/Unlock

This is my 3rd Nexus and this time, I'm going to try to keep this as close to Google's vision as possible. So if I'm not going to use a custom ROM, do you see any other reason to bother unlocking the phone and rooting it?
freicook said:
This is my 3rd Nexus and this time, I'm going to try to keep this as close to Google's vision as possible. So if I'm not going to use a custom ROM, do you see any other reason to bother unlocking the phone and rooting it?
Click to expand...
Click to collapse
If you dont want to alter the stock rom in any way or flash custom roms or kernels then there is no need to unlock the bootloader.
If you dont want to perform any actions that need root permission i.e. adfree to block popup ads in apps, permissions to disable certain apps permissions, setcpu to adjust profiles or titaniumbackup to make backups of your installed apps and settings then you really dont need to root your phone.
If you want to do any of those things then yes its worth it. Unlocking the bootloader and rooting your phone wont harm anything and wont affect your stock rom but they WILL give you more options in the future if you change your mind. If you get all your phone set up and then decide you want to unlock the bootloader then the process will wipe your phone and you will lose everything you have installed so its better to do it now than later
Mark.
Firstly, how in hell did you manage to already get through two Gnex's? Secondly, yes, unlocking the boot loader and rooting is still useful even if you don't want to put a custom ROM on it. You can use root tools and uninstall system apps, change the dpi, install new kernels and over clock/underclock etc etc
If you unlock the bootloader you can always manually download OTA updates from Google's server and apply them yourself instead of waiting for the update to arrive.
Sorry, I meant this is my 3rd Nexus phone. Nexus One, Nexus S, and now Galaxy Nexus.
Thank you for your replies. I think I'll just unlock it...because, why not?
the only reason i can think of is to have the carrier ic spyware removed, it's been pretty big lately.
kms108 said:
the only reason i can think of is to have the carrier ic spyware removed, it's been pretty big lately.
Click to expand...
Click to collapse
and its also been said that carrierIQ isnt on nexus phones FWIW
Is there a way to UNroot and LOCK the phone in case of warranty?
Flashindude said:
Is there a way to UNroot and LOCK the phone in case of warranty?
Click to expand...
Click to collapse
Yes:
http://forum.xda-developers.com/showthread.php?t=1366806
fdm1 said:
and its also been said that carrierIQ isnt on nexus phones FWIW
Click to expand...
Click to collapse
where did it say that.
kms
The CarrierIQ thing is supposedly something that carriers put on themselves, not Google. If that's the case, the Nexus line of phones in the past wasn't attributed to any carriers. Looks like Verizon might actually be branding theirs, since rumors are their name will now be on the backplate.
And of course, since we're in a developer forum, it's only appropriate to echo Cyanogen and his saying that they never have and never will include the CarrierIQ statistics on their ROMs.
kms108 said:
where did it say that.
kms
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=1372643&highlight=spy
but I don't know if it's true. I have just found out what carrierIQ is.
I'm not going against anyone from this forum, as i could be wrong, but i still dont believe all the BS that the companies says about not having the ciq in it's phone, also this links do say nexus phone, but does not state which one, and to my recall, the latest version galaxy nexus, the rom although vanilla google, the rom has been developed with samsung, google did not 100% made the rom, and the latest update through OTA was produced by samsung.
but you can correct me if you do think i'm wrong, as many member in this forum do have many years experiences in programming and development of roms.
I don't believe that any of the "true" Nexus devices have had this on it...otherwise myself and many others likely would have found it much earlier and we would not be wondering this now. With that being said I wouldn't count out the Nexus S(Sprint version) and the Galaxy Nexus(Verizon version) from the list of carrier IQ devices. Only time will tell as I'm not planning on ever owning either of those devices.
Justin
There was a Statement issued by Verizon That none of their phones Used Carrier IQ.. Something We Don't need to worry about on the SGN... Anyways Google handles Updates...
There's no debate: CIQ is NOT on this or any Nexus phone. AOSP is open source. It would be plainly obvious in the source code.
Sent from my Galaxy Nexus using XDA App
Deleted...

phone arriving on wednesday - first things to do?

ello guys.
going from my 2 year old htc desire to this....
so...what are the first things to do with this galaxy nexus?
Vital apps needed?
specific things to do in the settings to make it run better?
it would be nice to make a guide to follow.
first thing ive done so far is buy a TPU S line case, and Expertshield screen protector.
If the battery life is rubbish i'll have to get the extension pack....but hardly anyone in the UK seems to sell them...lots of korea sales for genuine ones on ebay.
would a non-genuine thing still be as good?
heard of this dodgy issue with a 'yellowy' tint screen - what to do there? have to root the phone?
etc.etc...
Fast boot OEM unlock
Sent from my Galaxy Nexus using XDA
Unlock the phone a root it first because unlocking it will wipe the phone clean of EVERYTHING. So get that done first and the rest is up to you stay stock or flash a rom.
Sent From My Sprint Galaxy Nexus via XDA Premium
Here are my favorite apps on my Galaxy Nexus
-Chrome Beta
-Boid (Twitter)
-Tasks (Google Tasks)
-Weather Flow
-Intsagram
-Wolfram Alpha
-Icy Time (Timer and Stopwatch)
-Wallbase (Wallpapers)
Now that you have Android 4.0 you'll most likely fall in love with the Holo design guidelines. A list of some of the apps that use these guidelines can be found here and some good looking apps in general can here.
If you plan on rooting your phone or think you might want to in the future Unlock the bootloader, if you don't you will regret it, trust me. As for the battery life, I can get through the whole day with no problems while others complain that the battery life is bad, I suggest that you use the phone for a week before you get an extended battery.
There's a forum about the yellow screen issue here if you experience this at all then send it back as soon as possible despite the desire to play with your brand new toy.
If you have more questions just ask.
Sign for it
Take it out the box
Charge it
Press power
Sent from my Galaxy Nexus using Tapatalk 2
If you like miui and don't want to root. Miui launcher is now available as an apk. That's one of the first things I installed when I got mine. The stock launcher is pretty good too.
Mi Launcher
http://forum.xda-developers.com/showthread.php?t=1623026
Sent from my Galaxy Nexus using XDA
try ur phone with everything stock for a few days, see if everything works, no reboots, overheating etc etc (might want to check if u got an OTA update though, coz there's a big difference for example between 4.0.1 and 4.0.4 in terms of stability)... if u're satisfied with stock , there is no need to root then , if u want to play around a lil u'll figure what to do urself.
p.s. i also owned a desire, but went through some devices in the middle before the gnex, nways, the desire can't be even mentioned in the same sentence with what u're getting now. welcome aboard
First things to do:
1) Unlock your bootloader, even if you never plan on rooting or flashing a custom ROM. Do this even before booting Android for the first time.
2) Check to see if you are running yakju or takju. If you are running a build other than those two (for GSM devices), flash one of them (by following the link in my signature). Run one of those two builds for a while, so that you get a feel for what a stock ROM is.
3) Everything else.
Sent from my Galaxy Nexus using Tapatalk 2
Keep it stock for at least a week, get to know the phone. Saves having to post about problems you're having on a custom rom just to find out its not the roms fault. This will also allow you to give real feedback when comparing roms as a opposed to these douches who flashed on day one n insist that rom x is better than stock
Sent from my Galaxy Nexus using xda premium
i will definitely run stock for a few weeks and get used to it all.
however i am one to fiddle, but im totally new to this phone world in terms of rooting, custom ROMS etc, never bothered before.
put it this way though......i dont own any apple products
can anyone point me to the best guide for rooting, and installing custom Roms?
also can anyone link me to a list of custom roms for the gnex, that are either finished or in development?
im just asking for the links because im very sure the question 'how do you root' has been asked a hundred times - i could google it - but i presume you guys will immediately know a link to the best and safest guide.
having a read through, it seems people have already tweaked the gnex for better things - better kernels? to get better battery life? etc.etc...
is that part of the firmware? is that what you get with custom roms?
i need to understand the basics first.
(im buying the phone sim free unlocked)
Everything you need is in the q&a and development sub forums where you found this one
Sent from my Galaxy Nexus using xda premium
schueyisking said:
i will definitely run stock for a few weeks and get used to it all.
however i am one to fiddle, but im totally new to this phone world in terms of rooting, custom ROMS etc, never bothered before.
put it this way though......i dont own any apple products
can anyone point me to the best guide for rooting, and installing custom Roms?
also can anyone link me to a list of custom roms for the gnex, that are either finished or in development?
im just asking for the links because im very sure the question 'how do you root' has been asked a hundred times - i could google it - but i presume you guys will immediately know a link to the best and safest guide.
having a read through, it seems people have already tweaked the gnex for better things - better kernels? to get better battery life? etc.etc...
is that part of the firmware? is that what you get with custom roms?
i need to understand the basics first.
(im buying the phone sim free unlocked)
Click to expand...
Click to collapse
HERE you go
http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3
doesnt rooting or installing a new kernel void the warranty?
schueyisking said:
doesnt rooting or installing a new kernel void the warranty?
Click to expand...
Click to collapse
You can always flash back to stock.
No warranty problems.
Backup your /efs partition... =o)
a week of stock? i don't last more than 3 hours, and that's if i'm trying to really be patient. within an hour of getting mine i had flashed the radios, bootloader, rom, and the kernel.
tspderek said:
a week of stock? i don't last more than 3 hours, and that's if i'm trying to really be patient. within an hour of getting mine i had flashed the radios, bootloader, rom, and the kernel.
Click to expand...
Click to collapse
How do you even know what stock ICS is if you only use it for 3 hours?
Sent from my Galaxy Nexus using Tapatalk 2
I just got my GN directly from Google and didn't do any unlocking of any sort. Just turned it on and added some apps I plan on using. Changed my homescreen and other screens/settings to fit my personal use and etc.
The phone is amazing without the need of unlocking.
Not really sure... the phone is already unlocked -.- (SIM wise)
pinoyplaya4life said:
[snip]
The phone is amazing without the need of unlocking.
Click to expand...
Click to collapse
Do you understand what unlocking means? We are talking about unlocking the bootloader. Unlocking the bootloader does NOT mean that you are changing anything related to the ROM. I does NOT mean that you are "rooting", and it does not mean you are planning to use a custom ROM.
All it means is that it gives you the ability to use fastboot commands. With this ability, you may be able to save some data off your device in case something happens and your devices' OS crashes. There have been a few reports on these forums of users who kept their bootloaders locked, then something happened and they couldn't boot their device. If their bootloaders had been unlocked, they could have at least saved their personal files (photos, music, etc) from the /sdcard directory. But, because their bootloaders were locked, too bad so sad, photos gone (they were not auto-backup to the cloud).
+1
Definitely unlock the bootloader - I learned the hard way on my N1 that getting an 'unlocked phone' is different from having a phone with an unlocked bootloader. (hunting down a bootloader locked root method so I can Titanium Backup 2 years of apps and data is a PIA).
Unlocking the bootloader on a brand new phone will not outwardly do anything to your phone other than add a little unlocked padlock to the bottom of your startup screen (the one with Google written on it).
I did 2 weeks ago what you're talking about doing now. It's super easy with the Galaxy Nexus Toolkit that mskip has created.
http://forum.xda-developers.com/showthread.php?t=1392310
[EDIT] P.S. - don't worry about losing warranty when unlocking the bootloader - the above GNex Toolkit can get your phone back to stock and then re-lock the bootloader for you if you ever need to use the warranty.
efrant said:
First things to do:
1) Unlock your bootloader, even if you never plan on rooting or flashing a custom ROM. Do this even before booting Android for the first time.
2) Check to see if you are running yakju or takju. If you are running a build other than those two (for GSM devices), flash one of them (by following the link in my signature). Run one of those two builds for a while, so that you get a feel for what a stock ROM is.
3) Everything else.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse

Why is it so easy to unlock but not root?

I wonder why google has made it so simple to unlock the bootloader on the Google Play version of the Pixel phones while at the same time they are supposedly pushing so hard to make achieving root more difficult with Android 7?
Is there any benefit of having an unlocked bootloader without root access? If so what is it?
Flashing factory images instantly is one benefit.
norcal61 said:
I wonder why google has made it so simple to unlock the bootloader on the Google Play version of the Pixel phones while at the same time they are supposedly pushing so hard to make achieving root more difficult with Android 7?
Is there any benefit of having an unlocked bootloader without root access? If so what is it?
Click to expand...
Click to collapse
Root was achieved on Nougat when it was in beta. It's the new partition layout of the pixel that makes the current method unusable. But the guy behind SU gets one soon and will figure it out. Things change. They aren't making it harder. If they wanted to make it harder they would lock the bootloader down like Verizon.
Gizmoe said:
Root was achieved on Nougat when it was in beta. It's the new partition layout of the pixel that makes the current method unusable. But the guy behind SU gets one soon and will figure it out. Things change. They aren't making it harder. If they wanted to make it harder they would lock the bootloader down like Verizon.
Click to expand...
Click to collapse
I don't know how valid they are but I've read several articles claiming the Google is purposely trying to make it more difficult for devs to accomplish root. If that is true it doesn't make any sense that the bootloader isn't locked down right outta the gate. Idk. Just hope we get root for these things soon. I spent forever on at&t with both a galaxy s 4 and a note 4, waiting for ever for root, which as far as I know never came. If it did it wasn't until after I moved on. I hope that doesnt happen with the pixels.
norcal61 said:
I don't know how valid they are but I've read several articles claiming the Google is purposely trying to make it more difficult for devs to accomplish root. If that is true it doesn't make any sense that the bootloader isn't locked down right outta the gate. Idk. Just hope we get root for these things soon. I spent forever on at&t with both a galaxy s 4 and a note 4, waiting for ever for root, which as far as I know never came. If it did it wasn't until after I moved on. I hope that doesnt happen with the pixels.
Click to expand...
Click to collapse
As long as you have the google store version it's just a matter of time. I'm guessing by December. When the layout of a device changes as drastically as the pixel it takes the devs behind the exploits to rewrite code. Chain fire stated somewhere I read that he was only waiting for it to ship to him and then he will start coding for it. Also devs like beanstown are getting one in November and then purenexus Roms will follow. Beans stated specifically he was not getting the device if those rumors were true and he is getting the device. It means that google is releasing the source. They all ready released kernel source as I see despair has a kernel in the dev section. This all means that it can and will be done. Just be patient. Google store devices get all the attention. The pixel will be no different.
Everything will be fine, most odd the devs don't even have the phone yet. Chainfire will figure it out, once we figure out out the partition layouts, its just a matter of time before we can flash twrp, which allows us to flash su.. . All in time my good friends. Blame Google for their slow shipping times
Skipsoft made it sound like Root was already available but wasn't getting enabled/released until after TWRP is released.
I sort of thought that was weird.
After reading this thread, I'm bummed out.
Didn't realize we were still waiting on Chainsoft, et.all. to get the phone still.
My XL arrived today and there are a few dozen apps I can't install until after Root is available.
Ugh.
http://www.androidauthority.com/google-pixel-root-chainfire-724857/
Pixel news in general getiing better and better. Unlocked VZW bootloader, root and tmo giving you $325 back, all we need is some in stock ahem...gooooogle..

I have a Google store pixel running on the Verizon build, and it seems hard to fix.

I'll try to keep it short, but;
I bought a Google edition Pixel XL from swappa because I saw a really good deal on it and couldn't pass it up. Though even though it's a google bought phone (I checked the IMEI and unlocked the bootloader with no problems, so it basically has to be), I'm on the Verizon build of NDE63X instead of NDE63V, which is the "regular" build. I'm not sure if this could pose any problems in the future, but I thought I'd try to get on the regular build in case.
I tried sideloading the normal OTA image, but it denied by saying it was out of date as compared the build I'm on now? It was downloaded straight from the Google developers page, so that doesn't seem to make sense to me. Eventually I toyed around and ended up flashing the phone with the google edition of the OTA, and everything seemed to be in order. All of this was a pretty long and painstaking process because I've known barely anything about the intricacies of Android before like 2 days ago and have just been learning it all from scratch. However, when I finally was in the V build over the X build, I saw my phone had an update; I went ahead and installed it just thinking that it was standard and maybe the OTA I flashed in was lacking the November security patch or something. When this update went through, it put me back on the X build. Needless to say I was a little frustrated, I kinda felt like I just wasted a royally large amount of time.
So I guess that leaves the question of; why/how exactly did this happen? Is it an issue?
My bootloader is unlocked now after that whole fiasco; should I relock it? Is it any kind of significant security issue? I've heard that relocking the bootloader can brick the phone entirely, and lord knows I don't want that.
If I keep the bootloader unlocked, what exactly can I do with it? I know it allows to install custom kernals/roms, but I'm not exactly sure what that's like or what it's exactly capable of. I know, this is a very general question that I could google. But I'd also just like to hear people's inputs about it.
Will my phone get regular updates with the bootloader unlocked, or would it unable/cause some kind of error?
Thanks in advance for any replies! Like I said, I'm still really new to this whole thing, so if you could kind of explain answers and/or instructions in kind of a black-and-white way that would help me a lot. All of this is kind of intimidating, but it's also been a lot of fun, I like learning about it all.
@cam30era
This is what I did, I actually had it on the V build, for all of about 20 minutes. Then it pushed an update through and the update changed it back to the X. I'm not sure if I screwed something up along the way or exactly how it happened, but it seemed like a kind of unique thing.
Actually, if you'd like to downgrade, make sure your bootloader is unlocked. Flash the boot image from the factory image zip. After that you can sideload the V ota.
Sent from my Pixel XL
So what exactly is your problem with the build that you have other than being the "Verizon" version? The phone isn't going to function any different and there are probably little to no differences in the software other than a letter on the build number.
Sent from my Pixel XL
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
That would only affect models sourced from Verizon...
Sent from my Pixel XL
imnuts said:
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
Click to expand...
Click to collapse
Agreed. AS long as you keep your bootloader unlocked you can flash what you want. If you see something amiss flash another version.
Flashing the verizon firmware on a Non verizon phone should be fine. @imnuts said, same questions and answers with the Nexus 6. I flashed all sorts of builds just to see how they would perform... IN the end there were all the same.

New to Pixel 2. Questions re Root/Magisk

Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks
jewnersey said:
Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks
Click to expand...
Click to collapse
No reason to not to root lol
Custom roms will come but slow
You can root pie as well with no problems
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Use this unofficial version of Magisk (1674) as opposed to the official (1671). https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Why? Some users are experiencing boot issues with the official. This fixes it
Thanks for that. I am going to bite the bullet and do it today.
AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.
jewnersey said:
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.
Click to expand...
Click to collapse
Did you just follow the steps one by one and it worked? I'll be doing this on Mac. Could install a VM with Windows if it makes it any easier.
I'm on windows, but you should be fine on Mac after installing ADB. Mac instruction for doing that are in the first post.
After that just follow directions to unlock and then install TWRP (my preference) .
Save everything important to your PC because it will get wiped.

Categories

Resources