yashsingh1/xdaforums huggingface dataset:
[Android Software Development] danarama:
Works great to be honest. Other than preventing people formatting stuff, I cant think of anything to improve things. If I have an epiphany though, i'll let you know,
[Android Software Development] Phil3759:
As i said, some kernels do allow f2fs on other partitions

I prefer letting it open rather than starting with flags at compile time: less device tree maintenance

Else, just add exceptions there in code, not so hard. A few if strcmp exceptions
[Android Software Development] kronikings:
Anyone out there have any ideas on how to resolve my issue? Phil? Please help
[Android Software Development] danarama:
Yeah I understand. We'll go with your preference ;)

That's the only idea I had.
[Android Software Development] Phil3759:
It is just to simplify code maintenance, i am lazy on some parts sometimes...
[Android Software Development] kronikings:
Ok I guess I am just going to be ignored again and again...I sit here for hours waiting for a response while I continue to see conversation back and forth ignoring my request. forget it. thanks anyway.
[Android Software Development] danarama:
No problem!

I'll let you know if I think of anything but right now, process is simple and easy to use.

Only problem I had was adb pushing my /sdcard data back after migration. Permissions screwed or something. Had to boot into Android and use MTP and all was well.

---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------

That's because this is the development thread for developers. You're not posting about development so your posts get ignored. If you want user help, post in your user thread For your device. This thread discusses the future of Philz recovery, not md5 mismatch
[Android Software Development] kronikings:
Thanks for the response. I made a mistake by asking my question in the wrong thread and after many hours you have pointed that out to me and sent me in the right direction. Thanks.
[Android Software Development] danarama:
The problem here is probably no one in this thread has your phone. I don't even know which you have
[Android Software Development] kronikings:
Well the reason why I asked here is because my devices thread has almost no action since 3 months ago. I have the hltevzw...dev edition verizon galaxy note 3....

http://xdaforums.com/showthread.php?p=53073723
[Android Software Development] noskojv:
Support Samsung GT-I9295 Galaxy S IV Active 4.4.2

Please
[Android Software Development] metalspring:
[MENTION=4666971]Phil3759[/MENTION] is there any update for the m8 version of your recovery coming soon? I'd like to try to build an f2fs rom and kernel but need a compatible recovery (and I have never built any recoveries before so I have no idea how to add the needed commits lol)
[Android Software Development] Phil3759:
So that f2fs be of any use for you, you must first have a kernel compatible with f2fs!
[Android Software Development] metalspring:
The m8 does have kernels compatible with f2fs-

https://github.com/metalspring/android_kernel_htc_msm8974/commits/kk44/fs/f2fs
[Android Software Development] Pons:
Needs to be enabled.

https://github.com/metalspring/andr...4-test/arch/arm/configs/cm_m8_defconfig#L3451
[Android Software Development] metalspring:
True, but I do have it enabled in my local source, plus I do know where to find more f2fs source if need be, plus I know where to get different kernel f2fs source if need be, and how to add support for f2fs in the rom but just never messed with building recoveries before so I have no idea how to add f2fs source to the recovery
[Android Software Development] danarama:
Well building the recovery cwm builds from cm11 source and compiles the cm11 kernel so you'd add the commits in to the cm11 kernel in exactly the same way. Or use prebuilt kernel but not sure why you'd do that
[Android Software Development] Phil3759:
I see you have 3.4 kernel, so adding f2fs code to cm-11.0 tree is easy

Will release an m8 update with f2fs support enabled
[Android Software Development] Phil3759:
6.43.5 (01.06.2014)

This fixes a small annoyances: after a COMPLETE formatting of /data, the recovery would default to /data/media instead of /data/media/0

While it is ok for Android 4.1 devices, it is not expected for those on +4.2

Now, by default, recovery will always default to /data/media/0 unless set at compile time or defined by user in Advanced menu
[Android Software Development] 4peace1:
PLEASE can you make one for LG L90 D410 4.4.2
[Android Software Development] danarama:
You can also ask a developer of your device to read post 2 of this thread and make one for you!
[Android Software Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION]

wired

You seem right

I ended up testing it myself and data media path is not created!

Back to the sources :crying:
[Android Software Development] danarama:
Ah ok.

It is not critical. You've done a massive amount this weekend, please take some time off!
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION]

i uploaded PhilZ Touch 6.43.5 for you for:

- P3100

- P3110

- P5100

- P5110

- Golden

as flashable ZIP and odin flashable *.tar.md5. i zipped all together: philz_touch_6.43.5.zip - 75.85 MB

This time i followed your file-nameing rules :) Feel free to upload to goo.im

philz_touch_6.43.5-golden.tar.md5	8,10 MB
philz_touch_6.43.5-golden.zip	8,23 MB
philz_touch_6.43.5-p3100.tar.md5	7,39 MB
philz_touch_6.43.5-p3100.zip	7,53 MB
philz_touch_6.43.5-p3110.tar.md5	7,32 MB
philz_touch_6.43.5-p3110.zip	7,45 MB
philz_touch_6.43.5-p5100.tar.md5	7,46 MB
philz_touch_6.43.5-p5100.zip	7,59 MB
philz_touch_6.43.5-p5110.tar.md5	7,38 MB
philz_touch_6.43.5-p5110.zip	7,52 MB
[Android Software Development] Phil3759:
Huge thanks (out of my daily :good: limit)

However, can you compile 6.43.6 rather :o

It fixes a bug when creating /data/media/0 after full /data formatting

I am uploading sources in a few minutes
[Android Software Development] Android-Andi:
Sure, i will do ;)

Gesendet von meinem GT-I8190 mit Tapatalk

Edit:

Never out of THX on Tapatalk :D
[Android Software Development] Phil3759:
6.43.6

[MENTION=2872010]rootSU[/MENTION]

I tested and it works properly now
[Android Software Development] Android-Andi:
THanks [MENTION=4666971]Phil3759[/MENTION] :)

P3110 and P3100 allready recompiled :) :p will upload later together with P51XX and Golden.

---------- Post added at 12:36 AM ---------- Previous post was at 12:01 AM ----------

[MENTION=4666971]Phil3759[/MENTION] here we go :)

P3100 and P3110:

philz_touch_6.43.6-p31xx.zip - 29.64 MB

P5100 and P5110:

philz_touch_6.43.6-p51xx.zip - 29.91 MB

Golden:

philz_touch_6.43.6-golden-tar.md5-and-zip.zip - 16.30 MB

(every zip includes flashable *.zip and Odin flashable *.tar.md5)
[Android Software Development] stewwmann:
thanks

Thanks for this awesome tool, I have been wiping cache, wiping dalvic cache under advanced tab and wipe data/factory reset when installing a new rom. Should I be using "clean to install new rom" instead of wipe data/factory reset? I have always been afraid of wiping the ext sd card,which is where my backups and the new rom usually live. Thanks, I have looked and can't find a good explanation of the difference, but I see in videos that one of the steps in "new rom" is format ext sd. Yikes.......

I also posted this in device specific thread.
[Android Software Development] Android-Andi:
[MENTION=5102426]stewwmann[/MENTION] the differents mentioned in FAQ on first Page ;)

You can use "Clean to install a new rom",

else you should at leaset:

Wipe Data Factory Reset -> Wipe Data Factory Reset

Wipe Cache

Advanced -> Wipe Dalvic cache

Mounts and Storage -> format /system

flash Rom

flash GApps

"Format /system" needed to not gettings problems because of some GApps changes (in the past some of the backup-scripts for GApps caused problems on our Galaxy Tab 2) .
[Android Software Development] stewwmann:
yeah,thanks. I read that, and right there it says "format ext-sd". One of the reasons for my confusion........
[Android Software Development] danarama:
No it doesn't. It says "sd-ext" not "ext-sd". Completely different things.

Ext-sd = external sd card

Sd-ext = ext partition formatted on your sdcard used for symlinking /data/* directories on low storage devices
[Android Software Development] stewwmann:
Thank you Sir, the lights are on, and now someone is also home.
[Android Software Development] danarama:
Haha. Yeah maybe but you should also get an alarm because I just snook in and took your TV ;)
[Android Software Development] Phil3759:
6.43.6 rolled out:

Huge thanks to the developers who compiled it and ported for all their devices
[Android Software Development] Android-Andi:
F2fs not added to p31xx and p51xx - sperate blackhawk-f2fs recovery compiled therefor.

Golden do not have f2fs kernel, no need atm :)

Gesendet von meinem GT-I8190 mit Tapatalk
[Android Software Development] Phil3759:
ah, :good:

will edit my post
[Android Software Development] danarama:
It's been a fun weekend :)
[Android Software Development] joni2012:
Great, you upload m7?.i have nandroid backup image data error you help my?. Very thank
[Android Software Development] fylim:
Can someone help create CWM for Note 3 Neo ?

http://xdaforums.com/note-3-neo

There are 2 versions.

- Samsung GALAXY Note 3 Neo 3G SM-N750

- Samsung GALAXY Note 3 Neo LTE+ SM-N7505

Thank you !!
[Android Software Development] Phil3759:
Thanks a lot for all your generous donations
[Android Software Development] danarama:
No problem. I'd give more if I could but I have to be careful each month :)

Please don't feel the need to openly thank me for donations. I do it to thank you for all the work you do, not for recognition :)
[Android Software Development] joni2012:
Because it gives me error when doing nandroid? Error data image
[Android Software Development] bangdes:
Galaxy tab plus P6200 please....
[Android Software Development] cantenna:
Hi Philz, we desperately need a recovery for the ekgc 200 galaxy camera 2. Building it myself is way beyond the scope of my abilities and my wife will divorce me if I brake the camera she gave me. If you could work your magic, I and I'm sure others would be very appreciative. Best Regards,
[Android Software Development] danarama:
If your device has CM 11, simply ask a developer in your device forum to build it.
[Android Software Development] cantenna:
Thank you but there are no custom ROMs or kernels available for the galaxy camera 2. All that is avilble is chain fire super su so my camera is rooted, its a bit like unprotected sex atm
[Android Software Development] danarama:
If there is no CM11 source, then it's really hard to do.
[Android Software Development] cantenna:
How much will it cost me? There plenty of development (custom ROMs and kernel) for galaxy camera 1. How different could they be?
[Android Software Development] danarama:
I cant answer that. Maybe its just a waiting game.
[Android Software Development] cantenna:
Perhaps, nobody seems interested in developing for it, been in circulation for a year now. :(

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

Is an awesome camera though, even better rooted.
[Android Software Development] shoxxy:
Hi

Hey at all

Since version ~6.41. i have the known problem, that not all buttons + Touch works correct, i could select a menu point, but to go into the menu i must use hardware button. (gui settings are correct). have someone maybe a solution for this :) ???

Regards
[Android Software Development] jurben:
it looks like it's time to ask. i don't want to interupt top developers discussion days before .. :D

my PhilZ-CWM cannot mount usb storage.

After inserting logging commands in function control_usb_storage (in file extendedcommands.c) i find out that :

if i add voldmanaged= flag for my external storage in recovery.fstab then fs_mgr_is_voldmanaged is true, but vold_is_volume_available is false, so mount usb storage is not functioning, further more, my external storage is not in the list on "mount and storage"

if i do not add voldmanaged= flag for my external storage then both fs_mgr_is_voldmanaged and vold_is_volume_available are false, so mount usb storage is not functioning either, but my external storage is in the list on "mount and storage"

the weidr thing (i think) is: when i run adb shell and execute

# setprop sys.storage.ums_enabled 1

# echo "/dev/block/mmcblk1p1">/sys/devices/platform/msm_hsusb/gadget/lun1/file

then my external storage is mounted as usb mass storage.

what must i do in order to make mount usb storage functioning normally? (or to make my external storage state is fs_mgr_is_voldmanaged and vold_is_volume_available ?)

(sorry for bad my English. i hope understandable)
[Android Software Development] XxM4tzexX:
Is there any chance of creating a app for flashing this recovery on the go. I find it quite time-consuming downloading it from browser and flashing it manually in recovery or odin.
[Android Software Development] danarama:
Flashify. Mobile Odin...

Recovery is not time consuming.
[Android Software Development] Orphee:
Hello,

Latest 6.43.6 for moto_msm8960 ready :

http://xdaforums.com/showpost.php?p=53103684&postcount=158

:)
[Android Software Development] Phil3759:
If you are compiling it on your own, just add this line to your device.mk

PRODUCT_DEFAULT_PROPERTY_OVERRIDES += \
sys.storage.ums_enabled=1

and this one to your BoardConfig.mk

BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun1/file"

Before building, clean up all recovery and vold/minivold intermediates

If you are unsure, remove whole device out folder

You must also be using the proper vold path in your fstab, but it could work with /dev/block/mmcblk1p1 I think

does this work?

https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en

Hard to say, seems the mount point for /cache is causing some issues...

Maybe try to ask some of the members who could port it to MTK devices and look at their ramdisk after unpacking it
[Android Software Development] XxM4tzexX:
Apparently they doesn't support my s4 mini GT-I9195.

---------- Post added at 08:45 PM ---------- Previous post was at 08:31 PM ----------

Thanks this one is perfect!
[Android Software Development] MasterAwesome:
[MENTION=4666971]Phil3759[/MENTION], what does operation not supported on transport endpoint mean?

I took mount points from a working recovery... Can you check if the flags in recovery fstab are correct?

Regards

MasterAwesome
[Android Software Development] Phil3759:
6.43.8 (02.06.2014)

There is no point updating from 6.43.6 to 6.43.8 except for devices with a recovery.fstab setting f2fs as main format

As far as I know, only falcon does such thing
[Android Software Development] SevenMaxs:
PhilZ Touch 6.43.6 for Zopo Zp990+

Я сделал PhilZ Touch 6.43.6 recovery для Zopo Zp990+ (mt6592).

Но есть одна проблема, при резевном копировании в формате TWRP я получаю такой путь TWRP/BACKUPS/0000000000000000/ для резервной копии...

Не могу понять почему так получается.

И еще один вопрос - как добавить в список резервного копирования и восстановления разделы:

/uboot
/nvram
/logo

Прошу прощения за плохой англиский!

Спасибо!

I compiled PhilZ Touch 6.43.6 recovery for Zopo Zp990 + (mt6592).

But there is one problem: when the backup I get this way "TWRP/BACKUPS/0000000000000000 /" for backup ...

I can not understand why this is so.

And one more question - how to add to the list of backup and restore partitions:

/uboot
/nvram
/logo

Sorry for the bad English!

Thank you!

My BoardConfig.mk

TARGET_COMMON_NAME := Zopo Zp990+
BOARD_USE_MTK_LAYOUT := true
BOARD_MTK_BOOT_LABEL := "/boot"
EXTRA_PARTITIONS_PATH := "/nvram"
EXTRA_PARTITIONS_PATH := "/logo"
TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080
BRIGHTNESS_SYS_FILE := "/sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness"
BATTERY_LEVEL_PATH := "/sys/class/power_supply/battery/capacity"
TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID := true

My recovery.fstab

/dev/bootimg	/boot	emmc	defaults defaults
/dev/recovery	/recovery	emmc	defaults defaults
/dev/uboot	/uboot	emmc	defaults defaults
/dev/misc	/misc	emmc	defaults defaults
/dev/logo	/logo	emmc	defaults defaults
/dev/nvram	/nvram	emmc	defaults defaults
/dev/block/mmcblk0p5	/system	ext4	ro,noatime wait
/dev/block/mmcblk0p6	/cache	ext4	noatime,nosuid,nodev,noauto_da_alloc wait
/dev/block/mmcblk0p7	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/devices/platform/mtk-msdc.0/mmc_host/mmc0	auto	auto	defaults	voldmanaged=sdcard0:8
/devices/platform/mtk-msdc.1/mmc_host/mmc1	auto	auto	defaults	voldmanaged=sdcard1:auto
/devices/platform/mt_usb	auto	auto	defaults	voldmanaged=usbotg:auto

My extra.fstab

/dev/block/mmcblk0p8	/storage/sdcard0	auto	defaults	defaults
/dev/block/mmcblk1p1	/storage/sdcard1	auto	defaults	defaults
/dev/block/mmcblk1p2	/sd-ext	auto	defaults	defaults
/dev/block/sda1	/storage/usbotg	auto	defaults	defaults

In default.prop add

ro.cwm.forbid_format=/boot,/recovery,/logo,/uboot,/nvram
ro.cwm.forbid_mount=/boot,/recovery,/logo,/uboot,/nvram
[Android Software Development] Orphee:
You're too fast :p building again ^^
[Android Software Development] joni2012:
For any phone.? To m7? Thanks
[Android Software Development] starbucks2010:
goo.im was down all day for me. Same for anyone else?
[Android Software Development] Pons:
http://isup.me/Goo.im
[Android Software Development] starbucks2010:
Yes, it seems to be ok now.
[Android Software Development] kronflux:
I'm wondering - when building PhilZ touch, is there a way to set a theme I've created and saved to be default for the recovery rom I build?

obviously these settings are -somewhere- but I don't really want to have to go poking around to find it. thought it might be best if I just ask here :)

Thanks in advance!

ps: the reason I ask, is because my device has a very small screen, and the default theme doesn't fit nicely nor does it look right. the theme I've created fixes this.

also, where can I change the "PhilZ Touch 6" at the top? I'm not trying to change the credit, I just want to remove the word "Touch", because along with the default theme not looking right, touch doesn't work very nicely. I'll be leaving the ability to turn on touch in the rom, but I want the default setup to be non-touch. Same goes for the bottom text with the full version.
[Android Software Development] danarama:
You can it use grep to find the version numbers. Or even look at the commits on github since version is changed every release
[Android Software Development] Phil3759:
Most theme settings are defined here:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/libtouch_gui/touch_gui.h#L194

You can even change one line:

// #define PHILZ_MAGENTA_THEME true
#define PHILZ_BLACK_THEME true

and you get the old classic black theme
[Android Software Development] SevenMaxs:
Help guys!

:crying:
[Android Software Development] shoey63:
Are you building with cm11 sources?
[Android Software Development] danarama:
in the fstab
[Android Software Development] SevenMaxs:
yes

My recovery.fstab

/dev/bootimg	/boot	emmc	defaults defaults
/dev/recovery	/recovery	emmc	defaults defaults
/dev/uboot	/uboot	emmc	defaults defaults
/dev/misc	/misc	emmc	defaults defaults
/dev/logo	/logo	emmc	defaults defaults
/dev/nvram	/nvram	emmc	defaults defaults
/dev/block/mmcblk0p5	/system	ext4	ro,noatime wait
/dev/block/mmcblk0p6	/cache	ext4	noatime,nosuid,nodev,noauto_da_alloc wait
/dev/block/mmcblk0p7	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/devices/platform/mtk-msdc.0/mmc_host/mmc0	auto	auto	defaults	voldmanaged=sdcard0:8
/devices/platform/mtk-msdc.1/mmc_host/mmc1	auto	auto	defaults	voldmanaged=sdcard1:auto
/devices/platform/mt_usb	auto	auto	defaults	voldmanaged=usbotg:auto

My extra.fstab

/dev/block/mmcblk0p8	/storage/sdcard0	auto	defaults	defaults
/dev/block/mmcblk1p1	/storage/sdcard1	auto	defaults	defaults
/dev/block/mmcblk1p2	/sd-ext	auto	defaults	defaults
/dev/block/sda1	/storage/usbotg	auto	defaults	defaults

Thank you!
[Android Software Development] danarama:
Don't forget the one in your device fstab.devicename
[Android Software Development] Phil3759:
1-

Read well the use of extra.fstab

It is there only to add support for blk_device2, fs_type2 and fs_options2

You cannot define extra partitions there, just extra info for partitions defined in main fstab

---> Move your sd-ext line to recovery.fstab

2-

Again, read well the comments help for using the flags:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L16

the below line seems wrong to me:

/dev/bootimg	/boot	emmc	defaults defaults

verify if the mount point shouldn't be:

/dev/bootimg	/bootimg	emmc	defaults defaults

3-

Again, you doesn't read:

boot, uboot and recovery are automatically backed up if you enable MTK flags

4-

finally, you really don't read ;)

the below comments explain how to add support for extra partitions:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L36

This should answer all your questions

Finally, take time to read first page, include the FAQ and the post 2

http://xdaforums.com/showpost.php?p=39433612&postcount=2
[Android Software Development] SevenMaxs:
Phil3759, Thank you!

I studied all the instructions, but it does not work mt6592.

I simply do not understand English.

My BoardConfig.mk

TARGET_COMMON_NAME := Zopo Zp990+
BOARD_USE_MTK_LAYOUT := true
BOARD_MTK_BOOT_LABEL := "/boot"
EXTRA_PARTITIONS_PATH := "/nvram"
EXTRA_PARTITIONS_PATH := "/logo"
TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080
BRIGHTNESS_SYS_FILE := "/sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness"
BATTERY_LEVEL_PATH := "/sys/class/power_supply/battery/capacity"
TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID := true

Why do so

/dev/bootimg	/boot	emmc	defaults defaults

---------- Post added at 04:41 PM ---------- Previous post was at 04:31 PM ----------

But this is not necessary - always make a backup copy of partition /uboot.

In any case, thank you very much!

You did a great job. :good:
[Android Software Development] danarama:
EXTRA_PARTITIONS_PATH := "/nvram", "/logo"
[Android Software Development] SevenMaxs:
Phil3759

rootSU,

Thank you so much!
[Android Software Development] Phil3759:
proper code

TARGET_COMMON_NAME := Zopo Zp990+
BOARD_USE_MTK_LAYOUT := true
BOARD_MTK_BOOT_LABEL := "/bootimg"
TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080
BRIGHTNESS_SYS_FILE := "/sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightness"
BATTERY_LEVEL_PATH := "/sys/class/power_supply/battery/capacity"
TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID := true

[MENTION=2872010]rootSU[/MENTION]

you cannot define multiple EXTRA_PARTITIONS_PATH flags :eek:

just do not define it and use this fstab:

/dev/bootimg	/bootimg	emmc	defaults defaults
/dev/recovery	/recovery	emmc	defaults defaults
/dev/uboot	/uboot	emmc	defaults defaults
/dev/misc	/misc	emmc	defaults defaults
/dev/logo	/extra_part1	emmc	defaults defaults
/dev/nvram	/extra_part2	emmc	defaults defaults
/dev/block/mmcblk0p5	/system	ext4	ro,noatime wait
/dev/block/mmcblk0p6	/cache	ext4	noatime,nosuid,nodev,noauto_da_alloc wait
/dev/block/mmcblk0p7	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

/dev/block/mmcblk1p2	/sd-ext	auto	defaults	defaults

/devices/platform/mtk-msdc.0/mmc_host/mmc0	auto	auto	defaults	voldmanaged=sdcard0:8
/devices/platform/mtk-msdc.1/mmc_host/mmc1	auto	auto	defaults	voldmanaged=sdcard1:auto
/devices/platform/mt_usb	auto	auto	defaults	voldmanaged=usbotg:auto

extra.fstab

/dev/block/mmcblk0p8	/storage/sdcard0	auto	defaults	defaults
/dev/block/mmcblk1p1	/storage/sdcard1	auto	defaults	defaults
/dev/block/sda1	/storage/usbotg	auto	defaults	defaults
[Android Software Development] danarama:
Really? I was confident I did do that in my source

EXTRA_PARTITIONS_PATH := "/efs1", "/efs2"

My box is powered off though so cannot sftp in to check :/
[Android Software Development] SevenMaxs:
Thanks for your help guys!

Today I will make compiling.

And then I will tell about result.
[Android Software Development] Phil3759:
It won't work that way

But it is rather a good idea