Develop Bugs

After flashing TWRP, will not boot system

Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!

if you have 3.0.2 i think there was a problem with early build causing this. there was a link posted for the new one that supposedly fixed it. or just use the 3.0.0 build.

Mike02z said:
Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!

Mike02z said:
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!
Click to expand...
Click to collapse
Here is the direct link for TWRP_dragon_3.0.2.0.img:
https://onedrive.live.com/?authkey=...&id=479EB75F5DD9DA59!131&cid=479EB75F5DD9DA59
Here is the complete folder: (TWRP flashable stock kernel)
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers

Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.

redukt said:
Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.
Click to expand...
Click to collapse
And connect everytime with PC to do a manual reboot via fastboot .. seems a little bit too much for a simple reboot. At least for me
A proper TWRP with proper vboot will boot always correctly, like the one from xceed.
Did you ever had to do a manual reboot on his version ?
Should be fixed at the root cause .. Hope you agree ?
Cheers

I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...

redukt said:
I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...
Click to expand...
Click to collapse
Interesting .. I did not have any reboot issues with xceed TWRP versions .. I had to use the fix fastboot option once, but this is another topic.
But thanks for your information ...

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.

Annan Denis said:
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.
Click to expand...
Click to collapse
Wrong device thread .. anyway just restore "stock" ROM/recovery to make it working again.
Good luck !

Help with Suhide in Zenfone2

Hello guys, somebody can help me install Suhide on Zenfone 2? I've tried the guides around, everything went fine thru the install in temporary TWRP, but when I relock the bootloader I end up in a bootloop.
My steps:
1-Unlocked phone with the unlock.bat
2-Turn off Cellphone
3-Started in Bootloader
4-Flashed Temporary TWRP
5-Go into Recovery
6-Flashed Magisk, SuperSu for magisk (2.76), dropped command in terminal echo "SYSTEMLESS=true" > /data/.supersu, flashed SuperSu (2.78)
7-Reboot into Bootloader
8-Relock phone with restore.bat
Even if I just flash SuperSu for Magisk (2.76) and doesn't update to 2.78 my phone ends in Bootloop.
Are I missing something?

Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk

kenbo111 said:
Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
so, I'm supposing that the fifth option in this tool is SuHide instead of PHH?

Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk

kenbo111 said:
Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I was using Magisk+PHH, I want to use Suhide to test, because I used to use SuperSU.

I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.

Abex, thank you, I will try tomorrow when I arrive on my Job, there is my PC with all the stuff to do, I will post news if everything went fine or goes bad

abex181 said:
I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.
Click to expand...
Click to collapse
thanks. I was searching this for a long time.
is there a place where to find @shakalaca's contributions to Zenfone?

Abex, when I flash SuperSu 2.76 or 2.78-R1, even the version you've posted I got stuck into loading screen.

Hi all.
I am currently having the exact same issue with my Zenfone 2 ZE551ML. Things I have learned (Which may be very obvious to some)
The device cannot boot with the bootloader unlocked.
Locking the Bootloader with any kind of custom recovery installed causes the device to only boot into the bootloader. Recovery or stock ROM cannot be accessed.
The only way around this is to unlock the bootloader, flash the stock recovery and then relock the bootloader.
Steps I have taken:
1) Unlock the bootloader
2) Boot into the bootloader and flash latest TWRP recovery for ZF2 (twrp-3.0.2-0-Z00A.img)
3) Reboot into TWRP recovery
4) Flash the Xposed Uninstaller (latest version)
5) Flash the Magisk Uninstaller (latest version)
6) Flash Magisk-v6_repack_for_zf2_601.zip
7) Flash SuperSU-v2.76-magisk.zip
8) Enter TWRP Terminal, issue command - echo "SYSTEMLESS=true" > /data/.supersu
**Note at this point, I get no response from the terminal, just the next command line. I think I should be expecting one? And therefore something is failing at this step?**
9) Flash SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip
10) Flash xposed-v86.2-sdk23-topjohnwu.zip (I am lead to believe that this is the only version that won't trip Safetynet, even later versions like 86.5 do)
11) Flash suhide-0.53.zip
12) Reboot to Bootloader
13) Flash the stock recovery
14) Lock Bootloader and reboot
This causes a bootloop on the splashscreen (White on black, so bootloader is locked) and on one attempt, a notification before the splashscreen informing me the device failed verification. The only solution I have found for this is to re-unlock the bootloader, enter recovery (stock) and sideload UL-Z00A-WW-4.21.40.134-user.zip
Then reboot to bootloader, lock bootloader again and reboot. No data missing or anything, but the phone is not rooted.
I'm wondering if suhide or superSU require the bootloader to be unlocked permanently- in which case, we need a solution for that. Could this be the case?
Or is it that we need a superSU v2.76 fix for Zf2 version, much like the v2.78 graciously posted by abex?
Perhaps it makes sense to sideload the Stock Marshmallow ROM at some point via TWRP, BEFORE returning to stock recovery? But even then, I think flashing it before superSU v2.76 seems pointless, as there are issues there- and does flashing it after simply wipe out all the hard work?

@kemp7, @Alterius:
If, after flashing a zip, you are getting stuck on boot or find that you can only boot to recovery, you can try flashing the boot.img from UL-Z00A-WW-4.21.40.134-user.zip in fastboot. This should get rid of any modifications to the boot image made by the various systemless mods you may have flashed previously. Any files added to the filesystem will still be present, but there should be no hook to load any systemless scripts like su.d or magisk. If you were using a custom kernel, it will no longer be installed. Of course, if you reflash the MM update zip in its entirety, this will be included, though I thought I should mention this to save you some time.
Before flashing any zip, you should try to get a general idea of what it will modify. If you've been flashing many zips and getting errors, it's a good idea to go back to a clean slate before trying something new. In fact, every time you flash a recent SuperSU zip, the script actually restores the boot image to a backup that was made the first time you flashed a recent SuperSU zip. This behaviour may be desirable, or it may unwittingly uninstall a custom kernel....
I also have to reiterate that its probably a bad idea to mix Magisk-based systemless mods with ones based on SuperSU's su.d.
Regarding the zip of SuperSU v2.78-SR1 that I posted, I'm not sure if it will work if you re-lock your bootloader afterwards. I can only report what I've tested and I keep my phone unlocked. That being said, the ZF2 can definitely boot with an unlocked bootloader, modified recovery, root, kernel, etc. Note that for MM rom, you will need to flash a modified TWRP in order to boot in to android (3.0.2-M1).
In this thread, I've reported a working instance of SuperSU v2.78-SR1, systemless xposed v86.2, and suhide v0.53 on my ZF2 with unlocked bootloader and TWRP-3.0.2 installed. To get there, I've only just followed the instructions on the suhide thread, except with the zips replaced with the ones patched for our ZF2 that I posted in that thread.
If you are having trouble, go back to stock MM rom. You can do this by flashing the stock recovery.img from the 4.21 zip in fastboot, then ADB sideload the whole zip. I think you should be able to do this with unlocked bootloader. Reboot into android to make sure all your data is still there.
Then, you can flash TWRP 3.0.2 for MM roms using fastboot. Your bootloader will need to be unlocked for permanent custom recovery. You might be able to dothe following with temporary TWRP (fastboot boot TWRP.img), but I haven't tested this.
From there you can follow the instructions in the suhide thread: flash SuperSU v2.78-SR1, (optionally reboot first, there will be a couple boot cycles before android starts up), flash suhide v0.53, (optional reboot), optionally flash systemless xposed v86.2, wipe dalvik cache, reboot.

Abex, thank for all the support again!
I've downloaded all the modified files for zenfone 2 from your posts ( SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip and xposed-v86.2-sdk23-topjohnwu_repack_for_zf2.zip ), except the suhide installer (suhide-0.53.zip) that is the original file from suhide thread.
For Unlock & reLock Bootloader I was using one tool I found here on XDA that comes with two files (unlock.bat & restore.bat from this thread) but it makes my phone unbootable if I just unlock it if I remember correctly.
Theres any good and safe tool that do you recommend for just Unlock the bootloader so I can give I try?
Today I did a mess on my phone while trying to figure out the things, so I reflashed a RAW imagem from LL .196 and did the upgrade with the MM zip on Internal Card, then did a factory reset afterwards, so I'm basically "starting fresh" , so I believe that theres no trace from my old messy tries.

Root for OxygenOS 4.1.6

Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.

Please describe in steps what you did.

AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!

Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk

I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.

AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?

ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb

AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.

I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.

Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!

Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver

I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3

Asus Z00A(ZE551ML) bootloops into Recovery!

Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!

dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.

sukhwant717 said:
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
Click to expand...
Click to collapse
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.

dantekb43 said:
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
Click to expand...
Click to collapse
which version of super su you are flashing?

dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.

Vorstedt said:
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Click to expand...
Click to collapse
I've had the same problem and your solution fixed it!
Thank you very much, sir! :good:

Pixel 2 XL Root [Going Mad About]

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!