OK, how about a custom kernel??
Insecure boot!
Code:
127|shell@android:/ $ cat default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
I fixed my bootloop problem. In technical parlance, I think the ramdisk offset should be 0x04000000. The stock mkbootimg has a different offset. While you are at it, I think the kernel_offset should be 0x00000000 as well, but mkbootimg will allow you to change the base address, so you can manually fix the kernel_offset from the command line. The ramdisk_offset problem is cursed, so you'll need a hex editor.
Simply change the word at 0x16 to 0x50. You can confirm that the ramdisk address for your modded boot.img is the same as the stock one.
There are also 256 words of data appended to the end of the boot.img. I presume this is the signature to test if the boot.img is stock.
For reference, here is the header for the stock boot.img
Code:
Magic: ANDROID!
Kernel size: 0x5307A0 (5441440)
Aligned size: 0x530800
Kernel addr: 0x80208000
Ramdisk size: 0x2FFA3 (196515)
Ramdisk addr: 0x81[B][COLOR="Red"]50[/COLOR][/B]0000
Second size: 0x0 (0)
Second addr: 0x81100000
Tags addr: 0x80200100
Page size: 0x800 (2048)
Name:
Cmdline: console=null androidboot.hardware=qcom user_debug=31