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.
Related
Hey guys, i just bought the phone and flashed zips immediately But have a question as i've never encrypted my phones till now(it's forced). So i'm on stock kernel and latest 4.5.14 Nolimits rom. Now I want to install xposed, bluspark kernel and remove the encryption from my device(i read something like a dm-verity disabler). Which order and method I should chose to flash those ? I saw something about decyrpted device in the first page of the rom's aroma installer and an option for the xposed but not sure and i don't want any bootloops
Thanks!
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??
I want to have a Samsung Stock based ROM and a LOS/AOSP ROM on my phone and switch between them, but I can't get it working. I always end up on a bootloop at the S7 Edge logo.
My bootloader and modem is updated to latest version. I wanted to install Hyper ROM and LOS 16.
So I first installed Hyper ROM, downloaded the latest version of Dual Boot Patcher, open it, allow root access, go to ROMs in the app, select my System to set the kernel. Then I go to patcher section, add the LOS-zip, gapps-zip and magisk-zip (does magisk even work with this? have tried without but also no luck) and patch them as secondary. I reboot into recovery, flash patched LOS and gapps, reboot aaaand... I'm stuck at a bootloop.
This seems to happen no matter what I try, how I switch them around, also if I patch the Hyper ROM zip as primary first. Nothing seems to help. Am I doing something wrong here?
So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.
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.