Hi guys, I'm actually on stock rom (android 6.0.1) with Androplus kernel v40 on my Sony Z5 Compact.
I currently have SuperSU 2.78 SR3 and Xposed systemless v86.2. I also have Magisk v8 installed.
I want to get rid of Magisk (I know it's possible), but when I flash Magisk Uninstaller zip, my root is gone. If I flash supersu again (any version, even 2.76),it tries to install systemless but it's not installing su binaries (a problem with ramdisk).
I can't uninstall Xposed ; if I have Magisk installed, Uninstaller is working but after reboot, xposed is still here. If I uninstall Magisk, Uninstaller doesn't work and ask for Magisk.
I've tried to flash again Androplus, but I still need to flash Magisk in order to avoid ramdisk error.
I've tried to restore Boot from the Stock Backup (backup done just after clean flash of Android 6.0.1) with TWRP : I got stuck on Android Startup (after the app optimization), so I go back to today's Boot backup.
What can I do to uninstall Magisk and use systemless root? Use another kernel?
Thanks a lot
UPDATE 1: I've tried to update to Magisk v9 but if I do so, I can't install supersu (sr1 3 or 4).
UPDATE 2: I've tried to install v7 or v9, but when I Uninstall, v8 is still here.
Which files/folder must I remove to get rid of magisk v8?
UPDATE 3: I want to upgrade to v9 without any traces of v8, or totally remove Magisk to have only root and xposed
It was initially posted here
Bump please
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
At this point, your boot partition is hopeless mixed with so many different installs, many of them will not play happily with the other unless installed in the right order.
Your best bet is to start over with a stock ROM completely, or at least a stock boot partition. Then install one by one the mods you truly need. In this case, it seems like root and xposed are you highest priorities.
Hi, thanks for the reply.
Should I totally clean install, or just the boot partition?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Thibault1171 said:
Hi, thanks for the reply.
Should I totally clean install, or just the boot partition?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
Try the boot partition first, no harm if it doesn't work first with that.
Though Run magisk uninstaller before that. And if course do a data backup.
Thanks. Uninstaller aren't working. Maybe there is a specific one for v8
Sent from my Sony Xperia Z5 Compact using XDA Labs
Thibault1171 said:
Thanks. Uninstaller aren't working. Maybe there is a specific one for v8
Sent from my Sony Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
It won't make a difference if you are back to stock boot. There probably will be an extra magisk folder in /data which you can delete manually afterwards.
. (TT)klv6+! D,
Related
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!
BUTThe SGP771 stucks in a boot loop!!!Can you tell me if I forgot something?
Regards
Ansgar
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Nope, just flash the latest magisk zip and it's done. But yes, you also have to install the Magisk Manager when you boot up after flashing the zip.
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
equlizer said:
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
Click to expand...
Click to collapse
Hm... Absolutely no issues on my OP3T, OOS 4.1.6 and Franco Kernel r25 with Magisk v13.1. Maybe you have a module causing issues (long shot, I know)?
No issues here with Open Beta 10, Stock Kernel, Magisk 13.1 and Manager 5.0.4.
Root is working, passes SafetyNet with all modules activated and properly hide root from my Banking App. All good!
Akhayev said:
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Click to expand...
Click to collapse
Just Simple flash the Magisk v13.1 and install the latest magisk manager v5.0.4.
I feel you should flash magisk immediately, while flashing the ROM through custom recovery. Install magisk manager after first boot.
You can do a dirty flash without formatting anything to get rooted.
Sent from my OnePlus 3T using Tapatalk
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Jô$èph D said:
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Click to expand...
Click to collapse
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
Ok then ill give it a shot
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
I need to get stock boot img I don't have it pls help
Jô$èph D said:
I need to get stock boot img I don't have it pls help
Click to expand...
Click to collapse
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Can you pls link me the post for that file
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks
Jô$èph D said:
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks and I will stay active on this and other threads
Click to expand...
Click to collapse
Sure thing. See you around!
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
I wanted to use systemless xposed framework because the official version is not supported on my device. Also I wanted to use the modules that are specifically for magisk
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
Systemless xposed does not work either found this out earlier today device would not boot after installation of xposed through magisk
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
yaconsult said:
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
Click to expand...
Click to collapse
I will have to see if it works when a new version of magisk is launched.
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
netgar said:
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
Click to expand...
Click to collapse
Probably not waiting long enough after reboot.
ashyx said:
Probably not waiting long enough after reboot.
Click to expand...
Click to collapse
After flashing xposed in twrp. I am unablebto boot at all.
netgar said:
After flashing xposed in twrp. I am unablebto boot at all.
Click to expand...
Click to collapse
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
ashyx said:
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
Click to expand...
Click to collapse
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
netgar said:
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
Click to expand...
Click to collapse
You don't need to decide. The latest version is dynamic and will install the correct version.
Guys I have Xperia Z3 compact and rooted+twrp+su since 3 yrs and all going good. I want to shift to Magisk owing to its capabilities over Su.
Have these queries:
Does latest Magisk works with lock BL?
If not then can I later re-lock my bootloader (by restoring TA.img using iovyroot/Backup-TA) later after Magisk succeeds? Will it keep Magisk working properly or will I run into issues like boot loop or no root?
To remove existing SuperSu shall I use the inbuilt Root uninstaller inside Supersu or do you recommend any other flashable zip?
If via flashable zip, then once I remove supersu+root, do I immediately need to flash Magisk or first reboot and then again in twrp do Magisk flashing?
I'm asking all this as I dont again want to brick my phone and go through the pain of reflashing whole rom+root+recovery etc. To save my time.
Thanks and awaiting answers in the same order.