If you all are having a hard time looking for root on 7.1.2 nexus 5x I have the solution.
I confirm this works on my nexus 5x running 7.1.2 NPG05D currently
-Download SuperSU SR3 here: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
-Then flash in twrp
-Profit!
Kudos to Chainfire and everything he has done.
SR3 fourm: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Thanks,
Thanks man. Just flashed this and so far everything is working perfectly
Now NPG05D is missing from https://developers.google.com/android/images#bullhead .
I can flash in 7.1.2 N2G48C, but failed in installing SR3-SuperSU-v2.79-SR3-20170114223742 and SuperSU-v2.82-201705271822.
Do you have to wipe? When to wipe?
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
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
yohouse2 said:
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
Click to expand...
Click to collapse
It's been discussed 100 times on the xXx thread that it's not recommended to switch between stable and beta the dirty way cause you're facing issues. Like you.
It's also not recommended by oneplus in the official threads cause of issues.
A clean installation(look at the beta thread) saves you hours on troubleshooting/headaches in the future.
And latest stable build has advanced reboot menu instead of beta
My stock rom has a wifi problem and I want to flash a fix via twrp, but I still want to obtain ota updates. Is booting into twrp via command prompt temporary? Like once I exit twrp without flashing installer zip it would be gone, right?
Sorry, for the noob question. I'm still new to a/b devices.
Try
fastboot boot twrp (the name of your twrp-image)
I am using this all the time to uninstall / install magisk and do an OTA-update inbetween
Tiemichael said:
Try
fastboot boot twrp (the name of your twrp-image)
I am using this all the time to uninstall / install magisk and do an OTA-update inbetween
Click to expand...
Click to collapse
There won't be any problems with stock pie, right?
As I need Xposed, I have not tried PIE yet.
If you are worried trying PIE, flash OREO (Nov 2018) and then do an OTA-update before rooting with TWRP and MAGISK
Tiemichael said:
As I need Xposed, I have not tried PIE yet.
If you are worried trying PIE, flash OREO (Nov 2018) and then do an OTA-update before rooting with TWRP and MAGISK
Click to expand...
Click to collapse
I'm on latest Jan patch. :/
WhatzIt2Ya said:
There won't be any problems with stock pie, right?
Click to expand...
Click to collapse
I think theres only one TWRP version which will work with Pie.
Hello,
i'm running the OOS Version 9.0.1 and want the new 10.0 Version. I cleared the cache/data and tried to flash this ota with the 3.3.1 blu_spark twrp but it drops in fastboot everytime. What i'm doing wrong?
Did you managed to work it out? I'm planing to update oos 9.0.1 to 10 too with root.
I have no problem with this, OP5 upgraded on A10 with twrp and magisk
Did wipe everything... now i got android 10 and magisk
Knightrid3r said:
Did wipe everything... now i got android 10 and magisk
Click to expand...
Click to collapse
Does VoLTE and VoWIFI work? I absolutely need VoWIFI.
Knightrid3r said:
Did wipe everything... now i got android 10 and magisk
Click to expand...
Click to collapse
How can I Android 10 can u post here magisk version with twrp ?
Dirty flashed with magisk and no problem.
(actually I uninstalled magisk before upgrade, and installed it back again after).
Works fine.
erik.aragorn said:
I have no problem with this, OP5 upgraded on A10 with twrp and magisk
Click to expand...
Click to collapse
Can you use Gpay?