Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.
echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.
Related
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,
My system was working fine with Magisk v12, I saw there was a big new update, I was interested and updated.
But using the latest Magisk Manager, it says root is not detected.
It's not a big problem, I will restore back to v12 for now, but did anyone else get it working?
Thanks
Asus zenfone 2 flash update manual Magisk 13.1 crash recovery recovery then AD
Same here with Xperia XZ. With v13.1 Root is not detected. v12 is working fine.
Have tried to reinstall it by completely removing and flashing from TWRP, but still no luck.
13.1 and 13.2 working on 7.1 with repacked stock kernel with drmfix fix. It will also work with newest genesis kernel
I upgraded Magisk 12 to 13 beta, then 13.1 and 13.2 without problems.
Even SafetyNet Check passes.
I'm using genesis-nodrm kernel.
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
qvmuhuuxz said:
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
Click to expand...
Click to collapse
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
realtuxen said:
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
Click to expand...
Click to collapse
Ok I'll try that.
I believe I flashed v13.2 straight over v12.
But when downgrading back to 12, I did flash the uninstaller first.
I'll try uninstalling and then updating
- Still no luck, it didn't work.
I tried updating Magisk 12 -> 13.1 thru the manager, and it would download the zip then do nothing. I found the zip in the Magisk directory, and installed it like it was a module, thru the manager, and it appeared to work. I got the new Magisk Manager (5.0.4) and it says I'm on Magisk 13.1 but that Magisk is not installed, and there is no root.
Following the installation instructions, I rebooted a few times, no change. So I flashed Magisk uninstaller, cleared cache/davlik, and rebooted. Uninstalled Magsick Manager. Rebooted. Booted to TWRP and flashed Magisk-13.1.zip. Rebooted twice. Same issues; Manager 5.0.4 says I'm on Magisk 13.1 but that it's not installed, no root.
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
voilsb said:
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
Click to expand...
Click to collapse
I didn't have to reboot after flashing magisk uninstaller, I just flashed v12 straight after.
And I just uninstalled the new magisk manager then the old one right away, I think?
Magisk manager 13.1 not working for me either tried installing thru app but it does not work
might be related to this https://github.com/topjohnwu/Magisk/issues/265
Also it might be related to this - https://github.com/topjohnwu/Magisk/issues/166#issuecomment-298765812
"Use rootkernel tool from tobias.waldvogel to fix drm instead of PoC TA fix. It seems to be incompatible to Magisk while rootkernel tool patched images work"
I swapped over to Genesis kernel (1.05, the current latest) to try and see if it would help my device pass safety net, since for some reason it is not passing anymore (I tried lots to fix it, flashing etc)
As I posted directly above, it looks like Magisk v13 doesn't like ta_poc, so I used the drmfix version, and Magisk v13.3 works great, and once again my device passes safety net
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix
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.