So today I received a XT 1056. I then proceeded to unlock the bootloader and flash SU.
So I then tried flashing a CM 12 nightly build and all went well. I was able to setup the device until the screen was locked and then the phone instantly starts looping through the "Unfortunately, system UI has stopped." error. I've tried flashing an older version of the ROM, and I've tried numerous other 5.0 ROM's but each one will crash as soon as the screen is locked.
And it would not seem like a great idea to revert to an older version of Android and risk bricking the device.
So if someone could advise me how to get rid of the loop error it would be much appreciated.
I have TWRP 2.8.3 currently flashed if that makes any sort of difference....
Install the gApps...
690sid said:
Install the gApps...
Click to expand...
Click to collapse
I tried a fresh install of this CM12 with the gapps it says to use and once again I can setup the phone and as soon I get to the home screen the system UI loop happens. http://forum.xda-developers.com/moto-x/development/rom-unofficial-nightly-lollipop-5-0-t2960768
I also saw your post in that thread to try flashing with these instructions, but it still has the same error.
1 - Download an earlier version of the ROM that booted on you phone along with the gapps.
2 - Flash the ROM and gapps with a suitable recovery... CWM or TWRP 2.6.
3 - Download the latest release that you want to install.
4 - Flash the latest release over the pre - installed ROM without wiping anything.
Is it possible to just flash 4.4.4 or do I risk bricking the device?
I have a stock Oneplus 3T, updated to 4.1.3. I wanted root access to allow Cerberus more control.
So I followed the Oneplus 3T root guide by "Theunlockr" .com
I downloaded:
TWRP v3.1.0-1-oneplus3t.img
SuperSU v2.78 SR5
No-Verity opt encript v5.1
I followed the instructions as closely as I could, I installed the TWRP and cleared the phone (that booted normally),
Then I went to flash SuperSU and No-Verify, cleared the cache, restarted and my phone, and It didn't boot, the red dot logo animation would just play on a loop, I left it for an hour because it did warn me that it would take a while.
When I was satisfied that it wasn't going to start, I restarted it a couple of time, no-dice.
I also tried flashing a more up-to-date SuperSU. (v2.79), still didn't work.
So, now I've gotten myself further stuck, I flashed the stock recovery back onto the phone and decided i wanted to flash the Open Beta 5 OS.
But now when I go into recovery (stock), I can't connect to ADB properly.
I click " Install from ADB " - I've been using this, but it only seems to allow Sideload, but If I try to sideload it, it tells me it can't read the ROM.
So I changed ADB versions to the ones from mfastbootv2.
and now it says "error: protocol fault (no status)",
I can't use the push command because it just says "Error: closed"
So I'm kinda stuck for what I can do from this point forward to get my phone working again...
Android Debug Bridge version 1.0.31
Any suggestions?
Thanks for your time
Evan
There's so many different builds of SuperSU that it's getting hard to keep track of which one works. I know that flashing an older version does tend to cause endless boot animation. SuperSU 2.79 should work, though you'll likely need to dirty flash OOS again before flashing it.
I've also found ADB to be rather finicky in recovery. My advice is to use an USB OTG adapter and load any files that you need on a flash drive. Afterwards, follow these steps:
1) Boot into fastboot and flash TWRP again using your PC and fastboot commands
2) Download whatever version of OOS you want (stable or open beta) and somehow load it onto your phone, whether through ADB or USB OTG
3) Boot into TWRP and flash the OS that you've downloaded, wipe cache/Dalvik. You can clean flash if you want, though dirty flashing should suffice in this situation.
4) Flash either SuperSU v2.79, or Magisk v12.0. Both Magisk and SuperSU will root your phone, I just prefer Magisk due to its extra capabilities and more straight-forward development.
5) Reboot, the rebooting process shouldn't take more than a few minutes.
Using a flash drive also has other benefits, you can save nandroids directly onto it through TWRP. This both saves space in internal storage and keeps the backups safe in the event that your phone gets inadvertently wiped from any unforeseen incidents.
Additional notes:
-You don't need to flash the no-verity.zip if you flash either SuperSU or Magisk, both of them contains the necessary scripts
Fantastic!
Thanks a ton, that solved my issues completely.
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Lucarje said:
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Click to expand...
Click to collapse
This has been posted a million times all over the forum. A quick search here or Google would have revealed the answer
You need to flash a revision 2 firmware. So that would be something like t813xxu2 in the firmware build number.
Sorry for being late with reply. Your advice helped me fix my tablet! Thanks so much!
I was running LineageOS 14.1 up until 15.1 came out. I re-flashed my Nexus 6 with the first build of 15.1 along with OpenGApps. About a week later I decided to flash AddonSU. Here's where it gets goofy. For some unknown reason my brain decided to download and flash SuperSU. Once flashing completed, I went into developer options to enable Root, and to my surprise, root options weren't available. I flashed SuperSU again and still no root options. I then realized that I flashed the wrong SU zip. So, I downloaded and flashed AddonSU. Back into developer options and Root options were available. A few days later, the Nightly 4/30 OTA update became available. The update failed during install. I then flashed the nightly build along with the MindTheGapps zip this time. A week or so later, the Nightly 5/8 OTA update was available. That update also failed during install. I read in multiple forums here that the OTA updates fail due to a conflicting SuperSU binary, and that the only way to remove SuperSU was to reflash stock factory Android, in this case 7.1.1. So, I downloaded and flashed stock Android rom for Build N6F27M. Relocked the bootloader. Unlocked the bootloader. Re-flashed TWRP 3.2.1-0. I booted into recovery and went to File Manager and noticed that the SuperSU folder is still there. I deleted the folder and went through the entire flashing of Stock Android again, one .img file at a time. Locked and unlocked the bootloader again. Flashed TWRP again. Go to File Manager and guess what was there... The SuperSU folder was back!
Before I flash anything else, how can I totally remove SuperSU from my device once and for all?
Current setup:
- Using ADB and Fastboot on Lenovo X230 running Fedora 27 Linux
- Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
MadFoss1 said:
I was running LineageOS 14.1 up until 15.1 came out. I re-flashed my Nexus 6 with the first build of 15.1 along with OpenGApps. About a week later I decided to flash AddonSU. Here's where it gets goofy. For some unknown reason my brain decided to download and flash SuperSU. Once flashing completed, I went into developer options to enable Root, and to my surprise, root options weren't available. I flashed SuperSU again and still no root options. I then realized that I flashed the wrong SU zip. So, I downloaded and flashed AddonSU. Back into developer options and Root options were available. A few days later, the Nightly 4/30 OTA update became available. The update failed during install. I then flashed the nightly build along with the MindTheGapps zip this time. A week or so later, the Nightly 5/8 OTA update was available. That update also failed during install. I read in multiple forums here that the OTA updates fail due to a conflicting SuperSU binary, and that the only way to remove SuperSU was to reflash stock factory Android, in this case 7.1.1. So, I downloaded and flashed stock Android rom for Build N6F27M. Relocked the bootloader. Unlocked the bootloader. Re-flashed TWRP 3.2.1-0. I booted into recovery and went to File Manager and noticed that the SuperSU folder is still there. I deleted the folder and went through the entire flashing of Stock Android again, one .img file at a time. Locked and unlocked the bootloader again. Flashed TWRP again. Go to File Manager and guess what was there... The SuperSU folder was back!
Before I flash anything else, how can I totally remove SuperSU from my device once and for all?
Current setup:
- Using ADB and Fastboot on Lenovo X230 running Fedora 27 Linux
- Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
Click to expand...
Click to collapse
This seems like overkill but if you go to Advanced Wipe in TWRP and wipe everything, then flash each .img file again from Fastboot there should be no way SuperSU could survive that.
The answer is to dirty flash the ROM in recovery. You need to overwrite the system and boot partitions with the lineage release. This does not mean using a lineage OTA.
But I'm at a loss why why you indicated indicated the N6 is;
Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
Click to expand...
Click to collapse
Did you revert to stock?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Yes, I reverted to stock Android. I read somewhere here that it was the only way to remove SuperSU. And, yes, I did dirty flash. I wiped each partition one by one before flashing. After each wipe, I rebooted to recovery until all were wiped. I also deleted the SuperSU folder. And every time I rebooted into recovery, I'd go to File Manager and the SuperSu folder would re-write itself.
You're mixing and matching things here.
The supersu folder will show up in TWRP even if you've never rooted the device.
A modern, systemlessly rooted device modifies the boot image, not the system partition. By dirty flashing the ROM, you replace the modified boot.img with the "stock" ROM version. Stock is in quotes because it's stock to the custom ROM, not meaning a stock ROM.
Wiping each partition is not a dirty flash. If you were going to dirty flash to remove root, all you needed to do is remove the relevant supersu script in system/addon.d, reboot to recovery, flash the ROM normally, wipe data and cache then reboot.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I forgot you were originally taking about lineage. Using lineage's su.zip, you will (I think) be rooted in system mode, so dirty flashing will result the original system.img reverting the changes.
As stated above, in systemless it's the boot.img that needs to be reverted.
As an additional caveat, if a third party kernel has been flashed, AND you have systemless root; first you dirty flash the original ROM, then re-flash the kernel to unroot.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
The last "good" flash I completed was with Lineage nightly 4/30. Once I realized that there were still issues, I completely wiped all 5 partitions one at a time (Dalvik/Art, System, Data, Internal Storage, Cache) from TWRP. After rebooting to bootloader, I then fastboot flashed factory 7.1.1 images one at a time (bootloader, radio, boot, cache, recovery, system, and userdata). I then rebooted to stock recovery and selected Factory reset, then rebooted system. 7.1.1 loaded without a hitch.
I just finished flashing TWRP recovery back, wiping all 5 partitions again, and adb pushed only Lineage Nightly 5/15, and MindTheGapps zip's to sdcard and flashed them.
Besides the problematic SuperSU zip (previously installed), those were the only zips and images that were flashed to the device.
I would think after all that, SuperSU would be gone! Your saying I might also have to re-flash the kernel? Wouldn't the latest Lineage zip resolve that?
Please quote the part where you think I told you to do anything more than dirty flash the ROM. I'm trying to figure out why you think I said flashing the lineage ROM is insufficient.
What you have done is serious overkill, but does get the job done (removing root).
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
First, let me preface that I am new to flashing ROM's. Second, I was unclear of the differences between dirty and clean flashing.
Third, I didn't realize that the "supersu" folder at the root of the device, is persistent. Had I known this in the first place, none of this conversation would really be necessary as I believed that SuperSU wasn't going away.
Fourth, nowhere do I even remotely insinuate that flashing a Lineage ROM is insufficient.
Fifth, here is your quote from post #6 where you mention the possibility of flashing more than the ROM, "...first you dirty flash the original ROM, then re-flash the kernel to unroot."
Finally, any forum I've been a part of, details have always been a prerequisite to receiving feedback. All I've done here is provide those details so that anyone, (not just you) could be best informed of my situation.
I do agree now that what I've done with my device is serious overkill. Everything I've done thus far has been done from the advice of other Devs or experts here on XDA, Reddit, or other forum posts somewhere on the internet. However, I, in no way, intentionally or unintentionally tried to undermine your expertise (as I sensed you have in your last post). I am merely a noob in the world of custom ROMS, and all I seek is advice. And for the advice that you provided I am grateful, and I sincerely thank you. If I offended you or made you feel your advice and expertise was inadequate, I do apologise!
Again, I thank you, as well as all of the Developers and experts here on XDA for your knowledge and advice. I look forward to possibly talking to you again in the future.
As, in the future, you read solutions to problems you post, please keep in mind that it's not uncommon for people to post complete explanations that may not totally apply to the situation at hand. There are a couple of reasons for that.
One is that it can help develop understanding of the larger picture the specific problem fits into.
Another, and often why I almost always expand answers, it so future readers of a thread get a more complete view of the process under discussion.
In the case where I expanded on the idea that if an additional custom kernel is used on top of a custom ROM, then that has to be taken into account when removing root. I did make an assumption that if you didn't use a 3rd party kernel, then you would understand that didn't apply to you.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
alryder said:
This seems like overkill but if you go to Advanced Wipe in TWRP and wipe everything, then flash each .img file again from Fastboot there should be no way SuperSU could survive that.
Click to expand...
Click to collapse
BTW, thanks for your input. This Definitely should take care of it. This would have been much easier had I known that a supersu folder existed at the root of the device. For all the times I've flashed my phone, I've never noticed it. Lesson learned. Thanks again.
Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!