Rooted but Magisk not available

[lavish440]

Rooted but Magisk not available

[lavish440]

[newbit1]

which avd?
Complete log please.

[lavish440]

which avd? Complete log please.

Android API 34

./rootAVD.sh system-images/android-34/google_apis/x86_64/ramdisk.img                                                                                      [!] and we are NOT in an emulator shell
[*] Set Directorys
[-] source.properties file exist
[*] AVD system-image Pkg.Revision=7
[-] Test if ADB SHELL is working
[*] ADB connection possible
[-] In any AVD via ADB, you can execute code without root in /data/data/com.android.shell
[*] Cleaning up the ADB working space
[*] Creating the ADB working space
[-] Magisk installer Zip exists already
[*] Push Magisk.zip into /data/data/com.android.shell/Magisk
[-] ./Magisk.zip: 1 file pushed, 0 skipped. 189.9 MB/s (11278270 bytes in 0.057s)
[-] ramdisk.img Backup exists already
[*] Push ramdisk.img into /data/data/com.android.shell/Magisk/ramdisk.img
[-] /home/lavish/Android/Sdk/system-images/android-34/google_apis/x86_64/ramdisk.img: 1 file pushed, 0 skipped. 245.1 MB/s (2226696 bytes in 0.009s)
[*] Push rootAVD.sh into /data/data/com.android.shell/Magisk
[-] rootAVD.sh: 1 file pushed, 0 skipped. 77.3 MB/s (79634 bytes in 0.001s)
[-] run the actually Boot/Ramdisk/Kernel Image Patch Script
[*] from Magisk by topjohnwu and modded by NewBit XDA
[!] We are in a ranchu emulator shell
[-] Api Level Arch Detect
[-] Device Platform is x64 only
[-] Device SDK API: 34
[-] First API Level: 33
[-] The AVD runs on Android 14
[-] Switch to the location of the script file
[*] Looking for an unzip binary
[-] unzip binary found
[*] Extracting busybox and Magisk.zip via unzip ...
[*] Finding a working Busybox Version
[*] Testing Busybox /data/data/com.android.shell/Magisk/lib/arm64-v8a/libbusybox.so
[*] Testing Busybox /data/data/com.android.shell/Magisk/lib/x86/libbusybox.so
[!] Found a working Busybox Version
[!] BusyBox v1.34.1-Magisk (2022-03-22 04:11:29 PDT) multi-call binary.
[*] Move busybox from lib to workdir
[-] Checking AVDs Internet connection...
[!] AVD is offline
[*] Re-Run rootAVD in Magisk Busybox STANDALONE (D)ASH
[-] We are now in Magisk Busybox STANDALONE (D)ASH
[*] rootAVD with Magisk '25.2' Installer
[-] Get Flags
[*] System-as-root, keep dm/avb-verity
[-] Encrypted data, keep forceencrypt
[*] RECOVERYMODE=false
[-] KEEPVERITY=true
[*] KEEPFORCEENCRYPT=true
[-] copy all x86_64 files from /data/data/com.android.shell/Magisk/lib/x86_64 to /data/data/com.android.shell/Magisk
[*] Detecting ramdisk.img compression
[!] Ramdisk.img uses lz4_legacy compression
[-] taken from shakalaca's MagiskOnEmulator/process.sh
[*] executing ramdisk splitting / extraction / repacking
[-] API level greater then 30
[*] Check if we need to repack ramdisk before patching ..
[*] After decompressing ramdisk.img, magiskboot will work
Detected format: [lz4_legacy]
[-] Checking ramdisk STATUS=1
[-] Magisk patched boot image detected
[*] Verifying Boot Image by its Kernel Release number:
[-] This AVD = 6.1.23-android14-4-00257-g7e35917775b8-ab9964412
[-]  Ramdisk = 6.1.23-android14-4-00257-g7e35917775b8-ab9964412
[!] Ramdisk is probably from this AVD
[*] repacking back to ramdisk.img format
[!] Rename Magisk.zip to Magisk.apk
[*] Pull ramdiskpatched4AVD.img into ramdisk.img
[-] /data/data/com.android.shell/Magisk/ramdiskpatched4AVD.img: 1 file pulled, 0 skipped. 156.0 MB/s (2226696 bytes in 0.014s)
[*] Pull Magisk.apk into 
[-] /data/data/com.android.shell/Magisk/Magisk.apk: 1 file pulled, 0 skipped. 141.7 MB/s (11278270 bytes in 0.076s)
[-] Clean up the ADB working space
[-] Install all APKs placed in the Apps folder
[*] Trying to install Apps/Magisk.apk
[*] Performing Streamed Install
[*] Success
[-] Shut-Down & Reboot (Cold Boot Now) the AVD and see if it worked
[-] Root and Su with Magisk for Android Studio AVDs
[-] Trying to shut down the AVD
[!] If the AVD doesn't shut down, try it manually!
[-] Modded by NewBit XDA - Jan. 2021
[!] Huge Credits and big Thanks to topjohnwu, shakalaca, vvb2060 and HuskyDG

[newbit1]

your avd is offline, that is why you dont get to choose the Magisk version.

Did you do a cold boot?

[lavish440]

Yes. I did a coldboot and my AVD is not offline.

[lavish440]

Fixed the issue by installing AVD with Android API 30. But now Magisk ask for additional setup every time I open it.

[newbit1]

[!] AVD is offline

You log says different.

[-] Checking ramdisk STATUS=1
[-] Magisk patched boot image detected

restore to your stock ramdisk and try again
./rootAVD.sh system-images/android-34/google_apis/x86_64/ramdisk.img restore

Fixed the issue by installing AVD with Android API 30. But now Magisk ask for additional setup every time I open it.

That is totally normal.
If you install Magisk 26.x, you must use the FAKEBOOTIMG argument to install Magisk proper.
Read the pop up message carefully and
check out the readme, it is all written there why and how.

./rootAVD.sh system-images/android-34/google_apis/x86_64/ramdisk.img FAKEBOOTIMG

[lavish440]

My bad but the issue is still there for API 34

[newbit1]

I am sorry, without any further informations, I can't help you.

[lavish440]

I will try to reproduce the issue tomorrow. Only logs are needed or something else?

[newbit1]

no logs are fine.
And don't forget to coldboot.
Another user mentioned that even with coldboot, his avd load a snapshot.

[lavish440]

I will use emulator -no-load-snapshot. Also, which command should I run? Is ./rootAVD.sh system-images/android-34/google_apis/x86_64/ramdisk.img enough or do I need any other command for API 34.

[newbit1]

when you create the avd, you can set it up, only to cold reboot it. This is my default settings. As I said, use the fakeboot img argument for magisk 26.x

[lavish440]

Working now with API 34. Closing this issue as completed. But it still doesn't ask me the Magisk version to install.
Thanks for your time and effort to make this project.

[newbit1]

so you saying good and bad news...

I ve seen this a few times when I started the avd via command line. Not sure how this is related.

Sometimes the avd needs to be running for a little while, so that the script can detect its online status.

You can try to run the script with the DEBUG argument, a couple times, until you see the the avd is online status. Then run the script normally without the DEBUG.

Which system you running the script? Mac? Linux?

[lavish440]

When the issue happened with me, I wasn't running the AVD from Command line. Maybe I was doing something wrong with your script. The second time I reinstalled the AVD and your script worked flawlessly.
I am using Linux (Arch Linux).

[newbit1]

When the issue happened with me, I wasn't running the AVD from Command line. Maybe I was doing something wrong with your script. The second time I reinstalled the AVD and your script worked flawlessly.
I am using Linux (Arch Linux).

Maybe you mixed up the ramdisk with another avd, happens all the time.
Yeah this avd is offline thing, is most of the times, some sort of false positive.
Perhaps I should look for a different way to check the online status.