Related
i have been following instructions from http://androiding.how/root-moto-x-pure/
i have everything correct once in flash the latest supersu my device freezes at the boot image of moto.
If you're running MM make sure to use a systemless root.
I can vouch for the 2.62 version working on this phone. It is the only version I've tried.
Versions above 2.62 did not work, although I've seen some discussion in the forum that 2.67 is ok.
I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
That looks like a really old tutorial, and some of those links may be way out of date.
The bootloader unlock process hasn't changed (since we're pretty much just using Moto's official method), but you'll probably want to grab current versions of TWRP (3.0.0-1) and SuperSU (either 2.65 Stable or 2.67 Beta), IIRC.
Might also be simpler to use a tutorial here on XDA.
Edit: Don't quote me on this, but some older versions of TWRP may not work properly on the MM bootloader. So it could be that the minimum recommended version of TWPR (for 6.0) is newer than whatever is linked to from that old tutorial, which could explain your issue. If that's the case, updating to a newer TWRP via Recovery or Fastboot might just fix your problem.
Mejilan said:
I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
Click to expand...
Click to collapse
So you simply flashed SuperSU 2.67 via TWRP and you have fully functional phone and root?
Interesting, as it does not appear to work for everyone...
Yup. I'm not interested in engaging with the systemless root since it's still so experimental and early. I prefer going with a more stable experience.
Titanium Backup and Xposed are part of my bread and butter software environment. If root were broken, I would damn well know, right? Heh.
Gotta have my GravityBox and Enable Ambient Display...
A few weeks ago, I ditched TruPure and followed a Fastboot-heavy guide in order to restore my phone to stock 6.0. Was a pain, but I powered through.
Then I unlocked my bootloader again (with the same code Motorola provided to me months ago), and flashed TWRP 3.0.0 via Fastboot (later updated to 3.0.0-1 via TWRP itself).
Finally I booted into recovery and flashed SuperSU 2.67 beta and Xposed v80. Installed SuperSU Pro from the Play Store, and have been good to go since.
I'm pretty sure that I've been using SuperSU 2.67 for quite some time now, both on TruPure (up to 2.5 before I ditched it) and on stock MM.
I've been updating SuperSU more or less as quickly as Chainfire has been releasing Beta updates, as I'm pretty sure he's been focusing on MM compatibility fixes in recent months.
I didn't realize there were any issues with flashing (though I think TruPure has SuperSU baked in).
i have latest twrp, i didnt bother with the supersu step, but im currently having issues getting turbo charge to work on any rom i tried...
I flashed 2.66 after running commands in terminal to make root systemless & my phone booted normally.
Sent from my Moto X Pure Edition using Tapatalk
Hi all! I'm new here (at least at account level) and with my first thread I want to help people which can't flash 6.0+ roms in official 2.8.x TWRP for our Moto X 2013 (like @dziarski in TWRP 2.8.7.0 thread).
I have Moto X 2013 (XT1052 model for reference) and I unlock bootloader, root and put costum roms not so long ago but here out to resolve this.
You need to upgrade your TWRP because TWRP <3.x don't support 6.0+ rom flashing well (edit: mochi579 below report twrp 2.8.7.0 can work for flashing too even I recommend latest 3.0.x version for avoid all problem especially with 7.x roms). I advice you to check out unofficial TWRP 3.0.2-0 by fantastic TeamMEX here.
This updated version grant you to flash both 6.0+ and 7.0 roms (tested myself) without any error.
There are my ROMs test to try this TWRP:
Legenda: (Android version)
TWRP 2.8.6.0 official:
Resurrection Remix 5.7.4 (6.0.1) -> failed immediately with this error
Code:
E: Error executing updater binary in zip "/..."
Error flashing zip "/..."
After some research I understood I need to updated my TWRP and here's the result
TWRP unofficial 3.0.2-0 by @TeamMex:
RR 5.7.4 (6.0.1) again -> succes without problem (I use right now)
CM13 (6.0.1) -> succes
CM14 (7.0) -> succes
OctOS Oct-M (6.0.1) -> succes
Xperience 11.0.0_rxx (7.0) -> succes
All succes without any error during flashing.
Just in case I want to add my step even its very common:
1) Make a NANDroid backup if I don't have it already
2) Wipe Cache, Data, System, ART/Dalvick cache
3) Optional factory reset (cache,art/dalvik and data)
4) Flashing ROM + Gapps from OpenGapps (remember to select ARM)
5) Reboot and finish
If there's a problem in the post or its wrong place (its here or Q&A) please let me know
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
mochi579 said:
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
Click to expand...
Click to collapse
Hi,
I was using 2.8.6.0 because in the root thread by Kidjoe here in General he write about a possible read error about SD card in the phone (clearly a bug because we don't have it xD), so my experience with 2.8.7.0 is zero unfortunately but I think it's very similar.
I have zero problem flashing the rom I listed, for various reason some mod I flashing more than one time (never because flashing problem, usually rom itself problem or just jumping back and forth).
I flash xperience 2 times, cm13/14 and OctOS one time and Resurrection Remix many times if we include backup when coming back from these ROMs.
The only know bug I experienced in 3.0.2-0 is slow flashing in "normal" condition. Just follow the note in the op of recovery thread:
Code:
NOTE: If you have slow format on ext4 go to Settings->Use rm -rf instead of formatting
Copy pasted from TeamMEX thread.
Hello, i was using Skydragon 5.1.1 and it started to become slow, got optimizing apps everytime i restarted the phone, and wanted to flash to LineageOS
Figured I`d update TWRP to latest version, so I got that from their site, version 3.1.1-0 and when I wanted to boot to recovery it would become stuck at the bootscreen. Same thing with any other version over 3.0.2-0.
Used FirstAid to revert to older version of TWRP, and managed to install 3.0.2-0 again and boot to recovery normally.
With this version it seems i cannot install LineageOS because it gives an error.
How do I go about installing Nougat ? Thanks !
First u should install the 3.6.0 Firmware then try install Nougat
cosmin.dark said:
Hello, i was using Skydragon 5.1.1 and it started to become slow, got optimizing apps everytime i restarted the phone, and wanted to flash to LineageOS
Figured I`d update TWRP to latest version, so I got that from their site, version 3.1.1-0 and when I wanted to boot to recovery it would become stuck at the bootscreen. Same thing with any other version over 3.0.2-0.
Used FirstAid to revert to older version of TWRP, and managed to install 3.0.2-0 again and boot to recovery normally.
With this version it seems i cannot install LineageOS because it gives an error.
How do I go about installing Nougat ? Thanks !
Click to expand...
Click to collapse
I have the same problem. Have you found a solution yet?
Simple question, but not easy to find answer, without reading 1000s of posts i guess, for someone who has not spent much time here in recent past.
I read Official guide to root OP5.
It gives option to use either Official TWRP or Blu_Spark? Which is better and more recomended?
Use Super SU or Magisk root?
On OP3T i was using Super SU for days and it had bootloop and other issues, after days i read a post in some threat Super SU has issues with that specific thing, use Magisk, i used it issue was gone.
Save me again from reading for hours, kindly someone with should answer my question, for me and for others like me.
Thanks in Advance.
Update: Answer is Blu_Spark and Magisk
About TWRP I'm not entirely sure. They all work for flashing stuff, but some can't restore data very well.
I personally use Magisk. And probably most people too.
Magisk is up to date and You can pass safetynet. SuperSu is number one Root app since years but Magisk is the future and better in my option.
I hope the Twrp guys will bring a updated recovery soon. Official can Not restore data... If u use blu_spark Kernel the blu_spark recovery is Best joice
You don't need to use Blu Spark kernel to use Blu Spark TWRP. Blu Spark TWRP is much more up to date than official TWRP and it works perfectly. You can make Nandroid backups with data and restore them with no issues in Blu Spark TWRP. In official TWRP your phone will go into a bootloop.
Magisk is a better root option if you want to pass safety net after rooting. If you don't care about that then people generally use SU instead. Magisk also has modules to add functionality but those are extremely hit or miss and don't work as intended on all devices.
jhs39 said:
You don't need to use Blu Spark kernel to use Blu Spark TWRP. Blu Spark TWRP is much more up to date than official TWRP and it works perfectly. You can make Nandroid backups with data and restore them with no issues in Blu Spark TWRP. In official TWRP your phone will go into a bootloop.
Magisk is a better root option if you want to pass safety net after rooting. If you don't care about that then people generally use SU instead. Magisk also has modules to add functionality but those are extremely hit or miss and don't work as intended on all devices.
Click to expand...
Click to collapse
So it is safe to say Average/Layman here should use Blu_Spark TWRP.
Super SU is fine for other devices, it was Okay on OP3, but on my OP3T, it was as good as unusable, which is also called waste, so Magisk is better option.
I don't know (or in need of) saftynet, don't want to mess with kernals, OOS is fine enough for me, my only genuine need to root device is to use medium roboto (bolder) and to use titanium back, and to batch freeze Apps when i need to hand device to someone.
Other than that i am fine OOS.
Then use blu_spark recovery and magisk Root and u Arena Google to Go. Using magisk online for Kernel Apps so u can use the Option in magisk settings only Main Funktion. Which means Root.
latest Blu_Spark TWRP and Magisk 14.3 highly recommended ... they are up-to-date and working great.
Anyone mind sharing link of Blu_Spark recovery?
G0dofWar said:
Anyone mind sharing link of Blu_Spark recovery?
Click to expand...
Click to collapse
most recent version: https://forum.xda-developers.com/devdb/project/dl/?id=26860
usmanxhmed said:
So it is safe to say Average/Layman here should use Blu_Spark TWRP.
Super SU is fine for other devices, it was Okay on OP3, but on my OP3T, it was as good as unusable, which is also called waste, so Magisk is better option.
I don't know (or in need of) saftynet, don't want to mess with kernals, OOS is fine enough for me, my only genuine need to root device is to use medium roboto (bolder) and to use titanium back, and to batch freeze Apps when i need to hand device to someone.
Other than that i am fine OOS.
Click to expand...
Click to collapse
If you can use official TWRP then you can use Blu Spark TWRP. Same interface and buttons.
this
ulxerker said:
latest Blu_Spark TWRP and Magisk 14.3 highly recommended ... they are up-to-date and working great.
Click to expand...
Click to collapse
Had a hard time finding this recovery, so I post links if that helps someone:
Thread: https://forum.xda-developers.com/oneplus-5t/development/kernel-t3706295
Downloads: https://forum.xda-developers.com/devdb/project/?id=21949#downloads
Github mirror for downloads: https://github.com/engstk/op5/releases
Recoveries are files ending with .img
What about Codeworxx TWRP?
Which one (bluespark or codeworxx) is recommended particularly with regard to Pie?
epr said:
What about Codeworxx TWRP?
Which one (bluespark or codeworxx) is recommended particularly with regard to Pie?
Click to expand...
Click to collapse
Codeworkx or blu spark latest ones
Twrp blue spark 3.2.1-x
Dear sir ,
can you please share TWRP version 3.2.1-X blue Sparks version
SANDIP PRAJAPATI said:
Dear sir ,
can you please share TWRP version 3.2.1-X blue Sparks version
Click to expand...
Click to collapse
You can get it on engstk's Github : https://github.com/engstk/op5/releases
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