Related
Ok, so my problems began after I updated to the the HTC ADP 1.6 ROM. I figured after I got it installed, I would just run fix permissions and be off to the races. That didn't work because I kept getting the error "cp: not found" when attempting to copy the script to /system/bin from the sdcard.
On a possibly related note I couldn't load Cyanogen's 1.4 recovery image either (currently using JF's v1.51) because of the error "flash_image: not found."
Doing some googling I found out that the function 'cp' was enabled by busybox. So I figured that maybe during the course of upgrading to 1.6 I lost busybox. I followed the directions here to reinstall:
http://benno.id.au/blog/2007/11/14/android-busybox
So in short, I'm about 1000% sure I messed up somewhere. The question is, at this point is it possible to fix what's wrong, or should I go through the steps to root my phone again? I'd like to avoid the latter if at all possible.
And at this point I'm not even sure that I have root anymore. I ran a script to reboot the phone (which requires su privies) so I guess I do.
Any and all help is appreciated.
http://forum.xda-developers.com/forumdisplay.php?f=507
Minker17 said:
http://forum.xda-developers.com/forumdisplay.php?f=507
Click to expand...
Click to collapse
...and which thread there should I follow?
the.snks said:
Any and all help is appreciated.
Click to expand...
Click to collapse
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.
the.snks said:
...and which thread there should I follow?
Click to expand...
Click to collapse
Please differentiate between forums. You posted a question in the developepent forum. If you are not presenting something that you have developed for the dream/android platform, you should post in another forum. Questions, of course, go in the Q & A forum.
stogchris81 said:
Please differentiate between forums. You posted a question in the developepent forum. If you are not presenting something that you have developed for the dream/android platform, you should post in another forum. Questions, of course, go in the Q & A forum.
Click to expand...
Click to collapse
Gotcha. I don't see how to move or delete this thread.
Mods?
jashsu said:
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.
Click to expand...
Click to collapse
I wasn't completely clear in the first post, I updated to the HTC ADP 1.6 with rooted base. I'm not sure if I eveb need busybox. That was just part of the attempt to install Cyanogen's 1.4 recovery image using the below instructions:
http://forum.xda-developers.com/showthread.php?p=3915123
I kept getting a "flash_image: not found" error. I would just install the CM's new ROM (http://forum.xda-developers.com/showthread.php?t=567610), but that's a no go since I can't get the recovery image loaded.
At this point I don't care anymore if I have to wipe. If I can get CM's recovery image loaded, I can go from there.
jashsu said:
ADP1 builds do not have busybox or a su binary installed. You can install them yourself if you need the functionality. The "rooted base" in this thread has an already setup Superuser.apk protected su if you are lazy (you'll still have to install busybox though). Also if you use tethering you'll need to replace the kernel.
Click to expand...
Click to collapse
Actually, ADP1 builds *do* have "su", it is just limited to root and shell users (i.e., it'll work if you already have root privileges -- switch user to a RESTRICTED user to test file access permissions, or switch from shell to *any* user from adb).
Eff it. I'm going to totally downgrade and then root again using the sticky in this section. This just isn't worth the hassle.
Thank you to everyone that tried to help.
Mods: You can delete this thread.
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible :crying: Thanks for help
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
In rootcloak, did you specifically add the securego app to it's block list?
Sent from my SCH-R220
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer.
Under "Remove native root detection for apps", the box "SecureGo" is checked.
b*_gently_*d said:
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer. [emoji14]
Under "Remove native rott detection for apps", the box "SecureGo" is checked.
Click to expand...
Click to collapse
In your app drawer (if Xposed is properly unstalled) should be the Xposed app. After you install an Xposed module you have to activate the module in the Xposed app and reboot for it to work. Sounds like that hasn't been done. How did you install Xposed?
Sent from my SCH-R220
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
b*_gently_*d said:
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
Click to expand...
Click to collapse
Ok, that doesn't sound can you post a screenshot of what you are talking about including the list of modules installed in Xposed?
Sent from my SCH-R220
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
b*_gently_*d said:
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
Click to expand...
Click to collapse
Sorry, didn't notice the typo, it looks like you are using and old version of Xposed and a BETA version of rootcloak, have you tried the stable version?
Sent from my SCH-R220
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
b*_gently_*d said:
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
Click to expand...
Click to collapse
Have you taken a look at this, maybe this could help : http://forum.xda-developers.com/showthread.php?t=3450396
Sent from my SCH-R220
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
b*_gently_*d said:
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
Click to expand...
Click to collapse
It would allow you to utilize this workaround
Sent from my SCH-R220
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
b*_gently_*d said:
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
Click to expand...
Click to collapse
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
Check the thread for your device, a quick Google search shows some MM ROMs for your GT-I9070P
Sent from my SCH-R220
still failure
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
b*_gently_*d said:
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
Click to expand...
Click to collapse
Check the suhide thread, other people have the same sort of issue, in that you are using CM SuperSU that is not systemless, need to disable it for systemless su to work
Sent from my SCH-R220
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
Click to expand...
Click to collapse
Yes, at least how it's implemented in the ROM
[*]I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Click to expand...
Click to collapse
Is your Busybox up to date?
[*]Do I need ADB installed? I'm asking because it appears in the commands.
Click to expand...
Click to collapse
If you have to issue these commands from your computer to the phone you would need ADB on your computer. Is ADB turned on in developer options?
[*]I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
Click to expand...
Click to collapse
Did you type su in Terminal Emulator?
[*]But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Give me some time, I'll do a backup and see what you are seeing.
Sent from my SCH-R220
---------- Post added at 12:33 PM ---------- Previous post was at 12:11 PM ----------
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
In looking at Chainfire's thread to install Systemless root, I discovered that there are special boot.img files that need to be flash, my device is not on that list. But he does have some things that might shed some light on the issue.
1) Is your device one of the supported devices?
2) If so, did you do a clean flash? Did you flash the boot.img and su zips immediately? The thread says you need to make sure to flash the systemless stuff before the built in su does anything because the systemless flashing doesn't clean up other root implementations and can create problems. That's why it is mandatory for a clean flash of the ROM.
3) After you do all that, install the SuperSU app from the play store and see what happens
Sent from my SCH-R220
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
b*_gently_*d said:
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
Click to expand...
Click to collapse
http://forum.xda-developers.com/app...rshmellow-t3219344/post63197935#post63197935
Sent from my SCH-R220
Unable to install xposed modules. When I hit download the module starts download and progress bar appears. Once download completed the bar disappears and download button comes again. No install button. What is the problem??
Almost the same problem!
Why is so difficult to find a solution?
Two days now I'm searching thru the forums but no luck. I can't find even where I must write down my problem with xposed modules framework installation.
When from xposed modules app menu choose "(+) Install Xposed Framework" it shows me a totaly white screen and downloading keeps forever!
I'm forced to "force stop" the downloading from "apps" "dowloadings".
I downloaded the v32 (de.robv.android.xposed.installer_v32_de4f0d.apk) which as they said is more stable with lower bug risk and I installed from SD but nothing happened.
Any help please?
My phone: gt-i8260, 4.1.2
Sukinesh said:
Unable to install xposed modules. When I hit download the module starts download and progress bar appears. Once download completed the bar disappears and download button comes again. No install button. What is the problem??
Click to expand...
Click to collapse
AntonyMan said:
Almost the same problem!
Why is so difficult to find a solution?...
Click to expand...
Click to collapse
When the XPosed Installer downloads a Module, they're typically stored in the following directory.
"/storage/emulated/0/XposedInstaller"
When you locate those apk files, you can just manually install them the same way you would install any app.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
When the XPosed Installer downloads a Module, they're typically stored in the following directory.
"/storage/emulated/0/XposedInstaller"
When you locate those apk files, you can just manually install them the same way you would install any app.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I searched for the location but no such folder exists !!
Sukinesh said:
I searched for the location but no such folder exists !!
Click to expand...
Click to collapse
The first option you should be taking advantage of is to post your question/Issue within the appropriate support thread for whichever XPosed Installer your using.
The following threads depend upon the XPosed Installer you have as well as the Android Version it's installed in (on your device).
For Questions/Support regarding Rovo89's...
XPosed Installer v2.7 Experimental:
http://forum.xda-developers.com/showthread.php?t=2788124
Xposed Installer for Android Lollipop:
http://forum.xda-developers.com/showthread.php?t=3030118
XPosed Installer for Android Marshmallow:
http://forum.xda-developers.com/showthread.php?t=3249095
For Questions/Support regarding DVDandroid's...
XPosed Material Design Installer for Android Lollipop/Marshmallow/Nougat:
http://forum.xda-developers.com/showthread.php?t=3137758
I wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi Guys,
My Pixel 2XL "magically automatically" updated itself to Android 11, so I've been forced to migrate to the Canary build of Magisk
to get root back etc.
The problem I have, is that the modules are not being 'detected' despite being installed.
EG: Active Edge Mod for Pixel, module is installed in Magisk, but the app doesn't detect the installation.
Same for other Magisk modules.
I'm hoping its something simple I need to do to detect these, I've searched, but found no definitive answer.
Anyone have any suggestions? Or can point me to more info on canary?
Thanks in Advance!
I noticed v21 has been released, so I jumped back to the stable channel and updated app to 8.0.1, but strangely still have the same issue!
Modules aren't being detected.
I get the following error when I try to run energized in terminal;
/system/bin/energized[13]: .: /sbin/ .magisk/modules/energizedprotection/system/bin/setupFiles.sh: No such file or directory
You've got two rather special modules there, so they're hardly the benchmark for if things work or not.
For Active Edge Mod you're probably better of asking for help with the developer. And judging by that error the Energized developer also need to update their module, since that path no longer exists on A11 (and it's bad practise to hardcode the path like that anyway). You could edit the energized file in the module directly, to point to the correct path (check the module thread, I'm sure someone has brought this up already).
So, in conclusion: unless there are other more "normal" modules that doesn't work there's no issue and you need to contact the developers of these two modules so that they can fix them.
Thanks @Didgeridoohan, I wasn't aware that the paths had changed. That would explain a lot...
Out of curiosity, what would you consider a "normal" module? For testing purposes..
Cheers!
Thanks @Didgeridoohan, I wasn't aware that the paths had changed. That would explain a lot...
Out of curiosity, what would you consider a "normal" module? For testing purposes..
Cheers!
I always like @osm0sis' modules. They utilise the module installer scripts very nicely and pretty much always work (and if they don't something usually has gone horribly wrong).
Well, hijack the module installer scripts nicely.
Well, I do have @osm0sis BusyBox Magisk Module installed, but I think I read a tweet that TopJohnWu was incorporating a busybox binary in Magisk..
I can see that all of my Magisk modules (except Systemless Host) has a "folder icon with an i" on it. Can't find what that means.. and I get a blank screen when i press it.
Magisk has had Busybox integrated for ages... Lately it's become more usable for scripts and modules though. It's not exposed to the rest of the system like @osm0sis module is.
The icon you're seeing is the module readme. Click that and it should open in the window that you see.
This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060.
Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk.
Important : This Magisk Alpha thread was created to share information about Magisk Alpha Public Releases with XDA members that do not use telegram.
If Magisk Alpha doesn't work for you try one of the other versions of Magisk (See Useful links below).
How to install Magisk Alpha?
Magisk Alpha is installed and uninstalled through the Magisk application (App). Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool. By customizing Recovery is not a supported way.
Detailed Instructions for the first installation of Magisk Alpha on Google™ Pixel™ phones.
Note: These Instructions may not apply to all Google™ Pixel™ Phones.
If you have another version of Magisk (Beta/Stable [Forks - Cygisk/Delta] Stable) installed:
Open the Magisk Manager app and disable/remove all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
Uninstall Magisk
Extract boot/init_boot.img from Factory Image
Download the latest Factory image to your phone.
Extract the Factory Image file (aaaaaaa-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-aaaaaaa-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file will be in this folder.
Patch the boot/init_boot.img.
Download Magisk Alpha (app-release.apk)
Install the Magisk Alpha App
Open Magisk Alpha App
Tap Install (next to Magisk)
Tap, Select and Patch a File
Navigate to the folder that you extracted the Stock boot/init_boot.img to and select it.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Move the patched boot/init_boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Copy it to a USB drive and transfer it to your computer.
Move it to your computer using adb push
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot --slot all "name of patched boot".img or fastboot flash init_boot --slot all "name of patched boot".img without the quotation marks at the Prompt and press enter.
When it finishes installing the patched boot.img or init_boot.img, type fastboot reboot at the Prompt and press enter.
Important Notes:If your phone boot loops try one of the following options:
Flash the 'stock' boot/init_boot.img to both slots: fastboot flash boot/init_boot --slot all boot/init_boot.img
Boot Safe Mode - Keep Pressing the Power Off button until you see boot Safe Mode ==> Press Ok.
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Useful Links
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
Magisk Alpha 26101 - 12 Apr (Pubic release)
https://github.com/vvb2060/magisk_files/find/alpha/
Tap app-release.apk
Tap the 3 dot menu across from 10.9 MB
Tap Download
Magisk Beta 26.1 - 11 Apr
Magisk Canary 26103 - 23 Jun
https://github.com/topjohnwu/magisk-files/blob/5b2934603f979d7133e67bbc30c6ce3fa0d8e31e/notes.md/
Tap the 3 dot menu across from 5b2934603f
Tap Go to file
Tap app-release.apk
Tap the 3 dot menu across from 10.9 MB
Tap Download
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta
Magisk Stable 26.1 - 11 Apr
Magisk Documentation
Fox's Magisk Module Manager
Fox's Magisk Module Manager - Releases
LSPosed Framework
LSPosed - Releases
LSPosed - Shamiko Releases
kdrag0n Safetynet Fix -Releases
If Kdrag0n Safety Net Fix doesn't work for you try Displax's SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
alpha changelog
Magisk (98874be1-alpha)
- [App] Delete backup file after restoring boot image
- [App] Built-in current version update log
- [General] no longer automatically unlock device blocks
- [App] Compatible with Android 12L
- [App] Added crash statistics
- [App] Allow loading zygisk modules
- [General] Signature Verification
- [MagiskInit] Fix Android 8.0-9 not installed after booting
How to install?
Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool. By customizing Recovery is not a supported way.
Upstream changelog
Magisk (704f9154) (24305)
- [App] [MagiskSU] Properly support apps using shared UID
- [Zygisk] Fix function hooking on devices running Android 12 with old kernels
- [BusyBox] Add workaround for devices running old kernels
Diffs to v24.3
- [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
- [MagiskInit] Introduce new `sepolicy` injection mechanism
- [App] [MagiskSU] Properly support apps using shared UID
- [Zygisk] Fix function hooking on devices running Android 12 with old kernels
- [BusyBox] Add workaround for devices running old kernels
The author of Magisk Alpha is extremely untrustworthy. It is highly recommended to use the official version.
imma add my 5 cents worth, fwiw
magisk alpha was a good and useful fork (along with custom) after TopJohnWu announced he was removing magiskhide in line with his job at Google and people lost their collective shizz, even though common sense should have told them this was needed and sane. Many of us appreciated the hard work of the alpha and custom devs, but at some point, as announced again by TJW, other hiding methods would come to fruition. And they have. Not to in anyway to devalue the contribution of alpha and custom devs, but there was always goign to be a point where mainstream magisk/magisk canary was going consolidate the attention and focus of the userbase and senior members here long into magisk, again. i for one dont miss testing/switching between 4 different forks anymore. magisk alpha was my chosen fork for a long time
Magisk Alpha is fine to use as long as you understand its shoehorning in things removed from the mainstream magisk, and that was certainly appreciated at times, but those could cease to work, introduce issues not present in mainstream magisk leading to people expecting support from the main magisk threads where it would make life harder for those trying to answer questions. so temper your expectations those of you who choose to use.
For my 5 cents, id recommend using mainstream magisk, unless you have an edge case where it doesnt work, at which point ordinarily, one would file on issue on github
As for the alpha devs personality, ill admit, it could be variable at times
73sydney said:
As for the alpha devs personality, ill admit, it could be variable at times
Click to expand...
Click to collapse
Like the weather? ... But I like you fine too mate... Like the weather...
The real question re. personality here is 'Are you a maverick?'... If not, stick to official Magisk... PW
Homeboy76 said:
This thread is for Magisk alpha users: Support
Hopefully, @pndwal and others with much more knowledge of Magisk alpha ,than I, will share their knowledge with us.
Click to expand...
Click to collapse
Prolly don't qualify then; not a user! PW
mlgmxyysd said:
The author of Magisk Alpha is extremely untrustworthy. It is highly recommended to use the official version.
Click to expand...
Click to collapse
To be very honest: I hate this childish behavior of developers bashing developers.
I love both your work and the work of the LSposed developers and I have donated to both of you. Just because developers could document / announce better there's no need to move against each other.
The reason why I use Alpha is exactly, because of the removal of MagiskHide and John's involvement with Google. imho that's just gonna hurt Magisk in the end.
And your words also mean basically stay away of Shamiko. That's not gonna happen. Unfortunately Google went down that rabbithole against rooting, etc., which is why I'm still very unsure whether I even keep rooting my phones from now on...
dr4go said:
And your words also mean basically stay away of Shamiko
Click to expand...
Click to collapse
You missed the point that alpha is a personal fork, Shamiko is a team of dev work (LSPosed team), alpha's author is one of them, don't scramble between them.
pndwal said:
Prolly don't qualify then; not a user! PW
Click to expand...
Click to collapse
Any help with Magisk alpha is greatly appreciated.
For all intents and purposes, once you enable zygisk thereby removing Magisk Hide functionality, the Alpha fork is the same as the official build.
But with one key difference.
The app and package name are different, so no need to hide it. Or for that matter remember to unhide it before an update "just in case"
This is why I use it.
dr4go said:
To be very honest: I hate this childish behavior of developers bashing developers.
I love both your work and the work of the LSposed developers and I have donated to both of you. Just because developers could document / announce better there's no need to move against each other.
Click to expand...
Click to collapse
dr4go said:
The reason why I use Alpha is exactly, because of the removal of MagiskHide and John's involvement with Google. imho that's just gonna hurt Magisk in the end.
Click to expand...
Click to collapse
Disagree. However, isn't MagiskHide gone from alpha now?
dr4go said:
And your words also mean basically stay away of Shamiko. That's not gonna happen. Unfortunately Google went down that rabbithole against rooting, etc.,
Click to expand...
Click to collapse
When? What? Where?... Think you're a bit confused... But you wouldn't be the first.
dr4go said:
which is why I'm still very unsure whether I even keep rooting my phones from now on...
Click to expand...
Click to collapse
Of course you can!... Who's going to stop you?... Unless you buy late Huawei! PW
Stillhard said:
You missed the point that alpha is a personal fork, Shamiko is a team of dev work (LSPosed team), alpha's author is one of them, don't scramble between them.
Click to expand...
Click to collapse
I never intended to - sorry if that was suggested. I just meant: if one of the developers of Shamiko isn't trusted and it's closed source, would you use it?
pndwal said:
Disagree. However, isn't MagiskHide gone from alpha now?
Click to expand...
Click to collapse
Yes it is. There is still a fork around that uses it, but not Alpha.
pndwal said:
When? What? Where?... Think you're a bit confused... But you wouldn't be the first.
Click to expand...
Click to collapse
See previous post. I am definitely confused, but not regarding that.
pndwal said:
Of course you can!... Who's going to stop you?... Unless you buy late Huawei! PW
Click to expand...
Click to collapse
Google. Once HW backed SafetyNet is enforced there is no way around it. But let's not get offtopic here and keep talking about Alpha if the thread was created for it...
pndwal said:
Mate, I can read and did not disagree... I said "Quite."... as in "I agree... enough is enough... Fine!" ...
You seem to be lifting my remark right out of context, So Please read my edit carefully, (you are the OP) and what I was addressing; it won't change;
You said:
I said:
and that until then I'd prefer to post non-Alpha Magisk information in existing TJW General Support / Discussion thread... If I'm just not interested in taking it to "PM" or "Conversations", what's the problem?
... and I edited the earlier post so as not to further congest this thread...
...three more posts wasted. PW
Click to expand...
Click to collapse
I have now created a cat-and-mouse-game discussion thread:
https://forum.xda-developers.com/t/...ng-and-mod-hiding-cat-and-mouse-game.4425939/
HippoMan said:
I have now created a cat-and-mouse-game discussion thread:
https://forum.xda-developers.com/t/...ng-and-mod-hiding-cat-and-mouse-game.4425939/
Click to expand...
Click to collapse
Thank you!
PSA:
I recently asked here if anyone had been been surprised by unusual actions in the April 1 release of Magisk Alpha (changelog posted in OP post #2 here) being referred to in the TG Alpha Magisk discussion group as the 'April fools limited edition'.
This was in view of these official notices accompanying the build in the separate 'Magisk alpha' update thread (Chinese translated):
Warning to developers: In libsu v4.0.0 and later, Shell.rootAccess() has a behavior change that returns true even if the user refuses to grant root privileges.
Click to expand...
Click to collapse
and
Warning to developers: Magisk 24302 and later, the magiskpolicy tool may not exist or be inconsistent with the Magisk version.
Click to expand...
Click to collapse
My query has been inexplicably deleted from this s thread!
However, those 'Warning' messages are still up, so, as nobody has responded here (not surprisingly), I have just installed this Alpha build and tested it on a secondary device.
I can confirm that, despite some claims of in-app messages stating that root has been granted to apps despite users denying access, I could not produce / have not seen such worrying behaviour...
So it appears that the Dev's "Warning to developers" notices themselves are the only 'April fools' joke.
Of course there is also NO substance to the assertions either that John's libsu root app solution has or is responsible for such behaviour, or that there are inconsistencies with the magiskpolicy tool (or consequently with SELinux policies) post 24302.
This may allay concerns if anyone translates / reads those 'warnings' in Magisk alpha TG.
Regarding the removal of my initial post regarding this and my posts in general, I accept and understand that some have been off topic, and have said that I agree to stay on topic several times (responses now removed). The OP here has however misconstrued my intentions. For whatever reasons, alpha related posts put up in good faith are now being removed without communication. This saddens me...
I hope this thread can become useful for Alpha users / enquiriors... PW
pndwal said:
PSA:
I recently asked here if anyone had been been surprised by unusual actions in the April 1 release of Magisk Alpha (changelog posted in OP post #2 here) being referred to in the TG Alpha Magisk discussion group as the 'April fools limited edition'.
This was in view of these official notices accompanying the build in the separate 'Magisk alpha' update thread (Chinese translated):
and
My query has been inexplicably deleted from this s thread!
However, those 'Warning' messages are still up, so, as nobody has responded here (not surprisingly), I have just installed this Alpha build and tested it on a secondary device.
I can confirm that, despite some claims of in-app messages stating that root has been granted to apps despite users denying access, I could not produce / have not seen such worrying behaviour...
So it appears that the Dev's "Warning to developers" notices themselves are the only 'April fools' joke.
Of course there is also NO substance to the assertions either that John's libsu root app solution has or is responsible for such behaviour, or that there are inconsistencies with the magiskpolicy tool (or consequently with SELinux policies) post 24302.
This may allay concerns if anyone translates / reads those 'warnings' in Magisk alpha TG.
Regarding the removal of my initial post regarding this and my posts in general, I accept and understand that some have been off topic, and have said that I agree to stay on topic several times (responses now removed). The OP here has however misconstrued my intentions. For whatever reasons, alpha related posts put up in good faith are now being removed without communication. This saddens me...
I hope this thread can become useful for Alpha users / enquiriors... PW
Click to expand...
Click to collapse
I saw that on Alpha TG and I was worried about, although I don't use Alpha, since they mentioned libsu
I don't really know if roots grants from the Magisk app go through libsu, but I tested with the latest Canary 24305 and everything was ok:
- I revoked the root grant to the Reboot app (by Petrus).
With the app you can easily reboot, reboot to Recovery or Fastboot.
Obviously, the app requires root grant to work
- I opened Reboot app and chose to reboot, and I was immediately popped-up to grant the root
- I denied to grant the root and I choose again to reboot, but it didn't reboot (correct behavior, without the root grant Reboot app cannot execute reboot)
- Again through Magisk app, Superuser tab, this time I granted the root and then Reboot app worked to reboot
In parallel I was checking in magisk.db, Policies, and everything looked ok (you can see by UID and policy values if the root grant is given/revoked to the particular app)
zgfg said:
I saw that on Alpha TG and I was worried about, although I don't use Alpha, since they mentioned libsu
I don't really know if roots grants through the Magisk app go by libsu,
Click to expand...
Click to collapse
Yup, since Jan 2018, Magisk Manager / App "uses `libsu` for all root related operations".
zgfg said:
but I tested with the latest Canary 24305 and everything was ok:
- I revoked the root grant to the Reboot app (by Petrus).
With the app you can easily reboot, reboot to Recovery or Fastboot.
Obviously, the app requires root grant to work
- I opened Reboot app and chose to reboot, and I was immediately popped-out to grant the root
- I denied to grant the root and I choose again to reboot, but it didn't reboot (correct behavior, without the root grant Reboot app cannot execute reboot)
- Again through Magisk app, Superuser tab, this time I granted the root and then Reboot app worked to reboot
In parallel I was checking in magisk.db, Policies, and everything looked ok (you can see by UID and policy values if the root grant is given/revoked to the particular app)
Click to expand...
Click to collapse
Did similar test on Alpha; just wanted to see if it somehow claimed root granted when denied...
I wasn't worried about TJW Magisk as I was certain libsu & magiskpolicy 'warnings' were an 'April fools' hoax, but I wouldn't have put it past Devs to also implement false indicators... (Appears that if done at all, this must have expired after April 1 ?) I didn't find any...
Have to wonder how John views this hoax, especially since, surprisingly, there's been no retraction...
Thanks for confirming.
Nb. As I speak speak, TG Alpha discussion group name is being changed between names w/ sexual overtones by admin Canyie... Kids!
PW
As per Nb. above, Canyie's original "Alpha 讨论组" (Alpha discussion group)" is currently simply named 西大师 奶子... !?
No real idea why; Joking around? Trying to disguise Alpha discussion group? Deter 'foreigners'?
Members there are also asking questions... PW
... now it's 西大师 live! ... PW