After I run the root command nothing happens

[newbit1]

After I run the root command nothing happens

[newbit1]

Oh thats a new one.
Can you connect via adb shell to the avd?
which terminal is it? Cmd?

[mthp1999]

I think so

[mthp1999]

I stopped bypassed the test adb function to see if it actually worked

no dice

[mthp1999]

Yeah just using windows terminal

[mthp1999]

Was able to shutdown the devices through shell

[newbit1]

Looks pretty good to me. And did it worked now?

[mthp1999]

It doesn't seem so, no magisk app is installed even on reboot. Doesnt look like it finishes the script based on your gif

[newbit1]

do you have a full log? As text and not just as screenshots.

[mthp1999]

where would the log save?

[newbit1]

Just copy & paste the command window output

[sdlee3]

Same to me, after run the command , the emulator closed
./rootAVD.sh ~/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a/ramdisk.img

I manually start the emulator again, then the emulator was stuck in a black screen forever, and did not proceed to startup the device. I check "adb devices" and "adb shell", it show the device is offline

[newbit1]

Same to me, after run the command , the emulator closed
./rootAVD.sh ~/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a/ramdisk.img

I manually start the emulator again, then the emulator was stuck in a black screen forever, and did not proceed to startup the device. I check "adb devices" and "adb shell", it show the device is offline

Please provide the complete log

[wubaojie]

Same to me, after run the command , the emulator closed ./rootAVD.sh ~/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a/ramdisk.img

I manually start the emulator again, then the emulator was stuck in a black screen forever, and did not proceed to startup the device. I check "adb devices" and "adb shell", it show the device is offline

i have encountered the similar problem, maybe you can try my approach.
first, use cmd shell to start the emulator, and the cmd is " ~/Library/Android/sdk/emulator/emulator -avd Pixel_2_API_30 -writable-system"
second, if the emulator runs ok, then you can try to launch emulator by android studio

[smoothdvd]

@mthp1999 @wubaojie @sdlee3 @newbit1 Try add arg -no-snapshot to emulator. Like this:

emulator -no-snapshot -avd Pixel_5_API_30

[ricklambrechts]

Same issue. I remove @echo off from the script for debugging and this is the output:

rootAVD-master>REM Set Folders and FileNames

rootAVD-master>echo [*] Set Directorys
[*] Set Directorys

rootAVD-master>set AVDPATHWITHRDFFILE=InstallApps

rootAVD-master>for /F "delims=" %i in ("InstallApps") do (
set AVDPATH=%~dpi
 set RDFFILE=%~nxi
)

rootAVD-master>(
set AVDPATH=rootAVD-master\
 set RDFFILE=InstallApps
)

rootAVD-master>REM If we can CD into the ramdisk.img, it is not a file!

rootAVD-master>cd InstallApps  1>nul 2>&1

rootAVD-master>if "1" == "0" (call :ShowHelpText )

rootAVD-master>if 1 == 0 (call :restore_backups )

rootAVD-master>call :TestADB

rootAVD-master>SetLocal EnableDelayedExpansion

rootAVD-master>set HOME=C:\Users\Rick Lambrechts\AppData\Local\

rootAVD-master>set ADB_DIR_W=Android\Sdk\platform-tools\

rootAVD-master>set ADB_DIR=""

rootAVD-master>set ADB_EX=""

rootAVD-master>echo [-] Test if ADB SHELL is working
[-] Test if ADB SHELL is working

rootAVD-master>set ADBWORKS=

rootAVD-master>adb shell -n echo true  1>tmpFile 2>&1

rootAVD-master>set /P ADBWORKS= 0<tmpFile

rootAVD-master>del tmpFile
rootAVD-master>                       ) else (
rootAVD-master>