My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts). I already flashed Xposed, and it seems work fine, Root Checker also shows I have root access, so I think I got root right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!
matif525 said:
My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts).
I already flashed Xposed, and it seems work fine, Root Check also shows I have permission, so I think I got ROOT right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!
Click to expand...
Click to collapse
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here
donkeykong1 said:
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here
Click to expand...
Click to collapse
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?
matif525 said:
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?
Click to expand...
Click to collapse
You can use the normal adaway, not the systemless one. Find it in xposed
donkeykong1 said:
You can use the normal adaway, not the systemless one. Find it in xposed
Click to expand...
Click to collapse
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?
matif525 said:
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?
Click to expand...
Click to collapse
I just remembered. You are on stock kernel, right? Because stock kernel has system write protection and you can't use AdAway. You can flash a custom kernel with system write protection disabled and you should be fine
Related
Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.
crazykas said:
Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.
Click to expand...
Click to collapse
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.
luigi311 said:
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.
Click to expand...
Click to collapse
RUU in this thread http://forum.xda-developers.com/sprint-htc-one/general/sprint-htc-one-android-5-0-coming-soon-t3001541.
Thanks i'll check that out
Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.
Robert542 said:
Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.
Click to expand...
Click to collapse
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
This method seems to work just fine for me. After installing supersu in TWRP then opened supersu selected TWRP and it downloaded the latest binaries and flashed in TWRP and worked fine after reboot.
I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).
coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
retiredtrebor said:
I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).
Click to expand...
Click to collapse
Write protection needs to be disabled.
Robert542 said:
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Write protection needs to be disabled.
Click to expand...
Click to collapse
And how does one go about disabling write protection?
retiredtrebor said:
And how does one go about disabling write protection?
Click to expand...
Click to collapse
From my understanding, that has to be done by a ROM and/or kernel developer.
Hey all,
I have a HTC one M7, i had to recently send it off for repair due to battery and camera issues. It has now returned fixed... but updated.
It has S-ON and the latest hboot (1.66???) and from what i've read, is not possible to get S-off at this time unless paying for a service online.
I have rooted it using DEVunlock, flashed a custom recovery and ROM but im finding it soo very hard to do anything with 'root access' for example, game killer need root access and when granted, says "root privelege is needed" although superSU has granted it access, Amplify a battery app needs root and cannot obtain it even it has been granted and Xposed installer cannot install without manual recover (which seems to goto recovery and do nothing...)
From what i can understand, i do have root i think? but why can't i install any apps that require root? is it due to it being S-ON?
what can i do? really not sure what to search for and whats its called
bump
stevey88 said:
Hey all,
I have a HTC one M7, i had to recently send it off for repair due to battery and camera issues. It has now returned fixed... but updated.
It has S-ON and the latest hboot (1.66???) and from what i've read, is not possible to get S-off at this time unless paying for a service online.
I have rooted it using DEVunlock, flashed a custom recovery and ROM but im finding it soo very hard to do anything with 'root access' for example, game killer need root access and when granted, says "root privelege is needed" although superSU has granted it access, Amplify a battery app needs root and cannot obtain it even it has been granted and Xposed installer cannot install without manual recover (which seems to goto recovery and do nothing...)
From what i can understand, i do have root i think? but why can't i install any apps that require root? is it due to it being S-ON?
what can i do? really not sure what to search for and whats its called
Click to expand...
Click to collapse
Download Root Checker from Play Store to check to see if you are properly rooted. If not, then re-install your custom recovery (TWRP includes root). What I generally do is install SuperSU right after I install TWRP.
majmoz said:
Download Root Checker from Play Store to check to see if you are properly rooted. If not, then re-install your custom recovery (TWRP includes root). What I generally do is install SuperSU right after I install TWRP.
Click to expand...
Click to collapse
okay, ive downloaded it and its confirming that i have root access, i have a feeling it could be something to do with s-on...
stevey88 said:
okay, ive downloaded it and its confirming that i have root access, i have a feeling it could be something to do with s-on...
Click to expand...
Click to collapse
You can have root access and S-ON at the same time. So, it is not S-ON. Update SuperSU and see if it does not fix the issue. If not, you might want to install Busybox you can get if from the Play Store as well.
majmoz said:
You can have root access and S-ON at the same time. So, it is not S-ON. Update SuperSU and see if it does not fix the issue. If not, you might want to install Busybox you can get if from the Play Store as well.
Click to expand...
Click to collapse
Thank you for your replys!, the only reason i mention about S-ON is because ive been through this trouble before, i just cant remember what i did to fix it, i think it was due to it being a HTC my friend said, hence why i have a feeling it could be due to S-ON locking me out of certain parts of the phone.
I think i have the latest SuperSU v2.46, i installed busybox which also made no difference, still dont have access to lots of stuff...
stevey88 said:
Thank you for your replys!, the only reason i mention about S-ON is because ive been through this trouble before, i just cant remember what i did to fix it, i think it was due to it being a HTC my friend said, hence why i have a feeling it could be due to S-ON locking me out of certain parts of the phone.
I think i have the latest SuperSU v2.46, i installed busybox which also made no difference, still dont have access to lots of stuff...
Click to expand...
Click to collapse
If you have SuperSU installed and you can open it from the app drawer and the same with BusyBox then you have root. It might be the programs you are trying to run are not compatible with your phone or OS version. If that is the case then if you are S-ON or S-OFF it will not make a difference.
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.
Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.
I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
DripleX said:
I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
Click to expand...
Click to collapse
Better option for you on that situation is to use a dns proxy for ad filtering
something like this app
https://f-droid.org/en/packages/org.jak_linux.dns66/
Yes I use a app like this, but the problem is, that sometimes it takes up to 1 - 2 min till it is connected to the DNS Server.
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
vofferz said:
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
Click to expand...
Click to collapse
Yes, I tried this, but as I read in some other threads, this will only work with newest Magisk.
But then I have to recompile the kernal for myself.
@DripleX, If you like to check if magisk is causing your (banking) apps to detect root, you may try this:
j4nn said:
Dear @albenex, although I would also assume it should be possible to resolve this with use of magiskhide and other settings, I've uploaded not-pre-rooted kernels for the latest fw version into my experimental folder here.
So you can clean up all traces of magisk (factory reset may be needed to be sure) and use a boot-*-47.2.A.10.45-hideunlock.img kernel to test it. Also be sure to run unmodified stock fw.
Click to expand...
Click to collapse
These kernels are not pre-rooted with magisk but include the patch to hide bootloader unlock.
That should provide you setup very close to still locked phone (if you have your TA-locked restored).
If the app is working with the *-hideunlock.img kernel, magisk would need to be made hidden to get it working with a rooted kernel.
If it did not work even with the not-prerooted kernel, it would mean BL unlock is detected some other way (most likely using your Android Attest key - assuming you have it "provisioned") as it seems to be the case with google pay.
A donation was received on Tue Apr 30 15:03:03 UTC 2019 - I assume it has been from you @DripleX.
If so, thank you.
Thank you @j4nn for your reply!
I will check this after my vacation.
And yes, I made the donation