For some reason the phone loses Magisk after every reboot. I'm guessing there's a flashable zip somewhere to fix this or something?
Choose an username... said:
For some reason the phone loses Magisk after every reboot. I'm guessing there's a flashable zip somewhere to fix this or something?
Click to expand...
Click to collapse
which magisk version you flash ?
Blueman1990 said:
which magisk version you flash ?
Click to expand...
Click to collapse
16. It's not my phone, it's a friend's, so i haven't really read much here
Choose an username... said:
16. It's not my phone, it's a friend's, so i haven't really read much here
Click to expand...
Click to collapse
Any idea what ROM they're running?
You could try uninstalling magisk, then flash a clean kernel (either from a backup made before rooting or if your friend is running a custom ROM, they could dirty flash the custom ROM. If rooting on stock, flash a clean stock Motorola kernel before reflashing ElementalX or vegito), then re-flash magisk.
If there were other root managers installed before magisk, this should remove any traces of those root managers on the kernel - even after uninstalling the previous root manager, which can interfere with magisk. At any rate, that should also provide a clean slate to root on again.
echo92 said:
Any idea what ROM they're running?
You could try uninstalling magisk, then flash a clean kernel (either from a backup made before rooting or if your friend is running a custom ROM, they could dirty flash the custom ROM. If rooting on stock, flash a clean stock Motorola kernel before reflashing ElementalX or vegito), then re-flash magisk.
If there were other root managers installed before magisk, this should remove any traces of those root managers on the kernel - even after uninstalling the previous root manager, which can interfere with magisk. At any rate, that should also provide a clean slate to root on again.
Click to expand...
Click to collapse
Yes, I installed AICP on it first but for some weird reason the GPU usage would go up to about 80 or 90% on idle and the UI would get laggy as hell. I switched over to Pixel Experience now and it's fine. On AICP i also tried Waver kernel and it didn't retain magisk if that's what you are saying.
I would suggest to flash stock firmware. All those alpha Oreo builds still have lots of bugs, especially with memory management, camera stuff and they tend to produce laggy interfaces. With stock firmware you're on the safe side, everything works perfect and you'll even have better battery backup and overall better performance.
You can root it with Magisk (ElementalX kernel) aswell.
Choose an username... said:
Yes, I installed AICP on it first but for some weird reason the GPU usage would go up to about 80 or 90% on idle and the UI would get laggy as hell. I switched over to Pixel Experience now and it's fine. On AICP i also tried Waver kernel and it didn't retain magisk if that's what you are saying.
Click to expand...
Click to collapse
Honestly, nothing like this has happened on my device! have you given try to RR or lineage 15.1? Or any nougat custom ROMs? like RR or Invicta? Are you flashing any modules along with Magisk??
Related
Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.
Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.
Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?
Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.
Hi,
To be honest I am a bit bored of the standard ROM, having come from other phones where I root and have a play. I did try to root once and did so successfully and installed a new ROM (Was CM13 or 14 I think) but some of my work applications (email, calendar etc) and some games (e.g. Pokemon Go) require you to not have root.
I found some website links to use hideSU and Magisk but I couldnt get it to work when toggling, and was stuck with it showing as rooted. This was around 6 months ago though
When I try to do a search now, most of the links relate back to the old Magisk process which didnt work for me last time and is still 6-12 month old links. Does anyone have an easier, step by step process of how to root, flash ROM and then hide root?
I am familiar with flashing, so no issue explaining that - I just need to know what steps in between/after flashing I need to do to hide root.
Thanks
Install any rom with Magisk. Then go to Magisk Manager app, enable Magisk hide under its settings, and then install your applications normally. It's so simple. Don't forget to check root status in Magisk app. Sometimes SafetyNet shows as not passing, but there are fixes to make it work.
I personally recommend ResurrectionRemix and AOSP Extended ROMs, but there are lot of roms with Magisk now.
Ah, I have to install ROM through Magisk? I did mine through TWRP I think and then did Magisk, this might be where I went wrong. Will try again, thanks
3sixty said:
Ah, I have to install ROM through Magisk? I did mine through TWRP I think and then did Magisk, this might be where I went wrong. Will try again, thanks
Click to expand...
Click to collapse
Nope. Install ROM that includes Magisk (and gapps) through TWRP, then use Magisk Manager app that is included in ROM. Sorry for missing that part. Quote me next time so I get the notification.
fabrquila said:
Nope. Install ROM that includes Magisk (and gapps) through TWRP, then use Magisk Manager app that is included in ROM. Sorry for missing that part. Quote me next time so I get the notification.
Click to expand...
Click to collapse
Ah thanks, so need specific ROM that includes Magisk.
If i want to say install RR Remix, anyway i can flash the ROM and then Magisk separately?
Hi 3sixty , How did you succeed in hiding your app through magisk ? any positive methods.. I will be happy to know as I'm trying to solve a similar problem with my samsung galaxy note 5.
Flash any ROM, flash magisk, update magisk manager and enable magisk hide
Sent from my ONE A2005 using Tapatalk
Well, I never used Magisk, but i used to hide root by installing Root Cloak App from Xposed. So you have to flash Xposed framework as well. It used to work with most of the apps with android 4-6, except for 1-2 banking apps.
For Custom Roms, I recommend Ressurection Remix over all ROMs after MIUI ROMs. MIUI ROMs are available for other handsets as well and not just Xiaomi.
Hi all,
maybe it is a dumb question or I am doing something wrong, but now I am facing a problem with losing root on Lineage os, when I use custom kernel. I use Magisk and flash everything through twrp recovery.
What I tried:
I completely wiped telephone, for to be 100% sure it is clean, so I went back to stock rom, lock bootloader.... and so on. After this I unlocked...root....
And even when I have only custom rom, without any additional apps only clean LOS, Magisk and custom kernel with developer app, for example Boeffla kernel and his app or from Flar2 elementalx kernel and his app and change something in their app, lets say frequency It automatically breaks root on next restart and after this root is not avaliable everytime when I boot up. I tried reflash magisk but without success. (And I am not using kernel for OOS on LOS, everytime the kernel is built for LOS)
On freedom OS 1.8 I dont face to this issue, for now I am on Freedom OS with Boeffla kernel and his app without problem. But really I am familiar more with LOS than OOS due to more clear system than OOS. (But this is my opinion :-])
Always I am using the newest versions - LOS - 02/10, Magisk 14.0....
And next note - I used LOS on OP3T with same settings and custom kernels without any issues only now on OP5 I have this problems.
Can you please tell what is wrong or if you have the same problem? Thank you for a help.
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Flapjack said:
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Click to expand...
Click to collapse
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Choose an username... said:
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Click to expand...
Click to collapse
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
So install just boot.img from twrp and flash magisk.
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
Either do what WesTD says or find a SuperSU uninstaller zip (i think there's one around), or wipe system and reflash the ROM
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Click to expand...
Click to collapse
Good stuff. Thank you!
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
AnonVendetta said:
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
Click to expand...
Click to collapse
Could you say which problems you had with Magisk?
If you had f2fs then of course. But usually Magisk works as it should and has the module system which is very useful too.
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
What firmware or ROM are you currently running, and what version of magisk are you using?
kwebber321 said:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
Click to expand...
Click to collapse
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
ALPH000 said:
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
Click to expand...
Click to collapse
Is there a custom kernel known to be compatible with the stock Pie ROM?
harryspar said:
Is there a custom kernel known to be compatible with the stock Pie ROM?
Click to expand...
Click to collapse
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
echo92 said:
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
Click to expand...
Click to collapse
For Nougat, stock kernel is not rootable.
You have to replace it with elementalx kernel and then flash magisk.
However, when talking about Oreo stock firmware,
Situation gets inverted.
When flashed magisk with ElementalX 3.0.1, phone will not boot up.
And, stock kernel can be easily rooted by simply flashing magisk.
So, there is no need of ElemenralX kernel for rooting Oreo stock ROM unless you need it.
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
harryspar said:
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
Click to expand...
Click to collapse
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
echo92 said:
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
Click to expand...
Click to collapse
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
harryspar said:
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
Click to expand...
Click to collapse
I hope you get xposed working on Oreo - if you do get magisk functioning, maybe this xposed plugin could work? https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Else there's edxposed https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768 though I have no idea if xposed functions on stock Oreo.