Database Users

D802 CM13 SuperSU binary needs to be updated

Hello!
I have spent around 5-6 hours tonight fixing my phone. Before it had CM13 working just fine but my recovery didn't work (got an error when trying to enter recovery). I manged to solve that problem by doing lots of things I have already forgotten about now and to be honest I didn't really have any idea what I was doing as I am very new to this and have no knowledge about it.
Right now my CM13 works just fine. No problems booting. My recovery works just fine. I have CAF bootstack and the latest TWRP recovery that was mentioned in the guide. However, my SuperSU doesn't want to work properly. At first, I had to download the SuperSu app from Play Store. I don't know if that's how it is supposed to be. When I start the app it says "The SU binary needs to be updated. Continue?". I press Continue and it says "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?". I have two options: "NORMAL" and "TWRP/CWM". If I press "NORMAL" it proceeds to installing and the circle is spinning and spinning... "Installing, please wait..." After about 30 seconds it says "Installation failed! Please reboot and try again". Rebooting and trying again doesn't help. If I try the TWRP/CWM option it reboots me into TWRP Recovery but nothing happens there. If I reboot system from recovery the problem remains. I googled a bit and found some thread where they said I needed to download some SuperSU zip-file and install it from recovery. I did that but that just broke it even more giving me some error saying SuperSu wasn't installed at all, or something like that. I ended up re-rooting the device and installing bootstack, CM, and GAPPS again.
I have enabled root access in the CM developer options menu, for both apps and ADB. I have downloaded Root Checker and it says i am rooted. In download mode it also says rooted.
Is there some step I have missed? Please help me. I just want CM13, Recovery, and SuperSU to all be working at the same time. Not just pick two, like I have done before.

I had the same problem on my d802. That thing you did in development settings worked for me. Is supersu so neccesary?

"Installation Failed" MI A1 OTA UPDATE

Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).

Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....

Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.

Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.

Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool

RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!

Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data

I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857

The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).

1+5 Home button doesn't work after recovery and OTA failed.

1. H2OS 3.5.0, BL unlocked., rooted by magisk. It worked fine for 1 year. Today, I tried to updated magisk from 17.1 to 18.0, after reboot, it stucks at startup.
I have to use TWRP to do a recovery. But after that, the "Home" never works again.
2. There is a OTA update: H2OS 5.1.2, but the update always failed.
I tried do official recovery by flashing stock-recovery.img. Then I tried OTA update again, it still failed.
3. I tried lock BL again, but after that it can't boot. I have to unlock BL again.
Anyone can help?

> Is it just the fingerprint scanner?
> Have you tried disabling lockscreen security? If not, try setting it to 'None'), reboot your phone, and try to register your fingerprints again.
> What happens when you use the onscreen navbar?
Last resort: did you backup your data? I suggest wiping completely and flashing the latest official ROM (link: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 , use the full zip).

Bluetooth not working after Magisk installation

Hey everyone,
I have a bit of a problem.
I used the root method that doesn't disable stock OTAs, but noticed that whenever I'm using a Magisk patched boot image (hence I have root access), my Bluetooth doesn't turn on, and sends me 'Bluetooth keeps stopping' error messages.
Tried on 8.0, 8.1, 9.0, the problem persists.
Stock ROM + kernel, no TWRP
What could be the solution?
Please help, I want root access but I'd prefer staying on stock.
Thanks in advance.

Check if you using proper boot image to create patched_boot. If you use older version, wifi and bluetooth may not work.
Try flash stock boot, than fastboot boot patched_boot, than install magisk with magisk manager (full install), than reboot. Not flash patched_boot with fastboot, just boot phone with it.

Help, t380 unable to root

Closed Per OP Request
(ONLY READ IF YOUR GONNA TO REPLY!!!!!!)I had to reset my device using the format data option in TWRP, now if TWRP is installed, the error "CANT GET FDT" shows up and the tablet goes into download mode, how do i fix this? I reflashed stock in Odin and it is doing the same thing when flashing TWRP. I have been flashing t380_pp.img, then magisk I even tried magisk first and it is still doing this, I also flash rmm bypass and the forced enycpriton diabler. How do I fix this?

PLS REPLY

Do not reply, I fixed it by using a differnt BOOT.IMG