Gitiles
Code Review Sign In
gerrit.aospa.co / AOSPA / android_device_sony_recovery / 2db74d738899849373e3bcf20636fff017b15b95
commit2db74d738899849373e3bcf20636fff017b15b95[log] [tgz]
authorAdam Farden <adam@farden.cz>Fri Jan 09 16:29:00 2015 +0100
committerAdam Farden <adam@farden.cz>Fri Jan 09 16:32:45 2015 +0100
tree3335a6fe99174d96c9d004b28c8b0e31a2d1f071
parentfd478d7fa0bc95bc78e817ebfca2e40d0220ca7b [diff]
Add recovery for amami
2 files changed
tree: 3335a6fe99174d96c9d004b28c8b0e31a2d1f071
  1. extract_elf_ramdisk/
  2. rhine/
  3. yukon/
  4. Android.mk
  5. busybox
  6. custombootimg.mk
  7. init.sh
  8. README.md
README.md

Recovery for Sony Devices

Sadly, this is probably not what you were expecting.

This is simply a cache of CyanogenMod Recovery ramdisk-recovery.img files for each Sony device supported in AOSP 5.0 Lollipop.

What is this for?

Two major challenges face AOSP developers of Xperia devices:

  1. Sony devices cannot boot into the recovery partition.
  2. Custom recoveries such as ClockworkMod or TWRP cannot be built with AOSP.

So how do we install OTA based scripts such as Gapps?

Easy hack: put the recovery in the boot partition!

With this script the device's LED will shine purple on boot. During this time the user can press and hold Volume+ to enter recovery.

How do I use this?

You need to define these in your device repo:

  1. BOARD_CUSTOM_BOOTIMG := true
  2. BOARD_CUSTOM_BOOTIMG_MK := device/sony/recovery/custombootimg.mk

You will also need these two commits in your /build folder:

  1. 1ba97de5ae66175c8c8c6a54285b2a8562917f17
  2. 22913dea82299eac7e1a5e754102b89af4796a0d