Is there any option to root my phone apart from SuperSU? Coz SuperSU gives some error. My sim card is not detecting after installing SuperSU. If I unroot sim card is working.i am using twrp harpia in Moto g4 play and lineage 14.1 rom 7.1.2 nougat.
mathantn said:
Is there any option to root my phone apart from SuperSU? Coz SuperSU gives some error. My sim card is not detecting after installing SuperSU. If I unroot sim card is working.i am using twrp harpia in Moto g4 play and lineage 14.1 rom 7.1.2 nougat.
Click to expand...
Click to collapse
Most Lineage builds come pre-rooted. Enable developer options and look for the root toggle. Might need a reboot to take effect.
Lineage must be compiled differently for SuperSU to work. The ROM builder will know if this was done.
Magisk is an alternative to SuperSU. I don't have experience with it on this device but it should work fine. You'll need to do a little reading to become familiar with the installation procedure.
Davey126 said:
Most Lineage builds come pre-rooted. Enable developer options and look for the root toggle. Might need a reboot to take effect.
Lineage must be compiled differently for SuperSU to work. The ROM builder will know if this was done.
Magisk is an alternative to SuperSU. I don't have experience with it on this device but it should work fine. You'll need to do a little reading to become familiar with the installation procedure.
Click to expand...
Click to collapse
Thanks bro. It worked
Related
Tested on a clean install of CypherOS. It installs and passes SafetyNet without doing anything complicated. Assuming it should work on any rom without root built in like Lineage OS.
Grab it here and thank @topjohnwu. Remember to enable Magisk Hide in settings or it will not pass SafetyNET.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.
rsocon said:
I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.
Click to expand...
Click to collapse
On a clean install I just flashed rom, gapps, and magisk in that order.
BTW over night Magisk lost root, a reboot and root was back though. Might be bug, might be a one time thing, I don't know.
After trying everything listed still no luck getting this to work.
Guess no Android Pay for me
I tried to install on stock ROM, it seem it dosn't work, i'll try with a custom ROM
i'm running this just fine with just the core AND the latest version of magisk. safetynet check passes too on cypherOS.
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.
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
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.
I’ve followed about 5 different guides, my boot loader is unlocked and root access is acquired, however, I can’t get Super SU or Magisk to install. I’m trying to install LineageOS, but I keep getting error 255. RAM disk fails with Super SU and Magisk says it goes through, but it doesn’t. What am I missing here? This is getting quite frustrating. I’m on OPS28.85 17-2, whatever the latest Oreo 8.1.0 update is.
metllicamilitia said:
I’ve followed about 5 different guides, my boot loader is unlocked and root access is acquired, however, I can’t get Super SU or Magisk to install. I’m trying to install LineageOS, but I keep getting error 255. RAM disk fails with Super SU and Magisk says it goes through, but it doesn’t. What am I missing here? This is getting quite frustrating. I’m on OPS28.85 17-2, whatever the latest Oreo 8.1.0 update is.
Click to expand...
Click to collapse
You have to give more information.
What did you do in what order?
Have you used unsu.zip between trying to flash SuperSU and Magisk or at least magisk uninstaller?
Which magisk/SuperSU build did you try? Which TWRP?
Is your data partition encrypted?
Provide a recovery log from flashing procedure.
If you want to flash lineage have you tried their own root solution?
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You have to give more information.
What did you do in what order?
Have you used unsu.zip between trying to flash SuperSU and Magisk or at least magisk uninstaller?
Which magisk/SuperSU build did you try? Which TWRP?
Is your data partition encrypted?
Provide a recovery log from flashing procedure.
If you want to flash lineage have you tried their own root solution?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I forgot to reply here yesterday. I did find out what my issues were. I guess I didn’t have the latest versions of TWRP or Magisk. Then I still had some issues installing Lineage until I wiped the device again. I followed the Lineage guide that’s sticky’d here. I always wiped before trying another method, but it was just the versions of Magisk and TWRP that I had.