Database Develop

Sense ROM - Help needed

Okay, so like many I have been waiting for another user of this forum to post his update of the sense ROM, but he seems to be taking a while. So, I decided I will try and fix the ROM myself, currently I am going to try adding libs from other ROMS ofcourse I will not be posting anything on the ROM unless I get things working, then I will seek permissions to post the ROM from the correct owners... I am cuurently flashing the ROM to my x8 now..
Just a quick question also.. Does anyone know how to add libs directly to the system.img?

There is a decompiler for the .img file somewhere around the xda forum, i'll have a quick search for you and get back to you on it
Beans
Sent from my X8 using xda premium

Thank you very much, I will also need to recompile, I believe this can only be done on linux? or the AVD emulator? or can it also be done on windows? I know the decompiling can be

Yeah i found something for you, i cant try it for you before i recomend it because my pc has been stolen, but heres a link to the thread - http://forum.xda-developers.com/showthread.php?t=1315111
Both decompiling and recompiling can be done on wondows so far as i know with a linux emulator, or you could partition the hard drive on your pc and install linux on the second partition
Hope i helped
Beans
Sent from my X8 using xda premium

bbeanss said:
Yeah i found something for you, i cant try it for you before i recomend it because my pc has been stolen, but heres a link to the thread - http://forum.xda-developers.com/showthread.php?t=1315111
Hope i helped
Beans
Sent from my X8 using xda premium
Click to expand...
Click to collapse
Thank you, the decompiling on windows works, I'm just not sure about recompiling as linux isn't my Forte so to speak.. also my AVD emulator doesn't seem to be loading any android VM's I have created..

The best way i found when i was trying to port sense was to take it slowly, modifying/replacing 1 lib file at a time, it takes forever, but if it doesnt load up then that way you know the source of the problem, ill pull up a few sites on basic linux for you if you want?
Beans
Sent from my X8 using xda premium

smyth12 said:
Okay, so like many I have been waiting for another user of this forum to post his update of the sense ROM, but he seems to be taking a while. So, I decided I will try and fix the ROM myself, currently I am going to try adding libs from other ROMS ofcourse I will not be posting anything on the ROM unless I get things working, then I will seek permissions to post the ROM from the correct owners... I am cuurently flashing the ROM to my x8 now..
Just a quick question also.. Does anyone know how to add libs directly to the system.img?
Click to expand...
Click to collapse
Sense lib is different
you can't take Cm7/Cm6 lib
they have license on their lib
you can edit lib
recompile
and repaired Ramdisk from salsa

bbeanss said:
The best way i found when i was trying to port sense was to take it slowly, modifying/replacing 1 lib file at a time, it takes forever, but if it doesnt load up then that way you know the source of the problem, ill pull up a few sites on basic linux for you if you want?
Beans
Sent from my X8 using xda premium
Click to expand...
Click to collapse
That would be awesome please..
Superuser.Angga said:
Sense lib is different
you can't take Cm7/Cm6 lib
they have license on their lib
you can edit lib
recompile
and repaired Ramdisk from salsa
Click to expand...
Click to collapse
I was going to try some of the better known ROM libs just now, gonna send them through ADB because I can't use root explorer due to the "SD card removed" bug.. Decompile the libs and then recompile them then?
Where can I get the ramdisk?

Im off to bed now becaise its 1:20am where im at and ive got to get up in 6 hours, but of the 4 or 5 websites ive quickly scanned through i found this one to be the most imformative - http://bash.cyberciti.biz/guide/Main_Page
I hope it helps you out mate
goodnight ;D
Beans
Sent from my X8 using xda premium

bbeanss said:
Im off to bed now becaise its 1:20am where im at and ive got to get up in 6 hours, but of the 4 or 5 websites ive quickly scanned through i found this one to be the most imformative - http://bash.cyberciti.biz/guide/Main_Page
I hope it helps you out mate
goodnight ;D
Beans
Sent from my X8 using xda premium
Click to expand...
Click to collapse
Cheers mate, in the UK? me too haha...
I'll have a look through them probably tomorrow morning now, adb seems to be being a pain and not pushing the files across.. Thanks very much,
Good night mate ;D

Gud luck to you bro

phoenix883 said:
Gud luck to you bro
Click to expand...
Click to collapse
Thanks man, looks like I'm gonna need it lol

This Help you replace the lib
Camera service lib:
Code:
libcameraservice.so Need:
libui.so
libutils.so
libbinder.so
liblog.so
libcutils.so
libmedia.so
libcamera_client.so
libsurfaceflinger_client.so
libcamera.so
libc.so
libstdc++.so
libm.so
Replace Libcameraservice too
Open Gles/3D
Code:
libGLESv1_CM.so Need:
liblog.so
libcutils.so
libEGL.so
libdl.so
libc.so
libstdc++.so
libm.so
Code:
libGLESv2.so Need:
liblog.so
libcutils.so
libEGL.so
libdl.so
libc.so
libstdc++.so
libm.so
Code:
libEGL.so Need:
liblog.so
libcutils.so
libutils.so
libdl.so
libc.so
libstdc++.so
libm.so
Replace libEGL.so, libGLESv2.so, libGLESv1_CM.so
Oem Camera
Code:
liboemcamera.so Need:
__fixunssfsi liblog.so
libcutils.so
libdl.so
libc.so
libstdc++.so
libm.so
Wifi Fix
Replace Build.prop
Code:
wifi.interface = tiwlan0
to
Code:
wifi.interface = wlan0
replace libwpa_client.so
replace tiwlan.ini to correct config
Done
Camera Fix
????????????????????????
it's hard to ported camera
need
Modified Camera.apk to make 3.15mp not 5mp
removed autofocus
recompiled lib
Anyone Help Me?

Superuser.Angga said:
This Help you replace the lib
Camera service lib:
Code:
libcameraservice.so Need:
libui.so
libutils.so
libbinder.so
liblog.so
libcutils.so
libmedia.so
libcamera_client.so
libsurfaceflinger_client.so
libcamera.so
libc.so
libstdc++.so
libm.so
Replace Libcameraservice too
Open Gles/3D
Code:
libGLESv1_CM.so Need:
liblog.so
libcutils.so
libEGL.so
libdl.so
libc.so
libstdc++.so
libm.so
libGLESv2.so Need:
liblog.so
libcutils.so
libEGL.so
libdl.so
libc.so
libstdc++.so
libm.so
libEGL.so Need:
liblog.so
libcutils.so
libutils.so
libdl.so
libc.so
libstdc++.so
libm.so[/CODE]
Replace libEGL.so, libGLESv2.so, libGLESv1_CM.so
Oem Camera
liboemcamera.so Need:
__fixunssfsi liblog.so
libcutils.so
libdl.so
libc.so
libstdc++.so
libm.so
Wifi Fix
Replace Build.prop
Code:
wifi.interface = tiwlan0
to
Code:
wifi.interface = wlan0
replace libwpa_client.so
replace tiwlan.ini to correct config
Done
Camera Fix
????????????????????????
it's hard to ported camera
need
Modified Camera.apk to make 3.15mp not 5mp
removed autofocus
recompiled lib
Anyone Help Me?
Click to expand...
Click to collapse
Wow thanks, so in theory I can take existing libs from working roms and replace the libs you mentioned and things will work?

You can test it
replace that lib from working rom
but
i use different way
edit the lib
it will take a month to edit all lib
but that's is only way

Superuser.Angga said:
You can test it
replace that lib from working rom
but
i use different way
edit the lib
it will take a month to edit all lib
but that's is only way
Click to expand...
Click to collapse
okay, Thank you, alot! I'm sure with a bit of time I should get this working...
Any fix for the 3g?
Edit: Vibration has come alive now..

Ah ha nice to see the Operation Sense is rolling along still... don't know what Salo-S is doin but still no proof of his Rom....?
Any way I could help? I'm not dev but if there's a easy but time consuming job that needs doing (typing stuff...?) Then I'm up for it.lol
peace
Sent from my X8 using xda premium

match_stick said:
Ah ha nice to see the Operation Sense is rolling along still... don't know what Salo-S is doin but still no proof of his Rom....?
Any way I could help? I'm not dev but if there's a easy but time consuming job that needs doing (typing stuff...?) Then I'm up for it.lol
peace
Sent from my X8 using xda premium
Click to expand...
Click to collapse
I'll keep you in mind my friend.. Just trying to figure stuff out at the moment but the typing things could be of use updates and findings etc... PM me your email?

Yo man, finally someone who approaches this subject seriously, do not pretend to be someone all knowing and is not a crook. Respect for this, man.
... Salo-s and SuperuserAngga still don't get any proof.
I can help if I can, just PM me. I'm a beta tester of ROU UI now, but I think I can help something from time to time.
Peace!

jahlovePL said:
Yo man, finally someone who approaches this subject seriously, do not pretend to be someone all knowing and is not a crook. Respect for this, man.
... Salo-s and SuperuserAngga still don't get any proof.
I can help if I can, just PM me. I'm a beta tester of ROU UI now, but I think I can help something from time to time.
Peace!
Click to expand...
Click to collapse
Thank you, aside from testing do you do any coding?
or anything along these lines? fine if you don't, beta testing is just as important!

Help for custom boot loader for Cyanogenmod 7.1

I have installed Cyanogenmod 7.1 and modified my bootanimation. I would like to also modify my bootloader screen, the first screen that appears just after the phone boots. Please help on t this topic! Thanx in advance!

Well that's not as easy as changing the bootanimation.... Cause i think you need to build your own kernel.

Thanx! Could you please make or modify a kernel for the cyanogenmod 7.1 that I'm using. I'm pretty new to this android development, all I know is how to root, change bootanimation, and other basic things. Thanx in advance!

Ya kernel...read it can be changed in the param.lfs without having to build a kernel. Not sure how true this is in the case of mini.

What do I have to read and edit? And where can I find this param.lfs? Thanx in advance dude!

I replies on your other thread in Galaxy Mini General. Try modifying TASS.rle in root folder. I don't know if you need to unpack-then-repack your boot.img though.
Edit :
Since this "TASS.rle" doesn't exist in CM7 update zip file, then it means you do have to unpack your boot.img, open the ramdisk folder then edit the extracted TASS.rle" using image editor or something. I never modified TASS.rle so I don't know exactly how to do it.
If you're using Windows, you can use dsixda kitchen+custom cygwin package+Java Dev Kit to do the unpack+repack. It's somewhere in xda.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

Thanx a lot dude! But are you sure it'll work? I'll try it out, but is there any simpler method than this. Some way that I can modify it using my phone itself? By the way are you using cyanogenmod 7.2 RC 3 by squadzone? How is it? Please give the link too... thanx in advance!

Like I said, I never modified TASS.rle so I have no clue if it will work or not. I did unpacked and repacked boot.img several times using dsixda kitchen and they worked.
I don't know if easier method exist, so I only suggest what I know from browsing.
It looks like in order to do what you want, several steps are needed :
1. Unpacking your boot.img into zImage file (kernel) and ramdisk folder.
Anything inside ramdisk.folder will be flashed into your system partition each time you boot your device. Examples are init.rc, default.prop and TASS.rle. You can do whatever you want with these files, say modifiying their contents, but the changes only persist as long as you do not boot your phone, which will restore them back to initial state as I explained above.
2. Converting TASS.rle found inside ramdisk folder into editable format such as PNG
3. Modifying the converted PNG in point 2 (using Photoshop or other app)
4. Re-converting the modified PNG from point 3 back into RLE format
5. Re-packing (compiling) zImage file and ramdisk folder (having modified TASS.rle from point 4) back into boot.img
6. Flashing boot.img from point 5 into your phone.
To make it short, you need to learn how to :
1. Unpack and repack boot.img, which you can do using dsixda kitchen from here : http://forum.xda-developers.com/showthread.php?t=633246
2. Converting RLE to PNG and vice versa. More info here : http://forum.xda-developers.com/showthread.php?p=20128066
3. Flashing boot.img into phone. You can compress your boot.img into TAR (type this in cygwin shell window "tar -cf boot.img.tar boot.img" and flash it using ODIN with one package option or you can create a flashable zip file.
CM 7.2 RC3 works great for me, better than RC2; but that's my personal judgement and there's a chance you will not agree with me after you try it.
Head over to CM 7.2-RC3 by squazone for download link.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.

roofrider said:
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
Click to expand...
Click to collapse
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Thanks.
I have Ubuntu on a vm

And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Ya...but I didn't try cpio to extract ramdisk..simply clicking it mounted the ramdisk and it's contents were visible...I wonder if I make any change and unmount it will be saved or not?! Then no need to gzip and cpio

Thanx guys! roofrider and distan7 for all your help and support! If I had a bank account, I would have donated by now, but since I don't all I can do is click the thanks button! Thanx a lot dudes!

You're welcome mate
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

I've attached the tass.rle converted to tass.png thanks to ketut.
but this is only one of the 2 images that appear while booting.
I have to dump the stl6 to find the other i think...but dumping stl5 bricks the phone (stepph) so a little nervous...but i might give it a try.
edit: no harm done.
but stl6 had nothing....anyone got any ideas?
the .jpg or whatever is hidden somewhere, at least that is how it is for galaxy s variants.

[System Dump] Android 4.1 Jelly Bean SDK...Let the hacking begin!!!

Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRN83C
ro.build.display.id=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.version.incremental=391408
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1
ro.build.date=Sat Jun 23 01:40:53 UTC 2012
ro.build.date.utc=1340415653
ro.build.type=eng
ro.build.user=android-build
ro.build.host=vpak16.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk
ro.product.brand=generic
ro.product.name=sdk
ro.product.device=generic
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.fingerprint=generic/sdk/generic:4.1/JRN83C/391408:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
The system dump for Android 4.1 has been pulled from the GSM Galaxy Nexus update, and ready for developers to get their talented little hands on
Download:http://minus.com/lby5qoGOSNGmyS
What i've done until now:
- /system/app
- fonts, framework, media, tts, usr, xbin
- copyed busybox from CM9
- Edited build.prop
- Added some missing files in /system/bin
Doing now:
Unpacking boot.img
Problems:
ramdisk

Sweeeeeeeeeeeetttttt

Let make this post on the top of thread....make easy for all our talent Rom Developer

:good:

oh~ wow!!!

NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull

Does it work, i mean... even a bit on our N7000 ?

Wait for imilka, cm team or kang team
Sent from my GT-N7000 using Tapatalk 2

Nice bro thanks :victory:

sorcio46 said:
Does it work, i mean... even a bit on our N7000 ?
Click to expand...
Click to collapse
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Ya...not much different...can't wait jellybean port at note

Rulinglionadi said:
NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull
Click to expand...
Click to collapse
Dun worried all senior developer will releases their own custom rom soon...

kfheaven said:
Dun worried all senior developer will releases their own custom rom soon...
Click to expand...
Click to collapse
True...we will be seeing a CM 9.1 midNightlies ....soon... :silly:

My body is ready.

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Depending on lib dependancy on kernel drivers the best you can hope for will be a port based on ICS kernel which will be fugly.
Frameworks etc in their compiled state are only reversible to smali and xml so the significance of this isnt great for any real development. First one needs to wait for flagship releases and then the source to drop.
Sent from my GT-N7000 using xda premium

Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Go for it then
Sent from my GT-N7000 using xda premium

this is for the samsung galaxy note or to sdk on computer ? .

:good:

kfheaven said:
Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
Click to expand...
Click to collapse
:good::good::good:All the very Best our whole wishes with you......cant wait to be ported in jellybeam android v4.1.... :good::good::good:

S5830i defconfig use cooperve_defconfig when building from source

Hi friends of XDA,
I think this might be helpfull for some of you trying to compile kernel from source for S5830i, for the first time.
If you are following the great tutorials to build your first kenrel like:
http://forum.xda-developers.com/showthread.php?t=1748297 from thewadegeek
The first thing taht will happen, is that you cant pull defconfig from /proc/config.gz for S5830i.
Why? There is no such file for your device in there.
Normally the next you will do, is go to the stock sources readme file. And will find out the defconfig is totoro_defconfig
You will compile the kernel with no errors, and you will feel very happy, until you flash your recently compiled kernel and see that you get stuck in the boot_logo screen.
Ok, dont panic, solution is very easy. Samsung readme file is a general readme.
Here is the quid of the question:
totoro_defconfig is not the correct defconfig for S5830i.
S5830i defconfig is bcm21553_cooperve_defconfig
You will find this defconfig in the sources, at:
common/arch/arm/configs folder
Hope this helped. If it helped dont doubt to press the thanks button, this will be very appreciated.
Thank you and sweet kernel development.

Samsung's readme file isn't general, they just took the Galaxy Y's readme (even the model says GT 5360).
What's stranger is that the CHN sources have the correct info.
Also, I didn't need to pull anything. I just used the default config:
Code:
export ARCH=arm
export CROSS_COMPILE=<path>
make bcm21553_cooperve_defconfig
make -j16

Hi GermainZ,
Thats right,never had a look at the CHN readme. I wonder why the other sources are uploaded looooollll strange Samsun guys.
Never the less, forgot to post the next in the original thread.
I recomend to have an original copy of bcm21553_cooperve_defconfig as when you start modifing it some options may fail and its recomended to have a fresh one to copy paste quicly.
Even more for my kernel i copy original file and rename it to nit_defconfig and give it a version number ej nit01_defconfig, its agood practice have latest working defconfig as you will be modifying the file a lot, btw nit is how i call my kernel as you all ready know, this comes from new innovative technologies the name of one of my companys i created recently
But good appreciation GermainZ is always my pleasure to talk with you
Sent from my GT-S5830i using xda app-developers app

Thanks for your tips bro! You had a significant part in booting my kernel. Will add u in credits

No problem hell_lock.
Thank you.
Sent from my GT-S5830i using xda app-developers app

I need p880 file for edify_defs dsixda's kitchen

hi guys I need p880 file for edify_defs dsixda's kitchen i want to know if i really need that file to run kitchen so i don't know how to build that file
for example p990 file:
# LG Optimus 2X
change_mnt=yes
fix_boot=yes
param1=ext3
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p1
cache_mnt=\/dev\/block\/mmcblk0p2
boot_mnt=\/dev\/block\/mmcblk0p5
data_mnt=\/dev\/block\/mmcblk0p8
sdcard_mnt=\/dev\/block\/mmcblk0p9
p999 file:
# LG Optimus G2X
change_mnt=yes
fix_boot=yes
param1=ext3
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p1
cache_mnt=\/dev\/block\/mmcblk0p2
boot_mnt=\/dev\/block\/mmcblk0p5
data_mnt=\/dev\/block\/mmcblk0p7
sdcard_mnt=\/dev\/block\/mmcblk0p8
so how to build that file i just copied p990 file and renamed into p880 and changed param1=ext3 to param1=ext4 but i don't know if that solve my problem .

Code:
# LG Optimus 4X HD P880
change_mnt=yes
fix_boot=yes
param1=ext4
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p3
cache_mnt=\/dev\/block\/mmcblk0p4
boot_mnt=\/dev\/block\/mmcblk0p2
data_mnt=\/dev\/block\/mmcblk0p8
This is what I can think of now. I didn't test it. If you do so and it works well, I will reach out to dsixda to add official support. Thanks!

Adam77Root said:
Code:
# LG Optimus 4X HD P880
change_mnt=yes
fix_boot=yes
param1=ext4
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p3
cache_mnt=\/dev\/block\/mmcblk0p4
boot_mnt=\/dev\/block\/mmcblk0p2
data_mnt=\/dev\/block\/mmcblk0p8
Click to expand...
Click to collapse
thanx now i can start my project > stock based rom

Do revert after you finish and it works.

Adam77Root said:
Do revert after you finish and it works.
Click to expand...
Click to collapse
sorry but i don't test it right now

i'm not sure if that is working
Adam77Root said:
Do revert after you finish and it works.
Click to expand...
Click to collapse
i'm not sure if your p880 file is right because sdcard_mnt=\/dev\/block\/ is missing i make a photo of my terminal on windows i searched on the internet http://forum.xda-developers.com/showthread.php?t=2186015 and again i cannot find ex mmcblk0 :|
# LG Optimus 4X HD P880
change_mnt=yes
fix_boot=yes
param1=ext4
param2=EMMC
sys_mnt=\/dev\/block\/APP
cache_mnt=\/dev\/block\/CAC
boot_mnt=\/dev\/block\/LNX
data_mnt=\/dev\/block\/UDA
metadata_mnt=\/dev\/block\/MDA
misc_mnt=\/dev\/block\/MSC
modem_mnt=\/dev\/block\/MDM
recovery_mnt\/dev\/block\/SOS
staging_mnt=\/dev\/block\/USP
sdcard_mnt=\/dev\/block\/p1
Click to expand...
Click to collapse

The problem with SD card is that ours is a datamedia device, the internal SD card is on the data partition.
Is that option really needed? Does the kitchen throw any error about it?
Sent from my LG-P880