Database Develop

MagiskSU version of su fails, saying "Permission denied"

I recently had a problem (see here) with SuperSU, so I decided to give MagiskSU a try. As it turns out, it seems to have the same issue. When I run a process that requires su, it stalls for a while. In the case of MagiskSU, I then get "Permission denied" after about 20 seconds.
Here's what I get with a few basic commands:
Code:
[email protected]:/ $ su
Permission denied
Code:
[email protected]:/ $ su -v
8:MAGISKSU (topjohnwu)
Code:
[email protected]:/ $ su -V
8
Additionally, when I view the log with adb logcat, I see the following message attributed to su:
Code:
exec am failed with 2: No such file or directory
It looks like this is a message produced here, related to loading am.jar. Unlike in my SuperSU situation, this error happens regardless of whether Magisk is set to "prompt" or "grant".
Any idea how I can debug this? Thanks in advance.

Just to make sure: Have you updated the Magisk Manager so that it's just not the stub installed by the Magisk zip?
And if so, does the Manager report you're properly rooted?

I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process
Frankly I'm surprised this didn't render my phone unbootable! Nothing else was noticeably affected.

I have the same problem, just logcat says:
W/Magisk: su: request rejected (2000->0)

I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.

I found in the Magisk app under Superuser that "shell" had the toggle turned off. Once I turned it on, su worked in ADB.

Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
You are my Hero...
:good::good::good:Thank You Very Much brooo... :good::good::good:​

Hi all,
I have Magisk v18.1 and I'm also trying to get root access from shell. When I run 'su' in a terminal emulator, I get the message 'Permission denied'.
I did install "ADB & Fastboot for Android NDK" as suggested above. I also checked the root options in the magisk app (v7.0.0) and they are all the default, nothing unusual there.
Could you kindly advice if there is anything I can do in order to get root access from the shell with Magisk?
Thanks a lot in advance

I have a same issue on kitkat

Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!

geo909 said:
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
Click to expand...
Click to collapse
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.

madbat99 said:
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
Click to expand...
Click to collapse
Honestly, that was a classic case of not knowing what I'm doing and just blindly following what other people tried. But good to know what the purpose of that module was, I was wondering!

Hint: Perfdump is the adb shell program, do not disable SU for it
I add my hint: after getting this error message, I checkd the list of apps in Magisk SU: it turned out that I had disabled the "Perfdump" app, because I did not know what it was. It is the adb shell indeed!

I had exactly the same problem on my Android 6.0 with Magisk v19.3 + Magisk Manager v7.3.1. I tried everything, what you wrote (enabled, disabled the "ADB and fastboot" stuff, checked the symlink, ...), but nothing helped me. FYI: previously, I used LineageOS 16 (Android 9.0) on the same phone with this latest Magisk without any problem (but I decided to turn back to the original OS version to avoid instabilities). But now I'm fighting with this dragon.
My wife has Android 6.0 also w/ Magisk, but she got Magisk v18.0 and this works well now... I tried this at me, and surprisingly, that was worked well. Now, I decided to find out, which is the last working version, where is the bug.
The results:
* the Magisk v18.0 with the bundled Magisk Manager - GOOD
* the Magisk v18.0 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v18.1 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v19.0 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.1 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.2 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.3 with the latest Magisk Manager v7.3.2 - BAD
I don't know, the freshest working Magisk v18.1 + Magisk Manager v7.3.2 is a good combination for all cases, but looks working.

Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
Yup thanks it still works up to date

Solved
i had the same problem on my redmi note 7 and the most easiest way is unistall your magisk 20.xxx and install a older one 19.xxx and that should do it but remember bouth zip file (flashibile zip) and magisk apk has yo be older than 20.xxx becouse the devs has made a mistake in the coding( or at leat this is what i think hope im wrong)

just update the magisk manager and install automatically the boot and reboot the phone it will be okay

Solution that works for me GalaxyS9 (starlte)
### restart adbd as root
adb root
### then
adb shell
### WORKS.
### I see '#' in prompt, `whoami` responses: 'root'
### My Magisk version. Reported by `su -v`
23.0:MAGISKSU

[OOS 11] Fix: Enable AOD, Re-enable DC Dimming & Removing OnePlus Login Option In Settings

I've just upgraded to OOS 11 on my OP7T Pro and noticed two major things: DC dimming isn't an option anymore (might be fixed in the future) and for some reason my EU firmware shows a OnePlus account login at the top of the Settings app.
Pre-requisites for everything​Without root
Use a PC with ADB (plenty of tutorials online)
Enable ADB debugging in dev settings of your device
(tap on the OOS 11 version number multiple times to enable dev settings)
With root
Use a terminal like Terminal Emulator and paste the code line without "adb shell".
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy ​​Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/​​What it does? It first asks for root permissions ("su") and then sets a prop that tells OOS to allow the AOD setting to be shown. At the end we restart SystemUI to allow the changes to be applied.​​​
Fixing DC dimming​Variant #1
On your PC using ADB type:
Code:
adb shell
settings put system oneplus_dc_dimming_value 1
Done. To disable change "1" to "0".
What it does? It sets the variable for DC dimming to 1 (enabled) or to 0 (disabled). Variant 2 does the same thing but it is accessed by opening up a hidden panel. As both require ADB this one is quicker and easier.​
Spoiler: Variant 2 (old method)
On your PC using ADB type:
Code:
adb shell
am start-activity -a oneplus.intent.action.ONEPLUS_LAB_FEATURE_DETAILS -e oneplus_lab_feature_key oneplus_dc_dimming_value
The settings panel for DC dimming will now start on your device
Enable or disable it as you please
What it does? It starts the part of the OnePlus Lab that contains DC dimming. It is still there but for some reason it is hidden. The command will start the panel and let you enable or disable it.​
​
Removing the OnePlus "Login in to account" Option in Settings​
On your PC using ADB type:
Code:
adb shell
pm uninstall --user 0 com.oneplus.account
Close the Settings app and thank me later
What it does? It removes the culprit (the app "com.oneplus.account") from the user space. Meaning it will act as it is uninstalled for your user account. If you use multiple user accounts on one device you need to do that for each user account. It could affect other OnePlus apps like the Community app so be aware. It is never truly removed as it is a system app.​
Re-adding the app is easy. Use:
Code:
adb shell
cmd package install-existing com.oneplus.account
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Log in to account" is added sometimes. The old way was to remove the /data/india/india.img file but on OOS 11 it doesn't exist.
I'm not sure if the EU version should even contain this but it is still annoying to some as it sits above all important settings options.
Please note: I'm not responsible for anything you do to your device. You use these tutorials at your own risk. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!

Works perfectly on rooted stable OOS11 on oneplus 7T.
Thanks a bunch bruh!

How to enable phone record?

Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/

Both of these methods work perfectly on my rooted 7T with latest OOS11 stable, bugfree smooth aff. Termux and magisk is all you need. I'm grateful that I'm not among those reddit crybabies, who cry over this **** all the time and are too afraid to root their phones.
Thanks a bunch devs!

joEmonkey351 said:
Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/
Click to expand...
Click to collapse
You're supposed to flash it from magisk manager, after applying the mentioned command in Terminal manager/adb shell.

Is there really no way to get DC dimming back? I really miss that feature already

iKlutz said:
Is there really no way to get DC dimming back? I really miss that feature already
Click to expand...
Click to collapse
If you read the op it works there is just no switch

toolhas4degrees said:
If you read the op it works there is just no switch
Click to expand...
Click to collapse
Re-read the OP my man. Dc dimming is gone in latest OS11 update. Another great feature that vanished was the manual screen rotate button that would appear if you turned the screen sideways. Hopefully further updates will put them back.

Works on OP7P

Great tip for removing the Log in to Oneplus Account stuff, thanks.

Removing the OnePlus login from settings is failing for me. Rooted, oos 11.0.2
$ pm uninstall --user 0 com.oneplus.account
cmd: Failure calling service package: Failed transaction (2147483646)
edit: above failure was entering the command via Termux. Connecting to a pc via abd and entering the commands
Code:
pm uninstall --user 0 com.oneplus
and
Code:
pm uninstall --user 0 com.oneplus.account
did the trick.

I am not completely sure if this is the right place to ask but - are there a similar way to replace the leftmost screen with OnePlus Shelf instead of Google Discover. (using the ADB)
Some people have:
- toggle switch on that page to choose which one they prefer (Shelf or Google)
- (or) a setting in OnePlus Launcher where to enable the leftmost screen and also specify if you want it to be the (Shelf or Google)
What I imagine is that there should be a hidden setting which can do that, and that can be altered through ADB. Could someone please help me find it? Or share another way to make the OnePlus shelf as the leftmost screen? I am using OnePlus 8.

Is it possible to remove "Tips & Support" from the settings menu? On OOS10 this is a useless function as there is no OOS10 support anymore and nothing is displayed in this menu. Maybe there is some ADB command to remove it? I found nothing on the internet about this.

Magisk 24.3 "su" Permission denied

Greetings, I've been attempting for several days to execute "su" from adb shell. Essentially, Magisk 24.3 is properly installed within Android 12 on a Google Pixel 6. My primary purpose for rooting is to add my LAN entries to /system/etc/hosts.
An androidforums.com thread details the steps taken several times.
I would very much appreciate your help in getting "su" to work in Android 12 on a Pixel 6. No such problem occurred in Android 8.2 on a Nexus 6P.
Magisk is now uninstalled from the phone, and doesn't appear in the list of apps on the Pixel 6.
On the laptop:
$ adb install Magisk-v24.3.apk
Performing Streamed Install
Success
Invoking Magisk on the phone indicates that the App 24.3 (24300)(27) is installed, Magisk "Installed: NA"
From the factory image, unzipping image-oriole-sp2a.220305.013.a3.zip into a tmp directory:
$ adb push boot.img /storage/emulated/0/Download/boot.img
boot.img: 1 file pushed, 0 skipped. 51.4 MB/s (67108864 bytes in 1.246s)
In Magisk Install "Select and Patch a file", the boot.img is selected. "LET'S GO" results in a sequence ending with the name of the patched file and "All done!"
On the laptop:
adb pull /storage/emulated/0/Download/magisk_patched-24300_jdnPc.img magisk_patched.img
/storage/emulated/0/Download/magisk_patched-24300_jdnP...ulled, 0 skipped. 35.6 MB/s (67108864 bytes in 1.796s)
$ adb reboot bootloader
$ fastboot flash boot magisk_patched.img
Sending 'boot_a' (65536 KB) OKAY [ 1.683s]
Writing 'boot_a' OKAY [ 0.100s]
Finished. Total time: 1.785s
Android reboots normally. The Magisk app reports "Installed: 24.3 (24300)
On the laptop:
$ adb shell
oriole:/ $ su
Permission denied
13|oriole:/ $ exit
$
Please tell me where was my rooting error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assure you that the correct factory boot.img was transferred to Magisk, and the correct patched *.img file was uploaded and flashed to the phone.

hstroph said:
Greetings, I've been attempting for several days to execute "su" from adb shell. Essentially, Magisk 24.3 is properly installed within Android 12 on a Google Pixel 6. My primary purpose for rooting is to add my LAN entries to /system/etc/hosts.
I would very much appreciate your help in getting "su" to work in Android 12 on a Pixel 6. No such problem occurred in Android 8.2 on a Nexus 6P.
Click to expand...
Click to collapse
I think what you are facing is less about su rights and privileges and more about modern versus legacy partitioning and file systems. See this StackExchange Q&A, in particular the second answer about a hosts file solution.
But instead of mounting /system in Android 12, which is more hardened than 10 and 11, a safer method would involve systemless hosts courtesy of Magisk. One issue with that, though, is that most people use systemless hosts for block lists that redirect in bulk to 127.0.0.0 or 0.0.0.0. Adding friendly host names and IPs gets tricky because ad blocking apps like Adaway tend to overwrite when updating, although Adaway's whitelisting option may do the trick. I've never tried it.
I'm in a similar boat since jumping from Android 9 to 12 when I bought a Pixel 6. Eventually I'd like to use my Pixel for accessing a localhost web server. Until a better idea comes along I'll either use my old Pie phone for local browsing or simply publish to the www server (for testing layouts and responsiveness, etc.). I haven't gotten serious about it yet but I'm interested in any method that doesn't involve /system modifications or reconfiguring my router.

manjaroid said:
I think what you are facing is less about su rights and privileges and more about modern versus legacy partitioning and file systems. See this StackExhange Q&A, in particular the second answer about a hosts file solution. ...
Click to expand...
Click to collapse
Thank you, that got me excited as termux allowed a root prompt. "mount -o rw,remount /" executed, the vi alias was created, but "vi /system/etc/hosts" informed me that the file was read-only.
Not sure what to do next, but again, thank you.

hstroph said:
Thank you, that got me excited as termux allowed a root prompt. "mount -o rw,remount /" executed, the vi alias was created, but "vi /system/etc/hosts" informed me that the file was read-only.
Not sure what to do next, but again, thank you.
Click to expand...
Click to collapse
We need to approach our hosts files differently than was possible with Oreo or Pie. The path with least resistance will be Magisk's built-in systemless hosts module. Mounting /system as rw may have worked for Android 10 or 11, but 12 is stricter and messing with anything on /system could cause a cascade of problems.
Also, the /system partition dynamically stays full despite usage reported in Settings/Storage, so there's no elbow room for even the smallest change and you might even see out of space errors if not read-only errors.
What to try? I don't have a good answer yet, only ideas. I will be looking into it and am happy to report back. Hopefully somebody smarter than me will chime in.

Thank you for your interest and efforts.

This XDA thread was revisited today and it reminded me to take a stab at my Pixel's hosts file. With little effort I'm now browsing web server hosts on a Windows laptop from Android 12. All I did was edit its hosts file same way I've always done. Obviously I didn't have have a good grasp of the Magisk overlay and how it symlinks Android's native hosts file.
/system in Android 10+ may be off limits to many legacy operations but not the hosts file as long as Magisk's systemless hosts module is enabled. For su access it's just a matter of granting it to a root capable file manager with a text editor, such as MiXplorer or Solid Explorer.
Here's an example of what's needed for Android 12 browsers to connect to Apache virtualhosts on Windows:
Windows 10 laptop (192.168.1.234) - c:\Windows\System32\drivers\etc\hosts
127.0.0.1 site1.local
127.0.0.1 site2.local
Android 12 Pixel - /system/etc/hosts
192.168.1.234 site1.local
192.168.1.234 site2.local
Hope this is pertinent to what you're trying. Sorry for making it sound impossible earlier.

manjaroid said:
This XDA thread was revisited today and it reminded me to take a stab at my Pixel's hosts file. With little effort I'm now browsing web server hosts on a Windows laptop from Android 12. All I did was edit its hosts file same way I've always done. Obviously I didn't have have a good grasp of the Magisk overlay and how it symlinks Android's native hosts file.
/system in Android 10+ may be off limits to many legacy operations but not the hosts file as long as Magisk's systemless hosts module is enabled. For su access it's just a matter of granting it to a root capable file manager with a text editor, such as MiXplorer or Solid Explorer.
...
Click to expand...
Click to collapse
I'd very much like to know what "little effort" it took, please.
Magisk has the systemless module enabled, both MIXplorer and Solid Explorer have root privileges, but neither can copy my downloaded hosts file to /system/etc/hosts ... no success using the MIXplorer text editor either as per your suggestion

hstroph said:
I'd very much like to know what "little effort" it took, please.
Click to expand...
Click to collapse
I edited the hosts file directly by tapping it in MiXplorer and picking an editor. Then I just added a few lines, saved, and that was it. If you have lots of tedious entries try copy/pasting your text instead of trying to replace the file.
I know it doesn't quite make sense since your file managers have root. But overwriting a file on read-only /system is something completely different than opening and editing the hosts file like an ad blocker would do, which is only possible because of the systemless hosts module.

manjaroid said:
... But overwriting a file on read-only /system is something completely different than opening and editing the hosts file like an ad blocker would do, which is only possible because of the systemless hosts module.
Click to expand...
Click to collapse
Which hosts file are you successfully editing, please? Android 12 absolute pathname, if you would be so kind.

hstroph said:
Which hosts file are you successfully editing, please? Android 12 absolute pathname, if you would be so kind.
Click to expand...
Click to collapse
Edit /system/etc/hosts just as you would have done before Android 10, which didn't require the systemless hosts module.
I don't understand most of how systemless root works. But as far as I know, Magisk's systemless hosts module 'hijacks' (for lack of better discription) the hosts file from the system and makes it systemless, similar to a system app converting to a user app.

manjaroid said:
Edit /system/etc/hosts just as you would have done before Android 10, which didn't require the systemless hosts module.
Click to expand...
Click to collapse
I have attempted that many times:
$ adb shell
oriole:/ $ su
Permission denied
13|oriole:/ $
This was in anticipation of a "mount -o rw,remount /system" command in Android 8.2 on a Nexus 6P phone. It no longer works on Android 12 on a Pixel 6. Even a successful su in Termux fails to edit the /system/etc/hosts, or to make either / or /system rw.
Are you actually using Android 12, or are you reciting from memory? Your screen shots are appreciated.

hstroph said:
Are you actually using Android 12, or are you reciting from memory? Your screen shots are appreciated.
Click to expand...
Click to collapse
My Pixel runs Android 12 build SPA2A.220405.004 and Magisk 24.3. Screen shots won't show anything useful.
The su command in adb shell or Termux aren't needed even if mounting /system with write permission was possible. You're chasing your tail going about it this way.
A root file manager used as described is all that's needed to edit the hosts file. If you're being denied write access there must be something wrong with Magisk, systemless hosts, interference from other Magisk modules or something else.
To trouble shoot Magisk,
- try disabling systemless hosts in Magisk, reboot, re-enable it again & reboot again
- if using Magisk Canary try the more stable 24.3
A simple way to test systemless hosts is to install Adaway, choose the root option and grant su access. If the module is working Adaway will build a large hosts file from preset lists.
- a storage full error on the first run isn't unusual, but it should write to the hosts file next run
- if there's constant errors something isn't right, probably with Magisk or systemless hosts
- if it does write to the hosts file you should be able to edit it manually
- disable all block lists before uninstalling Adaway to empty the hosts file

manjaroid said:
My Pixel runs Android 12 build SPA2A.220405.004 and Magisk 24.3. ...
Click to expand...
Click to collapse
My Pixel 6 runs Android 12 build SPA2A.220305.013.A3 with Magisk 24.3
manjaroid said:
A root file manager used as described is all that's needed to edit the hosts file. If you're being denied write access there must be something wrong with Magisk, systemless hosts, interference from other Magisk modules or something else.
...
A simple way to test systemless hosts is to install Adaway, choose the root option and grant su access. If the module is working Adaway will build a large hosts file from preset lists.
Click to expand...
Click to collapse
Before Adaway (from adb shell):
oriole:/ $ wc -l /system/etc/hosts
2 /system/etc/hosts
After Adaway:
oriole:/ $ wc -l /system/etc/hosts
110315 /system/etc/hosts
manjaroid said:
- if it does write to the hosts file you should be able to edit it manually
Click to expand...
Click to collapse
I can add a LAN line before all the 127.0.0.1 entries using the rooted MIXplorer text editor, but the file still won't save.
manjaroid said:
- disable all block lists before uninstalling Adaway to empty the hosts file
Click to expand...
Click to collapse
There were no previous block lists of any kind. I have simply been trying to add a couple dozen LAN entries on this new phone.
I think I've followed instructions as carefully as possible, but still no luck.

hstroph said:
My Pixel 6 runs Android 12 build SPA2A.220305.013.A3 with Magisk 24.3
Before Adaway (from adb shell):
oriole:/ $ wc -l /system/etc/hosts
2 /system/etc/hosts
After Adaway:
oriole:/ $ wc -l /system/etc/hosts
110315 /system/etc/hosts
I can add a LAN line before all the 127.0.0.1 entries using the rooted MIXplorer text editor, but the file still won't save.
There were no previous block lists of any kind. I have simply been trying to add a couple dozen LAN entries on this new phone.
I think I've followed instructions as carefully as possible, but still no luck.
Click to expand...
Click to collapse
Systemless hosts appears to be working if there were no errors and 110315 entries were written to hosts.
In MiXplorer's Settings/More Settings, is the first item for Allow Root checked? I don't remember if the default is checked or not but it needs to be checked. The equivalent setting in Solid Explorer is off by default.
My two screenshots show before and after enabling/disabling Adaway's block lists. The second image shows Adaway's leftovers along with my own lines added manually and the file is saved (save button being greyed out). If you're unable to get the same results I'm stumped and need to think about what's going wrong.

manjaroid said:
..
In MiXplorer's Settings/More Settings, is the first item for Allow Root checked? I don't remember if the default is checked or not but it needs to be checked.
Click to expand...
Click to collapse
It is checked in MIXplorer.
manjaroid said:
The equivalent setting in Solid Explorer is off by default.
Click to expand...
Click to collapse
I'm unable to locate an equivalent setting in Solid Explorer (SE), but root usage was granted through Magisk 24.3 when I used SE for the first time.
manjaroid said:
My two screenshots show before and after enabling/disabling Adaway's block lists. The second image shows Adaway's leftovers along with my own lines added manually and the file is saved (save button being greyed out). If you're unable to get the same results I'm stumped and need to think about what's going wrong.
Click to expand...
Click to collapse
My attached image shows a failure to save in MIXplorer after adding a single "192.168.1.13 tncpi" line.
I've been stumped on the matter ever since Android 12 on this new Pixel 6.

Is Zygisk enabled in Magisk? I assume you followed this guide for rooting.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Appending a line using Termux works for me also. Are you denied when you try?
Code:
$ su
# echo 192.186.1.234 site3.local >> /system/etc/hosts
If that works there's no reason a root file manager shouldn't work. (To enable root in Solid Explorer tap the hamburger icon upper left then the sprocket icon and scroll down.)
If nothing works I'm thinking either 1) root isn't complete or 2) attempts at /system mounting had a negative effect. Options to consider:
- remove Magisk and repeat the root process
- remove Magisk, install the April OTA update, then root
- factory reset or flash the April factory zip, then root
My suggestion: Might as well go the full route and factory reset or clean flash. Particularly if there's any chance something went wrong in the root file system.

manjaroid said:
Is Zygisk enabled in Magisk?
Click to expand...
Click to collapse
It is now, so I have more to learn what Zygisk enables.
manjaroid said:
I assume you followed this guide for rooting.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
Correct ... re-flashed factory image, then rooted with Magisk. Process repeated several times carefully, all with same results.
manjaroid said:
Appending a line using Termux works for me also. Are you denied when you try?
Click to expand...
Click to collapse
Appending a line works with Termux. Saving /system/etc/hosts after editing within Termux or Solid Explorer fails.
manjaroid said:
Code:
$ su
# echo 192.186.1.234 site3.local >> /system/etc/hosts
Click to expand...
Click to collapse
Success.
manjaroid said:
If that works there's no reason a root file manager shouldn't work. (To enable root in Solid Explorer tap the hamburger icon upper left then the sprocket icon and scroll down.)
Click to expand...
Click to collapse
Well, neither root file explorer works to save the file, but appending other text to /system/etc/hosts works, so I'll just write a simple shell script that I can run as needed.
I want to thank you so much for your patient help. I never thought Google would make things so difficult for those of us who need the use of a pocket Linux computer.
Please consider this thread closed.

How To Guide [GSI] Fix 'Communication error 22' on Android Auto

If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This error happens because Android Auto is not installed as a system app under /system/priv-app.
The following steps will ensure you can convert Android Auto from a user app to a system app. As usual, I'm not responsible for any damage to your device due to this guide.
Requirements:
Magisk and Magisk Manager (I've tested with 24.3)
Android Auto installed as a user app (I have 7.6.621734-release)
A computer with ADB or an app like Termux
I've tested this on a Xiaomi 11T Pro with Pixel Experience Plus Slim 12.1 (GSI) and Android 12, but it should work for other devices and ROMs as well.
Steps:
Install BusyBox from the Play Store
I could only install to /system/bin, but try out what works for you ROM
Click "Install" and wait for a successful message
(optional) This is just a BusyBox installer, I think you can remove the app at the end of this tutorial
Download terminal_systemizer Magisk module. Keep in mind the latest official release is outdated and does not work on Android 12 and Magisk 24.3. Because of this, you can download it from this post on XDA or clone this fork on GitHub and zip it
Install the Magisk module through Magisk Manager and reboot
Now connect your phone to your computer and launch an adb shell with adb shell, or open Termux
Enter root mode by typing su (not sure if this is required on Termux, but you must do it on adb shell)
Verify that the systemizer module is working by running the help command
Code:
# systemize -h
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
Usage: systemize
or: systemize [options]...
Options:
-nc removes ANSI escape codes
-f use 'Set SELinux' in the session for faster app listing
-a [package name] systemizes the package name(s) provided
-d [apk dir] systemizes the apk(s) provided
-l list all systemized apps
-h show this message
If you get a similar output, you're ready to proceed
Now run the systemize command without any arguments and answer the prompts accordingly. The app you want to systemize is com.google.android.projection.gearhead, which is Android Auto. You want to install it to /system/priv-app and NOT to /system/app.
Below is a sample output:
Code:
============================================
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
============================================
BusyBox v1.32.0-Stericson
/system/bin/busybox
============================================
Enter logs to upload logs
============================================
Set SELinux Enabled: false
SELinux Status: Enforcing
============================================
1 - Systemize Installed Apps (Listed)
2 - Systemize Installed Apps (Enter label)
3 - Systemize given APK
s - Set SELinux
0 - Exit
[CHOICE]: 1
Loading Apps [/]
============================================
Installed Apps =============================
============================================
...
18 - com.google.android.projection.gearhead
...
To systemize multiple apps, enter multiple number. Example: "1 23 30"
x - Back to Menu
r - Refresh list
0 - Exit
[CHOICE]: 18
============================================
Systemizing com.google.android.projection.gearhead
Checking APK directory - OK
Checking package name - com.google.android.projection.gearhead
Where to install?
< 1 - /system/app | 2 - /system/priv-app | 0 - cancel > : 2
Checking APK size - 41M
Transfering base.apk(com.google.android.projection.gearhead) to '/system/priv-app'...
Transfering libs
Granting Permissions
/system/bin/systemize[584]: aapt: can't execute: Permission denied
com.google.android.projection.gearhead - Done
Reboot to apply changes
Return to menu? < y | n >: n
Notice that it threw an error at the end, but it still worked for me. Not sure what happened, let me know if this also happened to you.
Reboot
Check that Android Auto is a system app by opening its app info page. If there is no uninstall button like below, it's installed as a system app
Please reply if you have any questions or issues!
Hope this helps

Good guide
Yh this error comes because Android auto needs to be installed as an system app.

Thank you for sharing this, I made all the steps, it worked without errors but I see the app as system app but I don't have "open" button, in fact the app itself doesn't appear with others (I had to search in settings>app)
Any idea? Thx

suiller said:
Thank you for sharing this, I made all the steps, it worked without errors but I see the app as system app but I don't have "open" button, in fact the app itself doesn't appear with others (I had to search in settings>app)
Any idea? Thx
Click to expand...
Click to collapse
Hm that's weird, I don't see how that could happen.
Try grabbing an APK from apkmirror and installing the app again (must be the same version or newer)

I managed it... now I see the app as regular (system) app...
The problem was busybox, I used that one provided as magisk module and worked at 1st attempt

diogotc said:
Hm that's weird, I don't see how that could happen.
Click to expand...
Click to collapse
I dunno why but busybox was the problem, I just installed the version provided here in 1st post, even if without error something happened so I had the app moved under priv but it wasn't available as regular/working app
Anyway I had to:
restore androidauto from systemize, reboot
deinstall androidauto, reboot
install busybox as module from magisk
re-run systemize as instructions at 1st post, reboot

Hi
no work for me
have asus rog 5 with china rom
installed android auto
root ok
i follow this guide...android auto install is marked ok and seems all ok....it is system app
but in my car i obtain a loop android auto: link, after 1 sec stop, then link, then stop and so away
if i run systemize again, android auto is not became a system app anymore

Thanks bro work great Xiaomi 12s ultra 13.0.8

Thanks for your guide,it worked on a Redmi Note 7 with latest PPUI ROM, but as soon as I remove Magisk the app reverts to user app and not system app. Since I cant get my bank app to work on rooted phones, even with Magisk hidden, is there a way to keep AA as system app without having to keep Magisk installed?

farrayoles said:
Thanks for your guide,it worked on a Redmi Note 7 with latest PPUI ROM, but as soon as I remove Magisk the app reverts to user app and not system app. Since I cant get my bank app to work on rooted phones, even with Magisk hidden, is there a way to keep AA as system app without having to keep Magisk installed?
Click to expand...
Click to collapse
As far as I know you'll need Magisk installed. The latest version of the Pixel Experience GSI already includes an Android Auto stub to avoid this problem, maybe you can ask that ROM developer to do the same.
Anyway, you should be able to bypass your banking app verification. Have you added it to the DenyList as well as change the package name of MagiskManager?
You can try an app like RootBeer to see what else you need to do.
It might also help deleting the data from the banking app, since it might store if you had root or not.
Hope that helps!

Skyline_r said:
Thanks bro work great Xiaomi 12s ultra 13.0.8
Click to expand...
Click to collapse
Does wireless android auto work for you? My AA crashes on the xiaomi mi fold x 2

Does Root is required to do so before start? Becuase I can't install Busybox if the phone is not rooted.

I tried this on my SM-X200 and all the steps worked (can not uninstall at app info) but when I went to plug the tablet into my car it still gives me error 22

Skyline_r said:
Thanks bro work great Xiaomi 12s ultra 13.0.8
Click to expand...
Click to collapse
hi, can i check if you performed these steps on a custom rom? or the chinese rom? thanks!

diogotc said:
If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car):
View attachment 5636057
This error happens because Android Auto is not installed as a system app under /system/priv-app.
The following steps will ensure you can convert Android Auto from a user app to a system app. As usual, I'm not responsible for any damage to your device due to this guide.
Requirements:
Magisk and Magisk Manager (I've tested with 24.3)
Android Auto installed as a user app (I have 7.6.621734-release)
A computer with ADB or an app like Termux
I've tested this on a Xiaomi 11T Pro with Pixel Experience Plus Slim 12.1 (GSI) and Android 12, but it should work for other devices and ROMs as well.
Steps:
Install BusyBox from the Play Store
I could only install to /system/bin, but try out what works for you ROM
Click "Install" and wait for a successful message
(optional) This is just a BusyBox installer, I think you can remove the app at the end of this tutorial
Download terminal_systemizer Magisk module. Keep in mind the latest official release is outdated and does not work on Android 12 and Magisk 24.3. Because of this, you can download it from this post on XDA or clone this fork on GitHub and zip it
Install the Magisk module through Magisk Manager and reboot
Now connect your phone to your computer and launch an adb shell with adb shell, or open Termux
Enter root mode by typing su (not sure if this is required on Termux, but you must do it on adb shell)
Verify that the systemizer module is working by running the help command
Code:
# systemize -h
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
Usage: systemize
or: systemize [options]...
Options:
-nc removes ANSI escape codes
-f use 'Set SELinux' in the session for faster app listing
-a [package name] systemizes the package name(s) provided
-d [apk dir] systemizes the apk(s) provided
-l list all systemized apps
-h show this message
If you get a similar output, you're ready to proceed
Now run the systemize command without any arguments and answer the prompts accordingly. The app you want to systemize is com.google.android.projection.gearhead, which is Android Auto. You want to install it to /system/priv-app and NOT to /system/app.
Below is a sample output:
Code:
============================================
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
============================================
BusyBox v1.32.0-Stericson
/system/bin/busybox
============================================
Enter logs to upload logs
============================================
Set SELinux Enabled: false
SELinux Status: Enforcing
============================================
1 - Systemize Installed Apps (Listed)
2 - Systemize Installed Apps (Enter label)
3 - Systemize given APK
s - Set SELinux
0 - Exit
[CHOICE]: 1
Loading Apps [/]
============================================
Installed Apps =============================
============================================
...
18 - com.google.android.projection.gearhead
...
To systemize multiple apps, enter multiple number. Example: "1 23 30"
x - Back to Menu
r - Refresh list
0 - Exit
[CHOICE]: 18
============================================
Systemizing com.google.android.projection.gearhead
Checking APK directory - OK
Checking package name - com.google.android.projection.gearhead
Where to install?
< 1 - /system/app | 2 - /system/priv-app | 0 - cancel > : 2
Checking APK size - 41M
Transfering base.apk(com.google.android.projection.gearhead) to '/system/priv-app'...
Transfering libs
Granting Permissions
/system/bin/systemize[584]: aapt: can't execute: Permission denied
com.google.android.projection.gearhead - Done
Reboot to apply changes
Return to menu? < y | n >: n
Notice that it threw an error at the end, but it still worked for me. Not sure what happened, let me know if this also happened to you.
Reboot
Check that Android Auto is a system app by opening its app info page. If there is no uninstall button like below, it's installed as a system app
View attachment 5636069
Please reply if you have any questions or issues!
Hope this helps
Click to expand...
Click to collapse
Hey Bro. I'm trying to follow your instruction but I'm not able to use the busy box it's saying that I should remove the superuser.
Can you please help?

Hi, diogotc
Thank you so much, worked flawlessly. The instructions you provided were excellent. I used the systemizer on AA 8.3.624114. I used this on a Lenovo Legion Duel 2 with CN rom Android 12, with Magisk 25.2.
One difference I had was the AA app was just named Android Auto (number 3) in the systemizer list, but I had zero issues.
Thanks again!

The con.android.... path does not appear... I stay un systemize option 1 por 2 and it tells me that the file does not existe, do i hace to create it un busybox?
I don't understand why it doesn't appear it xd

Thanks for this
Just followed your instructions running ThinROM A13 v4 [15/12/2022]-[GVK9-[EXYNOS]-[SM-N986B]-[SM-N985F] on my SGN20U (SM-N986B/DS)
I couldn't get SU permission, Terminal Systemizer was greyed out in MM, so installed ADB Root v1.0 and it all worked like a charm from there.

Hi,
Thanks for the guide. I want to install the Android Auto on Redmi Pad so that I can use the pad as an Entertainment HeadUnit in my car. Can I follow these instructions and still it will work ?
Let me know. Appreciate your help and support

Thanks for that useful post but i'm receiving error after choose 2 - /system/priv-app and paste com.google.android.projection.gearhead
/data/app/com.google.android.projection.gearhead-*/base.apk doesn't exist!
Android auto is already insattaled. i'm using windows 10 and adb shell command.
Any idea ?

Abnormal State - "su" binary not from Magisk has been detected

Hello!
I am on LOS GSI 19.1, S20 FE LTE Exynos (with TWRP) - when starting Magisk have this msg:
Abnormal State
A "su" binary not from Magisk has been
detected. Please remove any competing
root solution and/or reinstall Magisk.
What could be reason of that and how to fix it. :/ Maybe someone can help...

Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.

YoShake said:
Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.
Click to expand...
Click to collapse
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.

AirForceNBA said:
do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
if rom you use is complied with adb root capabilites, then just use linux mv command after connecting to shell
Code:
adb root
adb shell
mv /system/xbin/su /system/xbin/zu
if not, then maybe under twrp commandline it could be possible?

AirForceNBA said:
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
I solve this issue in my gsi evolution X android 13 after flash overlyfs.zip in my magisk manager ... Click Download System Rw in this site
Magisk Modules - some Daily use Magisk Mods in 2022 | Use these Modules Daily ! » Tech Karan
Magisk Modules are here !
techkaran.co.in
and then flash overlyfs.zip using magisk manager...
Need telegram apps and account to download the file...

Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?

Did
K_a_m_i said:
Any idea?
Click to expand...
Click to collapse
Did you set rw on /system or /system/xbin?
Set rw on the top dir, not nested one in which you want to make changes, or you won't get permissions to change anything in any nested directory you set rw on.
Try to copy the file somewhere else and then delete it from its original path. But I bet you won't succeed. Maybe changing the owner/group and all permissions to 777 would do.
I'd also try in safe mode, or in native recovery mode (not twrp, assuming you still have access to it) using ADB

For me it disapeard by reinstalling magisk by the TWRP.

K_a_m_i said:
Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?
Click to expand...
Click to collapse
Are you try to flash Overlyfs first without any module in your magisk...
After you flash magisk manager in your phone and installed already, open it and then restart your phone.. then
First: flash only Overlyfs.zip in your magisk without any module installed.. then restart your phone
Second: download root explorer and grant root
Third: find su in system/xbin and rename it in ZU and save and delete zu then restart your phone
I hope I helped you with this post