Is there a how to on rooting the pixel 2 xl for Google fi yet? Also a how to on enabling the built in call recording function? Thanks
This might depend on whether you bought from Google or Verizon (edit: just noticed you said Project Fi 2 XL). I've heard Verizon locks down the bootloader.
But even if your bootloader is unlockable, I think it still takes some time. The most important part is to have a recovery image that you can install on your phone to allow you to install anything from the menu. The developers of TWRP (or your preferred recovery) have to build that for the phone. I'm not sure if it's the case, but they may need access to the required open source bits to build it (like kernel source), and usually that's released shortly after the phone is.
After that, I think you can just install your SU apk of choice, unless they need to customize that on a per-phone basis as well.
I remember reading a long time ago, there is a file you change from a 0 to 1 in google that turns on the native call recording feature. I've got my phone unlocked now. I can't remember if it requires root or not to enable that simple feature. Does anyone here know? If so, where is that file and variable I have to edit? Thanks
Right now we cannot root yet, because of 2 reasons. If either of these were not the case we'd be able to root
1) Google has not released factory images for these phones yet. When they do, we will be able to root our phones without a custom recovery using the newest version of Magisk.
2) There is no custom recovery for our phones yet. When this is available, we can flash either SuperSU or Magisk in recovery to root.
Both rooting options above would require an unlocked bootloader of course.
ElementalWindX said:
I remember reading a long time ago, there is a file you change from a 0 to 1 in google that turns on the native call recording feature. I've got my phone unlocked now. I can't remember if it requires root or not to enable that simple feature. Does anyone here know? If so, where is that file and variable I have to edit? Thanks
Click to expand...
Click to collapse
Maybe a build.prop feature? If so, yes, that would require root, or custom recovery (you could technically modify this file in recovery without rooting)
BUT, since rooting requires an unlocked boot loader AND unlocking wipes your device, might as well unlock as soon as you can.
The first thing I do when I get a new phone is unlocked bootloader, then it can Rock!
I thought the newer versions of SuperSU can be applied from factory recovery.
Sent from my Pixel XL using Tapatalk
Colchiro said:
BUT, since rooting requires an unlocked boot loader AND unlocking wipes your device, might as well unlock as soon as you can.
Click to expand...
Click to collapse
Since my first Android phone (Motorola Atrix 4G) back in 2011, the first thing I do when I receive the phone is to unlock the bootloader. Then I wait for the root to arrive.
abuttino said:
I thought the newer versions of SuperSU can be applied from factory recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It can but that wasn't built for the Pixel 2 and you might brick it..
Well, that sucks. I hope that ChainFire will update SuperSU one or two more more times before he actually leaves.
I believe he's still consulting for now but, I hope he takes the ropes of the last phones of 2017.
Sent from my Pixel XL using Tapatalk
Related
Okay, I think I know the answer to this question, so forgive me. Just want to be sure before I go blow $500.
For the Nexus devices, regardless of the carrier, we'll be able to root them and ROM them as well as install new Kernel's because the bootloaders will be unlocked?
If that's correct please say so. If it's only partially correct, please explain it all to me.
Disgruntled Verizon User with a S6 Edge
THANK YOU IN ADVANCE!!!
Yes, its easy as pie.
nexuses are always devs favorites...
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Yes! Though I am not sure about the Pixel C. I am wondering if Google giving products the Pixel name means they lock them down? Sorry, little off topic.
I'm only curious how/if Google has the fingerprint security locked down when it comes to root
shimp208 said:
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Click to expand...
Click to collapse
Thank the sweet, tiny, infant squishy baby Jesus! I have yet to own a nexus phone (fed up with my GS5) and am about to pre order the 5X. I miss getting to try out different roms and such, so i'm really pumped about the 5X. the 6P is just too big of a phone for me i think.
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
owenrg said:
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
Click to expand...
Click to collapse
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
If I unlock bootload, will I have problem with OTA?
shimp208 said:
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
Click to expand...
Click to collapse
Awesome thanks!
Sent from my iPad using Tapatalk
menaceinc said:
If I unlock bootload, will I have problem with OTA?
Click to expand...
Click to collapse
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Thanks, I will just do that, unlocking bootloader. I really missed OTA as my current N5 is rooted.
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
In my experience, installing an OTA over a rooted phone would just kill root and you'd have to root it again, however, installing a custom ROM, the developer usually kills OTA so that all the custom stuff doesn't get jacked up.
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
Rooting will effect the built in method of OTA updates. This is not a problem though. 99% of the time you will have access to the updated via the nexus factory image site before you receive notification of an OTA update on your device. Download the update and extract the boot, bootloader, radio, and system images. Flash via fastboot in bootloader mode and you will update your device without losing data/settings. I believe that you can flash img files with recent TWRP builds also.
To root after update just reboot to TWRP recovery and reboot. You will be prompted to install root before system reboots.
May seem a little overwhelming if its your first nexus device but a lot easier than updating a non nexus rooted Android device.
For more info check out any one of the recent nexus routing guides sticky threads
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
SlyUK said:
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
Click to expand...
Click to collapse
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
metpage said:
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
Click to expand...
Click to collapse
Yes thats true, but I haven't heard of many people who have had problems with Wugfresh and it is a popular method. Everyone is different
I always rooted my Nexus (N4, N5 & N7), but I am not going to root my new upcoming Nexus 5X. Why? It just too much to flash/root since Google will release monthly security updates. Yes, I did use "fastboot flash xxx xxx.img" method. However, I will unlock the bootloader in case I change my mind in the future. With unlocked bootloader, I can always fix phone via flash factory images.
Will I be able to edit build.prop on a Verizon Pixel without root? Do I need to first flash TWRP recovery and then use adb shell to update build.prop? Afterwards, change file permission and flash the stock recovery? If this is correct, will this have any impact on safety net or future OTAs? Will my edits be overwritten by and OTAs?
Other than rooting, I'm assuming there's no (easier) way to accomplish the wifi tether check on this phone. I don't want to use the hack of using another app either (eg, flips the network then enable hotspot). I want to enjoy my pixel as stock without any further hacks. Otherwise, Verizon can keep their pixel.
Update:
Well, just remembered the Verizon Pixel boot loader is locked. I don't want to unlock it. Does this mean I can't flash recovery to accomplish the above? God, I'm so close to just saying f*ck it. I hate verizon.
My guess is once TWRP is released for pixel, you will need to flash a custom kernel to keep the build prop edit from reverting on boot. That is what I did for my N6 on 7.0. Just have to wait for TWRP to find out.
You do have to be rooted to edit your build.prop. You definitely will not receive OTAs once rooted, I believe it's been like this since Android 6.0. Even with stock recovery you can't get OTAs if you're rooted.
Edit...You still have to unlock the bootloader on a GS version in order to flash twrp.
Sent from my Pixel XL using XDA-Developers mobile app
Well, I found the Pixel XL at a local Verizon store----but, currently I have the Pixel (from Google). This hassle isn't worth it just for a bigger screen...plus, Verizon pixel only has 32 GB compared to my Google pixel with 128GB. This is the first android where I don't want to root----the phone and OS are that good now.
So, guess I'll cancel the Verizon pixel today. Was just hoping there'd be an easy way to "undo" the red devil's changes to Google's phone. Oh well.
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.
I've unlocked my bootloader but I am stock with no root. I haven't done anything yet because I'm waiting for twrp and Roms to mature a bit before I dive right in. Does anybody know if it's safe to update and keep the unlocked bootloader?
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
lars1110 said:
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
Click to expand...
Click to collapse
Yes, it's safe to take the OTA as long as your bootloader is already unlocked.
Yes, I installed it with no problem. Boot loader is still unlocked, and the new move gestures are mostly OK.
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Awesome thanks everybody about to do the OTA now
Mike01680 said:
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Click to expand...
Click to collapse
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
You can update... The OTA didn't work on my phone so I had to sideload it through ADB, still unlocked and worked like a charm
wrong thread
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
You can before this update that was just released. You have to unlock before taking update or you won't be able to unlock. Once you unlock you can still update with no problem
Sent from my Pixel XL using XDA-Developers mobile app
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
There is a tool that can force unlock the bootloader (depixel8?), but the exploit that it uses has been closed with this update.
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can if your on 7.1 but not if your on 7.1.1
EDIT: I misread the posting. It is locked in 7.1.1.
Scott said:
This is not correct. @jcase stated he updated the tool to work with 7.1.1...
I'll see if I can find that post again...
Click to expand...
Click to collapse
Really?? The news has been all over that the 7.1.1 update patched dePixel8. He even posted on his website about it and said to not ask for further support. I assumed he didn't have a pixel so wasn't going to spend any more time on it. From my understanding the first method was very simple for them to figure out.
Please reply if you can find the post this will be big for everyone!
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can unlock the bootloader with the dePixel8 method
Ad nauseum to the can you unlock or not. The latest update from Verizon makes the Verizon model locked. Period. If you haven't unlocked already, don't update to 7.1.1. If you plan to unlock. Depixel8 DOES NOT work for verizon pixel once the 7.1.1 update has been applied. If you unlock.... Don't relock. End of story. Stop with the round and round.
318sugarhill said:
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
Click to expand...
Click to collapse
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
So taking the OTA and flashing boot to root after will work if I'm understanding everything I've read this far? Also I have been unable to find the build specific for 7.1.1 for Verizon to download.
cntryby429 said:
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
Click to expand...
Click to collapse
Is this true? If so where is the post to someone doing this exact thing?
So I just got the pixel xl 128 gb from Google because my nexus 6p had the battery issue. Just got this sucker turned on and I realized it is still on April security patch with 7.1.2. Now I am Verizon but didn't get it from a Verizon store so this should be unlockable correct? Where is the easiest method to unlock and flash twrp? I used magisk systemless on the 6p. Noticed pixel is a different beast. Can someone help me or at least guide me to the correct places since everything is so buried now with android O out and stuff. Thank you!
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
Refugees over here.
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
You should be ok with unlocked device from Google.
Magisk method doesn't work yet on PixeXL...coming soon.
We also don't have a flashable TWRP for Oreo. Guess we have to fastboot into it.
There seem to be 2 threads in this Guide form detailing unlock/root for Oreo. Haven't figured out which one to use yet.
akenis said:
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
Refugees over here.
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
You should be ok with unlocked device from Google.
Magisk method doesn't work yet on PixeXL...coming soon.
We also don't have a flashable TWRP for Oreo. Guess we have to fastboot into it.
There seem to be 2 threads in this Guide form detailing unlock/root for Oreo. Haven't figured out which one to use yet.
Click to expand...
Click to collapse
Ya everything is much different. I'm avoiding the update as I hope I can unlock the bootloader and root on 7.1.2 thank you though!
theDK10 said:
Ya everything is much different. I'm avoiding the update as I hope I can unlock the bootloader and root on 7.1.2 thank you though!
Click to expand...
Click to collapse
Just throw the switch and then do what you want. The update has nothing to do with it.
Sent from my Pixel using XDA-Developers Legacy app
theDK10 said:
So I just got the pixel xl 128 gb from Google because my nexus 6p had the battery issue. Just got this sucker turned on and I realized it is still on April security patch with 7.1.2. Now I am Verizon but didn't get it from a Verizon store so this should be unlockable correct? Where is the easiest method to unlock and flash twrp? I used magisk systemless on the 6p. Noticed pixel is a different beast. Can someone help me or at least guide me to the correct places since everything is so buried now with android O out and stuff. Thank you!
Click to expand...
Click to collapse
This guide is the easiest to follow.
I am in the same boat as you and after some researching it's fairly straight forward. Don't root or flash a kernel via fastboot, that is the outdated method, use TWRP.
Follow the guide. The biggest thing is flashing RC2. Magisk isn't working, don't even bother with it until it's updated, use SuperSU for the time being. From what I've read Magisk is close to being done.
When flashing ROMs or anything via twrp, keep an eye on which slot is active (go to reboot in twrp, it will tell you which slot is active) If you flash something and it boots back to twrp, reboot into the other slot and try restarting the system.
The biggest thing is to not mess with installing/flashing stuff when you're not around a computer you can use fastboot on. You might get stuck with a non-booting phone or not have TWRP to boot into and would need to fastboot into the RC1.img