Where does your "sudo" command come from?I use Termux. Sometimes I need a root shell, so I granted root permanently to Termux, so I can use 'sudo bash' in Termux. But, as there is no password prompt, this is actually a security flaw. So I wanted to revoke root access and grant root access only on demand, when I really need it.
Revocation succeeded, but I can only grant root access permanently and not temporarily. The latter only happens when I grant root access to an app for the very first time.
Can't reproduce. If I revoke superuser access for Termux and then runI use Termux. Sometimes I need a root shell, so I granted root permanently to Termux, so I can use 'sudo bash' in Termux. But, as there is no password prompt, this is actually a security flaw. So I wanted to revoke root access and grant root access only on demand, when I really need it.
Revocation succeeded, but I can only grant root access permanently and not temporarily. The latter only happens when I grant root access to an app for the very first time.
su
I can pick "forever", "once" or one of the set time periods.The latest Canary apk is always linked in the main Magisk GitHub repo:
Did you look?
Now it worked:Can't reproduce. If I revoke superuser access for Termux and then runsu
I can pick "forever", "once" or one of the set time periods.
I use Termux. Sometimes I need a root shell, so I granted root permanently to Termux, so I can use 'sudo bash' in Termux. But, as there is no password prompt, this is actually a security flaw. So I wanted to revoke root access and grant root access only on demand, when I really need it.
Revocation succeeded, but I can only grant root access permanently and not temporarily. The latter only happens when I grant root access to an app for the very first time.
Just a guess as I never use Termux. I to use a standard android shell. And sudo is not supported. Its su in an android shell.Where does your "sudo" command come from?
I use Jack Palevich's Terminal Emulator. When I installed Magisk, I got an "su", but no "sudo". I defined an alias sudo='su -c' that works most of the time.
I told you all this so I could tell you: when I use "su", there's a pop-up asking me to grant permission. I always OK 10 minutes. I don't remember choosing my Superuser manager.
Was about to say I think It'll be considered, but see it's more than that already.@pndwal
I haz made my first Magisk related issue, lets see how quickly it gets closed
Born out of testing 4 ROMS this week is this "issue" was driving me nuts
https://github.com/topjohnwu/Magisk/issues/4333
Its not entirely out of bone idle laziness, but having to switch back after each module install was starting to get on my nerves
I dont hover around github enough to know if its been mentioned before
Could be no coincidence that Chris is on it though; what's with you compulsive testers / gluttons for punishment? PWJohn Wu, ?
I love the fact that despite being lazy, haven't worked on Magisk for almost a week, quite a few people start creating PRs to fix some regressions, burning down a lot of issues
Gotta say,
Open source sure is quite a nice thing! Maybe I should be lazy more often in the future /jk
It is just good testing.<SNIP>
Could be no coincidence that Chris is on it though; what's with you compulsive testers / gluttons for punishment? PW
https://qablog.practitest.com/should-all-testers-have-ocd/ PW
Quite.It is just good testing.
Does it work.
- No - Try to fix it.
- Yes - Find a way to break it.
The next step is figuring out why it doesn't work on one device when it works on the rest.
This is the difficult step.
Cheers.
But you HAVE figured it out. It's precisely BECAUSE they're so bad!... And nerds / geeks do still have a sense of humour (of sorts ), at least when they take a break.I don't like SPAM!
I still haven't figured out why some of the Python's bad sketches became so popular.
ALWAYS!My post was a bit too dry.
Sometimes I just need to remember to look on the bright side of life.
Re. OT: As the man with the wooden leg said, it's a matter of a pinion.
Awww, i expected some sort of witty comeback after which id have to remind you that i "know where you get your coffee in the morning"Was about to say I think It'll be considered, but see it's more than that already.
Re. idle laziness, I agree with John that Open Source is great!
Could be no coincidence that Chris is on it though; what's with you compulsive testers / gluttons for punishment? PW
https://qablog.practitest.com/should-all-testers-have-ocd/ PW
I am having trouble understanding what you are reporting.I think I remember seeing something a while back that Magisk manager merged with the App, but I still have both when I open Magisk. This is fine, but whenever I update the App, the Manager immediately shows an update to the same version, so I think maybe they are both not necessary any more.
Also, whenever Magisk tells me (via notification) there is an update, when I click download, it does, but the resultant file gives an error when I click on it, so I have to update from within the App itself.
Is there anything I should do at this point to consolidate, or is this just how it works now.
thanks for the help/guidance
Still 2 components, no longer released separately but both still needed and both require updating.I think I remember seeing something a while back that Magisk manager merged with the App, but I still have both when I open Magisk. This is fine, but whenever I update the App, the Manager immediately shows an update to the same version, so I think maybe they are both not necessary any more.
If working from within App, seems all is as it should be with Magisk. May be a general issue with package installer (settings / other) on device. What is the error? PWAlso, whenever Magisk tells me (via notification) there is an update, when I click download, it does, but the resultant file gives an error when I click on it, so I have to update from within the App itself.
Is there anything I should do at this point to consolidate, or is this just how it works now.
thanks for the help/guidance
Are you sure 5hat the version of Magisk app you used to patch is the same version you are installing after flashing the patched file?I can't find anything anywhere about it but I have a oneplus Nord 2T, I was using it with android 13 (oxygen) without problem to install the app and root the phone.
I finally upgraded to android 14 through the OTA, my root was gone of course I was able to patch the file and get root again after the reboot, the magisk app was gone.
When I try to install it I have no problem but when I open it the screen change to black for a second then comes back to the menu with the app gone.
I have an app called App Manager that can use root to install/remove or freeze all type of apps, it has a log of the removed app and I can see there it was removed.
I don't understand how or why only magisk seems to be a problem when I have other apps installed from unknown sources that are still there.
Any idea?
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.I'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or DebugIs the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about itI'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls!Direct Install with recovery mode checked worked for me. You were right.
After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
Difference may be related to new "atomic mount" I mentioned above, not sure, but be aware that DenyList is NOT designed for (proper) root hiding... I'd be trying with Shamiko which just hijacks list from DenyList but runs in hidelist mode. Nb. The same Devs responsible for most recent major refactoring in Magisk also maintain Shamiko.Sorry to bother with maybe a stupid question.
I am using Magisk and root for a long time on my Poco F2 Pro with latest xiaomi.eu ROM and XiamiEUModule App for NFC payment.
Everything was working fine with Magisk 26.4
A few days ago I updatet to Magisk 27.0 since then my normal banking app of an Austrian bank gives me a warning, but is still working. No problem witih NFC payment.
Would be nice to get rid of this warning again, have you any idea how to do so, or how to find out the reason.
*******************
On my new phone, Xiaomi 14 Ultra Global Edition FW 1.0.4 I applied for unlocking bootloader, did the unlock yesterday, which caused factory reset.
I patched init_boot.img after installing Magisk 27.0, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App Works, but also the warning about root detected.
So I flashed FW 1.0.2 via Fastboot with Clean_All Option, made update to 1.0.4 with the updater app (flashing 1.0.4. with fastboot failed, so I made safe bet with flashing 1.0.2. what I have already done successful this morning).
Then agan the same procedure but with Magisk 26.4, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App works without any warning.
Can you tell me why this behaviour with older Magisk or how to find out?
**************
Bonus info- NFC Payment with the app of my bank (not Google Wallet) does not work on Xiami 14 Ultra, but it did also not work as long bootloader was locked. Hoping for xiaomi.eu ROM for Aurora, and working NFC...