So I'm currently running Lineage OS, but for some reason I can't play FGO while using Magisk. Even though the game works normally, and Magisk should support it on the Canary build now, it starts detecting Lineage OS when Magisk is activated, even when using Magisk Hide. So how would I go about switching back to Stock? The other thread with stock roms has dead Links.
Download the stock firmware and Flash it with fastboot use RSD Lite. Or one of the many posts on how to install Stock firmware on that model.
This is the site I've gotten firmware to update my E4 XT1768 - https://mirrors.lolinet.com/firmware/moto/perry/official/RETAIL/
Related
I tried all methods which are there on site but each time same and only problem is coming that is my phone is not getting rooted correctly I tried so many times but when I'll check with root checker it says it's not rooted but I successfully unlocked bootloader but I can't complely root it, can someone help me?
What device do you have and what ROM are you running?
If you're rooting on the stock Motorola ROM, do you have TWRP flashed/booted, then flashed ElementalX? Afterwards, what root managers are you using? You could try magisk 16 or 15.3. However, if you've previously used SuperSU or another root manager, you may have to re-flash the original stock kernel (then flash ElementalX then root) to remove any remainders of the old root managers, else they may interfere with magisk to the point of the root not being stable.
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
MsK96918 said:
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
Click to expand...
Click to collapse
What root manager are you using? The official Lineage OS (as of Jan 2017) does not come with a root manager, you must download and flash your own. You could either use the Lineage_SU_addon (you'd want the arm variant for 14.1) or magisk or SuperSU as a root manager.
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
MsK96918 said:
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
Click to expand...
Click to collapse
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
echo92 said:
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
Click to expand...
Click to collapse
Thank you bro i finally rooted my device correctly . It help alot thank you once again
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
vinayroffl said:
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
Click to expand...
Click to collapse
The stock Motorola kernel in stock Nougat ROMs appears to have anti rooting measures included (I think DM Verity?) If you attempt to root on this stock Nougat kernel, you'll likely soft brick/bootloop your device.
A custom kernel (e.g. elementalX v2.0.1 for stock) does not have these anti rooting defences, so it's safer to root with magisk. I would recommend magisk as super SU hasn't been updated in some time.
It appears that this need to flash a custom kernel before rooting applies to Nougat stock ROMs; marshmallow stock ROMs and the Oreo soak test stock ROM appear not to require a custom kernel.
As an aside, custom kernels and root are not necessary to flash custom ROMs. The only tools you require are an unlocked bootloader and the correct TWRP. The kernels included with these custom ROMs may also have anti rooting measures disabled, so it's safer to directly root without having to use a custom kernel.
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.
Device: Moto G4 XT1625 retus (non amazon firmware)
Android version: Android 7.0 April 2018 security update
I have problems on installing magisk on my Moto G4. I have unlocked the bootloader and flashed twrp. When I installed ElementalX Kernel since it's a requirement for magisk to work, my phone just boots fine. But when I will install the latest or old versions of magisk, My phone gets stuck in a boot loop. I tried supersu ans other kernels but no luck of booting my phone with magisk installed. Is there anything that I did wrong? My phone only boots without magisk/supersu installed.
UPDATE: I used Vegito Kernel and now my phone boots with magisk installed.
Stock ROM doesn't like Magisk/SuperSU. You need to reflash the original boot image for it to boot again and I think it'll remove root access. From my experience, a custom ROM improves the hackability of the phone a fair bit (I'm using official Havoc OS, which looks like Android 9 but is based on Android 8.1. It's quite stable actually)
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.
Hi,
is anyone running latest B20 Oreo rom on an A2017U phone with Magisk v25?
When I patch boot image and flash it via EDL the phone doesn't boot it, I have to restore original boot.img to be able to boot android again.
Also, fastboot is not available in the stock EDL images, any idea how to get fastboot back?
Thanks
Hi,
For first, I flashed some ROMs earlier in my life but it was like 5 years ago. I'm not expert in that field. That being said... I'm running B02 Oreo ROM on A2017G but i had the same problem. I managed somehow to find somewhere (can't remember which site) that "Magisk 16.4 should work because 16.0 version had some problems". So I tried 16.4 and it worked for me. Unfortunately data partition, although it shouldn't after root, stays encrypted (in TWRP).
Also, if You boot to system and open Magisk manager it will show You that update is available. After updating to the latest app version it will say that your version of Magisk is not supported now and You should update it (meaning, flashing latest zip). I didn't try it but assuming that earlier it didn't want to boot with the latest version on "Magisk-v25.1.zip" it won't at this time too.
It's so hard to find any information about this phone this day's... I would love if someone knew how to disable this encryption. I tried I think every solution and nothings seems to work :/
I hope I'm not late and my post will help You