Related
So I just updated to the latest xt1644 Nougat JP25.93.14-4 and am having an issue installing TWRP and getting it to stick. I installed it and even did a backup, but once I boot to System and then back to bootloader, and finally to recovery, it goes back to stock recovery. Also I am unsure of how to root this device now with Nougat. I've seen on a few sites differing methods. One site had a download for what they called a root package and it was a SuperSU 2.76 version. Another site said to use Phh SU and just install TWRP and then flash Phh. I don't want to mess anything up, can someone point me in the right direction since it seems everything in this forum is for a device other than the XT1644. Lastly, is it possible to revert back to Marshmellow using fastboot, or is that now not possible? I have unlocked my bootloader, obviously. Thanks.
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
tywinlannister7 said:
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
Click to expand...
Click to collapse
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
robn30 said:
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
Click to expand...
Click to collapse
try latest twrp 3.1.0
I got it working. I had originally set it to read only and I think that was the issue. Reinstalled it and mounted system and then choose to allow modifications. It then worked. Now onto root, we will see how that goes.
Sent from my XT1575 using Tapatalk
tywinlannister7 said:
try latest twrp 3.1.0
Click to expand...
Click to collapse
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
echo92 said:
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
Click to expand...
Click to collapse
Thanks for all the information, it is very much appreciated. Thanks to pastorbob62 as well. This information will be very useful.
Sent from my XT1575 using Tapatalk
pastorbob62 said:
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
Click to expand...
Click to collapse
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
robn30 said:
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
robn30 said:
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
You are very welcome. Glad you got it figured out and all is working well. :good:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
1emrys1 said:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
Click to expand...
Click to collapse
Generally you'd have to revert back to a clean stock ROM, no TWRP, no ElementalX, no magisk. The stock ROM also needs to be in a read only state (no modifications allowed in TWRP) and cannot be debloated (OEM partition needs to be untouched).
You could revert back to a TWRP backup made before you flashed ElementalX, provided you did not let TWRP make modifications. You'd also have to find a stock recovery (if you flashed TWRP), and restore a stock logo.bin as well if you flashed a custom logo.bin to hide the bootloader warning. Then, you should be able to apply OTA/security updates. Attempts to apply OTA updates with TWRP on your device will likely fail and leave you in a soft bootloop unless you boot via the bootloader. You could try this to break the bootloop: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The easiest and safest method I've found is to re-flash the stock ROM you have. Ensure this is the same firmware as you currently have and the latest firmware that you've flashed onto your device (don't downgrade your firmware if possible). You can re-flash without erasing your data by omitting the fastboot erase userdata command. However, I would recommend you back up your device anyway (e.g. in TWRP) and any important files, as although this procedure should not affect your data with that command omitted, any firmware flash has the possibility of affecting your device stability. That may require a factory reset/device wipe to fix. Backing up your data should be standard policy when it comes to flashing anything affecting your device's system/underlying firmware.
After re-flashing the stock ROM, you should be able to apply the OTA update.
Thanks a lot for the detailed answer. I really appreciate people like you. [emoji3]
Sent from my Redmi Note 3 using Tapatalk
I would like to root my moto xt1575 pure to try everything to improve battery life
It is running Nougat OTA zip flashed through stock recovery
I unlocked the bootloader at Motorola's web site.
I installed adb and fastboot on my windows 10 laptop. Not all the adb commands work
I want to do the image dump that magisk requires before proceeding any further.
I used Sunshine SuperSu and xposed on my HTC one m8 vzw running kitkat 4.4.4
I apologize if this is covered elsewhere or in the wrong place. Perhaps no one has rooted a stock Moto xt1575 pure already running nougat yet. If I can't figure out how to do the image dump I'm stuck with stock. I
jim1sn1 said:
I would like to root my moto xt1575 pure to try everything to improve battery life
It is running Nougat OTA zip flashed through stock recovery
I unlocked the bootloader at Motorola's web site.
I installed adb and fastboot on my windows 10 laptop. Not all the adb commands work
I want to do the image dump that magisk requires before proceeding any further.
I used Sunshine SuperSu and xposed on my HTC one m8 vzw running kitkat 4.4.4
I apologize if this is covered elsewhere or in the wrong place. Perhaps no one has rooted a stock Moto xt1575 pure already running nougat yet. If I can't figure out how to do the image dump I'm stuck with stock. I
Click to expand...
Click to collapse
You say you unlocked the bootloader? Why not just flash the magisk 14.3 zip in a custom recovery? (TWRP?) That is what I would do, flash TWRP, and then flash magisk through that. To do this you are going to want to follow this tutorial http://www.droidviews.com/how-to-install-twrp-and-root-moto-x-pure-2015-xt1575/ and then once in TWRP click install -> magisk zip. Let me know if this is unlcear. But yeah install TWRP, and then flash magisk through that
Spencervb256 said:
You say you unlocked the bootloader? Why not just flash the magisk 14.3 zip in a custom recovery? (TWRP?) That is what I would do, flash TWRP, and then flash magisk through that. To do this you are going to want to follow this tutorial http://www.droidviews.com/how-to-install-twrp-and-root-moto-x-pure-2015-xt1575/ and then once in TWRP click install -> magisk zip. Let me know if this is unlcear. But yeah install TWRP, and then flash magisk through that
Click to expand...
Click to collapse
I installed Magisk Manager and made a patched_boot.img but I get the error no devices/emulators found when trying to run adb commands from my laptop. I uninstalled and reinstalled the motorola driver software on my laptop. I'm just trying to go by the red letters straight off the magisk page in xda, so why doesn't it work? Must be me! LoL!
You don't need patched boot image.
Flash or boot only twrp 3.x(one version can backup stock recovery, I don't remember n°).
fastboot boot nameTwrp.img
Into twrp backup all: boot, system, data(?), recovery, esp.
Important: after backup restore boot.
Flash magisk14.zip(link is in my signature).
Reboot. @jim1sn1
Dear all,
my question is: will OTA updates by LG still work if a have an BL unlocked, TRWP installed and Magisk installed?
I would like to keep my stock ROM and get the OTA, but I would like to make backups and be able to install software with needs root.
Can you recommend SU or Magisk?
Thanks.
you can recieve OTA but you can't install it , You need a zip update file and flash it with twrp
i use SU i never tested magisk
paabel said:
Dear all,
my question is: will OTA updates by LG still work if a have an BL unlocked, TRWP installed and Magisk installed?
I would like to keep my stock ROM and get the OTA, but I would like to make backups and be able to install software with needs root.
Can you recommend SU or Magisk?
Thanks.
Click to expand...
Click to collapse
With TWRP you cannot install OTA, so in any case you would need to remove it.
Also i don't advise to make OTA on a rooted device, doesn't matter if it's Magisk or SuperSU
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 followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
INSTALLATION
1.back up your system, data and boot partition. If the process fails restoring those will revert the changes.
2.Download and flash Magisk 15.3 (later versions didn't work for me, phone wouldn't boot at all) through twrp.
3.Flash the latest f2fs loop back work around.
4. Flash magisk manager for recovery (mm-2018.8.1.zip attached below)
5.Boot your phone
UPDATING TO MAGISK 16.0
Once the phone has booted:
1.install magisk manager 5.8.3 (attached below)
2.Open magisk manager
3.if any update is available for magisk manager, install it.
4.click on the button that tells you to update magisk to latest version.
IMPORTANT:
5. Select the direct installation method. Flashing the update through recovery will render the phone unable to boot again.
That's it, thanks.
=======
Downloads:
Magisk 15.3
f2fs-loopback-bug-workaround-2018.8.1.zip
mm-2018.8.1.zip
Magisk Manager v5.8.3.apk
freeZbies said:
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
....snip
Click to expand...
Click to collapse
Interesting.
For what is the magisk manager for recovery needed?
Wolfcity said:
Interesting.
For what is the magisk manager for recovery needed?
Click to expand...
Click to collapse
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
EDIT: Mm for recovery is actually a module that allows you to list and Uninstall modules from Twrp in case your phone no longer boots after flashing a module.
and you're correct, magisk 15.3 does include magisk manager and will install it. the problem I had is that I flashed magisk 15.3 over a system where either the boot.img was already patched, and I experienced that magisk manager sometimes wont be installed in these cases
Sent from my Moto G (5) using Tapatalk
freeZbies said:
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
Click to expand...
Click to collapse
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
nicolap8 said:
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
Click to expand...
Click to collapse
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
freeZbies said:
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
Click to expand...
Click to collapse
At least it's inside the official 15.3. But I remember that MM was often not installed in earlier builds.
Sent from my Moto G5 Plus using XDA Labs
I Got Another Method Also
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Sonisudhanshu said:
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Click to expand...
Click to collapse
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Sent from my Moto G (5) using Tapatalk
freeZbies said:
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Click to expand...
Click to collapse
I'm on 3.2.2.0 and it offers the ability to backup EFS, 3.2.1.0 also.
As said, for persist there are several unofficial builds but you can back it up with those commands in TWRP terminal:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
for backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
for restore.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
1. Because I didn't have any option to backup efs in twrp.32.bit
2. I was not sure but I just flashed it so that no problem occurs like booting issue..
Hope this helps
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming..... If this helped , i would be gladed
Do the magisk modules work ?
llucas_br said:
Do the magisk modules work ?
Click to expand...
Click to collapse
Which magisk module?
Sent from my Moto G5 Plus using XDA Labs
TWRP flashable Oreo 8.1 OTA updates
Sonisudhanshu said:
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming.....
Click to expand...
Click to collapse
There are already TWRP flashable Oreo 8.1 OTA updates available.
https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913
thanks
Chekm8Qc said:
I just installed magisk 17.1 and it worked right away. Even safety net passes.
Click to expand...
Click to collapse
Chekm8Qc confirmed here https://forum.xda-developers.com/showpost.php?p=77906610&postcount=56 that he could directly install the latest Magisk version (currently 17.1) on Oreo 8.1 OPP28.85-16 eliminating the need to install an older version first as recommended in this thread.
I can also confirm, installed straight away 17.1 and worked flawlessly, no bootloop and safety net passed.
Please Update!
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
G5-User7080 said:
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
Click to expand...
Click to collapse
in oreo stock you dont need f2fs bug module, because is working without it