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...
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've been trying to root my Honor 6 Plus PE-TL10. I've unlocked the bootloader and installed TWRP. Till there, everything works fine, but as soon as I install SuperSU, my phone won't boot up anymore. It passes the bootloader, but gets stuck at the animation. I've tried different SuperSU versions, clearing the cache and dalvik chache after rooting, and I've even wiped the data partition to see if it would help, but it didn't. I've flashed the most recent firmware version available, namely Android 6.0 Marshmallow.
I got the stock firmware from this site, and I used this tutorial to root my device.
I know how to get out of the bootloop, namely by rebooting to download mode and installing the stock ROM, which I already have on my SD card. I'm looking for a way to root my phone without getting stuck at boot. Does anyone know how I can successfully root my device?
Update:
I've tried the 2.67 and 2.65 versions of SuperSU as well. Unfortunately, they gave the same result. The device gets stuck at the very end of the boot cycle, as it does reach the point where it can transfer data with my computer. I've tried using the Honor 6 Multi Tool, but the program doesn't support the Honor 6 Plus on EMUI 4.0. When I select EMUI 4.0, the program returns to it's main menu without installing anything.
Update:
I've heard that Android 6 doesn't support system rooting, and that systemless rooting should be used instead. I'm now looking for a way to force-install SuperSU as systemless. In my installation logs, it always said that it used system rooting.
use the honor 6 multi tool to root and fix any bootloops its easier, its somewhere on this forum i cant remember where im on supersu 2.67 any higher and it bootloops for me
I've tried that just now, but everytime I select my EMUI version, the program goes back to it's main menu. The first time I started the tool, it gave an error message saying that some file could not be found. Now, it gets stuck at updating.
I've tried selecting EMUI 3.0 instead. It did install the recovery, but my phone restarts every time I try to boot to it.
Until now, I've laways tried the most recent version of SuperSU. I'll try version 2.67. I've also heard of a new superuser package, PHH's Superuser. Do you know if that one works with the Honor 6 Plus?
I've managed to find an answer on my own. Apparently, I needed to install SuperSU as systemless. By default, it installed as system, so I used this tutorial to force-install it as systemless: http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
sorry i didnt get notified when you replied to me. glad you fixed it
what happened with you?
and how did you let your device work again?
did lose all of your data?
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
den_zel said:
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
Click to expand...
Click to collapse
If you can get into TWRP dirty flash your ROM. Otherwise change to the other partition either via TWRP or via fastboot set_active A (or B).
Magisk is only installed on the active partition meaning switching it would let you boot into a non-rooted OS.
Apps etc. should be the same as it uses /data. Only /system and some other partitions are A/B.
Yesterday I got the notification to update LineageOS, so I downloaded the update through the Installer application, and rebooted the phone when prompted. After this it started bootlooping and I couldn't get into the system.
Since I don't want to lose the data on the phone, I tried reflashing the latest rom and older versions through TWRP, including the one I first installed, but after flashing it still loops. I had Magisk installed so I removed it but that didn't help. When I reflashed the rom, I also flashed the 'copy_partitions.zip' in the lineageos install instructions still to no avail.
I also tried the method here but the wipe option does not display the system option, so it didn't work.
Any help?
Hello
My phone has been rooted for a while now (without TWRP as it wasn't available yet back when I rooted it), but magisk suddenly got issues once I've tried to update my phone.
I downloaded the update KB2003_11_C.33 as soon as it was available on the Oxyen updater app, then i've proceeded to follow the usual steps to preserve root during the OTA update:
restored image in the magisk app -> started the update -> installed magisk to inactive slot in the app
I don't know if it had a real impact, but this time I've done the update through the settings of the phone instead of through the "System Update" app.
Once the phone turned off and back on, it was stuck in a bootloop (it rebooted maybe 3-4 times) until I pressed the buttons to access the Recovery mode, then I just booted it again and it somehow worked just fine. There seemed to be no issue until I opened the magisk app and saw the message "The hidden Magisk app cannot continue to work because root was lost. Please restore the original APK" then I've also noticed that my OxygenOS version was KB2003_11_C.21 instead of 33, so the update basically failed.
I'm not sure if it matters, but I've recently installed modules (Advanced Charging Controller, BlockAds and Universal SafetyNet Fix), magisk manager was hidden (I had access to the app through a fake "settings" app) and I also had zygisk, as well as the deny list enabled to pass SafetyNet.
I've uninstalled/reinstalled Magisk manager, patched the boot.img with it (extracted from the ZIP of my current firmware) then flashed it with adb (several attempts), but magisk manager just doesn't detect anything as it keeps displaying "Installed N/A". I also tried to update my phone again to KB2003_11_C.33, which worked fine this time around, but patching the image and flashing it still didn't do anything.
I don't know what to do anymore to root my phone, I thought I didn't need to factory reset since the bootloader is still unlocked, but maybe I have no choice now.
I found the issue myself actually, I had no choice but to install unofficial TWRP to properly uninstall magisk then to reinstall it and root the phone.
You can close the thread ^^