Database Develop

There is no SU binary installed. Help

My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.

I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.

Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00

Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs

[Solved] Magisk?

Solved: See this post.
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
Sony Devices: If you're using stock kernel, it is using Sony's special ELF format. Magisk will repack it to standard AOSP format, which requires your device to be unlocked.
Click to expand...
Click to collapse
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?

I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.

Chamelleon said:
I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.
Click to expand...
Click to collapse
I guess you must be lucky then since Chainfire has advised Xperia users to stay on 2.79, as per the news article I linked.
Still, regardless of whether SuperSU works for some people or not, I'd still like to find out if MagiskSU is a viable alternative for Sony devices and what the correct procedure is to install it and retain all the phone's features.

Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.

Chamelleon said:
Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.
Click to expand...
Click to collapse
Possibly; can't remember to be honest. Anyway, flashing back to 2.79 fixed the boot loop and I've disabled auto-update until Chainfire says otherwise.
I still want to learn about Magisk though; not keep discussing SuperSU
I found a few bits of info on the subject:
RootKernel can apparently repack the stock kernel with a DRM fix so that all the DRM features can be restored with an unlocked bootloader.
BootBridge can install Magisk without repacking the ELF kernel in AOSP format, which the author says is preferable. However, BootBridge itself requires an unlocked bootloader so the DRM is still an issue I guess... <-- This is only meant for specific older devices; not the Z3C.
Magisk Patch claims Magisk won't work without disabling Sony RIC and provides a fix if you haven't used RootKernel already.
Trying to piece it all together is a little confusing so if anyone has actually done it, I'd be interested to hear from you.

Do we even need the SuperSU updates? 2.79 works fine for me without any issues plus the new versions are maintained by the Chinese company (I'm using some different version compiled by Chainfire himself). The only problem is the update notification in Play Store tho....

nogaff said:
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?
Click to expand...
Click to collapse
actually, i have my DRM partition and Magisk on my z3c UB. Here is what i did, first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition. oh! magisk hide works properly as well giving me full access to SafetyNet.

espaciosalter20 said:
first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition
Click to expand...
Click to collapse
I finally got a chance to try this out and I'm not having much success to be honest.
I'm starting off with an unlocked bootloader and flashing stock MM 23.5.A.1.291, then flashing TWRP.
In TWRP, the current version of Magisk (v14.0) refuses to install; it just complains about Sony ELF32 format and instructs me to use BootBridge, which is only supposed to be required for older devices like the Z2.
Anyway, I tried installing Magisk via BootBridge and it claims to have installed successfully, but then Magisk Manager says Magisk is not installed when I boot into Android (yes, I've rebooted a couple of times as well).
Next, I started over from the beginning and tried Magisk v13.3 instead, which at least begins to install, but then fails to patch the boot image.
Does anyone have a working method they could describe here?

Solution
I figured it all out by myself in the end. For anyone else having trouble, here's what I did:
Made sure I had a backup of my DRM keys!!! I already had one from when I first rooted my phone on KitKat, but I decided to make another backup using Universal TA Backup v2, just in case anything was wrong with the original.
Obtained the official Marshmallow 23.5.A.1.291 firmware from XperiFirm, created a .ftf file with Flashtool, unlocked the bootloader on my device and flashed the .ftf file via Flashtool.
Flashed TWRP custom recovery via fastboot.
Extracted the stock kernel.elf boot image from the .ftf file using Flashtool.
Ran ta_poc on the kernel.elf file, answering "Y" when prompted to disable Sony RIC*. This produced a repacked boot.img with the DRM features added back in.
Copied the boot.img to my SD card.
Booted to Android and installed the Magisk Manager apk.
Used the "Install" button in Magisk Manager and selected the boot.img on my SD card.
Noted the location of the patched_boot.img that Magisk Manager created, then booted into TWRP and flashed patched_boot.img.
Booted back into Android and checked Magisk Manager status.
My device is now fully rooted, has all the DRM features intact and is passing all SafetyNet checks.
As an alternative to steps 7-9, you could simply flash the boot.img from step 6 via TWRP and then also flash the Magisk zip file via TWRP. You'd end up with exactly the same result at step 10.
I believe you could even complete the installation without TWRP or any custom recovery at all, by using Magisk Manager to create a patched_boot.img, then copying it to your PC and flashing it via fastboot.
* Disabling Sony RIC in my boot.img was what solved all my problems. This thread suggests you don't need to do that any more, but I couldn't get it to work without doing so.

Hi, I recently installed magisk 14, I get it to work. However, somehow it broke my wifi and LTE functionality. DNS NOT FOUND. I have a m4 aqua with 6.0.1 ver.1.33. Do you have any idea what could be the cause of this problem?
Enviado desde mi E2306 mediante Tapatalk

any know magisk for Z3 Compact Docomo MM 6.1 Bootloader Lock ?

Hi nogaff,
I tried your solution but there are two difficulties I can't resolve:
1) Where can I download a valid TWRP image for the Sony Xperia Z4 Tablet? My search in the internet was without success, and TWRP doesn't seem to support this device.
2) I used the same procedure to patch the kernel:
TA_POC'd the kernel with disabling DM-verity and disabling Sony-RIC
copied this image to a SD-card
put the SD-card into my SGP771
patched this image with Magisk 22.1 (this version of Magisk supports officially my Android 7.1.1)
flashed this image using FlashTool (because I don't have a TWRP recovery for the SGP771) - flashing ended without error!
BUT​​The SGP771 stucks in a boot loop!!!​​Can you tell me if I forgot something?​
Regards
Ansgar

Help ! Problems with Magisk, root and OTA.

Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.

Ibra2800 said:
Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.
Click to expand...
Click to collapse
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka

urbanboymne said:
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka
Click to expand...
Click to collapse
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.

Ibra2800 said:
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.
Click to expand...
Click to collapse
No you cant. You are lucky you didnt brick your phone. Flash uninstaller and than try OTA update. Download TWRP for your phone/new rom and flash working Magisk again and root phone. Is simple. Of course, if you are on TWTP you will be unable to OTA update your phone. You need stock recovery or wait for ZIP flash file of newes rom
Poslato sa VTR-L29 uz pomoć Tapatoka

@Ibra2800 There's no need to uninstall Magisk to update with an OTA. There are however a few prerequisites that need to be fulfilled:
You need to have the stock boot image installed. That can be done by using the restore images option in the Manager or manually flashing the boot.img file with fastboot or equivalent.
You need to have the stock recovery installed. This means the OTA will fail if you have TWRP or another custom recovery installed. Either keep the stock recovery installed and only boot the TWRP image when necessary (the fastboot boot command), or you make sure you restore the stock recovery image when you need to update.
You also need to have a few important partitions on your device untouched. Those include (but may not be limited to) /system and /vendor. If you've so much as mounted these as rw, the OTA will fail. This one can be tricky, because if an app has root access it can easily do this without you noticing.
If you manage to fulfill the above, you should be able to update your device. If the A/B method from @topjohnwu's OTA tips didn't work, use the general case instructions instead.
Right now, it sounds like you need to start from scratch though...
If you can get a hold of a full firmware file for your device, you might be better of flashing that instead. Or, wait for a flashable update, as stated above. And if you want to reinstall Magisk you might have to first uninstall it, to start clean. Use this uninstaller.

Thanks for trying to help me
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.

Ibra2800 said:
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.
Click to expand...
Click to collapse
The uninstaller is a zip that you flash in a custom recovery (i.e. TWRP) to uninstall Magisk completely. You should also be able to use the "Complete uninstall" option in the Magisk Manager.
TWRP is a custom recovery that you can use to make backups of your device partitions (so you don't loose any data if anything goes wrong, it's highly recommended to make regular backups in some way) and install custom ROMs and other modifications to your device. You can either install it permanently or just boot it whenever you need it (there are likely gonna be guides about this in your device's forum).
Since you seem to be quite new at this, I would suggest that you take some time to browse through your device's forum and familarise yourself with things like ADB, fastboot, custom recoveries, custom kernels, ROMs, etc. And if you have more questions like this, it's often best to ask them in the device forum, since there sometimes are device specific things that need to be done for everything to work right.

Stuck in Download mode bootloop after updating from v20.x to v21.x

Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.

n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there

Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?

@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk

If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.

Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.

I think it says Unsupported/Unknown image format

Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).

Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?

Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.

Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you

n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.

@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...

Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.

lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".

Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.

lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).

Thanks for the help guys, had to flash the ROM, now its working again.

Downgrade to 20.4 without custom recovery

I have a car Android device in which I am able to install magisk extracting boot.img and then patching it. I was having some problems and have reset, and now I am having some issues:
I flashed latest magisk and got bootloop, so I managed to install 20.2 version and it gives superuser access, but I can't install no modules (it seems to install them but they are not there after a reboot).
I think before the reset I had 20.4 installed, but I don't know how to update my version to 20.4, it always offers me latest version, which ends in bootloop. I don't have access to any custom recovery, so I think the only way to make it work is to update through a custom channel pointed to 20.4, but can't figure out how to set it.
Any help would be appreciated.

Ok, I realized a simpler way to do it: I downloaded 20.4 zip and flashed it through magisk. Now it works perfectly, but when I use Viper4android together with sygic, sygic crashes.