Related
I read the post about it. I'm new to this, it just looked like a lot of jargon. From what I can tell though I can't just downloaded supersu then flash it in TWRP. I tried it, it doesn't work. Can anyone explain in layman's terms how to root my phone? I have the pixel XL. Any help would be much appreciated. Thanks.
Thats exactly what you can do. If your bootloader is unlocked and you have TWRP RC1 installed you simply flash SuperSU v2.79 SR3 and all is well.
As noted, you will need to unlock the bootloader before using TWRP to flash the SuperSU zip. At that point the standard warning is: DO NOT LOCK THE BOOTLOADER. Items 1 and 8 from the following have more information.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
alluringreality said:
As noted, you will need to unlock the bootloader before using TWRP to flash the SuperSU zip. At that point the standard warning is: DO NOT LOCK THE BOOTLOADER. Items 1 and 8 from the following have more information.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
I did this, and it didn't work. I downloaded the SuperSU app and it said there aren't any SuperSU binaries. I tried flashing multiple times.
BDogg718 said:
Thats exactly what you can do. If your bootloader is unlocked and you have TWRP RC1 installed you simply flash SuperSU v2.79 SR3 and all is well.
Click to expand...
Click to collapse
I did exactly this, and it didn't work.
The latest beta SuperSU zip is at:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
The latest stable SuperSU zip is at:
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you are using TWRP RC1, it should come up with a message when it starts. Sometimes TWRP RC1 doesn't start with the message, and if that happens, I'm not sure if it will install a zip without following the additional instructions from Dees_Troy. Personally I installed the SuperSU v2.79 SR3 zip this past weekend just by booting TWRP RC1, and for a second install I used TWRP Alpha 2. Assuming your Pixel XL indicates it's unlocked, my suggestion would be just to boot the TWRP Alpha 2 image, don't install the TWRP zip, and then install whichever of the above SuperSU zips you want to use.
After Root open beta 17 stook on boot logo
Any solution
Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..
I have the same problem. Neither SuperSu nor Magisk works.
persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help
Use SuperSu 2.82
2.82 works fine for me! Many thanks!
My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)
TO root latest beta an stable version you can follow this guide:
I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks
I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12
We're can I download v8?
Sent from my Pixel XL using Tapatalk
The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.
Slowclap
Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse
Hi guys
I've just bought a used Pixel 2XL and now figuring out how to root. Just wonder if it's good to use Magisk stable ver 18.0 to root the pixel 2xl on November update?
Thanks
cnkhanh said:
Hi guys
I've just bought a used Pixel 2XL and now figuring out how to root. Just wonder if it's good to use Magisk stable ver 18.0 to root the pixel 2xl on November update?
Thanks
Click to expand...
Click to collapse
Yep, you should be fine :good::good:
How about the December update?
I got lazy...still on October.
TIA!
Badger50 said:
Yep, you should be fine :good::good:
Click to expand...
Click to collapse
docluv01 said:
How about the December update?
I got lazy...still on October.
TIA!
Click to expand...
Click to collapse
No worries there either. Running it myself!
just jumped from november to march update using OTA via adb push and after i flash magisk it causes the phone to bootloop.
looks like there is a problem with patching the boot.img from magisk, reflashing the stock boot file the pixel works but no root obviously....any idea?
beren said:
just jumped from november to march update using OTA via adb push and after i flash magisk it causes the phone to bootloop.
looks like there is a problem with patching the boot.img from magisk, reflashing the stock boot file the pixel works but no root obviously....any idea?
Click to expand...
Click to collapse
There are several scenarios you could try.
1. Fastboot into twrp, flash twrp installer zip, flash magisk and see if it boots.
2. Fastboot into twrp, flash twrp installer zip, flash magisk, flash magisk uninstaller, then flash magisk again and see if it boots.
3. Fastboot into twrp, flash twrp installer zip, flash magisk, reboot to twrp, flash magisk uninstaller zip, then flash magisk again and see if it boots.
4. Fastboot into twrp, flash magisk, then flash magisk uninstaller zip, then flash magisk again and see if it boots. Twrp will be gone as well.
5. Try some of the above, but add a custom kernel into the mix.
Sometimes it can take 4-5 tries before you'll get it to boot up with root. Just be patiently persistent my friend and you'll get it :good:
Badger50 said:
There are several scenarios you could try.
1. Fastboot into twrp, flash twrp installer zip, flash magisk and see if it boots.
2. Fastboot into twrp, flash twrp installer zip, flash magisk, flash magisk uninstaller, then flash magisk again and see if it boots.
3. Fastboot into twrp, flash twrp installer zip, flash magisk, reboot to twrp, flash magisk uninstaller zip, then flash magisk again and see if it boots.
4. Fastboot into twrp, flash magisk, then flash magisk uninstaller zip, then flash magisk again and see if it boots. Twrp will be gone as well.
5. Try some of the above, but add a custom kernel into the mix.
Sometimes it can take 4-5 tries before you'll get it to boot up with root. Just be patiently persistent my friend and you'll get it :good:
Click to expand...
Click to collapse
thank you for spending your time to help me, very appreciated :good:
the trick was to remove magisk flashing the uninstaller, that i didn't before, after this it worked from first time...
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
[Edit]
Theese are the steps i take
-flash recovery twrp (ok)
-reboot to recovery (ok)
-flash magisk v18 (loop)
megamarini said:
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
Click to expand...
Click to collapse
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
djcrystals said:
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
Click to expand...
Click to collapse
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
megamarini said:
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
Click to expand...
Click to collapse
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Badger50 said:
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Click to expand...
Click to collapse
Thank You mate, when I'll get home I'll try to follow yor steps and I'll let you know. Any suggestion about kernel on stock firmware? ElementalX it's ok?
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Sui77 said:
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Click to expand...
Click to collapse
Tryed everything but nothing works..
megamarini said:
Tryed everything but nothing works..
Click to expand...
Click to collapse
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Az Biker said:
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Click to expand...
Click to collapse
SOLVED
The only way (for me) to root my Pixel 2 XL is follow theese steps:
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Source: XDA Post
Thank you so much to everyone who tried to help me!