7.1.1 Bootlop when flashing magisk/phh SU - Nexus 6P Q&A, Help & Troubleshooting

Updated to 7.1.1 Beta. Flashed twrp. I then flashed magisk and then phh. I get stuck in a boot lop. I tried twice but each time I keep getting stuck in a bootloop. Does anyone have a work around? I've looked around and seems like everyone is getting it to work but me and a few others? Any help?

Not sure why you want magisk if xposed isn't supported on 7.0+ ? Just use superSU instead.
Edit: There is a (no longer a) benefit in using Magisk/phh, since magisk hide and using xpropset magisk module is detected by SafetyNet already, but see post below for the latest approach (if any):
http://forum.xda-developers.com/nexus-6/help/help-pass-safetynet-rooted-7-0-aosp-t3486834
suhide is not compatible w/ 7.1.1, so SuperSU is not an option for the 6P on the 7.1.1 Developer Preview

Flash magisk and phh su, works fine, but supersu get bootloop, something like this

7.1.1 with supersu (stable or sr1) boots fine, the problem atm is suhide, flashing suhide causes bootloops

Way possible, but without suhide is not very convenient, banks apps not working properly

So the latest superuser by chain fire works? Cause flashing magisk v8 then phh su just sends me to a bootloop.

I'm using magisk and the latest phh su on 7.1.1 and no issues what so ever even have it passing safetynet
All I did was flash the factory image, then two, then flashed phh su, magisk and then rebooted and installed xsetprop through magisk.

how are you getting this working? I haven't tested, but doesn't the 7.1.1 need a custom kernel to bypass safetynet? Kernel source isn;t out yet?

Related

Suhide 0.53 bootloop

I was trying to install xposed framework and still play pogo, but everytime I try to flash Suhide 0.53, I get stuck.
I'm using PureNexus 6.0.1 rom. Flashing SuperSU 2.78SR1 and systemless xposed 86.2 flash fine and system reboots easily but when I flash suhide, all I get is bootloop.
Any workaround or is purenexus the problem.
I think the reason was that PureNexus has SELinux as permissive. Just flashed Chroma (enforced SELinux), Pogo working with exposed.

Trying to root NBD91K sends the phone into a bootloop

I am running NBD91K build, but every time I flash supersu, it sends my phone into a bootloop. I am running the latest TWRP and tried SuperSu 2.78 SR5. Anyone having the same problem?
dewhashish said:
I am running NBD91K build, but every time I flash supersu, it sends my phone into a bootloop. I am running the latest TWRP and tried SuperSu 2.78 SR5. Anyone having the same problem?
Click to expand...
Click to collapse
Are you using suhide by any chance?
I've been stuck at bootloop when i tried to force system (not systemless) root on nougat. So my first thought was to delete /data/.supersu... then I've managed to reinstall root systemlessly, but after a few tries it stayed on the bootloop.... I had to reflash system.img and then I flashed the supersu once again and it works like magic.
Yes, I am using suhide
dewhashish said:
Yes, I am using suhide
Click to expand...
Click to collapse
Suhide does not work with 7.0+ roms with the November security patch. You need to flash the suhide Uninstaller and just use supersu
You're right, unintalling suhide and I can boot my phone after rooting, thanks. Too bad suhide doesn't work with the november patch, otherwise I can't get android pay working.
dewhashish said:
You're right, unintalling suhide and I can boot my phone after rooting, thanks. Too bad suhide doesn't work with the november patch, otherwise I can't get android pay working.
Click to expand...
Click to collapse
did you try Magisk v9 + phh Superuser?
Android Pay works like a charm for me on 7.1.1 DP2
blank
boqonx said:
did you try Magisk v9 + phh Superuser?
Android Pay works like a charm for me on 7.1.1 DP2
Click to expand...
Click to collapse
I installed magisk manager and phh superuser, how do I get Android Pay to work with it? do I need a custom kernel?
dewhashish said:
I installed magisk manager and phh superuser, how do I get Android Pay to work with it? do I need a custom kernel?
Click to expand...
Click to collapse
Ensure that you have uninstalled SuperSU prior to flashing Magisk v9 and phh Superuser.
After, install Magisk Manager apk posted on its thread and phh Superuser manager & SafetyNet Helper from playstore.
You can then hide Magisk from SafetyNet within Magisk Manager setting. Run SafetyNet Helper to test whether you pass the SafetyNet check or not. If everything is passed, then you should be able to use Android Pay & Pokemon Go .
boqonx said:
Ensure that you have uninstalled SuperSU prior to flashing Magisk v9 and phh Superuser.
After, install Magisk Manager apk posted on its thread and phh Superuser manager & SafetyNet Helper from playstore.
You can then hide Magisk from SafetyNet within Magisk Manager setting. Run SafetyNet Helper to test whether you pass the SafetyNet check or not. If everything is passed, then you should be able to use Android Pay & Pokemon Go .
Click to expand...
Click to collapse
that worked! thank you so much for your help!

Magisk 13.1 working for anyone?

Hi all,
My system was working fine with Magisk v12, I saw there was a big new update, I was interested and updated.
But using the latest Magisk Manager, it says root is not detected.
It's not a big problem, I will restore back to v12 for now, but did anyone else get it working?
Thanks
Asus zenfone 2 flash update manual Magisk 13.1 crash recovery recovery then AD
Same here with Xperia XZ. With v13.1 Root is not detected. v12 is working fine.
Have tried to reinstall it by completely removing and flashing from TWRP, but still no luck.
13.1 and 13.2 working on 7.1 with repacked stock kernel with drmfix fix. It will also work with newest genesis kernel
I upgraded Magisk 12 to 13 beta, then 13.1 and 13.2 without problems.
Even SafetyNet Check passes.
I'm using genesis-nodrm kernel.
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
qvmuhuuxz said:
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
Click to expand...
Click to collapse
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
realtuxen said:
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
Click to expand...
Click to collapse
Ok I'll try that.
I believe I flashed v13.2 straight over v12.
But when downgrading back to 12, I did flash the uninstaller first.
I'll try uninstalling and then updating
- Still no luck, it didn't work.
I tried updating Magisk 12 -> 13.1 thru the manager, and it would download the zip then do nothing. I found the zip in the Magisk directory, and installed it like it was a module, thru the manager, and it appeared to work. I got the new Magisk Manager (5.0.4) and it says I'm on Magisk 13.1 but that Magisk is not installed, and there is no root.
Following the installation instructions, I rebooted a few times, no change. So I flashed Magisk uninstaller, cleared cache/davlik, and rebooted. Uninstalled Magsick Manager. Rebooted. Booted to TWRP and flashed Magisk-13.1.zip. Rebooted twice. Same issues; Manager 5.0.4 says I'm on Magisk 13.1 but that it's not installed, no root.
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
voilsb said:
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
Click to expand...
Click to collapse
I didn't have to reboot after flashing magisk uninstaller, I just flashed v12 straight after.
And I just uninstalled the new magisk manager then the old one right away, I think?
Magisk manager 13.1 not working for me either tried installing thru app but it does not work
might be related to this https://github.com/topjohnwu/Magisk/issues/265
Also it might be related to this - https://github.com/topjohnwu/Magisk/issues/166#issuecomment-298765812
"Use rootkernel tool from tobias.waldvogel to fix drm instead of PoC TA fix. It seems to be incompatible to Magisk while rootkernel tool patched images work"
I swapped over to Genesis kernel (1.05, the current latest) to try and see if it would help my device pass safety net, since for some reason it is not passing anymore (I tried lots to fix it, flashing etc)
As I posted directly above, it looks like Magisk v13 doesn't like ta_poc, so I used the drmfix version, and Magisk v13.3 works great, and once again my device passes safety net

Magisk on sm-t350?

How could I replace SupedSU with Magisk ?
Running Fenix rom 6.0.1 currently
SupedSU appears to be Systemless.
When I try to flash Magisk though I get something about boot image patched.

Magisk hell resolved??!!!!!!!??!!!!!!!!!!??

im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix

Categories

Resources