Hello, I have the Pixel XL from Verizon. I unlocked the bootloader with dePixel8 and confirmed the bootloader was unlocked. Then I went to install SuperSU from Chainfire. I followed the instructions 100%, but have ran into an issue. The phone has been in the process of booting for the last half hour. The instructions say it should only take a few minutes. Anyone else run into this issue, and if so how did you fix this? thanks.
Flash the stock boot.img or a kernel and then try again
Sent from my Pixel XL using Tapatalk
Yep, thats what I would do.
Or even just try again without swapping the boot.img
If that doesnt work then try stock / customer boot.img.
AndroidMercury said:
Hello, I have the Pixel XL from Verizon. I unlocked the bootloader with dePixel8 and confirmed the bootloader was unlocked. Then I went to install SuperSU from Chainfire. I followed the instructions 100%, but have ran into an issue. The phone has been in the process of booting for the last half hour. The instructions say it should only take a few minutes. Anyone else run into this issue, and if so how did you fix this? thanks.
Click to expand...
Click to collapse
Page 64 of the [Root] Super SU thread. Hope it helps.
Related
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance! ?
DreyX said:
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance! ?
Click to expand...
Click to collapse
It would fail if you try since you're rooted. You'll need to sideload the OTA via recovery, then root again via fastboot before first the boot.
krypto1300 said:
It would fail if you try since you're rooted. You'll need to sideload the OTA via recovery, then root again via fastboot before first the boot.
Click to expand...
Click to collapse
Thank you. Will give it a shot.
DreyX said:
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance!
Click to expand...
Click to collapse
Same situation as you,
Got a question for ya, I just unlocked bootloader also yet its still gray. Is yours?
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
nbhadusia said:
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
Click to expand...
Click to collapse
I want to install the update but don't want to lose root is there a guide somewhere on how to side load it with adb?
canemaxx said:
I want to install the update but don't want to lose root is there a guide somewhere on how to side load it with adb?
Click to expand...
Click to collapse
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
nbhadusia said:
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
Click to expand...
Click to collapse
So you took the OTA or side loaded the OTA? If you took the OTA and it succeeded while being rooted, that would be great news.
nbhadusia said:
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
Click to expand...
Click to collapse
lyall29 said:
So you took the OTA or side loaded the OTA? If you took the OTA and it succeeded while being rooted, that would be great news.
Click to expand...
Click to collapse
Sideload the OTA then boot to bootloader and redo root before fully rebooting to android. Worked for me.
Sideloading OTA with custom kernel
Is the process for sideloading an OTA different if you have a custom kernel? I'd imagine simply sideloading it wouldn't work.
nbhadusia said:
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
Click to expand...
Click to collapse
Pretty much the same process to root it again after the update? Same root method?
Sent from my Pixel XL using Tapatalk
So should we anticipate having to sideload every OTA update from this point forward as well? Along with having to root the phone again? Or do we expect OTA updates to work on rooted Verizon phones with the bootloader unlocked in the future?
Forgive the ignorance but the last few phones have been developer edition or have had simpler root methods.
le0.br4zuc4 said:
Pretty much the same process to root it again after the update? Same root method?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup. Same method.
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.
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
First of forgive me if this question has been posted before:
I rooted my device - Pixel 2 XL (Oreo 8.1, Android 8.1.0 OPM1.171019.021) a couple of days after acquiring it. I used the Unified Android toolkit Ultimate version.
Root procedure worked successfully (as far as I can tell, no errors observed during the process). One major problem all my apps that require root will not work:
- Activating Titanium Backup,
- Installation of Busy Box
- Activating SupserSUE
All the above respond with a "Root cannot be detected" popup. Any ideas what I did wrong or what is missing?
Your assistance is greatly appreciated. Please let me know if there are any details the I left out that would be helpful.
Thanks.
As far as I know, magisk is the only root option for the 2xl.
muyela said:
First of forgive me if this question has been posted before:
I rooted my device - Pixel 2 XL (Oreo 8.1, Android 8.1.0 OPM1.171019.021) a couple of days after acquiring it. I used the Unified Android toolkit Ultimate version.
Root procedure worked successfully (as far as I can tell, no errors observed during the process). One major problem all my apps that require root will not work:
- Activating Titanium Backup,
- Installation of Busy Box
- Activating SupserSUE
All the above respond with a "Root cannot be detected" popup. Any ideas what I did wrong or what is missing?
Your assistance is greatly appreciated. Please let me know if there are any details the I left out that would be helpful.
Thanks.
Click to expand...
Click to collapse
What file did you flash for root?? It's like Larzzzz82 said, magisk is the only root method ?
Larzzzz82 said:
As far as I know, magisk is the only root option for the 2xl.
Click to expand...
Click to collapse
Badger50 said:
What file did you flash for root?? It's like Larzzzz82 said, magisk is the only root method ?
Click to expand...
Click to collapse
WOW! That was quick Badger50 & Larzzzz82. Nice to be heard and accommodated and assisted!
There were three files mentioned in the process, all of which I flashed in order as per instructions.
- recoveryl-twrp-3.2.1.0-ysimr.xip
- BETA-SuperSU-v2.28-SR5.zip
- UPDATE-suhide-v1.09.20171001222116.zip
---------------------------------------------------------------------------------------------------------------------------
If magisk is the only way to root the Pixel 2 XL. Is there a particular way I can unroot (the current root) without loosing all the data I imported and then re-root using magisk? Or is it best to factory reset/wipe my device and then go ahead with magisk root? Is there a link you can send me for using magisk (I've heard/read of it peripherally but never researched the exact procedure.
Thanks!
muyela said:
WOW! That was quick Badger50 & Larzzzz82. Nice to be heard and accommodated and assisted!
There were three files mentioned in the process, all of which I flashed in order as per instructions.
- recoveryl-twrp-3.2.1.0-ysimr.xip
- BETA-SuperSU-v2.28-SR5.zip
- UPDATE-suhide-v1.09.20171001222116.zip
---------------------------------------------------------------------------------------------------------------------------
If magisk is the only way to root the Pixel 2 XL. Is there a particular way I can unroot (the current root) without loosing all the data I imported and then re-root using magisk? Or is it best to factory reset/wipe my device and then go ahead with magisk root? Is there a link you can send me for using magisk (I've heard/read of it peripherally but never researched the exact procedure.
Thanks!
Click to expand...
Click to collapse
I think the only way to fully unroot is to flash factory March update. I did that to my 1 day old pixel 2xl, than re-root.
https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
Sent from my [device_name] using XDA-Developers Legacy app
If you have TWRP just flash a custom kernel, TWRP, and Magisk in that order. If I understand your situation, then you are not rooted yet. Don't know why the tool kit would try to use SU unless you chose a wrong option somewhere.
Be sure you upgrade the toolkit first if you use it again.
wtherrell said:
If you have TWRP just flash a custom kernel, TWRP, and Magisk in that order. If I understand your situation, then you are not rooted yet. Don't know why the tool kit would try to use SU unless you chose a wrong option somewhere.
Be sure you upgrade the toolkit first if you use it again.
Click to expand...
Click to collapse
The device is actually rooted and shows the "insecure device... " warning (I guess typical with rooted Google Oreo devices) when booting.
Will this method preserve or delete my data. I may have to find a way to backup my data without having to use cloud storage solutions, then factory reset and go from there.
Thanks.
muyela said:
The device is actually rooted and shows the "insecure device... " warning (I guess typical with rooted Google Oreo devices) when booting.
Will this method preserve or delete my data. I may have to find a way to backup my data without having to use cloud storage solutions, then factory reset and go from there.
Thanks.
Click to expand...
Click to collapse
That insecure device warning is because your bootloader is unlocked. If you haven't flashed magisk in twrp you are not rooted.
I followed Larzzzz82 & evolishesh advise. I flashed the factory image to the phone then rooted using magisk. Luckily I still have my old phone and had not wiped so I can slowly retrieve most of my data.
Thanks for the support! Appreciated.
There probably a thread on his subject already but I can't seem to find it, but anyway is their a way to unlocked the bootloader on the Verizon edition of the pixel 2 xl if so can someone point in the direction so I can learn how to do it
Bootloader is locked and it cannot be done. Any exploit found was quickly patched out. Last one that worked was over a year ago. Sorry.
GenuineDickies99 said:
Bootloader is locked and it cannot be done. Any exploit found was quickly patched out. Last one that worked was over a year ago. Sorry.
Click to expand...
Click to collapse
Can the Verizon pixel 2 xl be rooted or is that out of the question
lavin40 said:
Can the Verizon pixel 2 xl be rooted or is that out of the question
Click to expand...
Click to collapse
Unlocking the bootloader is the first step in rooting a phone, so no. And you can't install Magisk or Xposed either due to them needing a custom recovery, which requires a..... you guessed it, unlocked bootloader.
GenuineDickies99 said:
Unlocking the bootloader is the first step in rooting a phone, so no. And you can't install Magisk or Xposed either due to them needing a custom recovery, which requires a..... you guessed it, unlocked bootloader.
Click to expand...
Click to collapse
Late follow up, you can install 'Virtual Xposed' now, it gives some limited functionality for Xposed on the Pixel but it's not a true root nor can it do everything that Xposed can.
If there is any justice in the world... Verizon will go out of business in a fire sale.