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
I am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
WTF? said:
I am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
Click to expand...
Click to collapse
Unlock your bootloader, which will void warranty.
Flash TWRP to your recovery partition via fastboot
Make sure you boot into TWRP first, then back into system
Install Magisk Manager, then download the latest version of Magisk through the app
Reboot to recovery the BACK UP EVERYTHING
Install the Magisk zip located under /MagiskManager
Reboot to bootloader
Flash stock recovery
Reboot to system
NOTE: If you cannot boot after Magisk is installed, you will need to restore your boot partition from within TWRP.
Personally, I don't think you should root and keep up with OTA, it may brick your system with root. (Never happened to me, I've only seen it happen)
Hit thanks if I helped.
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
anirbannath said:
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
Click to expand...
Click to collapse
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
sunshinebhushan said:
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
Click to expand...
Click to collapse
mine also any sol to fix this?
Steps to fix any root mess-up that might happened and/or corrupt system from tampering with files.
1. Follow this guide, you can start from the flashing part
2. Download the mi flash app + a1 fastboot stock rom
3. Flash using the guide, make sure you select 'save user data'! or you will lose all your data!!
4. Once the flashing is complete you will reboot into the august patch, go to updates and install all the updates as usual
5. Root/Flash recovery using your favorite method.
I played around the system partition too much and had some issues with play services, also I couldn't update to october patch, after doing the above, everything works great. just use this guide anytime you want a clean slate.
Also always backup everything on twrp, always a useful thing to do.
Good luck
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
sunshinebhushan said:
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
Click to expand...
Click to collapse
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
Hi. As I mentioned, I am not even on the September patch. I used to be but then I rooted it today (installed Magisk) and suddenly I'm back to the August patch. September patch only installs in 'a', which is not rooted. That doesn't really serve my purpose.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
Hi. There seems to be a problem with what you suggest. The video I followed does almost the same thing. I even have TWRP, along with Magisk of course. The problem is, when I boot to 'a' (the partition that successfully installs the September update), I find that it isn't rooted. Magisk is inactive. And root checker says that root isn't properly installed. So obviously, the question of unrooting is rendered moot.
I want to be able to install the OTA update in my rooted partition and make it stick. People have installed OTA updates to rooted ROMs (mostly using FlashFire), but Flash Fire is giving me an unusual error, something about being unable to install OTA even though it has detected it due to being unable to find some files in boot/recovery folder or something like that.
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Ex-Hunter said:
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Click to expand...
Click to collapse
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
anirbannath said:
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
Click to expand...
Click to collapse
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
Code:
fastboot getvar all
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
sunshinebhushan said:
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
Click to expand...
Click to collapse
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Ex-Hunter said:
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Click to expand...
Click to collapse
I am trying to edit directly, what is the other way to edit?
sunshinebhushan said:
I am trying to edit directly, what is the other way to edit?
Click to expand...
Click to collapse
You've to use resetprop tool for that. You can modify an existing module or put a script at /magisk/.core/service.d (I think.... haven't done that in a long while). You can ask magisk related queries here (unofficial magisk 13.4) or here (official)
Ex-Hunter said:
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
kiran8631 said:
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74203817&postcount=4
by flashing with flashfire rooted and installed supersu without twrp flash and now wifi stopped working rest everythig works just fine..for now i m back2stock...can any one tell me the most safe procedure wich do not break any drivers. i m on 1st october patch. thank you in advance
I am hoping I can bounce my plan of attack for updating my Pixel 2 XL that is already rooted (using Magisk Manager + Magisk) and currently running Magisk Manager 5.6.4 + Magisk v16.0 and Android 8.1 (build OPM1.171019.021) to the latest and greatest version of Android (looks like its currently v9.0 w/ build# PQ1A.181105.017.A1)
First off, I didn't use TWRP when originally rooting android v8.1 on my Pixel 2 XL previously, I didn't think I needed it and had no plan to ever install a custom ROM. I am still in this boat and would prefer not to install or use TWRP if possible. I went the route letting the magisk manager app on my phone update the (at that time) newest factory image of android then flashing that image back onto my phone via fastboot and everything went great.
Anyway - If anyone would look over my approach here and let me know if this should work or not I would appreciate it!
My plan for updating to android 9.0 and keeping root:
1. Download the last android factory image from google (currently PQ1A.181105.017.A1)
2. Backup everything on my phone I care about (pictures, etc)
3. Use fastboot to flash the latest factory image to my phone (I understand this will reset everything on my phone and I'll lose root for the time being)
4. Download magisk manager apk from ******************
5. Make sure my phone is setup to allow installation of apps from unknown sources, then install magisk manager on my phone
6. Use Magisk Manager to install magisk and use the option to "patch boot image file" to patch the boot.img file from the latest factory android image (currently PQ1A.181105.017.A1)
7. Use flashboot to flash the patched version of the latest factory android image (currently PQ1A.181105.017.A1) to my phone, then finally check that root is working by using Magisk Manager. Then restore my backed up files to my phone (e.g pictures)
Thanks in advance for the advice!
I'm rooted with magisk, i took the ota, knowing full well it wasn't going to complete while I'm rooted. Haha me... It took. Didn't lose a thing except root. 10 minutes later, I'm rooted on pie. No issues for me.
As for twrp, you don't flash it, you boot it. It runs until you reboot. I turn off security on the phone before I re- boot into the bootloader. Twrp did or still does have an issue with patterns. Otherwise it works great for my needs.
I used Magisk to do an OTA update to Oxygen OS 12, but it feels like my root is gone because TWRP disappeared, the bootloader was locked after the update, and I had to unlock it. But when I do root check, it still says I'm rooted. Most of my Root access requiring apps don't work properly either like battery limiter and Adaway. But I check root status in Momo, and it says the environment is abnormal. Upon restart it doesn't pop up with TWRP as recovery; it goes to default OP recovery. Also, the warning at startup where it says the warning about the bootloader being unlocked is also gone, even after reunlocking my bootloader after the OTA update.
Also, slightly unrelated, but my fingerprint sensor has also stopped functioning completely. I couldn't use it to unlock my phone so I removed all fingerprint data and I tried adding it back and it wouldn't even detect my finger when I tried to add it back.
What is a true test to check if I need to wipe and reroot and install TWRP again?
How did TWRP just disappear?
Did I do the OTA wrong?
Why would my phone allow me to grant root access to root checker if I wasn't still rooted?
Would a simple fix be just reinstalling Magisk?
edit: So it seems that Adaway works, but battery limiter does not(I assume doing a fresh install of the APK might help). And my fingerprint sensor also does not work.
I am indeed rooted, but I am still wondering why TWRP just disappeared? And why does my fingerprint sensor not work at all?
I have the Oneplus 8 Pro American version.
Take a step back and read this.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
A12 is not in a good state anyway and most people use OOS11 or a custom rom.
IDK if battery limiter is a12 compatible but that does not matter.
You should NOT use TWRP with A12 and you should NOT do an OTA with magisk to a12.
What i would do now:
1. Read the thread i posted above carefully.
2. Backup all you data to a pc.
3. Backup persist image.
4. Use MSM Tool ro rollback to a clean state of OOS11.(https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
5. Flash latest A12 as local upgrade within the system updater twice (to ensure its on both slots)
6. Extract boot img with payload dumper and patch it via magisk.
7. Unlock bootloader
8. fastboot BOOT patched_boot_image.img
9. Start magisk and install
Enjoy rooted A12.
Or better simply stay on A11 its better anyway.