Running CM13. Went to update SuperSU to 2.46 using the flashable zip (Have TWRP), and am now stuck in a bootloop. Cleared cache/dalvik and still stuck here. Any ideas?
I have to wonder why you wouldn't just use the built in cm root manager. If you didn't know, enable developer settings and you'll see it's baked right in those options.
Related
Hi
I was running 5.1 stock and rooted with supersu.
I've manually flashed 5.1.1 and that seems to have gone well..the phone is up and working.
I downloaded SuperSU 2.46 and flashed it via TWRP, phone rebooted and I had a superSU icon.
When I click on it I got an error saying no binaries are installed.
So I booted to TWRP and flashed it again, then when exiting TWRP I was asked if I want to install SuperSU so I said yes.
Phone rebooted and now I have a superSU installer icon. I've run that and selected TWRP.
It downloaded a file, rebooted to recovery, flashed and restarted the phone.
The phone is backup but not rooted. I still have a superSU installer icon..
How do I root this phone ?
Thanks
I accidentally wiped system using twrp and now it says no is installed. I had rooted before and when I tried to install a custom ROM using twrp. It failed. Whenever I reboot, it shows device not rooted swipe to install supersu . I swiped with no use. Also installed SuperSU 2.5x beta. Install succeeded. But still shows device not rooted. Please help
If you can access recovery, try any custom rom (CyanogenMod is recommended) and then flash Chainfire's systemless root.
I flashed official ROM and it worked.
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
i was getting the same thing on my 1st flash into 13 from moar rom 7.0 but did some reseach and fixed it by wiping the dalvik and cache before the flash and then installed cm13 and then the gapps 6.0 stock all in twrp and fyi you dont need super su just unlock the developer mode and go to the bottom and turn on root access it made me crash my system after i installed new supersu hope these helps
you dont want to be on a MM baseband. Flash a LP tar.md5 in odin and reinstall CM13
I successfully updated from the August Oreo image to the October Oreo image today and installed the latest TWRP recovery image. Then I tried to install SuperSU (SR5) through TWRP, which seemed to go well, but the app wasn't added to in the app drawer, and none of my apps had root access. I rebooted into TWRP and reinstalled SuperSU (SR5), and still, the app wasn't listed in the app drawer. Then I rebooted into TWRP and installed SuperSU (SR3), the last version I'd installed before the October update that worked, and that didn't get added to the app drawer either. Rebooted, reinstalled SuperSU (SR3) in TWRP, and still, not listed. I then uninstalled SuperSU from Oreo, where it surprisingly was listed, and installed SuperSU from the Play Store. Then I opened SuperSU and it needed to update the binary, which I let it do normally (not via TWRP). Now My phone has been booting with the G logo for the past 10+ minutes. What should I do?
After 20 minutes, I rebooted via ADB and now I'm back at the G loading screen with the colorful G with a moving status bar underneath (not the dots).
After another 10 minutes with the colorful G with a moving status bar underneath (not the dots), I tried to reboot into recovery so I could try manually installing SuperSU via TWRP again. I found that there was no recovery partition installed.
Ended up reflashing the October Oreo update (OPR3), which worked on the first try, then reflashed TWRP, SuperSU, and suhide, one at a time. All of that worked, and now everything seems to be working.... Not sure what went wrong, but glad everything is back to normal and no data was lost!
Why do people still use SuperSU? Magisk is a much better alternative and I don't trust it now it's in the hands of some Chinese company.
I didn't know about Magisk... Wiping and installing now...
I was stuck with a working(sort of) root after dirty install 8.1->9.0 sideloading official OTA file. I tried to remove the magisk using the official uninstaller. Reinstalled Magisk 16.7 + APK 5.8.3(129) and was slapped with a bootloop.
Used uninstaller again and was able to boot fine, but no root(as expected). Reinstalled magisk and was stuck in a bootloop again.
Fix that worked for me:
1. Sideload latest OTA(9.0). (again)
2. Boot into it.
3. Reboot into TWRP(I load my TWRP using fastboot, not installed to recovery partition)
4. Sideload Magisk 16.7
5. Should work now.
Hopefully it fixes your bootloop.
I've been having a different problem. I'm able to install magisk 16.7 by flashing the patched_boot.img. Everything seems to work fine for a while. But after rebooting the phone a few times it eventually gets into a bootloop. Anyone else having this problem or know how to fix it?