Develop Bugs

SuperSu help, please!

There is no way to flash supersu on my phone on any rom, on freedomos rom when i select install supersu doesnt work with neither elementalx or stock patched kernel, i tried flashing stock unpatched kernel and then supersu neither that work, it always comes to boot image patcher and then says failure aborting, i had the same problem with other roms, can someone tell me whats the problem ?

Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.

ungeeked said:
Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.
Click to expand...
Click to collapse
Can I use this recovery for every rom in future or I have to go back to official one?

ach3fck said:
Can I use this recovery for every rom in future or I have to go back to official one?
Click to expand...
Click to collapse
No need to go back to official

ungeeked said:
No need to go back to official
Click to expand...
Click to collapse
Ok thanks, sorry to bother you, but should I flash the ROM again via Aroma or I should just flash SuperSu?

Just flash SuperSU. That should do it

Flashed SuperSU and got stuck in a bootloop, did a clean flash again and it worked, thanks a lot!

And now this, f*ck, maybe it could be because I restored backed up data partition, will try to do a clean flash and let you know.

I had this issue yesterday and fixed it today.
try deleting the su binary in twrp.
goto: /data/system/xbin
delete su
flash your SuperSU.zip again.
worked for me, because i had an systemless supersu installed, but an old su file in xbin.

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.

Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.

mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.

guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do

mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.

I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu

aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.

mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?

aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?

guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error

If I do a ROM update do I need to unSU and flash Magisk again?

Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.

aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?

guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?

aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).

guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.

Would using the wrong unSU version affect safetynet detection?

Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?

guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.

Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

Magisk on Pixel / Pixel XL - does it work yet?

So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...

wireaudio said:
So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...
Click to expand...
Click to collapse
Hey... Check the last paragraph of this post: https://forum.xda-developers.com/showpost.php?p=71502787&postcount=17 named "What's Next"
Cheers...

I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!

bravesfan171 said:
I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!
Click to expand...
Click to collapse
This is the exacts developer's words. It's been posted 23 hours ago:
topjohmwu said:
For the long awaited Pixel support, I think I'll start working on it, but the complexity of that device might take a very long time for me to understand, since I do not own the device. I can only borrow my friend's device for not that long of a period of time, so progress shall be really slow. I'll not get the Pixel device now, because I don't think it is worth the price and the hassle for me to import it into Taiwan, but I'll definitely get the Pixel 2 to replace my current daily driver lol.
Click to expand...
Click to collapse

Thanks guys! Much appreciated!

wireaudio said:
Thanks guys! Much appreciated!
Click to expand...
Click to collapse
Hello... Maybe take a look at this: https://forum.xda-developers.com/showpost.php?p=71573863&postcount=1029
Cheers...

Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.

funkybrunk said:
Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.
Click to expand...
Click to collapse
I'm getting an error when installing Magisk 11.6 on the Pixel, says:
"Updater process ended with Error: 1
Error installing zip file Magisk-v11.6-Pixel.zip"
Anyone else run into this with a fix?
----------------------------------------------------
Just wiped everything, still no go.
Getting the exact same error. This seems like an error with TWRP or the zip file I'm using.
The error pops up during the "Unpacking boot image" stage.

You need to used TWRP RC2. Your errors are because you are on RC1

funkybrunk said:
You need to used TWRP RC2. Your errors are because you are on RC1
Click to expand...
Click to collapse
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?

318sugarhill said:
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?
Click to expand...
Click to collapse
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.

pcriz said:
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.
Click to expand...
Click to collapse
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually

318sugarhill said:
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually
Click to expand...
Click to collapse
PN has its own kernel so I am assuming yes it will.

pcriz said:
PN has its own kernel so I am assuming yes it will.
Click to expand...
Click to collapse
Ok. Hopefully dirty flashing will just reset the kernel

318sugarhill said:
Ok. Hopefully dirty flashing will just reset the kernel
Click to expand...
Click to collapse
I should've been more definitive in my answer. Yes it will replace the kernel when you flash the rom, my bad.

I was using pure Nexus with Ex kernel....I flashed PN Rom (dirty flash) just to reset kernel....Flashed TWRP RC1 zip zip....Reboot system, then reboot recovery and flashed TWRP RC2 zip, reboot system, reboot to recovery flashed Magisk then reboot system again. Reboot to recovery flashed vendor img for PN and all is good. Enabled magisk hide in magisk app settings.....Then under magisk hide I hid it from DirecTV Now app. All safety net tests pass. Needed a build prop edit for directTV now to work correctly but all other apps blocked because of root are now working.
Thanks for the assistance

Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk

bb12489 said:
Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Working fine for me with Latest ElementalX Kernel

liam_davenport said:
Working fine for me with Latest ElementalX Kernel
Click to expand...
Click to collapse
Good deal. What do you think would be the best way to update to 7.1.2? I have TWRP recovery and elementalX at the moment. Should I flash stock boot.img, then update? I Imagine I would have to flash magisk again though.
Sent from my Pixel XL using Tapatalk

has anyone gotten any of the modules to work ?

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.

DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers

jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).

DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?

humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct

I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?

the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol

j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.

Check out this post, it works like a charm.

Where can i find a version of busybox that will work?

i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.

equlizer said:
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
Click to expand...
Click to collapse
Use the Magisk Module Busy Box for Android NDK. Works great.

felosisman said:
Use the Magisk Module Busy Box for Android NDK. Works great.
Click to expand...
Click to collapse
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?

equlizer said:
Where do i find it? thx
Click to expand...
Click to collapse
Open Magisk Manager, go-to Downloads, find and download "BusyBox for Android NDK 1.27.2", reboot and profit.

Noob question but what is BusyBox and what's it's purpose

mackentosh said:
Noob question but what is BusyBox and what's it's purpose
Click to expand...
Click to collapse
Busybox allows programs to perform actions on your phone using Linux commands. So some apps require it to run some commands and wont work without it.

equlizer said:
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
Click to expand...
Click to collapse
You shouldn't be getting that error anymore if you're using the latest Magisk release. He released version 15.0(1500) a couple days ago, but that was actually fixed in the last beta 14.6.
You would have to reflash your Kernel boot and dtbo and repatch though with the new version. I just used the Magisk Uninstaller script in TWRP, flashed the latest zip of flash Kernel then latest Magisk in TWRP and all good.