yashsingh1/xdaforums huggingface dataset:
[Android Studio] albrechtc:
Please look at this~~~

Windows 11

PS D:\Android\rootAVD-master> .\rootAVD D:\Android\AndroidSDK\system-images\android-29\google_apis\x86_64\ramdisk.img
[*] Set Directorys
[-] Test if ADB SHELL is working
[-] ADB connectoin possible
[-] In any AVD via ADB, you can execute code without root in /data/data/com.android.shell
[*] looking for Magisk installer Zip
[*] Cleaning up the ADB working space
[*] Creating the ADB working space
[*] Push Magisk.zip into /data/data/com.android.shell/Magisk
[-] D:\Android\rootAVD-master\Magisk.zip: 1 file pushed, 0 skipped. 511.1 MB/s (6874374 bytes in 0.013s)
[-] Backup exists already
[*] Push ramdisk.img into /data/data/com.android.shell/Magisk
[-] D:\Android\AndroidSDK\system-images\android-29\google_apis\x86_64\ramdisk.img: 1 file pushed, 0 skipped. 776.6 MB/s (898444 bytes in 0.001s)
[-] Copy rootAVD Script into Magisk DIR
rootAVD.sh: 1 file pushed, 0 skipped. 855.5 MB/s (1998366 bytes in 0.002s)
[-] run the actually Boot/Ramdisk/Kernel Image Patch Script
[*] from Magisk by topjohnwu and modded by NewBit XDA
[!] We are in an emulator shell
[-] Switch to the location of the script file
[*] Extracting busybox and Magisk.zip ...
chmod: /data/data/com.android.shell/Magisk/lib: No such file or directory
mv: bad '/data/data/com.android.shell/Magisk/lib/x86/libbusybox.so': No such file or directory
mv: bad '/data/data/com.android.shell/Magisk/lib/armeabi-v7a/libbusybox.so': No such file or directory
/data/data/com.android.shell/Magisk/rootAVD.sh[1463]: /data/data/com.android.shell/Magisk/busybox: inaccessible or not found
/data/data/com.android.shell/Magisk/rootAVD.sh[1463]: /data/data/com.android.shell/Magisk/busybox: inaccessible or not found
/data/data/com.android.shell/Magisk/rootAVD.sh[1463]: /data/data/com.android.shell/Magisk/busybox: inaccessible or not found
[-] Checking AVDs Internet connection...
[!] AVD is offline
[*] Re-Run rootAVD in Magisk Busybox STANDALONE (D)ASH
/data/data/com.android.shell/Magisk/rootAVD.sh[1463]: /data/data/com.android.shell/Magisk/busybox: inaccessible or not found

Always failed...
[Android Studio] newbit:
My apologies for that inconvenience, this is fixed now.
[Android Studio] Const_1c:
Sorry! I have some problen with rootAVD.. What can i do? Thanks
[Android Studio] newbit:
Sorry I've answered already on this post, but it seems it didn't get through.

You need to re download the script and try again, It looks like something was broken on the script.

I hope this works now.
[Android Studio] albrechtc:
Windows 11 Pro

AVD with Android 7.0 & 8.0, with no Google APIs

No matter which of the images i installed, the errors always came out like this:

PS C:\Users\Albre\Downloads\Compressed\rootAVD-master> .\rootAVD.bat D:\Android\AndroidSDK\system-images\android-24\default\x86_64\ramdisk.img
[*] Set Directorys
[-] Test if ADB SHELL is working
[-] ADB connectoin possible
[-] In any AVD via ADB, you can execute code without root in /data/data/com.android.shell
[*] looking for Magisk installer Zip
[*] Cleaning up the ADB working space
[*] Creating the ADB working space
[*] Push Magisk.zip into /data/data/com.android.shell/Magisk
[-] C:\Users\Albre\Downloads\Compressed\rootAVD-master\Magisk.zip: 1 file pushed, 0 skipped. 265.0 MB/s (6874374 bytes in 0.025s)
[*] create Backup File
[*] Push ramdisk.img into /data/data/com.android.shell/Magisk
[-] D:\Android\AndroidSDK\system-images\android-24\default\x86_64\ramdisk.img: 1 file pushed, 0 skipped. 631.6 MB/s (1709250 bytes in 0.003s)
[-] Copy rootAVD Script into Magisk DIR
rootAVD.sh: 1 file pushed, 0 skipped. 245.4 MB/s (7825022 bytes in 0.030s)
[-] run the actually Boot/Ramdisk/Kernel Image Patch Script
[*] from Magisk by topjohnwu and modded by NewBit XDA
[!] We are in an emulator shell
[-] Api Level Arch Detect
[-] Device Platform: x64
[-] ARCH32 x86
[-] Device SDK API: 24
[-] First API Level:
[-] Switch to the location of the script file
[*] Extracting busybox from script ...
[!] There is no busybox behind the script
[!] Run rootAVD with UpdateBusyBoxScript first

please help me....
[Android Studio] newbit:
It looks a bit like Const_1c issue. Your rootAVD.sh could be broken somehow.

Do you mind uploading me your rootAVD folder? You could also try to re-download and try it again.
[Android Studio] Drogon6:
I'm having this issue over and over please help me
[Android Studio] newbit:
It seems that you dont have adb installed.

EDIT:

I've updated the README.md on how you can install ADB (Android SDK Platform-Tools)
[Android Studio] thienha1:
I checked all things, Android SDK Platform-Tools checked and installed

Checked ADB Shell, work

But... Why rootAVD doesnt recognize i have them all?

Can you explain how it work?
[Android Studio] newbit:
Well done! Yes, you dont run the script with InstallApps as a first attempt. The first run is with the path to your ramdisk.img. I guess why people asking more and more about this issue is, it is showen in this How To Video. Which is wrong. I've already wrote to the Author of the Video to correct this, but I got no response yet. So run the script without anything, check if your ramdisk is listed in the examples, if not use the listallavds parameter, and then pick your path, copy and paste the whole line and hit it. Thats it, no need to installapps at all.
[Android Studio] thienha1:
I follow your instruction that running "with the path to your ramdisk.img" but it seem running as same as running with InstallApps

And this command "ListAllAVDs" seem doesn't work
[Android Studio] newbit:
Is your AVD running? Check the preconditions. Do you have any AVD installed? I can't see the whole output of the listallavds command. Did you set your ADB to PATH? There was indeed a typo in the testADB routine. Redownload the script please and try again. It should give you the right message what to do now.

Btw: Please don't use screenshots from the terminal output. Make a copy of the text please and paste it as code here. Thanks
[Android Studio] newbit:
wow very good. just copy and paste the command in your shell

set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%

No need to change the script itself

And btw: Android Pie API 28 is not supported. See the README.md for more explanations.

But you can root non Google Play Images out of the box via adb commands.

Follow this
[Android Studio] thienha1:
But this guide look like for Linux only, not Windows
[Android Studio] newbit:
Well the guide yes, but the commands work in windows as well. They are emulator and adb related. Or just pick another AVD API Level. 29 or 30 for example.
[Android Studio] thienha1:
I try paste command as well but shell not recognized this

set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%

Result

%PATH% : The term '%PATH%' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:52
+ set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (%PATH%:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[Android Studio] newbit:
this could be a powershell related issue. I never used powershell, only the classic cmd prompt. Try to run "cmd" and then the script from there.
[Android Studio] thienha1:
I tried running script in cmd instead of PowerShell and it work perfectly, thank you
[Android Studio] justfielding:
Thank you for this. Everything seems to be working just fine still! Only hiccup I had was i didn't noticed the prompt to choose a Magisk version.

Random info: aarch64/arm64 m1, API 31, magisk alpha
[Android Studio] Yanchik5261:
I'm stuck on this moment :

Spoiler content hidden.
[Android Studio] newbit:
Use cmd not powershell

And don't use installapps.

Use the path to your ramdisk instead.

Read the readme please.
[Android Studio] K9R15:
Boa tarde,

como usar o emulador de câmera android studio, eu quero que ele reproduza imagens do vídeo obs.

grato!

se possível indicar tutorial do youtube.

obrigado
[Android Studio] newbit:
Boa tarde,

depending on your Host OS, you can attach an USB Webcam without any mods.

But if not, you probably need some mods to pass an USB Device through.

Check out my [GUIDE] Build / Mod AVD Kernel Android [10] [11] [12] rootAVD [Magisk] [USB passthrough] [Linux] [Windows] [Google Play Store API]

I don't do Youtube Tutorials.

Cheers

NewBit
[Android Studio] Alberth-OC:
Can anyone help me? I'm not able to enter su. What is the problem?
[Android Studio] rk2429:
Is there a way to hide the root in AVD? I have tried a lot of tools and tutorials, but all in vain. I'm currently on Magisk 24.1. I have tried Zygisk and Riru, but no method works for me. No issues with root. Please help.
[Android Studio] newbit:
Did you try the DenyList? In Settings...
[Android Studio] rk2429:
Yes I have added Google play services ( tried with whole Google play services and with two sub options namely gms and unstable under Google play services) to Deny list. I have also used universal safety net and Magisk Hide Props.
[Android Studio] newbit:
Ah ok, so you want to pass safetynet checks. This wont work, it never did.
[Android Studio] mukund123rana:
it doesn't not to anything it just show

C:\Users\Mukund Rana\Desktop\rootAVD-master>rootAVD.bat installapps

[*] Set Directorys

[-] Test if ADB SHELL is working

else was unexpected at this time.
[Android Studio] newbit:
Thats normal. Didnt you README.md?
[Android Studio] 0xNet:
Is there a way to disable rootAVD on a specific emulator from Android Studio?
[Android Studio] newbit:
Can't follow you what you are trying to achieve, but it sounds interesting though.

Could you please more specific on what you are trying to do?
[Android Studio] 0xNet:
I am new to this, I used rootAVD to root my emulator on Android Studio. Then I spawned a new device on the emulator and I noticed that it was already rooted from the start. I don't know if that make sense, sorry english not first language.

Basically what I want is there's a rooted and non-rooted device on my Android Studio using rootavd
[Android Studio] newbit:
Ok i see. So the patched ramdisk with root, is replacing the stock ramdisk of your Device's System Image.

Every time you create a new device with that System image, this patched ramdisk is automatically used. I can't think of a way right now,

on how to "hot swap" the patched ramdisk with the original one. But you could just use/download a

different System Image. Does this makes sense to you? For example: You have an Android 10 Image with

a patched ramdisk, and then you have another Image, but with Android 11 and an original ramdisk.

If I come with another, more elegant, idea up, I will let you know. Or If you find something, you are welcome to share it with me.
[Android Studio] 0xNet:
Thanks for the response, it makes sense to me now.
[Android Studio] newbit:
What is your OS you are running your AVD Studio?
[Android Studio] 0xNet:
macOS, I'm using rootAVD to do some Mob App Security Research
[Android Studio] newbit:
Nice, me too.

I've added a little toggleRamdisk function into the script.

By calling the script with your path to the Ramdisk + toggleRamdisk,

it will switch between the patched and the original one.

./rootAVD.sh ~/Library/Android/sdk/system-images/android-Tiramisu/google_apis_playstore/x86_64/ramdisk.img toggleRamdisk

If I understood you right, the procedure would be:

Create two AVDs with the same Image i.e. Tiramisu

Start one of it and rootAVD it

once rooted and booted

toggleRamdisk

Start the second AVD

If both are closed, you need to toggleRamdisk again to get root back on your first AVD.

Another Option would be to call the emulator AVD from the terminal with the Ramdisk parameter.

newbit@rootAVD % export PATH=~/Library/Android/sdk/emulator:$PATH
newbit@rootAVD % emulator --help | grep ramdisk
-ramdisk <file> ramdisk image (default <system>/ramdisk.img

and if we stick to the setup from above:

newbit@rootAVD % emulator --help | grep avd
-list-avds list available AVDs
-avd <name> use a specific android virtual device
-avd-arch <target> use a specific target architecture
-id <name> assign an id to this virtual device (separate from the avd name)
newbit@rootAVD % emulator -list-avds
Pixel_4_API_Tiramisu
Pixel_4_API_Tiramisu_2

it will bring you here:

emulator -avd Pixel_4_API_Tiramisu_2 -ramdisk ~/Library/Android/sdk/system-images/android-Tiramisu/google_apis_playstore/x86_64/ramdisk.img.backup

But then you have to take care of the terminal that started the AVD.

Hope this helps.

Cheers

NewBit
[Android Studio] 0xNet:
Hi thanks for this, I'll have to understand the process first before trying the new function.

Btw, the restore function reverts it back to the original image right?

I'm trying to use it to bring it back to the non-rooted version however when i try it it says

[!] and we are NOT in an emulator shell
[*] Set Directorys
[!] Restoring ramdisk.img.backup to ramdisk.img
[*] Backups still remain in place

It's still rooted even if I tried to delete or reboot the AVD
[Android Studio] newbit:
Hmm, you either mixing up your system images, or you need to do a cold boot.

Is it really still rooted or is just the magisk app installed?
[Android Studio] 0xNet:
Magisk app isn't installed on the device, when I open an app it says the device is rooted. I already did a cold bot on the device and im still encountering the problem

I also tried to fully root the AVD and I can't restore it to a normal AVD using the restore function
[Android Studio] newbit:
Hmm, they must be a mixed up somewhere. Did you delete also all the downloaded system images

under ~/Library/Android/sdk/system-images/ ?
[Android Studio] 0xNet:
Yes,

I think the restore function works and I believe my AVDs went back to original since root checker says that root isn't properly installed. Its just the app that I'm doing research detects if its running on avd it will not allow it to run on it.
[Android Studio] newbit:
What is this Apps name you are researching on?
[Android Studio] 0xNet:
Its a confidential one can't mention it im afraid
[Android Studio] sylas0p:
Requesting for Help!

OS Mac : OS X , macOS monterey v12.3 , m1

ProductVersion: 10.15.7

Android Studio Version: Android StudioBumblebee | 2021.1.1 Patch 2

AVD Version: Google Play api pixel 4 XL arm64 api 31(google apis)

Terminal input & output:

[-] copy all arm64-v8a files from /data/data/com.android.shell/Magisk/lib/arm64-v8a 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]

[-] Test patch status and do restore

[-] Checking ramdisk status

[-] STATUS=1

[-] Magisk patched boot image detected

help!
[Android Studio] golinou:
Hi! I hope I'm not too late for the trend. I just recently downloaded Android Studio and I am trying to root my virtual device. I am sure I'd be able to understand the steps if I had more knowledge about the subject.. but the truth is that I am quite lost. Did you make a video about it? Or would someone be kind enough to explain in detail at a "beginner" level? I would really appreciate it thank you!
[Android Studio] newbit:
Read the readme from the first page
[Android Studio] golinou:
Hi! Thanks for answering me. I did read it and tried a lot of things but I just fail to understand it as a "new user". Is there a way you could help me please? There isn't much info about it out there
[Android Studio] newbit:
sure, on which stage do you stuck? Which preconditions did you met? Which not?
[Android Studio] newbit:
That's a very well known and common issue with the emulator binary itself. It doesn't get terminated

and stuck as a process somewhere in the background. Try to find it in the Task-Manager and kill it.

It is called Qemu-whatsoever.exe, it is usually grouped with the Android Studio processes.
[Android Studio] itandy:
It works! You're awesome! Thanks!
[Android Studio] newbit:
Hi,

try it with the stock ramdisk:

[-] Checking ramdisk status
[-] STATUS=1
[-] Magisk patched boot image detected
[-] Constructing environment - PAY ATTENTION to the AVDs Screen

Indicates that your ramdisk is already rooted.

Also, did you check my

[GUIDE] Build / Mod AVD Kernel Android [10] [11] [12] rootAVD [Magisk] [USB passthrough] [Linux] [Windows] [Google Play Store API]​

[Update 15.12.2021]

For Windows Only.

I hope this helps.
[Android Studio] theovero:
Hello how are you? I hope you're well. First I would like to apologize for the confusion created yesterday in my topic. It's the first time I'm dealing with rooted and right away it was by emulator. Secondly, I would like to thank you for the tutorial and your patience.

Today I really DISCOVERED what I need.

Can you help me?

I need to pass safetynet checks to access banking apps through android emulator. However, I've tried every possible way with safetynet kdragon, prompconfs and everything else. I've watched all the tutorials available on youtube possible, but the problem is that these tutorials only show how to do this through a real cell phone and not through an emulator. Would you help me?
[Android Studio] theovero:
Hello. I saw in a post of yours that you are (or were) having the same problem as me to activate safety net in the emulator through magisk. Have you already got the solution? Would you help me??
[Android Studio] -Star-Lord-:
what I'm doing wrong?
[Android Studio] newbit:
I don't know either.

What shell are you using?
[Android Studio] newbit:
No I can't help you with that. Never heard about anyone who made it possible to pass safetynet on an AVD.

Perhaps you should set a bounty out to achieve this.
[Android Studio] anmac1789@gmail.com:
Does this work with the latest edition of android studio with android 12 ? or even 13 developer beta ?
[Android Studio] newbit:
As the title of this thread implies, yes A12 works fine. A13 I didnt know exist already... Please give it try and report back.
[Android Studio] Whatcry:
Hi @newbit. I'm trying many times but am stuck at this. Can you help me, please?
[Android Studio] newbit:
Hi, seems like the script is broken.

Try to redownload the whole zip and try again.
[Android Studio] Whatcry:
Nothing changed. I try many times since last night. There is any problem with the newest AVD? I'm using

Android Studio Chipmunk | 2021.2.1 Patch 2 for Windows 64-bit (929 MiB)
[Android Studio] newbit:
Not sure, chipmunk is working fine ever since. The issue from the command says there is an issue with the code. And you are using already cmd shell instead of ps. if you run adb shell, does it connect the running avd?
[Android Studio] Whatcry:
Yes, it connect normal
[Android Studio] newbit:
I am sorry, but I can't help you.

I cannot reproduce your issue. The up to date script is working fine. So I can't really

say where your issue is coming from. I assume you didn't changed anything in the

rootAVD.bat script?! I am not sure if this could be OS ending related, but you could

try to re-download the rootAVD.bat file and overwrite it.

Good luck with it
[Xiaomi Mi A3 Questions & Answers] Guik LePutride:
Hi, I have bricked my girlfriend's phone after an attempt to replace Android 10 to MIUI 12 Laurel Sprout.

- I have already unlock it with fastboot.

- I test to install TWRP Laurel Sprout with official version but after this the phone bootloop on fastboot without succes.

Now when I test to reinstall TWRP I have this error :

View attachment 5187499

I'm without solution to install TWRP or another recovery, after this I think it will be good.

Do you have some ideas ?

Thanks for you help and sorry for my english.
[Xiaomi Mi A3 Questions & Answers] Guik LePutride:
I had move my post on another section most appropriate. I think you can close or delete this one.

Sorry for the inconvenience
[General Questions and Answers] soft-fix:
i am looking for the cloner-app that make this icons...

View attachment 5187507
[General Questions and Answers] Deleted member 1890170:
It's Samsung's Dual Messenger.
[LineageOS Questions & Answers] pol-der:
Hi XDA Family,

Hope you are well. I bought a new phone Mi Note 10 Lite and uninstalled all bloatware apps and replaced them with privacy based ones. I downloaded Lineage Phone (Dialer) from Apkmirror and installed. It is working like a charm on calls but i can't record the conversations. When i tap Record button i am getting "Failed to start recording" error. I did some research on the internet but no luck there is nothing about this issue.

Could you please help me about this issue?

Thanks in advance.

Kind Regards.
[LineageOS Questions & Answers] aabh121:
Go to twrp recovery

And tap Mount

Than tick system and vendor

Than go to system/product/priv-app/velvet

Than rename velvet.apk to velvet.apk.bak
[LineageOS Questions & Answers] pol-der:
I have no root. Is there any way to do this job without root?
[Touch Diamond, MDA Compact IV Themes and Apps] nitramk:
Hi!

Here comes another updated version of StopWatch. This time it's an update to version 2.2, and it is currently available for QVGA, VGA and WVGA screens.

The sleep-bug where the timer and stopwatch slows down when the phone goes into sleep mode has been corrected. Further, I've also included support for MoDaCo's AppToDate application for easy updating.

Info from earlier:

You can use both mp3s and Wav-files as alarm sounds, but it is advisable to use short clips, since there currently is no way to stop a started alarm. (This means that a played song for example wont stop play until either the program is exited or the song is ended.) I am currently working on this.

The program has also been reviewed in its latest version (2.0) by Gadgetmix.com:

http://gadgetmix.com/index/?p=2724

The new versions can be found at:

http://kaldma.se/programs/stopwatch/

Please report problems here!

/ nitramk

Version 2.3

- QVGA-version available

- Small corrections for QVGA screens

Version 2.2

- VGA and WVGA versions available.

- Bug when splitting times in advanced mode with d-pad corrected

- "Sleep mode"-bug corrected

- AppToDate support

Version 2.0

- VGA and WVGA versions available.

- Timer function

- Changeable timer alarm with vibrate alert

- Ability to use the D-pad instead of the screen

- Two ways to display split times, one as in V1 and one with focus on individual lap times as requested.

- The stopwatch and the timer both runs perfectly well when the phone goes to sleep or when you hit the power button to turn the screen off, compared to V1 where it didn't :P .

Version 1.0.1

- QVGA and VGA versions available.

- That small "closing app"-bug corrected.

Version 1.0:

- Only for VGA-screens!

Files below are of the latest versions!
[Touch Diamond, MDA Compact IV Themes and Apps] olstar:
Great stuff thanks! i will try tonight :)
[Touch Diamond, MDA Compact IV Themes and Apps] NisseDILLIGAF:
Nice!

Downloading and installing :D

maybe this could be something for 'D-MAN666', he was asking for something like this for a custum TouchFlo3D... :rolleyes:

take a look in this thread...

http://xdaforums.com/showthread.php?t=399212&page=20&highlight=manila
[Touch Diamond, MDA Compact IV Themes and Apps] luap:
great

this is highly usable, great job.

I think i keep my diamond and dont go to the iphone
[Touch Diamond, MDA Compact IV Themes and Apps] horstborsch:
Looks great, fits very well. Maybe you can release a german version? I´ll help translating.
[Touch Diamond, MDA Compact IV Themes and Apps] nitramk:
That would be possible and yes, I would need help with that since my German isn't that great. :P

First, though, I feel I have to complete the program a little by for example adding a timer function and making some other fixes.
[Touch Diamond, MDA Compact IV Themes and Apps] PLoK:
Why would you need to time anything tonight :) Some things are better left untimed :)
[Touch Diamond, MDA Compact IV Themes and Apps] sandtang:
if you make it count down too would be perfect. very nice job buddy!