teamwin / android_device_emulator_twrp Goto Github PK

Device configs for making a ramdisk-recovery.img that you can boot in the Android emulator

C++ 55.93% Shell 20.27% Makefile 23.80%

android_device_emulator_twrp's Introduction

Team Win Recovery Project (TWRP)

This is a set of device configs that you can use to build and test TWRP in the Android emulator. Note that adb will take about 10 to 15 seconds after TWRP is booted to become available. Just wait and it will come online eventually.

This branch of the device configs is intended to be used with Android 5.1.1 system image. In order to create fake boot and recovery partitions, you will have to boot the emulator with a custom kernel. We simply added support for reading a partition table to the kernel configuration. The source for this kernel is located here:

Kernel Source

To boot this in the emulator, build your recoveryimage. With the Android emulator make a new device based on a Galaxy Nexus. Name it TWRP. Allow it to have a hardware keyboard and a sdcard sized to 2000MB. Give it a decent sized data partition like 2000MB or more. TWRP will be using the data partition as an emulated storage setup as seen on most modern Android devices, so having some extra room may help. Then from your android-sdk/tools folder run the following command:

./emulator -avd TWRP -ramdisk ~/omni_folder/out/target/product/twrp/ramdisk-recovery.img -kernel ~/omni_folder/device/emulator/twrp/goldfish_3.4_kernel

After the first boot, wait for ADB to start up, then: adb shell /sbin/create_partitions.sh

This script will partition the sdcard with a boot, recovery, cache, and removable sdcard partition. It's designed to work with a 2000MiB sdcard. If you want a different sdcard size then you will need to modify the script in the omni_folder/device/emulator/twrp/recovery/root/sbin/create_partitions.sh location to suit your needs.

You can find a compiling guide for TWRP here.

More information about the project.

If you have code changes to submit those should be pushed to OmniROM's gerrit instance. A guide can be found here.

android_device_emulator_twrp's People

Contributors

Stargazers

Watchers

Forkers

mr2vzie morristech jimmymobile rynos snowxucker gisti kjhack zzzzpaul annwhite90 yangxianting tareq010676 mrchaweng projectopencannibal sndnvaps mico1119 leezhenghui omorjit mrader11 andrewgouw esc0rtd3w filipinotech ianlouth acung21 friyou1 smartmanru herawais russputin1992 alam1 monkey-l anmolmaniyar docs007 liuponghei gtpick jomadmann rakhithjk icprog shuixi2013 vampir83 christama antgorum lkinsfather cokebottlebody999 lomex1 purest1 git38438 rebirthza kupakunk despoixhugo2 surfndez intannabila99 daneballer727 soyoboi vernookz wuju86 ajerry681 hachtech zerocool4411 tk7777777ip rustyt23 alfian878787 alphadesignx pitchblackrecoveryproject jetwall ftservice creechuh hixio-mh rickfm1982 kingkeith518 tex8752 hemanthjabalpuri xxxpgr9yt cfukay9 dcoble87 grif667 govyman boy1z xirdigh mrwafflez17 mlb302 alexanderdj20034 opensourcefuture andra297 netken83 gtf35 arbabmashhadi tsepisod edorus mrameribrahim rsburn1 iversonenterprises2022 dt2285 yina150578 ahoneybee mariosbest poolesinc harjur12 davidjsykes86 waxmax1313 cxzstuff youwavex86

android_device_emulator_twrp's Issues

Version problem with latest version of Android SDK Tools

If I try using the goldfish kernel I get this:
"ERROR: New emulator backend requires minimum kernel version 3.10+ (currently got lower)"
Is there any way this can be updated somehow?

twrp

com.jakewharton:butterknife:(insert latest version)' annotationProcessor 'com.jakewharton:butterknife-compiler:(insert latest version)'

[ISSUE]Cannot boot 3.4.0-0 in AVD

@Dees-Troy

I have installed Android 4.4.2 armeabi-v7a with SDK Tools 24.2.0 with Galaxy Nexus as Target, Skin HVGA and 1500MiB as SDCARD.

TWRP 3.4.0-0 (and all 3.x) version(s) are not booting at all with above said AVD configuration. Last version booting is 2.8.5.0 in my AVD with 3.4 goldfish kernel from android-4.4 branch.

All the images above 2.7.0.1 except 2.8.0.1 are Android boot.img format, that is the reason TWRP may not boot. We have to unpack it and pack ramdisk.cpio as gzip(?).
2.6.3.0 is working fine with all skins available.
2.8.5.0 is working fine with all skins but not 2.8.0.0.

I don't know if we have to use it in specific android avd or not.

As @dadreamer said here, we have to use it in arm architecture AVD only!(?)

Please correct me if I am wrong. Since there is no simple guide which explains all these things, I am not sure how to choose which version of Android AVD, which version of kernel to choose and lastly which version of TWRP to use.

More instructions like answering above small questions at https://twrp.me/twrp/androidemulator.html will help people like me.

Thanks

Archive:  /sdcard/Download/twrp-2.8.6.0-d802.zip
  inflating: META-INF/MANIFEST.MF
  inflating: META-INF/CERT.SF
  inflating: META-INF/CERT.RSA
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
  inflating: recovery.img
  inflating: tmp/loki.sh
  inflating: tmp/loki/loki_flash
  inflating: tmp/loki/loki_patch
[flash_archive] Remount /system in rw
[flash_archive] Start file install
[ERROR][flash_archive] META-INF/com/google/android/update-binary is an ARM binary, using system updater
find: system/lib/: No such file or directory
  adding: META-INF/ (stored 0%)
  adding: META-INF/MANIFEST.MF (deflated 39%)
  adding: META-INF/CERT.SF (deflated 40%)
  adding: META-INF/CERT.RSA (deflated 33%)
  adding: META-INF/com/ (stored 0%)
  adding: META-INF/com/google/ (stored 0%)
  adding: META-INF/com/google/android/ (stored 0%)
  adding: META-INF/com/google/android/update-binary (deflated 35%)
  adding: META-INF/com/google/android/updater-script (deflated 54%)
  adding: recovery.img (deflated 5%)
  adding: tmp/ (stored 0%)
  adding: tmp/loki.sh (deflated 48%)
  adding: tmp/loki/ (stored 0%)
  adding: tmp/loki/loki_flash (deflated 34%)
  adding: tmp/loki/loki_patch (deflated 33%)
chmod: updater: No such file or directory
[ERROR][execute_update_binary] execution of update-binary ended with errors
[ERROR]{Result:KO};

Is there a way to get TWRP Working on Genymotion then?