What is Android Virtual Device?
An Android Virtual Device (AVD) is an emulator configuration that lets you model an actual device by defining hardware and software options to be emulated by the Android Emulator.
In simple words, this thing will let you use android phone in your PC! But, with some limitations.
This AVD comes with Android SDK. So, the guide starts now.
♦ Setup Android SDK -
● Download and install Java - Link or Link
● Download and install Android SDK - Link
● While installing SDK choose the directory C:\android-sdk-windows\ only (Install it in root directory, not in any extra folder).
● Now, you have installed sdk.
● Now, open SDK Manager from android-sdk-folder. Here, you will see a list of tools. In that deselect everything first and then select Android Version (API) of your choice.
● Click on install packages and let the packages to be downloaded and installed.
♦ Setup and start AVD -
● Open AVD Manager from android-sdk.
● Click on "New" button. A window will appear with many choices and selection.
● Fill every box as per your choices and requirements and click on ok.
● Window will hang for some time as it is creating your AVD.
● Once the AVD is created, close everything.
♦ Rooting AVD and Adding Google Play -
● Now, in your pc, open CMD (Start>run>cmd or Start>search>cmd)
● In cmd, type - cd C:\android-sdk-windows\tools\ In general, it is the directory where your android sdk's tools directory is.
● Now, we will start the emulator from command line. For that, type -
Code:
emulator -avd your avd name -system-partition 128 -no-snapshot-load
and press enter.
● It will start the avd. Now, we will push the needed files to system via adb.
● Download the attachment below. Extract all files to the "tools" folder in your android-sdk.
● In cmd, type -
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
● Now, we will push files to system, type -
Code:
adb push su /system/xbin/
adb push busybox /system/xbin/
adb push Superuser.apk /system/app/
● Now, we have to give permissions, type -
Code:
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /system/xbin/busybox
adb shell chmod 644 /system/app/Superuser.apk
Rooting done!
● Now, for Google play, we have to push the files -
Code:
adb push Vending.apk /system/app/
adb push GoogleServicesFramework.apk /system/app/
adb push MarketUpdater.apk /system/app/
● Now, permissions, type -
Code:
adb shell chmod 644 /system/app/Vending.apk
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb shell chmod 644 /system/app/MarketUpdater.apk
● Now, if you want -
Code:
adb push rootexplorer.apk /system/app/
adb push rootcheck.apk /system/app/
adb shell chmod 644 /system/app/rootexplorer.apk
adb shell chmod 644 /system/app/rootcheck.apk
● Now, important. We have to copy system to data for making it modifyable image. Type -
Code:
adb shell busybox rm -R /data/*
adb shell busybox ls /data
● Type -
Code:
adb shell busybox cp -a /system/* /data/
adb shell busybox ls /data
Done!
● Now, /data is your /system. So, now navigate to - C:\Users\yourusername\.android\avd\youravdname.avd\
and copy the file "userdata-qemu.img to a root directory such as C:\userdata-qemu.img. Rename it to "system.img"
● Close the emulator and then again type in cmd -
Code:
cd C:\android-sdk-windows\tools\
and type -
Code:
emulator -avd your avd name -system C:\system.img
This will start the AVD with your customized rooted system image. Everytime start the AVD like this.
● Now, check the root with root checker app and you are done..!!!
Now, Enjoy your android device on PC with root as well as Google Play.
Mods not now. Coming soon........
found this
http://www.ehalm.at/avd-4.3-gapps.php?l=en
pre built system img with su and market all ready to go
[Root AVD] Rooting Android Emulator (inc. 'x86_64') with SuperSU installable ZIP
maybe be useful for any..)
& !! of course GREAT THANKS to @Chainfire for amazing work !! &
#########################################
example result:
{
"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"
}
preface
tried before Genymotion, but ..
wish to FULL control my emu
//& really some performance issues, especially in comparison with x64 arch! )
read&try before some methods, but no any satisfied;
especially with AVD x86_64 based system images
so 'at last' - go to "primary sources" of SU http://su.chainfire.eu , and there
6 Embedding (Nov 27, 2014)
6.1 Files
6.2 Custom ROMs
6.3 Exploits
Click to expand...
Click to collapse
significantly http://su.chainfire.eu/#embed-exploit
6.3. Exploits
Over the past years, many exploits have installed SuperSU as their means of persistent root. Often the exploit leaves the system in an unstable state, and a proper and lengthy installation may not be possible. The APK can fix a partial install as long as basic root works. At the time of this writing, that means at least these files need to be present, and for the right architecture and amount of bits for the firmware (see the ZIP script for permissions and API levels):
/system/xbin/su
/system/xbin/daemonsu
/system/xbin/supolicy
/system/lib(64)/libsupol.so
Furthermore, daemonsu --auto-daemon needs to be launched somehow on boot. This is generally done via install-recovery.sh, 99SuperSUDaemon, or hijacking app_process([32|64]).
Alternatively, you can include the ZIP and run SuperSU's installation script. For this to work, at the time of this writing, the following commands need to be available on the PATH:
cat, chmod, chown, cp, dd, echo, grep, ln, ls, mkdir, mount, mv, rm, rmdir, sh, sleep, sync, umount, unzip
Additionally, sh needs test support ([ ] square brackets work in if statements). Aside from unzip, all of these should be present on a fully booted 4.3+ Android device. If not, you can provide a (SELinux capable) toolbox or busybox and symlink these commands somewhere on the PATH. Last but not least, /tmp should be writable. If all of these dependencies are met, you can install the ZIP as follows:
unzip /path/to/supersu.zip META-INF/com/google/android/* -d /tmp
sh /tmp/META-INF/com/google/android/update-binary dummy 1 /path/to/supersu.zip
Due to the script trying things in various ways to support different systems and recovery versions, it will throw errors at you regardless of if the installation is succesfull or not. Just ignore those, reboot, and see if the SuperSU GUI complains when you open it.
Click to expand...
Click to collapse
so - accord to @Chainfire rec:
Manual for rooting any version of AVD (emu) with SuperSU installable ZIP
in this example:
host machine:
Code:
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\Win
dowsPowerShell\v1.0\;C:\Program Files\PuTTY;C:\adb;c:\Program Files\Java\jdk1.8.0_25\bin;C:\Users\admin\AppData\Local\An
droid\android-sdk\platform-tools;C:\Users\admin\AppData\Local\Android\android-sdk\tools;C:\Users\admin\.android\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2a07
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
"d:\SU237" used 'as working dir'
"UPDATE-SuperSU-v2.37.zip" - last ver of installable ZIP at this moment )
"x86L_64r" - testing AVD:
Code:
d:\SU237>android list avd
Available Android Virtual Devices:
...
---------
Name: x86L_64r
Device: Nexus 4 (Google)
Path: C:\Users\admin\.android\avd\x86L_64r.avd
Target: Android 5.0 (API level 21)
Tag/ABI: default/x86_64
Skin: WXGA720
Sdcard: 200M
WXGA720 - my favorite skin
emu = emulator
acc. = according to
addit. = additional(ly)
rec. = recommendations
etc.
0. of course - "sdk tools have to be installed & AVD have to be created"
1. download last ver of SuperSU installable ZIP
2. unpack the content of "UPDATE-SuperSU-v*.**.zip" to supersu folder 'in working dir':
Code:
d:\SU237>tree /f
Folder PATH listing for volume D
Volume serial number is 2**
D:.
│
└───supersu
├───arm
│ chattr
│ chattr.pie
│ libsupol.so
│ su
│ supolicy
│
├───arm64
│ libsupol.so
│ su
│ supolicy
│
├───armv7
│ chattr.pie
│ libsupol.so
│ su
│ supolicy
│
├───common
│ 99SuperSUDaemon
│ install-recovery.sh
│ Superuser.apk
│
├───META-INF
│ │ CERT.RSA
│ │ CERT.SF
│ │ MANIFEST.MF
│ │
│ └───com
│ └───google
│ └───android
│ update-binary
│ updater-script
│
├───mips
│ chattr.pie
│ libsupol.so
│ su
│ supolicy
│
├───mips64
│ libsupol.so
│ su
│ supolicy
│
├───x64
│ libsupol.so
│ su
│ supolicy
│
└───x86
chattr
chattr.pie
libsupol.so
su
supolicy
d:\SU237>
3. start AVD
usually using '*.bat' file for starting AVD - as in this case addit. params can be used
for example 'my' "x86L_64r.bat":
Code:
cmd /k "emulator -cpu-delay 0 -cache ./cache -no-boot-anim -partition-size 900 -gpu on -verbose -shell -accel on -scale 0.5 -avd x86L_64r"
for details about params - of course look at:
http://developer.android.com/tools/help/emulator.html
http://developer.android.com/tools/devices/managing-avds-cmdline.html
addit. "-partition-size 900" - is due to often (esp. at def. params of sys partitions API <= 19 )
- there are no any free space on system partitions -- so 'rooting can not be done ("have no space for copying req. files"))'; for exmpl:
Code:
---------
Name: x86jb412
Device: Nexus S (Google)
Path: C:\Users\admin\.android\avd\x86jb412.avd
Target: Android 4.1.2 (API level 16)
Tag/ABI: default/x86
Skin: WXGA720
Sdcard: 50M
Code:
C:\Users\admin\Desktop>adb shell
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 441M 68K 441M 4096
/mnt/secure 441M 0K 441M 4096
/mnt/asec 441M 0K 441M 4096
/mnt/obb 441M 0K 441M 4096
[B][COLOR="Red"]/system 264M 264M 0K 4096[/COLOR][/B]
/data 388M 8M 379M 4096
/cache 64M 1M 62M 4096
/mnt/sdcard 196M 6K 196M 512
/mnt/secure/asec 196M 6K 196M 512
[email protected]:/ #
4. enter CMD (or in shell)) commands:
Code:
adb remount
adb shell mount -o rw,remount -t rootfs rootfs
adb shell mkdir /tmp
adb shell mkdir /tmp/supersu
adb push supersu /tmp/supersu
adb shell sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
adb shell su -v
adb shell su -V
adb shell stop
ping -n 5 -w 1000 127.0.0.1
adb shell start
ping -n 15 -w 1000 127.0.0.1
adb shell daemonsu --daemon
comments:
adb remount // -- (re)mount system writeable
adb shell mount -o rw,remount -t rootfs rootfs // -- (re)mount "/" as writeable for creating req following dirs -- acc. to @Chainfire rec. "Last but not least, /tmp should be writable." above
adb shell mkdir /tmp
adb shell mkdir /tmp/supersu
adb push supersu /tmp/supersu //-- transfer folder 'supersu' into emu
adb shell sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip //-- last param '/tmp/supersu/supersu.zip' can be ignored due to absence of toolbox or busybox at native emu - but that is 'no deal at all')
//-- example log of execution: - look at attach 'example_adb_log.txt'
adb shell su -v //-- check ver of su binary
adb shell su -V //-- check ver of su binary
adb shell stop //-- for SuperSU appear at "App drawer" - need 'restart emulator' --- and ("after updrading") -- SuperSU appear in "App drawer" )
ping -n 5 -w 1000 127.0.0.1 //-- timeout
adb shell start
ping -n 15 -w 1000 127.0.0.1 //-- timeout; after restarting (esp. at ARM arch!)
adb shell daemonsu --daemon //-- su daemon do need to be started! // another case: adb shell daemonsu --auto-daemon &
^C = CTRL+C - for exit from terminal
additionally:
Code:
adb shell am start -n eu.chainfire.supersu/.MainActivity
-- to open SuperSU app 'from adb'
Code:
adb shell su --self-test
--self-test //-- from "- Various logs (very important)" http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
Code:
adb shell su -h
-- help (interesting)
Code:
telnet localhost 5554
-- to control emu from console ))
for example - 'kill' emu (close instance)
or resize window (window scale 0.5)
+addit. Using the Emulator Console http://developer.android.com/tools/devices/emulator.html#console
------------
to save created (rooted) system image -- you can look at 'verbose view' of console (*.bat file) started emu
and there find like:
Code:
...
emulator: Mapping 'system' partition image to C:\Users\admin\AppData\Local\Temp\\AndroidEmulator\TMPF1D7.tmp
...
(exmpl. - attach "verbose_cmd.txt")
so (at moment of working emu!; of course when you close the emu - this file will be deleted! - http://developer.android.com/tools/devices/emulator.html#temporaryimages)
- just copy this "*.tmp" file to another place and use it "as your rooted system image!"
The thread http://forum.xda-developers.com/showthread.php?t=1886460 looks very promising for rooting my device (Star B94M Quad Core).
But there is no instruction on how to get it to run from Linux, and i can't figure it out. There are some .sh shell scripts and things that look like linux binaries (no extension name), but nothing that says what to run when. There's a readme.txt but it's full of characters my locale can't deal with and it doesn't specify which one it's in (but i'm guessing it belongs to a language i wouldn't understand).
Code:
├── RunMe.bat
├── stuff
│** ├── adb
│** ├── adb.exe
│** ├── AdbWinApi.dll
│** ├── AdbWinUsbApi.dll
│** ├── busybox
│** ├── busybox-armv6l
│** ├── busybox.exe
│** ├── checklt30.bat
│** ├── fakebackup.ab
│** ├── fastboot.exe
│** ├── install-recovery.sh
│** ├── libservicemenu.so
│** ├── onload.sh
│** ├── ric
│** ├── rootkittablet.tar.gz
│** ├── RootMe.tar
│** ├── script1.sh
│** ├── step2.sh
│** ├── step3.sh
│** ├── su
│** ├── SuperSu.apk
│** ├── Superuser.apk
│** ├── tabletS.ab
│** └── Term.apk
└── z_rootkit
├── getroot.sh
├── onload.sh
├── readme.txt
├── src
│** └── onloadhook
│** └── jni
│** ├── Android.mk
│** └── onLoadHook.c
└── usbux.ab
Also i can't post in that forum, that's why i'm posting here. I will try sending the OP of the thread a message to attract his attention to this.
ACtually you have to translate the bat file to sh or just wait for v26, i will add a unix compatible script into that one.
Regards
I tried running the adb binary, but
Code:
$ ./stuff/adb wait-for-device
never returns it prints
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then i killed it after some time.
Code:
$ ./stuff/adb pull /system/app/Backup-Restore.apk .
Gives "error: device not found"
Is this an indication that i need to use one of the other options from RunMe.bat?
I'll keep fiddling...
In v29 it's still the same: daemon started succesfully, then nothing happens.
PS The RunMe.sh contains Windows line ends, if anyone reads this it's easily fixed with vim, ':set fileformat=unix'
I am reviewing one of the update file for the Android device which is a ZIP package - when put on the root of the USB stick and reboot the device, it's automatically unpacked and installed (new software version).
ZIP file is called: vendor_Version.zip and contains a few files:
Code:
.
├── META-INF
│ ├── CERT.RSA
│ ├── CERT.SF
│ └── MANIFEST.MF
├── vendor_Version.dat (1 KB)
└── vendor_Version.enc (755 169 KB)
MANIFEST.MF contains:
Code:
Manifest-Version: 1.0
Created-By: 1.0 (Android SignApk)
Name: vendor_Version.enc
SHA1-Digest: C83q1xzzLihdxzgcci5kyO9ar8A=
Name: vendor_Version.dat
SHA1-Digest: +DdVkCEm8SasdwPnlpMMxG+mYY=
And here comes the question:
Is it possible to extract the vendor_Version.enc file, modify its content and pack it back?
Hey Xda!
I need help rooting this LG phone called a M153 "Fortune" running on android 6.0.1 Marshmallow. Does anyone know how to go about it?
With Android 6 by default Toybox ( no root ) is integral part of it. Update Toybox to version 0.8.5 what comes with root ( SU ).
jwoegerbauer said:
With Android 6 by default Toybox ( no root ) is integral part of it. Update Toybox to version 0.8.5 what comes with root ( SU ).
Click to expand...
Click to collapse
Thank you for your answer! But I'm somewhat of a noob, can you please elaborate?
You create a
Code:
TOYBOX-UPDATER.ZIP
|
│
├───bin
│ │ toybox_updater.sh
│ │
│ ├───busybox-1.29.0
│ │ ├───32
│ │ │ busybox
│ │ │
│ │ └───64
│ │ busybox
│ │
│ └───toybox-0.8.5
│ ├───32
│ │ toybox
│ │
│ └───64
│ toybox
│
└───META-INF
│ CERT.RSA
│ CERT.SF
│ MANIFEST.MF
│
└───com
└───google
└───android
update-binary
updater-script
and flash it by means of a Custom Recovery
Neo 2 kernel boots slow and then crashes then boots back again over and over , i found that if i enable a screen lock it just fix this issue temporarily and the system starts , i found that wifi and audio drivers not recognized there's no wlan0 no wifi connection , and no audio but camera works. I don't know if this issue is due to broken kernel source or the source is ported to specific variant of Android 11 say A.03 or whatever
Or is it just me not knowing how to append the kernel DTB to stock DTB but i tried
After compiling the kernel it gave me this list of dtbs
~/.../arm64/boot $ tree dts/
dts/
├── modules.order
├── qcom
│ ├── apq8016-sbc.dtb
│ ├── apq8096-db820c.dtb
│ ├── ipq8074-hk01.dtb
│ ├── modules.order
│ ├── msm8916-mtp.dtb
│ ├── msm8992-bullhead-rev-101.dtb
│ ├── msm8994-angler-rev-101.dtb
│ ├── msm8996-mtp.dtb
│ └── sdm845-mtp.dtb
└── vendor
├── 21615
│ ├── kona-mtp-overlay.dtbo
│ ├── kona-v2.1.dtb
│ ├── kona-v2.dtb
│ ├── kona.dtb
│ └── modules.order
├── 21619
│ ├── kona-mtp-overlay.dtbo
│ ├── kona-v2.1.dtb
│ ├── kona-v2.dtb
│ ├── kona.dtb
│ └── modules.order
├── modules.order
└── oplus
└── modules.order
5 directories, 22 files
Click to expand...
Click to collapse
I have no idea why is it doing that or what to do with them
However the stock dtb is roughly 22M in size those dtbs that the kernel gave me won't reach to that size so i thought i could use cat command and cat the stock dtb and kernels one into a single dtb but that didn't work i got a corrupted boot image screen when boot
I also tried to decompress stock dtb with dtc command and tried to recompress it, it resulted a dtb file less in size than the original one
Have anyone succesed in compiling and booting neo 2 kernel ?