Develop Bugs

Chainfire autoroot working, Stock, no custom kernel and no crash to lock screen

Just an informative message in case people were having same issues I was, reading the posts, I see many are.
The amazing @Chainfire has a working beta method which allows me a simple, fully stock rooted OL1, with deep sleep fixed, and a small tweak to get Titanium Backup (TiBu) working on my sprint galaxy s6 (SM-G920P).
Note that chainfire's site (http://autoroot.chainfire.eu/) as of 1/16/16 had a autoroot version for the G920P that installed the 2.65 NOT the 2.66 (or 2.67) (beta deep sleep fixed versions) of SuperUser SU, so you'll have to TWRP install the 2.66 or 2.67 to get the deep sleep fix
Here's the brief GUIDE how I did it:
1. Download OL1 here's the sammobile link http://www.sammobile.com/firmwares/download/62965/G920PVPU3BOL1_G920PSPT3BOL1_BST/
2. Download ODIN 3.10.6 http://forum.xda-developers.com/showthread.php?t=2711451
3. Download CFautoroot for the Sprint Galaxy s6, and consider donating to @Chainfire https://download.chainfire.eu/785/CF-Root/CF-Auto-Root/CF-Auto-Root-zerofltespr-zerofltespr-smg920p.zip
4. ODIN flash first the Stock OL1 and then the CFautoroot
5. Download and flash THIS TWRP https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html or select appropriate one from https://dl.twrp.me/zerofltespr/ *(note that 3.0.0-0 is now available, but I haven't tried it yet, 2.8.7.0 still working well)
6. DEEP SLEEP FIX Download SU 2.67 Beta https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
*** Note- this beta version of SU works PERFECTLY on my 920P phone, and fixed the deep sleep issue
7. Move the SU 2.67 Beta to your phone's hard drive. Put it somewhere you can find it easily.
8. Boot into TWRP recovery (power, home key and volume up). Click "Install" and select the 2.67 SU Beta zip folder you just downloaded.
OPTIONAL:
9. Fix TiBu: Easy fix- uncheck in SU the "mount namespace separation"
Done.
Finally- pure stock rooted, nearly no crashes, everything seems to work. :good:
UPDATE 2.20.16: Both Beta versions 2.66 and 2.67 SuperSu DID in fact eventually crash, but only after 10 days did i get my first, and after 5 weeks, it has only occurred with Dolphin Browser, and only rarely- so might be a setting related to that app. Still way better and more stable than unikernel method.

that's awesome!
Sent from my S6 using tapatalk

Did it trip Knox?

1619415 said:
Did it trip Knox?
Click to expand...
Click to collapse
I had previously used @djvoleur 's UniKernel v8 and v9, so I already had knox tripped

Saafir said:
It says he Odin'd TWRP so I would assume so. Kind of confused to what good ths method is lol
Click to expand...
Click to collapse
I couldn't find a pure stock with a pure stock kernel way to root. Rooting using the UniKernel method kept me with a very buggy system that repeatedly crashed, no matter what I did to manipulate it.
Once chainfire autoroot became available for the s6, that was great- but it had the deep sleep issue (and also messed with a TiBu setting). His 2.66 update fixed the deep sleep issue, and a simple settings change fixed the TiBu issue.
googling for these answers wasted a lot of my time, and reading posts- I saw that others were struggling with this too-- especially since they weren't sure his methods would work on the sprint version of the s6.
So I just thought I'd save people some time, confirm that the methods work great on the 920P, and give them links to how to do it

I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.

Huey Driver said:
I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.
Click to expand...
Click to collapse
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though it seems I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that also should work fine
good luck
**Correction: the newest TWRP is 2.8.7.0 for the G920P

It may well just be something I did. Like I said, brand new phone....
I used ODIN, and I got the downloads from the TWRP site (dl.twrp.me)...
Regardless, I got 2.8.7.0 to work and I have root. Not really sure what the differences are.
Just kind of putting it out there for others....

my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?

legola said:
my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?
Click to expand...
Click to collapse
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously

spammy l said:
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously
Click to expand...
Click to collapse
It actually won't, unless your stock. Unikernel will just keep overwriting it since it's prerooted.

spammy l said:
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that should work fine
good luck
Click to expand...
Click to collapse
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?

yaibakt said:
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?
Click to expand...
Click to collapse
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:

spammy l said:
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:
Click to expand...
Click to collapse
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.

yaibakt said:
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.
Click to expand...
Click to collapse
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.

spammy l said:
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.
Click to expand...
Click to collapse
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...

yaibakt said:
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...
Click to expand...
Click to collapse
hmmm- bizarre.
Not sure exactly what is going on with your system. As for the battery- mine has been working great (by s6 standards)- way better than unikernel v9, and at least as good as unikernel v8.
Are you sure it is deep sleeping? Positive it is running SuperSU v2.66? (could check on the settings page) Also, though I'm sure you'd know if it weren't deep sleeping, you could try running the "CPU Deep Sleep Info Widget" to double check. https://play.google.com/store/apps/details?id=de.cmweb.deepsleep&hl=en
As for mine- I'm over a week into this method, haven't crashed a single time to lock screen, battery is working great (for a s6), and all apps seem to work smoothly- without all the bugs I was experiencing with unikernel.
Hope your phone gets sorted out soon too

yeah, im sure that all the setting on my phone are the same between unikernel v8 and this method. i use SU v2.66 too.
i havent got any crash on v8 either, so basically i just compare v8 and this method in battery life.
i dont use v9 since it's reported to have lockscreen issue.
but well, i'll being using this method at least till weekend to see. i'll just be able to re-flash the rom if necessary at that time anyway.
thank you.

I have been away from the forums for a few weeks, i was curious if this or any method allows for rooting but retaining knox status? I am rooted (with the old pingpong method) but stayed on OE2 (5.0.2) to keep knox intact. I would love to get updated to the latest OS rooted but keep knox intact still.. not sure if its possible, so i check with yall..
sj
Sent from my SM-T210R using Tapatalk

If i were to skip the custom recovery flash, would i be able to receive ota updates?
Sent from my SM-G920P using Tapatalk

Root not working, stock Nexus 5x using Root Toolkit, trying to avoid a wipe

Hey all,
I realize this might need a wipe, but honestly if there is a fix it will save me a few hours headache of reloading and re-configuring everything.
Currently my phone will not root properly. I'm using the latest release MTC19V. I used the Nexus Root Toolkit to upgrade without wipe from the previous version like I normally do. After upgrading, I used the root function. There were no errors, however some applications are stating SU is not present.
SuperSU thinks everything is fine. Root requests are popping up normally.
BusyBox states "the su binary was not found on your phone", even after SuperSU pops up and I grant it permission. I assume BusyBox is no longer installed.
AdAway states "su binary could not be found" after I grant permission.
Greenify gets root access fine.
Xposed is working.
Also, after it is rooted, I no longer have access to DATA services over the 2G/3G/LTE networks, there is a "!" icon by the signal bars. WiFi works fine. If I flash back to stock without wipe, everything works normally.
I have tried:
- Unroot, flash back to stock MTC19T
- Removing all apps and installs of Xposed, SuperSU, BusyBox
- Using the uninstall and clean options in SuperSU
Going to keep messing around, but if anyone can point me in the right direction to avoid a full wipe, that would be fantastic.
Thanks.

Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.

Tarv said:
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Click to expand...
Click to collapse
Ok, the regular ole busybox and adaway don't work with systemless root. There are additional things that need to be flashed. When I get to my computer I'll post a link to the files.
Sent from my SM-G930V using Tapatalk
---------- Post added at 05:00 PM ---------- Previous post was at 04:51 PM ----------
Flash the systemless hosts file from THIS link to get adaway working.
Try THIS busybox. If it doesnt work try THIS one.

Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?
Sent from my Nexus 6P using XDA Labs

Spikedude said:
I think the problem might be a corruption of the Busybox installation
Click to expand...
Click to collapse
Spikedude,
I think I was in the same boat. Before it stopped working, I too was seeing BusyBox 1.24.1 and not able to upgrade to 1.24.2. I also did an uninstall.
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
I used the other method of installing BusyBox as PiousInquisitor mentioned, and it installed properly, although it's using 1.24.1. BusyBox by Stericson still does not show it's installed.
I also think the installer from Stericson is busted and what caused this whole mess.

Tarv said:
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
Click to expand...
Click to collapse
Hey Tarv,
Thanks for the update. When you wiped the phone, what method did you use? Factory reset from within settings, or using NRT to flash stock and unroot with the "no wipe" option to preserve user data disabled?
Also, you might be right about the broken Stericson Busybox installer. Busybox on Rails looks like a good alternative. I've disabled the NRT option to install Busybox by Stericson when rooting, so I'll just install Busybox on Rails after the fact.
Sent from my Nexus 6P using XDA Labs

Spikedude said:
When you wiped the phone, what method did you use?
Click to expand...
Click to collapse
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader

Tarv said:
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Click to expand...
Click to collapse
Thanks Tarv,
Followed your procedure and am once again rooted and have data connectivity.
Unfortunately, installation of Busybox was not successful. Tried the BB on Rails version, but it only installs to /system/xbin, not /su/bin. As a result, the same root apps that didn't work previously still don't work. BB by Stericson pops up the success message, but then indicates BB is not installed.
So almost back to square one. I'll try going back to stock and rerooting using NRT again, but this time enable BB installation as part of the rooting process. Maybe...
UPDATE:
First, I may have spoken too soon about BB on Rails not working. I based that on root mode of ES File Explorer not working properly, but that might be an ES problem. Play Store reviews are also complaining about the ES root problem. So maybe installation of BB to /system on systemless root is ok?
I wiped and rebooted with NRT, and allowed it to install BB by Stericson. This worked fine, allowing installation of 1.24.2 of BB to the /su/xbin directory. Originally it indicated /su/bin, and that the "cat" file was missing (whatever), but after reinstalling to xbin a couple times and some restarts it all looks normal. Adaway works, full data connectivity works, etc. Trying to flip the root mode switch in ES pops up an error, but I can still explore root, so no big deal (I'm using Solid Explorer more anyway).

Magisk on Verizon Note 4

Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.

Try going to the Samsung Note 4 international section.. I just flashed a Note 7 port to my wife's phone and it rocks..

Could you possibly link to which one? Is it this one? Xerrum525 N7 FullFramework PortedRom for SM-N910C / SM-N910H
Also did you use magisk with it to use pokemon go?

Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I'd like to know too.
What I did was install PaulPizz. Once it finished I deleted the SuperSU folder via TWRP.
It booted up fine, I still had the SU app in my drawer, I did full unroot via SU. I then flashed the uninstall for Xposed and now I can play pogo.
I Haven't been able to get Magisk to work... I get unable to detect boot image. I'm unrooted for now on PaulPizz and can play PoGo 0.37

Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I downloaded an older version of the app from http://www.apkmirror.com/apk/niantic-inc/pokemon-go/.
I uninstalled the new version. Reinstalled the older. Ran fine. I've heard they'll force an update sooner or later but its good for now.
I also made sure to turn off auto app updated in settings.

I did find a solution using PaulPizz and magisk. It relatively follows most other tutorials. Plus I found a way to toggle magisk with tasker, if anyone is interested. I'll post a step by step tomorrow or possibly later tonight. Sorry to make everyone wait.

So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.

Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
I still get unable to detect boot image :/

reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.

Tricil said:
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.
Click to expand...
Click to collapse
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.

reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
After clean install (wipe data, cache, system)
It says after mounting system
Mounting /system(ro), /cache, data
Device platform arm
unable to detect boot image
error 1
idk what to do

reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.

Tricil said:
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.
Click to expand...
Click to collapse
Thanks again, it looks like the only difference was that I was on CPF3.r-2.
I tried going back to CPD1 and still no luck.
I appreciate you letting me know.

I used the Kyubi rom and uninstalled root with supersu and installed all of the magisk stuff and it works like a charm. All of the xposed modules work good too with the system less xposed. It takes a while to boot up after flashing magisk and clearing cache but worth it. The buddy system is pretty cool lol

Anyone else only able to MAYBE play on WiFi?

Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
Well I have magisk installed but I dont know if the xposed went through entirely it says it flashed ok but according to the installer I don't have xposed installed? What's going on did I do something wrong

Did you remove the old xposed app after the flag and install the new xposed apk also? I think mine did the same, because I forgot to also install the xposed app after flashing the systemless xposed framework.

I was able to full unroot, delete the super su file in twrp. when I flash the Xposed uninstaller it removes the framework but leaves the APk in a form that I can't delete.
If I flash magisk and all the other stuff it goes through fine, but when I try to toggle root off in magisk it turns itself back on within a few seconds. I'm assuming this is because i didn't get Xposed all the way off?
Any ideas? Thanks in advance for the help.

Magisk will refuse to unroot while xposed is still there in the system form. Even a piece of it.

Well now I got Xposed off using tibu before I unroot. Everything installed, systemless Xposed registered as being active, but when I try to toggle root in magisk I get the same thing with it turning itself back on. If I try to request root privileges from an app I am told i have no root.
Ideas?

Hiding root for Banking App

Hi Everyone,
I'm currently looking for a way to hide SU so that i can use my banking app, but with so many threads i'm reading, i can't find a reliable source and procedure. I'm currently studying how magisk work but some says that it doesn't work.
If i missed out a good and updated thread on hiding root, please do let me know.

You can use root switch
https://www.asus.com/zentalk/tw/thread-173542-1-1.html

Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.

crazyates said:
Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.
Click to expand...
Click to collapse
Thank you for sharing you experience with Magisk! i'm also skeptical with this but i will try it later, see if it will works with me. Thanks!

crazyates said:
Back when I was trying to get PokemeonGo to work, I tried a couple of different apps and hacks, and very few of them work, and even fewer of them work well. That was before I switched to Magisk, which I was skeptical about at first (I've been using SuperSu for years), but it really does work quite nicely.
I use Magisk, with no SuperSU. IIRC, Magisk is a systemless root, meaning it doesn't touch your /system, it flashes into your /boot. I flashed my ROM, Kernel, Magisk zip, and then downloaded the app from the play store. Inside the Magisk settings, there's a toggle for "Magisk Hide". Simply switch that on, and everything works! Your SafetyNet checks work, your banking apps work, your PokemonGo/MarioRun work, etc. Apps that already have root will continue to work, but any new apps will not be able to obtain root unless you unhide.
Click to expand...
Click to collapse
Just a quick question, did you just restore your boot image then flashed the magisk zip? then downloaded the app manager from play store?

yoorie016 said:
Just a quick question, did you just restore your boot image then flashed the magisk zip? then downloaded the app manager from play store?
Click to expand...
Click to collapse
I switched to Magisk at the same time I was switching ROMs, so I did a complete wipe and flash. You could do a dirty flash, but I would reflash your /system and /boot withOUT wiping cache or dalvik or anything. I don't know what (if) your previous root installed anything into /system, in which case it probably won't like it.
So what I would do If I were you is boot into recovery, re-flash your ROM/Gapps (no need to wipe cache), reflash your kernel (optional), flash the magisk zip, reboot, install magisk manager from Store, and you're good to go!

crazyates said:
I switched to Magisk at the same time I was switching ROMs, so I did a complete wipe and flash. You could do a dirty flash, but I would reflash your /system and /boot withOUT wiping cache or dalvik or anything. I don't know what (if) your previous root installed anything into /system, in which case it probably won't like it.
So what I would do If I were you is boot into recovery, re-flash your ROM/Gapps (no need to wipe cache), reflash your kernel (optional), flash the magisk zip, reboot, install magisk manager from Store, and you're good to go!
Click to expand...
Click to collapse
Thanks! i'll try it later, hopefully i dont brick my phone. LoL.

I use PureNexus with Magisk, AndroidPay, snapchat or pokemon go works but not my banking app(ANZ GoMoney Wallet), I have yet to find a solution, give magisk a try and see if it works for you. The producure is basiclly wipe system in twrp - flash purenexus - flash magisk zip - boot and install magiskmanager from play store

P.Fan said:
but not my banking app(ANZ GoMoney Wallet), I have yet to find a solution
Click to expand...
Click to collapse
Did you manage to get this working?
I'm using latest Magisk, and I always fail/error when it's performing the encryption for the wallet functionality.

mouth said:
Did you manage to get this working?
I'm using latest Magisk, and I always fail/error when it's performing the encryption for the wallet functionality.
Click to expand...
Click to collapse
No, PureNexus will not bypass the root check in the banking app despite passing safetynet for some reason. However, since then I have switched back to official stock ROM with magisk installed and haven't had a problem so far.

I use a star Finanz banking app that fails with Magisk.
The solution I found is to uninstall Magisk manager when I need to use the push TAN app and then reinstall it(Magisk manager) from my internal storage when I'm done. Seems to work for me now.

Dumb question, but you guys are using Magisk Hide for the app bank's app right? Your device is showing up as certified in the play store settings correct?

OhioYJ said:
Dumb question, but you guys are using Magisk Hide for the app bank's app right? Your device is showing up as certified in the play store settings correct?
Click to expand...
Click to collapse
Yeah, it used to not work at all. Now on latest Magisk it hides it successfully 50% of the time.
Found it easier to just uninstall the manager and reload it after. Since I only need the push TAN for online transfers.
Android pay works without a problem for me.

Using Supersu with LineageOS (Q).

Hi.
I have a question regarding how supersu installs on LineageOS.
I recently flashed LineageOS ROM over OnePlusOne cyanogenMod.
With the help from members in Q&A forum I successfully flashed supersu.
Upon completion, the settings in Developer Option showed 2 options for Root access.
1. ADB-only 2. Disable (see screenshot). I selected adb-only. Installed root checker and Titanium backup and was able grant root permission and execute Titanium bkup.
I was under the impression, you must choose (adb and apps) for root access, but as you see on my screenshot that option is not available.
(Q): How did I get supersu root access for apps using adb-only?
Installation Performed:
After several failed attempts trying to install supersu, I went to my original TWRP backup and did a full restore of LOS and GAAP.
Copied supersu zip from PC to Phone internal storage, selected, Install and rebooted. (did not wipe).
When finish, selected adb-only (as I stated above) and supersu worked. (see screenshot).
I am aware there is a LOS extras patch available to install, having Root access (adb and apps) option, but I cannot understand why it worked with the option I choose.
Does LOS have an internally supersu root (all) flag built in their release that can be triggered by adb-only? I tried selecting adb-only and failed having Sultans LOS zip installed, before doing a full TWRP restore of my files as a last option.
The LOS build I used was 14.1-201707703-Nightly bacon.
The Supersu I installed was Update-Supersu-v2.82-20170528234214.
Thanks.
TC.

@tomx2x
I prefere LOS's addonsu.

Out of interest, why SuperSU? Have you given Magisk a try?

vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
Is there any advantage besides that safetynet thing?

kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Modules

vikashhero said:
Modules
Click to expand...
Click to collapse
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.

vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Some people prefer Coca-Cola, others prefer Pepsi. The nice thing is that there are choices, and we can use whatever solution we like (I use SuperSU, myself, as I've not encountered a situation where I'd need Magisk).

My preference is beer. But in AEX they only served that brown lemonades.
tomx2x said:
(Q): How did I get supersu root access for apps using adb-only?
Click to expand...
Click to collapse
Did you try to run SuperSU without adb-only? I think, these buttons are only beer bottle openers for addonsu. Thy have no effect on your lemonades. AEX has no built-in opener at all.

kurtn said:
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.
Click to expand...
Click to collapse
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.

vikashhero said:
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.
Click to expand...
Click to collapse
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su

kurtn said:
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su
Click to expand...
Click to collapse
phh's one was good, yeah
The LOS one works fine too, as you'd imagine. That's the one I'm currently using, but if I need to use Android Pay (on some weekends I do make use of it) then I'll switch over to Magisk.