Coming from the latest paranoid android build; did a complete clean flash, including format data.
Flashed June Vendor
Flashed June (6/12) Pure Nexus and Beans Gapps.
Flashed June (6/5) Flash Kernel
Flashed Magisk (I started with V12 and app version 4.x.x and when that didn't work, I used the uninstaller and tried the beta V13 and app version 5.x.x.)
Neither attempt had root but Magisk showed it as installed. In the Magisk app, in the side drawer, the uppermost choice is missing where it shows "Properly rooted", MAGISKSU:8, and Safetynet Check button. There is, however, a safety net check on the default page which fails.
I later flashed the latest beta of SuperSU (after again running the uninstaller) and it's partially working, some apps show no root but apps like Titanium Backup show root and work fine.
Is anyone getting root with Magisk on June PN? Am I doing something wrong or flashing in the wrong order?
I would like system root with Magisk, are there other steps I need to take?
Will report the magisk/supersu bugs to their proper locations as well.
Thanks for any help.
Don't use the latest beta app 5 it for me had issues when I switched back to last stable magisk app (4.33) all was working again. I've flashed magisk 12 zip before and after kernel both with success. If root doesn't work after booting up first time go back to recover and flash magisk zip again.
flashed without flash kernel, just bean gapps and Supersu 2.82 SR1.... everything working fine here.
You should really flash the vendor after everything like the kernel to be safe but that isn't an option.
---------- Post added at 09:00 AM ---------- Previous post was at 08:58 AM ----------
Also, my rom comes with magisk prebuilt so for me it is rom with magisk then beans gapps then kernel then other mods then vendor.
Related
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.
So I installed Tez by Google, and it's saying that I can't use it because my phone doesn't meet their security requirements.
Here's what I have:
Nougat (PureNexus) I didn't flash a kernel, I'm using the boot image included in the ROM.
Here's what I did:
Full unroot from SuperSu. I was expecting this would fix the problem, but it didn't.
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel.
I'm guessing I can't do that because I'm on Nougat.
Any ideas?
Try using magisk and go hide root on magisk , select tez apps
Droidcore said:
Try using magisk and go hide root on magisk , select tez apps
Click to expand...
Click to collapse
No that's not how it works
---------- Post added at 11:12 ---------- Previous post was at 11:01 ----------
sohamssd said:
So I installed Tez by Google, and it's saying that I can't use it because my phone doesn't meet their security requirements.
Here's what I have:
Nougat (PureNexus) I didn't flash a custom kernel, I'm using the kernel image included in the ROM.
Here's what I did:
Full unroot from SuperSu. I was expecting this would fix the problem but it didn't.
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel.
I'm guessing I can't do that because I'm on Nougat.
Any ideas?
Click to expand...
Click to collapse
Full unroot from SuperSu. I was expecting this would fix the problem but it didn't. - most likely SuperSU did not restore your stock boot.img
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel. - absolute proof that SuperSU failed to restore stock boot.img
Basically flashing magisk root on top of SuperSU will brick so magisk detects this and errors out
I'm guessing I can't do that because I'm on Nougat. - no it's not because of this
Nougat (PureNexus) I didn't flash a custom kernel, I'm using the kernel image included in the ROM. - I corrected your sentence slightly, oneplus 2 doesn't report verity values to the userspace so the kernel patch for safetynet has no effect
Oneplus 2 doesn't even support verity
What I suggest
Try this app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Let me know the result
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
After the last magisk update all of my magisk modules disappeared. I tried to reinstall them in magisk but discovered that the loopback fix was also gone. I rebooted into recovery and reflashed the f2fs bug fix, rebooted and then all my modules were back. But they disappear again every time I reboot and I have to again boot into recovery and flash the bug fix to get them back. Ive updated magisk several times over without having this problem. It seems to be a bug in the latest update. Any ideas?
AMShiech said:
After the last magisk update all of my magisk modules disappeared. I tried to reinstall them in magisk but discovered that the loopback fix was also gone. I rebooted into recovery and reflashed the f2fs bug fix, rebooted and then all my modules were back. But they disappear again every time I reboot and I have to again boot into recovery and flash the bug fix to get them back. Ive updated magisk several times over without having this problem. It seems to be a bug in the latest update. Any ideas?
Click to expand...
Click to collapse
The Magisk module for that is old and won't work with newer versions of Magisk. You'll have to revert to an older version of Magisk. I think 14.x or 15.x is the latest one compatible with that fix. It also needs to be installed in TWRP recovery, rather than a direct install within that Magisk apk or it won't work.
Jason M. said:
The Magisk module for that is old and won't work with newer versions of Magisk. You'll have to revert to an older version of Magisk. I think 14.x or 15.x is the latest one compatible with that fix. It also needs to be installed in TWRP recovery, rather than a direct install within that Magisk apk or it won't work.
Click to expand...
Click to collapse
I've been using magisk v16 the whole time but this time I updated the apk as well as flashing the zip. Usually i just flash the new zip which never seems to be a different zip. I just lose root randomly if I ignore the update notification too long. But the zip never changes. It's always 16.00. Did you mean to use an older version of the apk?
AMShiech said:
I've been using magisk v16 the whole time but this time I updated the apk as well as flashing the zip. Usually i just flash the new zip which never seems to be a different zip. I just lose root randomly if I ignore the update notification too long. But the zip never changes. It's always 16.00. Did you mean to use an older version of the apk?
Click to expand...
Click to collapse
Go back and read the op of the f2fs loopback bug fix module, and the last couple of posts in the thread. A few people have said 16. 3 is the last version that works completely properly. the developer of the module then made a recent update that may fix the issue but you need to go back and read the thread to be sure.
---------- Post added at 11:32 PM ---------- Previous post was at 11:27 PM ----------
https://forum.xda-developers.com/ap...icial-version-including-t3577875/post77520587
hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
so any advice anout that problem?
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Screenshot https://i.imgur.com/6IcIvJx.jpg
slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro