Related
This patcher is now outdated. Use the new SuperSU instead. http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This zip is a systemless version. That means that you'll get root and be able to use it normally, but your system partition will not be modified, like in normal root methods. Only for Marshmallow.
Keep reading for disadvantages and advantages
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
If you have rooted before, flash the system partition (or reinstall the ROM) before flashing this zip.
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Reboot to TWRP. If it asks you whether you want system to be mounted as r/w, and if you want to take OTAs later, choose to keep system read-only (this will replace TWRP with stock recovery on reboot).
Flash SuperSU-v2.56-20151030013730.zip
Reboot
TWRP will say that you are not rooted, just ignore that. Do not tell it to root it.
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Well done bro!
I'm just waiting for this
Help regarding installation
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Good.... Thanks for posting
metaspook said:
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Click to expand...
Click to collapse
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
<accidental double post, sorry. Can't delete>
kalpitandroid said:
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
Click to expand...
Click to collapse
You need to install a custom recovery first. Go to the Android One (First generation) General forums on this site. You'll find a how-to at the very top of the list of threads. Once you have a custom recovery, flash this using the "install zip" option.
out386 said:
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
Click to expand...
Click to collapse
Hmm... gotcha now.. Good work!
If u ever need any help just pm.
Thank you...
out386 said:
<accidental double post, sorry. Can't delete>
Click to expand...
Click to collapse
As far as I know there is no TWRP for Android x86_64 for PC. How could I ever get Magisk 14 installed?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I'm thinking on using it on Bliss which is running Nougat 7.2 x86_64. I really want root but some apps will not work with root.
Magisk manager has an option to install magisk without recovery, of course this means you will need some sort of root solution before hand
Xmaster24 said:
Magisk manager has an option to install magisk without recovery, of course this means you will need some sort of root solution before hand
Click to expand...
Click to collapse
No it doesn't. It means you'll need a copy of your device's boot image and some way to flash it to your device after the Manager has patched it. No root required...
Didgeridoohan said:
No it doesn't. It means you'll need a copy of your device's boot image and some way to flash it to your device after the Manager has patched it. No root required...
Click to expand...
Click to collapse
Well he is talking about a pc which does not use a boot image the same way a normal device does, anyways Bliss rom comes with root.
EDIT: actually now that you mention that I was not aware you could select a boot image to patch in magisk manager, if he does that he can just copy the boot image to wherever Bliss rom stores the emulated boot image
Xmaster24 said:
Well he is talking about a pc which does not use a boot image the same way a normal device does, anyways Bliss rom comes with root
Click to expand...
Click to collapse
I know... So in other words it's probably not gonna happen. Magisk relies entirely on patching the boot image.
My answer to your post was simply to prevent any future misunderstandings for anyone reading it. :good:
Well I think RMXtools or similar is used to mount the .img file and root it with SuperSU for Android x86 for PC. Could this also be done for Magisk?
I would need to know exactly where the files would need to go I guess and also which image to mount for Android x86 for PC
saulin78 said:
Well I think RMXtools or similar is used to mount the .img file and root it with SuperSU for Android x86 for PC. Could this also be done for Magisk?
I would need to know exactly where the files would need to go I guess and also which image to mount for Android x86 for PC
Click to expand...
Click to collapse
And that was made with the system or systemless type of install for SuperSU? Magisk can only be installed systemlessly...
If it's possible, you can probably find the info you need here: https://github.com/topjohnwu/Magisk
Android x86 has no boot partition. It contains kernel binary and initrd image.
Didgeridoohan said:
And that was made with the system or systemless type of install for SuperSU? Magisk can only be installed systemlessly...
If it's possible, you can probably find the info you need here: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
For PC installations of Android x86 you can edit the system and data images with that tool. I believe root is achieved by editing the system partition.
Bliss already comes pre-rooted or without root, depending on which *.iso is used for the installation. I picked the rooted image and tried to uninstall SuperSU which looks like I did successfully, however this app I have still detects that the device has been modified or is rooted it says.
I will install the non-root version today and see if the message goes away. If it does then I know there must still be traces of root on the other image. Now the ideal thing would be to get Magisk somehow installed because then I could hide the root which seems to work for the apps I have tried it on on my Shield Android TV Box.
**Edit**
Well Magisk on Android x86 sure seems possible judging by the posts and screenshots from youling 257
https://groups.google.com/forum/#!s...elevance/android-x86/omGg6QZlEGc/H4_QXjhQBwAJ
However this all seems way too complicated for me.
https://groups.google.com/forum/#!msg/android-x86/311n2ivCLYw/hfIZnqkXBwAJ
I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install script and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...
https://forum.xda-developers.com/phoenix-os/phoenix-os-news-qa--development/magisk-15-3-t3735310
Like the title says. I'm trying to install Magisk Root V16 and I read through everything. Still I don't get it. I even search on youtube and it doesn't say exactly what to do only to say read the entire post on xdadevelopers then download a few things on the phone and still nothing.
All the instructions you need are in the release thread.
Before you do anything you need to unlock the bootloader, so if you haven't already, start there. Keep in mind it'll most likely wipe your device, so make sure to have a backup.
Option 1:
Download the Magisk zip and flash it through a custom recovery, like TWRP. Done.
Option 2:
If you don't have a custom recovery, place a copy of your stock boot image on your internal storage, install the Magisk Manager (from the release thread), choose the option to install be patching the boot image (in the Manager), and finally flash the patched boot image (you'll find it in the MagiskManager folder on your internal storage) with fastboot or whatever is applicable to your device. Done.
If nothing works, make sure to provide as much detail as possible. Here's some useful reading about common issues and what logs to provide, etc:
https://www.didgeridoohan.com/magisk/Magisk
If you need help with the basics (bootloader unlock, custom recovery, etc), do a search here on XDA. You can usually find some good info that way:
https://forum.xda-developers.com/search?query=BLU advance 5.2
Is there a version of Magisk that works on the realme Pro 5g RMX2075?
I tried the version 20.4 after unlocking the bootloader and installing recovery-TWRP-3.4.1B-04-17-realme-x50-pro-wzsx150, but it fails the signature. If I disable checking the signature on TWRP, it loads but bricks the phone until I re-install the stock boot.img, and then Magisk is not installed.
Providing the install log is usually a good first step when troubleshooting.
And, if you can't get the stable release installed it's usually a good idea to try the Canary release since it might have been updated with more compatibility.
Didgeridoohan said:
Providing the install log is usually a good first step when troubleshooting.
And, if you can't get the stable release installed it's usually a good idea to try the Canary release since it might have been updated with more compatibility.
Click to expand...
Click to collapse
I'm not sure how to find the log, but I'll try the Canary release first, thank you very much for the quick answer.
Being a bit paranoiac (a LOT in fact), I have 2 RMX2075, so bricking is not catastrophic. I can take my time to find how to unbrick it.
Since some manips like unlocking the bootloader wipes everything, it make easier to restore using the clone phone app.
I know, I know, I should get a life...
Edit: just saw the log was a link, I will provide with the canary if it fails too.
Ok, some info I failed to provide:
realme X50 Pro 5G RMX2075
Android 10
realme UI version 1.0
TRWP installed with recovery-TWRP-3.4.1B-04-17-realme-x50-pro-wzsx150, and with the file EN_Recovery-twrp-oneclick-EN.bat.
I need to run this .bat file every time I want to use TRWP, Up (or Down) + Power does not work and gives me the standard bootloader, which I unlocked with the deep testing app.
With Magisk-v20.4.zip the signature test failed. I had the brilliant idea to disable checking it, and it installed and bricked my phone until I used again EN_Recovery-twrp-oneclick-EN.bat to re-install boot.img in the bot partition.
The signature failed also with magisk-debug.zip. I did not try to install without checking it first, once bitten...
The oppo_log directory is empty. Please let me know if there is another place to look. I don't have an ADVANCED directory in TRWP. I checked before rebooting, so instead, I send a screen cap.
I don't see how to attach a file, so here is a link:
https://postimg.cc/py17ct1q
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Didgeridoohan said:
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Click to expand...
Click to collapse
OK, I'll try later. Thanks for the info.
Didgeridoohan said:
You have to disable zip signature validation in TWRP or you won't be able to flash a Magisk zip at all.
The actually recovery log is completely necessary to be able to troubleshoot. The ADVANCED part in TWRP isn't a directory, but one of the buttons on the main page. You'll then be able to save a log and you'll find it in /sdcard. The log has to be saved directly after flashing the zip, or it won't show the info we need.
Click to expand...
Click to collapse
Same problem with the debug version, unable to reboot.
I used TWRP to create a log.
I'm not sure where it went exactly, here are all the logs I could find in various places, I don't have a /sdcard directory:
https://wetransfer.com/downloads/3f...4d3d4ca52a615682f34f182520200725060951/875fb2
If I missed the correct log, please let me have some info where to find it exactly and I'll try again. Now that I could unbrick twice my phone, I feel safer!
Thanks.
Hello all,
First of all, I'm not very familiar with recovery/rooting on phones. Although my daytime job is customizing embedded linux, so I have some knowledge
I got my hand on a few Alcatel 5033d devices, on which I want to run a software I created. However, this software needs access the notifications. And Android GO doesn't allow that. So I need to change the low-ram flag in build.prop. If possible I also want to remove the google apps from it and make my app a system app. But for the rest I'm happy, so don't need linageos or anything.
Is there a way to make a custom system.img, based on the original one, with only build.prop changed and load this complete firmware via the original recovery mode? I already saw you could load things via sdcard (adb doesn't work in stock recovery -> authentication required).
I already tried mtk-su (worked on a tablet before), but I guess that flaw is already patched
Something to try
This is from my head so if this doesnt work im sorry
1. install a custom rom.
2. install magisk onto the custom rom.
3. make a copy of the boot image
4. use "Mobile upgrade S" from alcatel to restore your phone
5. flash the backed up boot image from before.
6. if your lucky you may have root on the original system partition.
P.S i would use https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 rom because it doesnt touch the boot partition.