I have a Moto E4 XT1768 running Resurrection ReMix. I wanted to return to stock to take advantage of the Moto actions. My nandroid must have been corrupt because restoring to my stock backup failed. I then attempted to reflash the original stock firmware with RSD Lite but that failed on spareschunk_3 (multiple times)...even when flashing the files individually with adb.
Finally, I was able to flash the newest firmware PERRY_NPQS26.69_64_8_cid50_XT1768_7.1.1_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip with RSD Lite. I was able to root it and install Magisk, but I could not install any modules. Also, I was unable to install Xposed. The security patch was from July 2018. Does the newest security patch break Magisk/Xposed? Since there were mods that I wanted installed but couldn't, I wound up reverting back to my Resurrection Remix backup...and that's where I am again.
Anyone have any idea why Magisk modules failed, and why Xposed woud not install?
P.S. I had even flashed the latest CR Droid from the telegram group, and it worked wonderfully (security patch July 2018)...but again, Magisk modules failed to install. Didn't really need them with that ROM, but what gives? On a side note, the in-call volume on CR Droid was so crazy high I had to go back to Resurrection Remix again. It was literally blowing my ears off. Editing the mixer_paths.xml did not work either.
mn1968 said:
I have a Moto E4 XT1768 running Resurrection ReMix. I wanted to return to stock to take advantage of the Moto actions. My nandroid must have been corrupt because restoring to my stock backup failed. I then attempted to reflash the original stock firmware with RSD Lite but that failed on spareschunk_3 (multiple times)...even when flashing the files individually with adb.
Finally, I was able to flash the newest firmware PERRY_NPQS26.69_64_8_cid50_XT1768_7.1.1_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip with RSD Lite. I was able to root it and install Magisk, but I could not install any modules. Also, I was unable to install Xposed. The security patch was from July 2018. Does the newest security patch break Magisk/Xposed? Since there were mods that I wanted installed but couldn't, I wound up reverting back to my Resurrection Remix backup...and that's where I am again.
Anyone have any idea why Magisk modules failed, and why Xposed woud not install?
P.S. I had even flashed the latest CR Droid from the telegram group, and it worked wonderfully (security patch July 2018)...but again, Magisk modules failed to install. Didn't really need them with that ROM, but what gives? On a side note, the in-call volume on CR Droid was so crazy high I had to go back to Resurrection Remix again. It was literally blowing my ears off. Editing the mixer_paths.xml did not work either.
Click to expand...
Click to collapse
On stock, most Moto devices including this one have the f2fs loopback bug. You'll need to look for the f2fs workaround module. It's a magisk module but it needs to be flashed in TWRP.
That will allow all of your magisk modules to install properly.
Here I found it for you
https://forum.xda-developers.com/ap...icial-version-including-t3577875/post71554247
After flashing ROMs and moving around to different systems, if you want to restore one of your old stock backups, you'll probably have to format data. Not just wipe, Format.
I will look into it
TheLastAlphaUK said:
Just use sp flash tool ull never have this problem.... Fyi soon as you unlock the bootloader and flash a custom recovery just back up all partitione of the stock firmware so you can just restore no matter what happens
Click to expand...
Click to collapse
His device is Perry not Woods. So Qualcomm not mediatek
I tried again going back to stock. Used RSD lite to flash. Installed TWRP and rooted fine with Magisk. Installed the f2fs loopback patch. Seemed to work. Installed ios beta icons as a test and it installed fine. Rebooted and both Magisk modules disappeared. Tried redoing the f2fs patch again but it never showed up in the modules section, and all other Magisk modules failed to install.
I restored my Resurrection Remix back up and will stay on that.
mn1968 said:
I tried again going back to stock. Used RSD lite to flash. Installed TWRP and rooted fine with Magisk. Installed the f2fs loopback patch. Seemed to work. Installed ios beta icons as a test and it installed fine. Rebooted and both Magisk modules disappeared. Tried redoing the f2fs patch again but it never showed up in the modules section, and all other Magisk modules failed to install.
I restored my Resurrection Remix back up and will stay on that.
Click to expand...
Click to collapse
I've seen some people have that issue on the Moto G6 but not the E4. Make sure you're not wiping cache at any point. If you installed the f2fs fix it should still be in your download folder just install it through TWRP not magisk manager.
madbat99 said:
If you installed the f2fs fix it should still be in your download folder just install it through TWRP not magisk manager.
Click to expand...
Click to collapse
Tried. Didn't work. No interest in trying anymore. Sticking with Resurrection Remix.
Thanks for the replies though.
mn1968 said:
Tried. Didn't work. No interest in trying anymore. Sticking with Resurrection Remix.
Thanks for the replies though.
Click to expand...
Click to collapse
Cool.
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.
Guys,
Anyone successful so far in setting up Magisk 17.1 on stock B35 A2017U + TWRP 3.2.1.0?
I tried following ways but everytime I flash the Magisk 17.1 using TWRP, it boot loops to recovery mode. I tried clearing Dalvik + cache everytime but in vain.
1. Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop.
2. Flash Super SU, Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop
I cannot use Super SU, blanket root due to bank & workplace apps security restrictions.
Any help/guidance will be is appreciated.
Cheers
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
marcdw said:
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
Click to expand...
Click to collapse
Thanks.
Thinking of trying with v16.7 first. If that works then great.
mandrax.prime said:
Thanks.
Thinking of trying with v16.7 first. If that works then great.
Click to expand...
Click to collapse
it does. i'm staying on 16.7
It would be nice to always have a working version of Magisk as Google updates their Safety Net. We have to update as they update.
I ran into problems today with Magisk 18.1 on the latest official LineageOS 15.1, nothing I did was able to get magisk to work (no icon, no error messages).
Has anyone else tried?
Magisk should work fine on LOS, I use it (Magisk) when I have to (i.e. when there is a particular use for it, like converting a systemless mod to a system-installed mod).
On B35, no go, phone will bootloop. Magisk should work fine on stock ROMs up to B15 N, maybe also with the B25 and B32 OTAs too. I'm not a ZTE stock ROM fan, I dont spend alot of time rooting stock, but from the few tests I did,those were my results.
If you have an exFAT SD card, installing Magisk on stock ROM may make your SD falsely show up as corrupt, only solution is to use the inferior/antiquated FAT32 filesystem.
Maybe one day I'll write my own open source root solution, just to show the Android community that Magisk isnt the only game in town for rooting modern ROMs on modern devices. I dont need to hide from SafetyNet, I dont need stupid systemless mods, I just need root that work reliably. I know this will fall on deaf ears, but Magisk is more trouble than it's worth, I'd recommend staying unrooted instead of using it. @topjohnwu is a genius and means well, I'm sure, but in the real world Magisk just isnt reliable enough.
I tried Magisk 17.3, 18.0, and 18.1 on Axon 7 B19 and B35- bootloop on every try
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.
Hi, I'm on LineageOS 14.1 Optimized by JDCTeam.
However I'm not able to install the latest Magisk.
Is it just not possible anymore because you need fastboot to install a patched boot.img?
I tried flashing through the regular way as a .zip file (just renaming the magisk apk into .zip) in TWRP 3.2.x.x. Also tried flashing the patched boot.img file from the rom through TWRP.
But whenever I flash it and reboot, everything force closes.
Any help on that?
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Strephon Alkhalikoi said:
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Click to expand...
Click to collapse
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
crysen said:
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
Click to expand...
Click to collapse
Check my S4 Unified Collection & Guides. You will find everything you need.