I still receive messages, when I clear data and cache I can log in, but as soon as I log in it closes to my previous screen.. Tried a reinstall aswell, am on magisk root, stock oos 4.5.4 Ex 1.0.3 kernel
Not sure what to tell you, but I have stock 4.5.4 rooted with Magisk, and on stock kernel and I don't have this problem.
geoff5093 said:
Not sure what to tell you, but I have stock 4.5.4 rooted with Magisk, and on stock kernel and I don't have this problem.
Click to expand...
Click to collapse
It was related to the kernel for me, had to flash previous version to get it working again
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
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??
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
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.