Adaway reboot bootloop - Xiaomi Redmi Note 5 Pro Questions & Answers

I installed adaway after rooting. Configured hosts file and rebooted. The system went into bootloop. How should I install it? Any additional steps? I am using miui 11 with agni kernel.

ashbk37 said:
I installed adaway after rooting. Configured hosts file and rebooted. The system went into bootloop. How should I install it? Any additional steps? I am using miui 11 with agni kernel.
Click to expand...
Click to collapse
Did you acquire root correctly? How did you root? Did you install magisk manager? Was the device working perfectly after rooting? Did you flash ARB 4?

Prathamesh 27 said:
Did you acquire root correctly? How did you root? Did you install magisk manager? Was the device working perfectly after rooting? Did you flash ARB 4?
Click to expand...
Click to collapse
Yep root is alright. Everything works perfectly. I rooted by flashong magisk. Also installed magisk manager. Didnt flash ARB 4.

ashbk37 said:
Yep root is alright. Everything works perfectly. I rooted by flashong magisk. Also installed magisk manager. Didnt flash ARB 4.
Click to expand...
Click to collapse
Did you check on Magisk manager settings>systemless hosts?

SubwayChamp said:
Did you check on Magisk manager settings>systemless hosts?
Click to expand...
Click to collapse
Yeah. I enabled systemless hosts before installing adaway. I flashed everything again. I'll try Adaway once more and see if it works properly this time. Is there anything I should configure in the Adaway settings before I proceed with it?
Also I would like to add Energized hosts to adaway amd I clearly dont know how that works. It would be helpful someone gave some steps for that.

ashbk37 said:
Yeah. I enabled systemless hosts before installing adaway. I flashed everything again. I'll try Adaway once more and see if it works properly this time. Is there anything I should configure in the Adaway settings before I proceed with it?
Also I would like to add Energized hosts to adaway amd I clearly dont know how that works. It would be helpful someone gave some steps for that.
Click to expand...
Click to collapse
First two silly question; it is included in some custom ROMs. Are you sure that you didn't install it over other version?
And, the systemless hosts have to be activated then device have to be rebooted for first time and then update hosts on AdAway and then reboot again.
The better is to start for a clean install, tap on the Adaway icon and go to settings of the app, clear cache and then clear data and finally uninstall it.
It may be the version, I use the 4.2.6 and never did give me errors.
Regarding include Energized hosts you can add it navigating with a browser to Energized site, you will find different extensions (Spark, Blu, Ultimate, etc; according the target you want, I should use the txt format then open AdAway and upper to the left you will find the option to add a source inside "Hosts sources" then tap on + , paste the txt copied before, check the link that https is not duplicated or something like this, after that apply it so it can update it.

SubwayChamp said:
First two silly question; it is included in some custom ROMs. Are you sure that you didn't install it over other version?
And, the systemless hosts have to be activated then device have to be rebooted for first time and then update hosts on AdAway and then reboot again.
The better is to start for a clean install, tap on the Adaway icon and go to settings of the app, clear cache and then clear data and finally uninstall it.
It may be the version, I use the 4.2.6 and never did give me errors.
Regarding include Energized hosts you can add it navigating with a browser to Energized site, you will find different extensions (Spark, Blu, Ultimate, etc; according the target you want, I should use the txt format then open AdAway and upper to the left you will find the option to add a source inside "Hosts sources" then tap on + , paste the txt copied before, check the link that https is not duplicated or something like this, after that apply it so it can update it.
Click to expand...
Click to collapse
Okay. Thanks for that. And I've flashed stock miui rom. So its not included. I'll do it again following your advice. ?

Related

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?

Uninstall Root on Cm13?

I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Isn't root enabled via settings? Maybe turn it off in the settings or reflash and don't enable root?
I tried that but the system is still seen as rooted
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Click to expand...
Click to collapse
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
mrrocketdog said:
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
Click to expand...
Click to collapse
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
hmmmmm well just for something to try , how about reflasing superSU then see if it will open. idk. just something to try
"err on the side of kindness"
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install SUHide v0.54
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will hide your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
-Test Pokemon Go. You should have no problems!
6. Need a GPS spoofing app? I use Fake GPS (well worth the $2.99). It allows you to pin favorite locations (I bounce quickly between spots where I can hit multiple lured PokeStops at once), and has settings to randomly move within a radius at whatever intervals and speed. They also have a GPS Joystick and Routes app that I have not yet tested since they don't offer a trial or free version. I'll update on that if they do offer a trial.
I have fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
**UPDATE 10/7/2016 ** - edited to use updated suhide v0.54
FuNKSioN said:
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install suhide v0.53
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will spoof your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
Test Pokemon Go. You should have no problems!
***UPDATE***
I have just fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
Click to expand...
Click to collapse
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Shack70 said:
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Click to expand...
Click to collapse
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
FuNKSioN said:
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
Click to expand...
Click to collapse
Wow! Thanks I appreciate it.
Shack70 said:
Wow! Thanks I appreciate it.
Click to expand...
Click to collapse
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
FuNKSioN said:
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
Click to expand...
Click to collapse
Thanks for your help. I updated yo the newest nightly build, did a full factory reset and deleted the 2 su files. After rebooting i re-downloaded the newest version of Pokémon and installed it. Game is working fine.
I don't use root much so I'll see how it goes without root and if I need root i can put the su files back(I made copies and put them in Dropbox) or try superSU/hideSU.
I know the s3 is slow but I'm putting off an upgrade until i have to upgrade. Until i upgrade I won't really realize how slow my phone is
Sent from my SGH-T999 using XDA-Developers mobile app
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
FuNKSioN said:
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
Click to expand...
Click to collapse
Yeah i get this is a temporary solution. Thanks for all your help. You've really gone above and beyond
Sent from my SGH-T999 using XDA-Developers mobile app
no problem man!
Thanks!
FuNKSioN said:
no problem man!
Click to expand...
Click to collapse
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
romehu2 said:
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
Click to expand...
Click to collapse
Glad to help. I was in the same boat: so much info in all directions and none of it seemed to work. I keep up with ChainFire's G+ account. He had a few posts linked directly back to XDA. Those few posts had everything needed. I just put it in simple steps. All thanks to him really
Sigh
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
romehu2 said:
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
Click to expand...
Click to collapse
reflashed CM13 + GApps, used ADB to rename system/xbin/su & system/bin/su to /su-off, and SafetyNet is happy (and thus, so is PoGo). but now, of course, phone isn't rooted.
---------- Post added at 05:18 AM ---------- Previous post was at 05:05 AM ----------
on the plus side, CM13 comes with File Manager which allowed me, without root, to install the v39.1 PoGo apk that I downloaded last week.
Sit back and wait for an SU update... It's only been a hot minute.

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.

BusyBox installed but not interfering with OTA Update: is it possible?

I have a device rooted wit Magisk as in the thread [GUIDE] Install Magisk with proper support for OTA updates (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952). All is working fine and just installed 2nd November update withou any hassle.
Now I need BusyBox, but I 'm afraid it could interfere with /system, because I see it installs in /system/bin, and so should stop OTA updating using Magisk de-activated and then re-activated.
Has somebody an answer for this issue, may it works the same?
... or another way of installing BusyBox over/with Magisk and let all work flawlessly?
Thanks guys
There is a Magisk module for Busybox, just install it, reboot and you should be fine.
BubuXP said:
There is a Magisk module for Busybox, just install it, reboot and you should be fine.
Click to expand...
Click to collapse
Thanks a lot, I didn't think at all at Magisk Modules...already installed, it works and it put Busybox in /system/xbin/busybox, I hope it will be fine even if it's in /system...I have to wait next OTA and check the behaviour.
Surely it deserve to give it a shot
Thanks for the suggestion, always welcome from you
Grazie e ciao
Magisk works just like this, changing the /system partition without really touching it. That's because if you want to do OTA updates you need to do everything that involves /system from Magisk.
BubuXP said:
Magisk works just like this, changing the /system partition without really touching it. That's because if you want to do OTA updates you need to do everything that involves /system from Magisk.
Click to expand...
Click to collapse
Got it! At the end I'm starting to understand something more about this crazy Android partitions , also thanks to your input obviously!
Now I'm missing just one thing in my device: to have TWRP installed and working without problems with Magisk.
I think that if I un-install Magisk, then install TWRP, and then re-install Magisk again, it could work...
Maybe better to install Magisk flashing from TWRP ...
I'm not really sure, what do you think about this issue?
All the best, ciao
Hi,
I've installed Busybox magisk module but it breaks my mobile data. If it's disabled or uninstalled than data is back connected.
Anyone experienced the same issue?
Kind regards,
Germans.
Create your own xbin folder, download busybox by stephen, wait for app to collect sytem configuration then choose xbin folder and install, before ota, you must uninstall busybox then reboot, then delete xbin folder. The other method is to install straight to sbin, stephens busybox will auto install to sbin on every reboot, because sbin folder always goes back to original on rebooting, so basically you will just need to untick the toggle to stop auto install.
boe323 said:
Create your own xbin folder, download busybox by stephen, wait for app to collect sytem configuration then choose xbin folder and install, before ota, you must uninstall busybox then reboot, then delete xbin folder.
Click to expand...
Click to collapse
The only problem with this solution is banking apps root detection.
gkornaks said:
The only problem with this solution is banking apps root detection.
Click to expand...
Click to collapse
My halifax still works through magisk, honestly it doesnt affect magisk hide, i only mentioned doing it this way because the busybox magisk module kills the phone when you disable it, because the symlinks are still there, you cant log back into the phone.
Thank you! Will try later. BTW, my busybox module is disabled and I could login without any problem.
gkornaks said:
Thank you! Will try later. BTW, my busybox module is disabled and I could login without any problem.
Click to expand...
Click to collapse
Oh, ok it could of been a different module then, i just assumed it would be that one, sorry for that.
Is this really a problem I have busybox installed so it will interfere with the next update?
And if it will, just uninstalling it solve the problem?
Medo22 said:
Is this really a problem I have busybox installed so it will interfere with the next update?
And if it will, just uninstalling it solve the problem?
Click to expand...
Click to collapse
As long as it removes all the symlinks along with the busybox file.
boe323 said:
As long as it removes all the symlinks along with the busybox file.
Click to expand...
Click to collapse
How can I make sure of that?
Medo22 said:
How can I make sure of that?
Click to expand...
Click to collapse
I dont know every single file name but you can check against magisks own busybox library in sbin,magisk,busybox.Check through your bin folder after you uninstall busybox. Dont go deleting files though, thats why i make my own xbin. Id imagine if magisks busybox module in downloads is systemless theres nothing to worry about.

Oxygen Updater, OOS 10.0.11, Rooted

Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
davekaye said:
Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
Click to expand...
Click to collapse
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
jsgraphicart said:
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
Click to expand...
Click to collapse
This guide works dude
manan001 said:
This guide works dude
Click to expand...
Click to collapse
Yeah, I just did it myself a little earlier. Easy and no issues
When I follow the steps at
When an OTA is available, first go to (Magisk Manager → Uninstall → Restore Images).
Click to expand...
Click to collapse
It says "Stock backup does not exist!" Is there a way I can create stock backups?
adobrakic said:
When I follow the steps at
It says "Stock backup does not exist!" Is there a way I can create stock backups?
Click to expand...
Click to collapse
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Stock backup does not exist
jsgraphicart said:
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Click to expand...
Click to collapse
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
davekaye said:
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
Click to expand...
Click to collapse
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Upgrade rooted phone with OTA
JF-GINO said:
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Click to expand...
Click to collapse
I downloaded the new OTA version (I think from the Updater app - if I remember it allowed you to download the OTA) to the root of my phone and then just followed the directions from the first reply to my post. I had the latest version of Magisk (Uninstaller, the app, and the Manager) installed in it's own folder in internal memory. After I got the message, just proceeded as if nothing was wrong and in the end, the upgrade worked fine. I didn't document every step, but the instructions worked.
https://topjohnwu.github.io/Magisk/ota.html
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Does it pass SafetyNet check?
JF-GINO said:
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Click to expand...
Click to collapse
Yep, safety net check pass.

Categories

Resources