Notice I'm only interested in doing Qualcomm based Code Aurora Forum Devices. Do not submit any Moto or Samsung devices as they will be ignored. An easy way to see if its a Code Aurora device is that it will have a file named init.qcom.post_boot.sh in the / directory and a mounted partition named "persist" . Most LGE androids are CAF devices as are several others.
1. Device must be rooted
2. You must have adb setup and working for your device.
3. You must be capable of following these directions to dump and be able to test.
Ok lets get started!!!
cat /proc/mtd > /sdcard/mtd.txt
This will give you an output that looks something like this
Notice the recovery line in bold. It will be different per each device.
# cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00040000 "misc"
mtd1: 00800000 00040000 "boot"
mtd2: 12c00000 00040000 "system"
mtd3: 0a000000 00040000 "cache"
mtd4: 19000000 00040000 "userdata"
mtd5: 00300000 00040000 "persist"
mtd6: 00a00000 00040000 "recovery"
OK in the next step here you will need the mtd# of recovery for your device to dump it. For this example we use mtd6 as per the bold line above.
dd if=/dev/mtd/mtd6 of=/sdcard/recovery-dump.img bs=4096
I'll also need some info from df & about your sdcard setup
df > /sdcard/df.txt
ls /dev/block/mmcblk* > /sdcard/mmcblk.txt
mount > /sdcard/mounts.txt
This will pull your kernel config from running device and place file named config.gz in your sdk tools dir.
adb pull /proc/config.gz
Ok the final thing is I'll need to know the path for mass storage.
Using a app like root explorer is ideal for this step.
Navigate this path /sys/devices/platform and look for either of the two below or if neither exists look for somewhere in sys/devices/platform/ for
a lun0/file and give me the full path.
Usb gadget setup:
Usb function setup:
Final step is to mount your sdcard to pc and copy these files from sdcard to pc.
config.gz (this will be in your android sdk tools dir)
Please create a readme file with the exact device name, and model #, masstorage path, and your contact info and md5sum of recovery-dump.img. Zip these above files and upload with proper readme and post link in thread below along with device model # and name.
Linux users can find md5sum of recovery-dump.img with command from terminal md5sum recovery-dump.img
Windows users please use this Windows GUI Based MD5 Checker - Mike Dopp
NOTE: Any submissions without md5sum for recovery-dump will be ignored as I cant verify the integrity of the dump after downloading without it.
If you can't follow these directions without help this isn't for you. I will consider submissions and work on them as time allows. This does not mean I'll do it immediately or can I guarantee I'll be successful. PM's and nagging posts will do nothing but annoy me BTW
I'd also like to keep this thread absent of questions and be for submissions only