yashsingh1/xdaforums huggingface dataset:
[Android Software Development] rogersb11:
Well if I don't mess with common I get the previous error. I know the risk but I have a backup of the entire folder to swap out if building anything else. The S2 recovery was the same. Hung on boot slightly longer but recovery was no different. Ok here's what you asked for

lrwxrwxrwx root root 2014-08-08 05:23 PARAM -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-08-08 05:23 RADIO -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-08-08 05:23 RECOVERY -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-08-08 05:23 SYSTEM -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-08-08 05:23 TOMBSTONES -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-08-08 05:23 USERDATA -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-08-08 05:23 m9kefs1 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-08-08 05:23 m9kefs2 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-08-08 05:23 m9kefs3 -> /dev/block/mmcblk0p6

Also I do breakfast. Here's my command

. build/envsetup.sh && breakfast t0lte && make -j8 recoveryimage

noticed this at the end. There is no such file anywhere in samsung at all. Recovery worked without dual boot as I said to make sure I could build first to be safe

cp: cannot stat ‘/home/brett/android/system/out/target/product/t0lte/root/init.recovery.*.rc’: No such file or directory

make: [/home/brett/android/system/out/target/product/t0lte/recovery/root.ts] Error 1 (ignored)

mkdir -p /home/brett/android/system/out/target/product/t0lte/recovery/root/system/bin

cp -rf device/samsung/t0lte/recovery/root /home/brett/android/system/out/target/product/t0lte/recovery/
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] Where the CACHE block device? Please give me "ls -l /dev/block/platform/*" and "ls -l /dev/block/platform/*/by-name" output.
[Android Software Development] rogersb11:
first command

u0_a186@t0lteatt:/ $ su

root@t0lteatt:/ # ls -l /dev/block/platform/*

drwxrwxr-x system radio 2014-08-08 06:06 by-name

drwxr-xr-x root root 2014-08-08 06:06 by-num

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0 -> /dev/block/mmcblk0

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p1 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p10 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p11 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p12 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p13 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p14 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p15 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p16 -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p2 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p3 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p4 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p5 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p6 -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p7 -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p8 -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk0p9 -> /dev/block/mmcblk0p9

drwxr-xr-x root root 2014-08-08 06:06 by-num

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk1 -> /dev/block/mmcblk1

lrwxrwxrwx root root 2014-08-08 06:06 mmcblk1p1 -> /dev/block/mmcblk1p1

root@t0lteatt:/ #

And second

u0_a186@t0lteatt:/ $ su

root@t0lteatt:/ # ls -l /dev/block/platform/*/by-name

lrwxrwxrwx root root 2014-08-08 06:06 BOOT -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-08-08 06:06 BOTA0 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-08-08 06:06 BOTA1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-08-08 06:06 CACHE -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-08-08 06:06 EFS -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-08-08 06:06 HIDDEN -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-08-08 06:06 OTA -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2014-08-08 06:06 PARAM -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-08-08 06:06 RADIO -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-08-08 06:06 RECOVERY -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-08-08 06:06 SYSTEM -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-08-08 06:06 TOMBSTONES -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-08-08 06:06 USERDATA -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-08-08 06:06 m9kefs1 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-08-08 06:06 m9kefs2 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-08-08 06:06 m9kefs3 -> /dev/block/mmcblk0p6

root@t0lteatt:/ #
[Android Software Development] BarackMitzvah:
Hey Phil! The past few times I've tried to flash back to 6.26.6 on my VZW M8, I am never able to get into the recovery and even sometimes lose root. I am able to go back to 6.48.4 though, and that works fine. What do you suggest I do? Is there a newer recovery that works with aroma?

Thank you :)
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] Please confirm, this is incomplete "ls -l /dev/block/platform/dw_mmc/by-name/" output:

No CACHE, EFS, and HIDDEN there.
[Android Software Development] rogersb11:
Cache mmcblk0p13

Efs mmcblk0p3

Hidden mmcblk0p14

Thought they were there, my mistake. Thank you so much
[Android Software Development] puppettestpilot:
Thanks

I love the new touch swipe gestures thank you
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] Ready to build your own dual boot recovery?

1. Cherry-pick my last commit https://github.com/kumajaya/android_kernel_samsung_smdk4412/commits/cm-11.0 to enable LZMA compressed ramdisk support in t0lte kernel

2. Cherry-pick my last 2 commit https://github.com/kumajaya/android_device_samsung_t0lte/commits/cm-11.0-philz for PhilZ Touch dual boot recovery. The last commit optional but I prefer by-name symlink block device, in my opinion it's much safer

3. Cherry-pick my commit https://github.com/kumajaya/android_build/commits/cm-11.0 to enable LZMA compressed recovery ramdisk

4. You must use my PhilZ Touch repo: https://github.com/kumajaya/philz_touch_cwm6, cm-11.0 branch of course. My last commit enable t0lte dual boot recovery support

With all scripts and binaries for dual boot in device source tree, my recovery bigger than standard. That's why we need LZMA compressed ramdisk.

I follow gokhanmoral's dual boot recovery rules:

1. 2nd ROM recovery SYSTEM mounted from /data/media/.secondrom/system.img as /dev/block/loop0

2. 2nd ROM recovery CACHE mounted from /dev/block/platform/dw_mmc/by-name/HIDDEN as /dev/block/platform/dw_mmc/by-name/CACHE. Yes, I use HIDDEN partition as CACHE partition. It's a good idea to backup HIDDEN partition first.

3. Some modifications to make this dual boot recovery smarter, no need to repack a flashable zip for 2nd ROM recovery

For better explanation, please read http://xdaforums.com/showpost.php?p=47342541&postcount=3 and http://xdaforums.com/showpost.php?p=51364377&postcount=33
[Android Software Development] rogersb11:
You are awesome. I'm out at the moment but will be doing this as soon as I get home. Thank you so much. What should I try on the s2 build? Its builds with extras inside but nothing is different. Already a have released kernel that supports dual boot so wanted to finish it with this as it will be last kernel the i777 ever receives I believe. Gosh,you are so awesome. I'm way pumped. ????????????????
[Android Software Development] katinatez:
Ok been thinking about this all morning, compile bacon recovery like normal with my

BOARD_MKBOOTIMG_ARGS := --dt device/oneplus/bacon/dtb --ramdisk_offset 0x02000000 --tags_offset 0x00000000

then unpack switch out the zimage and dtb from twrp build, then repack. Correct?
[Android Software Development] Android-Andi:
Not tested, but looks good to me:

https://github.com/andi34/device_oneplus_bacon/commit/3f3fa7e1fadf245bbe3eedfce0777fed5e827cbd

Used https://github.com/xiaolu/mkbootimg_tools like mentioned by [MENTION=4666971]Phil3759[/MENTION] to extract kernel & dt.img from TWRP 2.7.1.1

kernel=zImage
ramdisk=ramdisk
dt=dt.img
page_size=2048
kernel_size=4426472
ramdisk_size=3887471
dtb_size=4235264
base_addr=0x00000000
kernel_offset=0x00008000
ramdisk_offset=0x02000000
tags_offset=0x00000000
cmd_line="console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3"
[Android Software Development] Phil3759:
[MENTION=5153662]Android-Andi[/MENTION] answer is good

maybe the kernel changed the battery path

By default, if you do not define one, recovery will use

BATTERY_LEVEL_PATH := "/sys/class/power_supply/battery/capacity"

while in recovery, try:

adb shell
cat /sys/class/power_supply/battery/capacity

check output value

Else, try to search for the battery path under /sys
[Android Software Development] Android-Andi:
[MENTION=3814731]katinatez[/MENTION] , [MENTION=4666971]Phil3759[/MENTION] TWRP is build on OmniRom by [MENTION=912474]Dees_Troy[/MENTION] if i am not wrong.

Maybe they use a differentkernel source? OnePlus One called "find7op" on OmniRom.

https://github.com/omnirom/android_device_oppo_find7op/blob/android-4.4/BoardConfig.mk#L8

https://github.com/omnirom/android_device_oppo_find7op/blob/android-4.4/omni_find7op.mk#L51
[Android Software Development] Phil3759:
It is too time consuming for me to debug kernels for devices I do not own.

You really must rely on a developer owning your device or having time to dig into your kernel sources
[Android Software Development] eris23:
~ # cat /sys/class/power_supply/battery/capacity

100
[Android Software Development] Phil3759:
can you change this line:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/libtouch_gui/touch_gui.c#L486

to

char value[10];

if still fails, after you boot into recovery, try to navigate into the menus using touch for 6 times at least and let me know if battery level appears right after that
[Android Software Development] eris23:
Okay. That seems to work. Thanks! I've uploaded the fixed version on the mako thread.
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION]

How you prepare 2nd ROM /data/media/.secondrom/system.img? I'm not sure because I don't know how your 2nd ROM boot. You can try prepare 2nd ROM system.img using Dual Boot Tool from 1st recovery Advance Menu.
[Android Software Development] Phil3759:
Setting char value size to 10 you mean?
[Android Software Development] eris23:
Yes.
[Android Software Development] Kjc99:
Hey guys quick question... I've asked this before but did not receive an answer... Can we just rename backups in a file Explorer I have so many and cant keep them straight... I know this has been asked but can't find it

Thanks
[Android Software Development] jesssiii:
Yeah, I did. What it said didn't work for me, which is why I posted. I'm not a noob, but perhaps this recovery is just too advanced for me.

Galaxy Nexus Toro
[Android Software Development] ooofest:
BTW, the first post mentions to wait a minute before activating "adb root in recovery" - I'm not sure what that means, unfortunately. If it simply means to wait a bit before trying to access the phone via adb shell from my PC, that hasn't been working thus far. Is there something else on the phone I should enable after booting into PhilZ Recovery to make abd work?

- ooofest
[Android Software Development] clsA:
is their a reason to use aromafm 1.8 and not 1.9 ?

also is USB OTG going to be supported soon ?

I'm on the HTC One M7
[Android Software Development] Roughnecks:
Is there any solution to fix the time bug with sgs4? Or is it possible to add an option to change the time manually?
[Android Software Development] Phil3759:
I have no idea why for a very few people it is broken. Could be a ROM issue as it relies on /system/bin binaries.

Without the device, it is hard for me and time consuming to look at it. It works for the majority though. Most if not all other recoveries are affected as I read. This one at least fixes it for most people

Maybe, if I have time, I will look at it again once
[Android Software Development] kgirlx:
P3113

So im guessing gt-p3113 isnt supported anymore since its not on the download list...am I correct...anybody
[Android Software Development] Phil3759:
Please ask [MENTION=4021423]ketut.kumajaya[/MENTION] to repack it with his flipped kernel. If he does no more, i will release it
[Android Software Development] 911-Future_Maker:
Thx for the new version Phil! :D
[Android Software Development] Roughnecks:
I heard about a simple solution. Just take the battery out of the sgs4 and leave it a whole Day without energy.

Succesfully tested by an Android Hilfe member

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Android Software Development] TeaM DaRkDrOiD:
Hey Philz i have successfully ported your recovery to my device i.e. Micromax A110Q

Thanks for the recovery here is the link of my post

http://xdaforums.com/showthread.php?p=43612542#post43612542

You can add it to your main post
[Android Software Development] wpkwolfseye:
I am using your CWM on my SGS-Note 2 (N7100) and even before I updated to the latest Version of this Mod, the following Problem remains. When I go on INSTALL FROM ZIP -> CHOOSE ZIP FROM SDCARD, I only get a few folders. Nothing more. Files I copied on there which I know is on there, is not visible at all. When I attach the device to my PC i can see all the files & folders, but

not

in your CWM.

However, when I go to CHOOSE ZIP FROM EXTERNAL SDCARD, I get where I am supposed to go. Why does it not work for my internal Sdcard ? Any idea ?

Thanks in advance, and thanks to Phil for his great work. ;)

Wolfseye
[Android Software Development] wpkwolfseye:
Hi Phil, I read what you say but I am afraid I don't know what you mean. I checked the FAQ. When its in there, I didn't notice something that fits to what I described. But then, I am no good with these things and maybe I just lack the necessary skills. ;) Who knows.

Any help you can specify what I need to do in order to make it work with the internal SDCard in your CWM is appreciated greatly.

Thank you in advance.

Wolfseye
[Android Software Development] TeaM DaRkDrOiD:
Philz added my recovery to the list??
[Android Software Development] Phil3759:
It is /data/media/0 issue probably. It's in the FAQ, set it to what you need
[Android Software Development] Phil3759:
New device:

Micromax A110Q (unofficial repack, credits to [MENTION=5093358]sukarang9[/MENTION])
[Android Software Development] wpkwolfseye:
Now I got it, and yes, that was it. ;) Thanks Phil.

Cheers

Wolfseye
[Android Software Development] RavenII:
With regards to backing up...how come when running regular CWM on my VZ S4...it doesn't take any where near the time to backup or restore as it does with this recovery...the backup is definitely bigger because there's a data.ext4.c? or something like that.
[Android Software Development] Phil3759:
As of size, only difference is that I include google cached music where cwm excludes it

I think that most people expect a nandroid backup to be like a raw image backup...

As of speed, issue is known with some 64Gb exfat cards, often when device is hot.

Please provide a log or at least the backup stats you get when done: size, time...
[Android Software Development] demlv:
Phil, have you considered adding an option to allow users to exclude cached Google music from a nandroid backup? :fingers-crossed:
[Android Software Development] Phil3759:
yes if you only rename folder and do not use wired characters like spaces and such:

0-9aA-zZ_

With those it should be fine
[Android Software Development] Phil3759:
reviewing the sources closer, I doubt that was the issue. I first thought about a memory overflow, but it cannot be the case

I updated beta branch with mainly this commit:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/fc38a871080b366296ffb8c5184967da76bbbb3a

please sync to 6.56.8 and let me know about the error shown in battery level
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION],

OK. That status 0 error is due to some issue in androidarmv6 bionic OR kernel. I'll consult the androidarmv6 team for that.

Your beta sources are all fine! :good:
[Android Software Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION], [MENTION=5554845]rogersb11[/MENTION] Please check my repo changes https://github.com/kumajaya/philz_touch_cwm6/commits/cm-11.0 .

rogersb11, for reboot support on Recovery Boot Menu, please also cherry-pick my last commit https://github.com/kumajaya/android_external_busybox/commits/cm-11.0
[Android Software Development] eris23:
No apparent problems with 6.56.8
[Android Software Development] rogersb11:
OK cool. Maybe I have an issue with kernel. Kernel must support dual boot correct? I haven't finished building by N2 kernel yet as my s2 supports it. Still new to git but how would I enable that if so. For the life of me a can't remember. I'll pick these shortly as well
[Android Software Development] Android-Andi:
[MENTION=5554845]rogersb11[/MENTION] yes, your kernel need dual-boot support also, without you can not boot 2nd Rom.

Send from OnePlus One using Tapatalk
[Android Software Development] rogersb11:
I figured. Problem is that I can't remember how I added it to my s2, was awhile back before it was public and before I had really started actually using git. Tip? I'll remember immediately if you could point me in correct direction. Ugh, I can't believe I forgot.
[Android Software Development] ketut.kumajaya:
It's fairly easy to port my dual boot recovery to a new device. Just forced update t0lte dual boot recovery: https://github.com/kumajaya/android_device_samsung_t0lte/commits/cm-11.0-philz

In short:

1. I copied lt01-common/recovery folder to t0lte: https://github.com/kumajaya/android...mmit/d67224eeffb154514bd15dc2145194177edfb71f

2. Made device specific changes for t0lte: https://github.com/kumajaya/android...mmit/9224846c4a8881da01f35dd9cd1ef01d4203df5d

For i9100:

1. Copy t0lte/recovery folder to i9100

2. Adapt step 2 above for i9100 spesific. The critical part bootmenu.sh, based on https://github.com/CyanogenMod/andr...s2-common/blob/cm-11.0/rootdir/fstab.smdk4210 info, change:

SYSTEMDEV="/dev/block/mmcblk0p9"
DATADEV="/dev/block/mmcblk0p10"
CACHEDEV="/dev/block/mmcblk0p7"
HIDDENDEV="/dev/block/mmcblk0p12"
[Android Software Development] rogersb11:
This is what I was missing then because it builds great. I have i777 but basically the same. Had everything but didn't get extra boot stuff. I know you obviously build dual boot kernel, how is it enabled? I just can't remember and I know it was actually not very difficult at all
[Android Software Development] ketut.kumajaya:
Dual boot kernel more complex than recovery, as I said before I follow gokhanmoral's rule but completely with different approach. For your reference https://github.com/kumajaya/android_dual_boot_lt013g
[Android Software Development] rogersb11:
Awesome. Exactly what I was looking for. I used gohk and dorimanx for reference on my s2 so this is fairly similar. Thank you very much. The recovery I have rebuilding again now with the changes to bootmenu. You're awesome
[Android Software Development] ketut.kumajaya:
Don't forget, add LZMA compressed ramdisk support to your kernel.
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] bugreport from p5110:

Will ask him for a recoverylog.

Send from OnePlus One using Tapatalk
[Android Software Development] Phil3759:
It could be a kernel update issue breaking touch driver after screen turns off automatically?
[Android Software Development] NHComp:
Thanks for a great app!. Just got it installed and now I'm checking out all the settings. I have an ATT S4 I337.

I chose "full wipe before flashing new ROM" before flashing the Skyfall ROM. I was expecting that it would wipe just about everything off the device but there are PDFs and pics in /storage/emulated/0/pictures, /storage/emulated/0/screenshots and in /storage/emulated/0/DCIM?Camera. Perhaps more directories, I haven't looked further. I haven't restored anything from backup.

Did I miss a wipe step? So far Skyfall seems to be working well.
[Android Software Development] Phil3759:
wipe media if you really want your sdcard deleted

Or, in format options, completely format /data include /sdcard
[Android Software Development] NHComp:
They were files on the phone itself, which is what surprised me.
[Android Software Development] danarama:
As Phil said, if you want to wipe your sdcard, there is an option for that.

Wipe data / factory reset doesn't wipe sdcard like some stock recoveries do, for good reason. Wipe form new ROM install is the same but wipes system too.

Wiping sdcard bus never necessary so it isn't included in these options. There is separate option for this in case you want to.
[Android Software Development] rogersb11:
Ok, so I got it going on my s2 but I'm after running boot tool and reboot to recovery I'm not getting options and just reboot back to first recovery. Any ideas?

Also anytime I try to backup data I get this

"unable to find volume."

"Error finding an appropriate backup handler.
[Android Software Development] tetakpatak:
I didn't hear of ketut's dual boot development for the S2. Are you trying ti install Tab 2 files on the i9100? Or did I totally miss his s2 development?

:D

tetakpatalked from N7100
[Android Software Development] ketut.kumajaya:
Please confirm if system.img successfully created in /data/media/.secondrom/

He try to port PhilZ Touch dual boot recovery to S2.
[Android Software Development] rogersb11:
It's not there. Also I can't backup data. Unable to find volume
[Android Software Development] Phil3759:
Recovery won't boot with any stock S2 kernel because of vold and selinux headers. That's why i stopped repack

Only a cm kernel is possible
[Android Software Development] rogersb11:
I have a custom cm kernel ��

Edit:Thought I would mention that it formats data no problem. I really appreciate the help. I'm obviously more than willing to do the work myself that needs done and will support the recovery there as well as it will come with my kernel and dual boot. Thanks again
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] As before, give me yours i777 "ls -l /dev/block/platform/dw_mmc/by-name/" output.
[Android Software Development] rogersb11:
lrwxrwxrwx root root 2014-08-10 10:02 CACHE -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-08-10 10:02 DATAFS -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-08-10 10:02 EFS -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-08-10 10:02 FACTORYFS -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-08-10 10:02 HIDDEN -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-08-10 10:02 KERNEL -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-08-10 10:02 MODEM -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-08-10 10:02 PARAM -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-08-10 10:02 RECOVERY -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-08-10 10:02 SBL1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-08-10 10:02 SBL2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-08-10 10:02 UMS -> /dev/block/mmcblk0p11

real adb this time and not terminal lol

RECOVERY MUST be with KERNEL. They are on the same block. I have a strange version that has a separate partition. This is very important. Kernel and recovery are packed together on this device as I'm sure you know
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] Don't ask me how to repack a recovery for your device, no idea.

Please search in your ported source, replace SYSTEM with FACTORYFS and USERDATA with DATAFS. You can use "grep -rl "SYSTEM" " command in your source directory. I hope you understand my point, by using symlinked block device, no brick even your fstab incorrect ;)