[G2 Android Development] blastagator:
FAQ

My OTA isn't working or I am now in a bootloop to TWRP.

To get out of the bootloop, connect to adb shell, and issue:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32

This should resolve the problem. If not, search the thread, some people have other suggestions for various places to nuke the bad commands residing in /misc. To avoid the future problem, contact your ROM maintainer with the following info.

Starting in Android N, the ROM uses /misc partition to communicate with recovery. (Therefore if your ROM is M or lower, OR uses the old communication method, this is not relevant to you). To address OTA problems, it is important to note the newly introduced bootloader offset.

https://review.lineageos.org/#/c/165001

Also, /misc needs to be mounted:

https://review.lineageos.org/#/c/19334/

Your ROM maintainer should add these to their device tree. This will insure that ROM will write to the exact place the recovery is reading from.

I see error: "E: mount -0 bind '/data/media' '/sdcard' process ended with error=255" when I switch partition type on /data.

Update to new version, 2.8.7.1. This problem is fixed.

I see error: "assert failed: run_program(" /tmp/loki.sh") == 0" when I flash X. Why?

Loki is only supported by JB BL. Loki is smart enough to check your BL version before flashing. If you are on KK BL and the thing you are flashing uses loki, you're going to get this error. New BL requires you to use bump.

Now that I have bump, how do I update to the KK bootloader?

If you have a d800 (or d801), see my thread here. If you have a d802, see [MENTION=2376110]dorimanx[/MENTION]'s thread, here. Credit's to dori for inspiring me to make the package for d800.

USB-OTG isn't working, why not?

To use USB-OTG your device needs to be formatted fat32, not NTFS.

I'm having trouble formatting partitions. Why doesn't it work?

Fixed: As of 2.8.3.1

The option to Format Data or do Factory Reset probably won't work. The fstab is set to auto to support f2fs and those two options don't know how to deal with auto (they don't know if you want them wiped to ext4 or f2fs). Therefore, you need to do Advanced Wipe, which works fine. If you are still having trouble, make sure MTP isn't on and make sure your USB isn't plugged in.

OMG, my TWRP thinks this is the 1970s?! HALP!

This is an issue that arises in Android L (for whatever reason). Member murdoch1 found this and confirmed that installing it fixes the 1970 issue in TWRP.

Does [xyz] work?

As far as I know, everything works except for known issues in the common twrp source.

I want to report [xyz] as not working, how do I do it?

Post in this forum. I'll do what I can to fix it.

When will the next version come out?

I don't plan on building again unless a bug is discovered that I can fix, or if TeamWin releases the next version.

Why don't you do [xyz]?

Why don't you do it?

Why doesn't F2FS work?

It DOES work in the recovery. To get it working on your ROM you need to have proper kernel support. Many AOSP ROMs support f2fs partitions. Additionally, dorimanx has added working f2fs on his stock kernel. :)

Why doesn't AROMA work?

AROMA is old. As of version 3.0.2-1, I added a hack to fix the graphics. If your zip file still isn't working, try my guide:

http://xdaforums.com/showpost.php?p=66747442&postcount=2591