[Android General] HypoTurtle:
FAQ/Fixes Continued

Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186

These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below

5.0 Modifications #186​

Android 5.0 Beta1 Beta2 Beta3

To gain adb access

Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini

Linux: ~/.android/adb_usb.ini

Windows: C:/Users/${Username}/.android/adb_usb.ini​

KingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.

Root

For root install SuperSU v2.11+

Confirmation

Custom Recovery

Recovery from [MENTION=5186178]carliv[/MENTION] - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).

Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)

This recovery seems to only work when the Lollipop Beta ROM is installed.

Gapps

64-bit gapps made for the Nexus 9.

My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.

Mirrored copy of the version I'm using.

(OP's thread has updated them and removed the previous version)

Busybox

64-bit busybox installation

Removing encrypted data (temporarily)

In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19

This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img​

Android 5.0 Beta Breakdown

Screenshots to come later.

Entering LK

VOL UP and POWER (this no longer enters recovery)

From lk menu: entering fastboot mode and normal boot works.

Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything different​

Charging battery

Flashing a custom recovery should allow you some way to charge the battery​

I haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. Confirmed​

RIL Memory leak

There seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode

I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane mode​

IMEI

IMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.​

Antutu Scores

64-bit Antutu Scores are around 28000

32-bit Scores are around 27000

Data-encrypted 4.4.4 Antutu scores are also around 28000​

Sensors

Backlight, sound ... can't be changed

Brightness can be fixed in MTK Engineering Mode #5​

ROM is not rooted; does not have gapps installed and data is encrypted.

TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).

Android L kernel config