Related
Hello everyone. Many users have problems with slowing phone after installing xposed. The same applies to me. No one has yet found a solution that would suit everyone. But I found something that might help someone. This is in a forum where solves slowdown S-Health application for Samsung. While I do not have Samsung (I have Jiayu G4S), so I tried it. I'm simply install certain module "XSecureStorage" in Xposed and really my phone runs without lags
Link here:
http://forum.freelatestmovies.org/note-4-tmobile/general/fix-how-to-fix-xposed-framework-lag-t2935423
Copied text from this URL:
Found and confirming a method on how to get the latest version of Xposed Framework working on Note 4 (T-Mobile SM-N910T). Also Wanam Xposed is working fine too inside Xposed Framework.
Step 1:
Insure that Xposed Framework is fully uninstalled from the device temporarily.
Step 2:
Go into Root Browser, or any browser of choice that has root privileges and go to /System/Build.Prop and open it as a text document.
Step 3:
Inside the Build.Prop file look for a line that says "ro.securestorage.support=true" [NOTE: IT IS THERE I PROMISE YOU, a bit hard to find] ...*I do not have this line*
Step 4:
Build.Prop finnished file
Change "ro.securestorage.support=true" to "ro.securestorage.support=false"
Step 5:
Go back into Xposed Framework, install and reboot and you MAY be fine. Most users will need to continue here. If you still have issues there are 2 methods to fully fix Xposed and S-Health
[Option 1: Download a fix module after Xposed re installed after the Build.Prop fix]
[Option 2: Disable S-Health completely]
Thanks to Compusmurf for mentioning about this module
Option1:
Step 1:
Go into Xposed Framework, download a module called "XSecureStorage"
Click Framework and hit Install/Update and you are good to go! If this module doesn't do the
trick, try Option 2. Option 2 is guaranteed to work since you will be disabling S-Health all together.
Option2:
Step 1:
In Settings App>>Application Manager find "SHealth" and select "Turn Off"
That will guarantee for Xposed to work fully fine with no lag. Leave a Thanks if this worked for you and post back if any questions or issues!
Last edited by chaunold; 2014-11-11 at 3:45AM.
Quick Reply Reply
12 users say Thank You to chaunold for this useful post
I only have ro.secure=0
Using Last pixel experience with Last alize Sanders kernel
I'm using official Omni 8.1. The issue I'm facing is that the Magisk Manager can't seem to remember the apps it has granted Superuser permission. Even in the Superuser tab it shows "No apps found". Result being I have to grant Superuser permission every time when I open an app like Root Explorer.
Please look into this issue.
Magisk Manager: v5.5.2
Magisk Root: v15.1 Stable
I don't have this issue on version 5.5.0 and 15.1 on the latest Omni 8.1 weekly on my Oneplus 3T.
Edit: You didn't mention what device, so I doubt anyone would be able to help you. But I guess you're running a Oneplus 3T or a Oneplus 5 since there are no 8.1 Omni weeklies for any other devices, yet. Maybe you could try to attach some logs.
For me Magisk v15.1 doesn't boot anymore, it just fails and goes back to recovery.
v14.6 works fine.
Omni 8.1 on Oneplus 5T
Same problem here. Any solution?
Look into this issue, doesn't boot, solutions?
Where are the logs?
How do you expect someone to help you without that?
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Jazavchar said:
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Click to expand...
Click to collapse
I'd say it has to do with the incredible speed that the Magisk development has been going at. Looking back over the past year, a lot has happened. This kind of speed can cause instabilities...
Now, it's most likely at a point where the focus will be on stability and compatibility development.
Having said that, though, all users experiencing issues can help with that by providing as much details as possible and relevant logs.
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
debichu said:
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
Click to expand...
Click to collapse
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Didgeridoohan said:
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Click to expand...
Click to collapse
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
debichu said:
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
Click to expand...
Click to collapse
Number 1 is an issue, because that's the su database... If there is none, it's no wonder why granted superuser requests aren't saved.
Hi, do you have a solution?
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
cpt.macp said:
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
Click to expand...
Click to collapse
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Didgeridoohan said:
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Click to expand...
Click to collapse
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
cpt.macp said:
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
Click to expand...
Click to collapse
Let me guess: you're not using OmniROM...
Since you're posting in this thread, I kind of assumed you did, so my answer was given accordingly.
If you need help, post all possible details and lots of relevant logs.
I've had the same error. Magisk seems unstable on OmniROM 8.1 on OnePlus 5. Probably an issue with the ROM, but the developer seems like the kind of guy who will tell you to go f*ck yourself if you have a problem like this.
Sometimes it works sometimes it doesn't.
A temporary workaround with the permission issue on /data/adb/magisk.db, even after not working trying 0666 permissions, was to change ownership. None of many other solutions worked for me until I found the user for Magisk. You can use a shell as root or with apps like FX File Explorer with root capability to see which user owns files in "/data/adb/magisk/" . Then I applied that user as the owner of magisk.db. Verified that apps which ask for root permission get saved now. The user of Magisk will be different for you since it is marked as "app_##' which I suppose is up to the amount of apps you have installed.
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
saidmsb said:
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
Click to expand...
Click to collapse
No... I don't think so. This thread is about an issue with Magisk and f2fs on Android 8.1 ROMs. Your issue could be that OmniROM sets some sensitive props to triggering values.
That can be taken care of by using Magisk and MagiskHide. Take a look here for more info:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Sensitive_props
If you decide to install Magisk, this part of the guide might also be useful (all of it is useful, really):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Mudule] Root Call SMS Manager Patch
THIS MODULE ITSELF IS NOT A CALL BLOCKER, It is patch to work this Root call manager properly with Magisk
Introduction :
Basically I was not using Magisk for two purposes (Even though there were many good aspects to have magisk, but ultimately it's matter of priorities)
1.Broken Dumpsys
2.Root level call blocker was not working which is must app for me. (I know about two root call blocker available on play store)
Since Magisk V15 bring dumpsys so finally thought to look into root call manager so I can use Magisk with it's awesome Magisk hide functions.
Module :
Root call SMS Manager available on play store have mentioned some work around to use with magisk but didn't worked for me.
I have looked into it and sharing here a module which I have made for me and working fine on my Samsung Galaxy Note8. I believe it should work on more devices as well so sharing here.
Installation :
1.Download attached RCM Patch 1.1.apk and Install as regular app
2.Clcik on app icon from drawer
3.Grant su permission
4.Keep patience while it activate module.
App is self destructive and will get uninstalled once module get activated.
Reboot device when asked/app get uninstalled.
Un-Installation :
Magisk Manager - Module - Root call manager Patch - Delete from here
Tips for RCM
- In System setting, you should set proper "submode' according your device
- Wait after reboot option recommended to keep 0 but if you need to increase, better keep below 20 sec.
Disclaimer :
I am not owner of Root Call Manager app, Just made a module and shared here to work application correctly with magisk root. Any query regarding RCM should go to proper channel and not here.
Can somebody confirm, what version of Magisk you are using?
From my end the apk is not working with the Magisk 18.1. Please, can you updated it?
Thanks you
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
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