Database Info

[Q] [P3100] wrong device flash /efs /modem /recovery corrupted

Hi every one!
I made a huge mistake yesterday evening: i flashed Zip's through CWM that don't belong to my p3100 but to i705.
According to MrHyde03, the files i destroyed were those partitions:
(p3100) /modem emmc /dev/block/mmcblk0p8 (TZ on i705)
(p3100) /efs ext4 /dev/block/mmcblk0p1 (MODEM on i705)
(p3100) /recovery emmc /dev/block/mmcblk0p6 (RPM on i705)
I Flashed those 3 files (!! DON'T DO IT !!):
MrHyde03 said:
a. TZ - Trust Zone VRBLL2_tz.zip
b. NON-HLOS - Modem VRBLL2_modem.zip
c. RPM - Resource Power Management -OPTIONAL-Some say it helps battery. I can't tell a difference. VRBLL2_rpm.zip
Click to expand...
Click to collapse
in the b-c-a order.
Now my phone boot lock: i can access download mode, recovery, can flash and run CWM.
I tried to flash stock odin rom, with pit and repartition for 16gb p3100.
Same results whatever the rom: it runs up to the animated logo, then show the logo forever. (no boot loop).
I guess /recovery is fine because i can enter and flash recoverys.
I guess /modem is fine because i flashed a p3100 JB modem and CWM said "DONE".
I guess is still have a partition problem with /efs
Fortunately: i made a adb copy of my whole /efs folder when i had my p3100...
My problem may be what CWM 6.3.0.0 (philz touch version) says:
W: failed to mount /dev/block/mmcblk0p1 /efs ext4 (invalid argument)
Error mounting /efs!
This is why i can't push anything into /efs: it is volatile and cleaned after each reboot.
Should i start odin and hit the infamous and dangerous "clear phone efs" button ?
Thanks a lot for your help.

You can try, but you should have a EFS backup, without a backup of your EFS don't doing this I have googled you Failure, think you must go to the repair center.

Dexxmor said:
You can try, but you should have a EFS backup, without a backup of your EFS you should not doing this I have googled you Failure, think you must go to the repair center.
Click to expand...
Click to collapse
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional

According to this thread i need to flash an empty EFS partition image in order for my files to STAY in /efs after each reboot.
EFS pro did the job of providing a well formatted /efs folder (every files,owner,group and rights were set) through its "clean efs" feature. (DON'T USE IT IF YOU HAVEN'T your OWN EFS BACKUP)
Now, i have to hand pick every files of my backup, and put them back in place in /efs...

FYI, the correct structure of /efs directory:
PHP:
drwxrwxr-x root root 2013-03-29 12:35 .files
-rwx------ radio radio 1048576 2013-03-29 12:35 .nv_core.bak
-rwx------ radio radio 32 2013-03-29 12:35 .nv_core.bak.md5
-rwx------ radio radio 2097152 2013-03-29 12:35 .nv_data.bak
-rwx------ radio radio 32 2013-03-29 12:35 .nv_data.bak.md5
drwxr-xr-x system system 2013-03-29 12:35 FactoryApp
drwxrwxr-x radio system 2013-03-29 12:35 bluetooth
drwxrwxr-x radio system 2013-03-29 12:35 imei
-rw------- radio radio 276 2013-03-29 12:35 nv.log
-rwx------ radio radio 2097152 2013-03-29 14:52 nv_data.bin
-rwx------ radio radio 32 2013-03-29 14:52 nv_data.bin.md5
drwxrwxr-x radio system 2013-03-29 12:35 wifi

I have restored all .nv_core and .nv_data files. They resist a phone reboot.
However, files nv_data.* are reseted to new content every phone reboot.
I wonder if i should plug my simcard back or if i should wait to know more: i already had issue with my phone operator's "network security team" and do not want to explain again what i messed up in my phone...
... 5 minutes later ...
nv_data.bin and nv_data.bin.md5 do not seems to be central to geting my imei back. Like this is writen everywhere: .nv_data.bak was !
So: i deleted nv_data*. Rebooted. i checked my rom imei (through phone command *#06#) against my real imei (micro-writen on back of device)... THEY MATCH !
i plugged my simcard back in, rebooted... and my rom doesn't ask for sim-card pin. What's the problem now ?
I think i need to check my modem...

Was just reading a post yesterday about someone flashing the wrong thing to their device. It's a different device but may steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1448765
Hope this helps, good luck

I've already done what's he said. repartition, reflash, formatted my corrupted /efs folder.
Only then i was able to boot a stock rom.
Then i fixed my efs folder and my imei.
Now i'm wondering why my phone doesn't ask for my simcard pin.
So i tried cm10.1 installation procedure:
Flashed philz touch recovery
wiped data and system through recovery
installed JB SBL
installed CM10.1
installed gapps
... YEAH !!!!
CM10.1 28/03 booted, asked me my sim pin code.
Hspda+ icon appear, my phone is safely back to normal operation.
Thank you MrHyde03 for your support,
Thank you all for your time reading my adventure and trying to help.

Maybe the story will different if you have a backup of /efs in raw format. Try in recovery:
Code:
mke2fs -t ext4 -b 4096 -L EFS /dev/block/mmcblk0p1
mount -t ext4 /dev/block/mmcblk0p1 /tmp
Open a new terminal window to push your /efs backup to /tmp.
Please confirm your command output:
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2013-03-29 21:37 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-29 21:37 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-29 21:37 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-29 21:37 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-29 21:37 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-29 21:37 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-29 21:37 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-29 21:37 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-29 21:37 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-03-29 21:37 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-29 21:37 SBL2 -> /dev/block/mmcblk0p3

Don't panic!
just download Odin and flash stock rom (google it)
Everything will be normal. You should get your device like how your get in factory reset/hard reset. :good:

how can I get efs.img
I have the same problem where my efs folder got error, but I don't backup the efs, where I can got the efs.
Thank you

doloop said:
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional
Click to expand...
Click to collapse
Do i need to change something for my p3110 ?

doloop said:
I have a full /efs copy from month ago. Thank to my dropbox account they are safe.
I figured out that busybox and mke2fs are available through adb shell...
I used adb shell:
mke2fs -t ext4 /dev/block/mmcblk0p1
My phone BOOTS UP ! Yeah !
Next step: restore my /efs folder files content:
Tried to adb push my whole directory into /efs => files copied OK but /efs still empty after reboot.
/efs mount correctly, and mmcblk0p1 pass e2fsck OK.
Now trying to restore my files through efs professional
Click to expand...
Click to collapse
plz can you upload ur full /efs copy , i need it dude.
coz i get IMEI null and i didn`t make backup of EFS partition

Safy4u said:
plz can you upload ur full /efs copy , i need it dude.
coz i get IMEI null and i didn`t make backup of EFS partition
Click to expand...
Click to collapse
Sorry you can't.
/efs is my personnal imei, so i'm afraid your phone is dead, and your samsung device is now wifi only.

Hard Brick, Stuck on Boot logo!!!!

I've been dealing with this problem for a couple of weeks now, I have gathered bits and pieces of information but I've had no luck getting this fixed. I was running a 4.3 release of Omni ROM and everything was running ok till I rebooted into recovery (CWM v6.0.3.6) and it asked me to fix root when I tried to reboot back to android. I did that and the tablet rebooted just fine, however the next morning when I woke up I found it stuck on the Samsung Galaxy Note 10.1 logo. I'm still able to get into recovery and download mode but after installing a few other ROMs through recovery and even returning back to stuck with ODIN, nothing has worked yet. Whenever I install a custom ROM in recovery the installation always completes without errors but once I reboot I can't get past the boot logo. On CWM I'm receiving the following errors: "Error Mounting /data!" and "Error mounting /efs!". On ODIN I have tried to return back to stock with and without a PIT file in hopes of re partitioning everything but still no luck. I have also tried to install a different recovery through CWM and ODIN but even though it always completes successfully, I'm unable to override my old CWM recovery partition.
These are the logs I was able to pull with ADB from Recovery:
Code:
/tmp # cat recovery.log
Starting recovery on Fri Jan 13 08:13:39 2012
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p5 (null) 0
3 /recovery emmc /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p8 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p12 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
8 /modem emmc /dev/block/mmcblk0p7 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=N8013UEUCMB3
ro.boot.serialno=41070cd112309f57
ro.serialno=41070cd112309f57
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=N8013UEUCMB3
ro.hardware=smdk4x12
ro.revision=6
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_n8013-userdebug 4.2.2 JDQ39E eng.hudson.20130824.094402 test-keys
ro.build.version.incremental=eng.hudson.20130824.094402
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 24 09:44:46 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=GT-N8013
ro.product.device=GT-N8013
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
ro.build.product=GT-N8013
ro.build.description=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALH2:user/release-keys
ro.build.fingerprint=samsung/p4noterfxx/p4noterf:4.0.4/IMM76D/N8000XWALG9:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=n8013
dalvik.vm.dexopt-data-only=1
ro.sf.lcd_density=160
ro.lcd_min_brightness=20
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130824-UNOFFICIAL-n8013
ro.modversion=10.1-20130824-UNOFFICIAL-n8013
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
Error mounting /data!
W:failed to mount /dev/block/mmcblk0p3 (Invalid argument)
Error mounting /efs!
/tmp #
along with this other info regarding the partitions on my device:
Code:
CWM Errors:
Error mounting /data!
Error mounting /efs!
~ # find /dev/block -path \*/by-name -exec ls -l {} \;
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 13 08:04 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 13 08:04 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 08:04 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 08:04 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 13 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 08:04 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 08:04 USERDATA -> /dev/block/mmcblk0p12
/etc # ls
fstab mtab recovery.fstab
/etc # cat recovery.fstab
# mount point fstype device
/efs ext4 /dev/block/mmcblk0p3
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p12 length=-16384
/preload ext4 /dev/block/mmcblk0p10
/modem emmc /dev/block/mmcblk0p7
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
/etc # cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
~ # ls
cache fstab.smdk4x12 sbin
data init sdcard
default.prop init.rc sys
dev lpm.rc system
efs preload tmp
etc proc ueventd.goldfish.rc
extSdCard res ueventd.rc
external_sd root ueventd.smdk4x12.rc
~ # cat fstab.smdk4x12
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p8 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p12 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
Any help would be greatly appreciated.
Thanks in advance.

Any ideas? Anyone????

Seems like a EFS problem.
AlexFG said:
I've been dealing with this problem for a couple of weeks now, I have gathered bits and pieces of information but I've had no luck getting this fixed. I was running a 4.3 release of Omni ROM and everything was running ok till I rebooted into recovery (CWM v6.0.3.6) and it asked me to fix root when I tried to reboot back to android. I did that and the tablet rebooted just fine, however the next morning when I woke up I found it stuck on the Samsung Galaxy Note 10.1 logo. I'm still able to get into recovery and download mode but after installing a few other ROMs through recovery and even returning back to stuck with ODIN, nothing has worked yet. Whenever I install a custom ROM in recovery the installation always completes without errors but once I reboot I can't get past the boot logo. On CWM I'm receiving the following errors: "Error Mounting /data!" and "Error mounting /efs!". On ODIN I have tried to return back to stock with and without a PIT file in hopes of re partitioning everything but still no luck. I have also tried to install a different recovery through CWM and ODIN but even though it always completes successfully, I'm unable to override my old CWM recovery partition.
These are the logs I was able to pull with ADB from Recovery:
Code:
/tmp # cat recovery.log
Starting recovery on Fri Jan 13 08:13:39 2012
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p5 (null) 0
3 /recovery emmc /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p8 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p12 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
8 /modem emmc /dev/block/mmcblk0p7 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=N8013UEUCMB3
ro.boot.serialno=41070cd112309f57
ro.serialno=41070cd112309f57
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=N8013UEUCMB3
ro.hardware=smdk4x12
ro.revision=6
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_n8013-userdebug 4.2.2 JDQ39E eng.hudson.20130824.094402 test-keys
ro.build.version.incremental=eng.hudson.20130824.094402
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 24 09:44:46 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=GT-N8013
ro.product.device=GT-N8013
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
ro.build.product=GT-N8013
ro.build.description=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALH2:user/release-keys
ro.build.fingerprint=samsung/p4noterfxx/p4noterf:4.0.4/IMM76D/N8000XWALG9:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=n8013
dalvik.vm.dexopt-data-only=1
ro.sf.lcd_density=160
ro.lcd_min_brightness=20
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130824-UNOFFICIAL-n8013
ro.modversion=10.1-20130824-UNOFFICIAL-n8013
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
Error mounting /data!
W:failed to mount /dev/block/mmcblk0p3 (Invalid argument)
Error mounting /efs!
/tmp #
along with this other info regarding the partitions on my device:
Code:
CWM Errors:
Error mounting /data!
Error mounting /efs!
~ # find /dev/block -path \*/by-name -exec ls -l {} \;
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 13 08:04 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 13 08:04 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 08:04 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 08:04 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 13 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 08:04 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 08:04 USERDATA -> /dev/block/mmcblk0p12
/etc # ls
fstab mtab recovery.fstab
/etc # cat recovery.fstab
# mount point fstype device
/efs ext4 /dev/block/mmcblk0p3
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p12 length=-16384
/preload ext4 /dev/block/mmcblk0p10
/modem emmc /dev/block/mmcblk0p7
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
/etc # cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
~ # ls
cache fstab.smdk4x12 sbin
data init sdcard
default.prop init.rc sys
dev lpm.rc system
efs preload tmp
etc proc ueventd.goldfish.rc
extSdCard res ueventd.rc
external_sd root ueventd.smdk4x12.rc
~ # cat fstab.smdk4x12
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p8 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p12 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:

Thanks for your tips but I guess my internal memory is fried; I tried all the steps above multiple times but once I reboot the device I'm still unable to get past the samsung logo. None of the changes survive a reboot; I can't even install a new recovery partition. The device is out of warranty maybe I should just sell it on ebay for parts or buy a new motherboard. Even though at this point I'm not even sure if it'd be worth it to spend money repairing it versus buying a new tablet. I'm certain about one thing though, I'm not buying any more Samsung devices; this is the second time I face this issue in less than a year - my old Galaxy Nexus phone had the same problem.

tanker32 said:
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:
Click to expand...
Click to collapse
But what you think about nand erase if i have kitkat 4.4.2? and what you think that is there anyway to make that boot image mod work for kitkat? is it impossible?

Well
Vihru said:
But what you think about nand erase if i have kitkat 4.4.2? and what you think that is there anyway to make that boot image mod work for kitkat? is it impossible?
Click to expand...
Click to collapse
There is all about Odin or Kies Samsung Rom update. So nand erase all has been break point! That was problem, not the solution! And yes, even if you have KitKat, your hardware is still the sma N8000. So again, yes, everything must work great! I'm the proof

tanker32 said:
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
Click to expand...
Click to collapse
Hi
I have the same issues as OP (my last_log looks very familiar).
The ODIN part fails because when trying to erase NAND it always tells me it fails....So I was happy you suggest a different method :laugh:
Thing is when i try your repair guide i get to run
Code:
mke2fs /dev/block/mmcblk0p3
and receive
Code:
~ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
after that when trying to mount i get
Code:
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
taking a look at fstab in fact there is no entry:
Code:
cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
after that i tried mounting with
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
but now I get
Code:
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
:crying::crying::crying::crying:
any other suggestions? any help is appreciated....and at least I know i am not the only poor sucker with this kind of problem

tanker32 said:
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:
Click to expand...
Click to collapse
with nand erase all this is the result
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XWALG9_N8000OXXALG7_N8000XXLGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin engine v(ID:3.1005)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Erase...
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

ameer3adel said:
with nand erase all this is the result
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XWALG9_N8000OXXALG7_N8000XXLGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin engine v(ID:3.1005)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Erase...
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Same Situation encountered. Did you get a solution?

Same here. Anyone find a workaround for this?
Aramis4u said:
Same Situation encountered. Did you get a solution?
Click to expand...
Click to collapse

[Q] Recovery can't properly access /data - WTF?

Hi all,
I don't remember when it started, but recently my Photon's recovery has been acting strange when accessing /data partition. I'm now using official TWRP 2.7.0.1, and the recovery "hot reboots" itself when wiping /data, effectively making it unable to restore backups (because to restore the /data partition it has to be wiped first). I tried an older version of CWM (6.0.1.2), and it "wipes" /data in a blink of an eye, which only means it didn't wipe successfully at all.
For reference sake, I can still use my phone normally. I can install apps, restore app backups, or even directly create/delete files in /data partition once I'm booted into Android, so the problem is only limited to recovery. I even tried RSD-ing back to stock and then start all over, but still no dice.
Any ideas would be welcome. If I need to grab any logs, please tell me which and how.

AndyYan said:
Hi all,
I don't remember when it started, but recently my Photon's recovery has been acting strange when accessing /data partition. I'm now using official TWRP 2.7.0.1, and the recovery "hot reboots" itself when wiping /data, effectively making it unable to restore backups (because to restore the /data partition it has to be wiped first). I tried an older version of CWM (6.0.1.2), and it "wipes" /data in a blink of an eye, which only means it didn't wipe successfully at all.
For reference sake, I can still use my phone normally. I can install apps, restore app backups, or even directly create/delete files in /data partition once I'm booted into Android, so the problem is only limited to recovery. I even tried RSD-ing back to stock and then start all over, but still no dice.
Any ideas would be welcome. If I need to grab any logs, please tell me which and how.
Click to expand...
Click to collapse
Recovery logs are stored in /cache/recovery .

kabaldan said:
Recovery logs are stored in /cache/recovery .
Click to expand...
Click to collapse
For TWRP, I thought it was just /tmp/recovery.log...
But either way, can you post a log from recovery after attempting to wipe?

I had something similiar when I wanted to restore a nandroid from my sdcard with TWRP (earlier, about a year ago).
At the end I chose to backup and restore on the internal sd (/data/media) instead of the external sd.
I am not sure if it was the sdcard but this solved my backup problems with TWRP.
Since then I always first backup to internal sd and then copy it to the external one.
I could not read if the problem comes by just wiping /data or while restoring a backup (which should first wipe a backup).

kabaldan said:
Recovery logs are stored in /cache/recovery .
Click to expand...
Click to collapse
Here is the last_log from TWRP 2.7.0.1: http://d-h.st/TKb . These 2 parts grabbed my attention:
Code:
I:Mount: Unable to find partition for path '/data'
and
Code:
I:wipe list '/data;'
I:wipe_path '/data'
Wiping data without wiping /data/media ...
[STRIKE]I:Unable to unlink '/data/bugreports'[/STRIKE]
I:Fixing /data/media/0 contexts
...What's that "/data/bugreports" all about?
And here's the last_log from CWM 6.0.4.8 (I built it via ClockworkMod Builder myself): http://d-h.st/zvK . These:
Code:
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Something even more strange is, although TWRP "hot reboots" / CWM "fast skips" when wiping /data, /data gets wiped anyways.
Loader009 said:
I could not read if the problem comes by just wiping /data or while restoring a backup (which should first wipe a backup).
Click to expand...
Click to collapse
Hmm, my problem can be triggered simply by attempting to wipe /data, so I'm pretty sure this is not relevant to my SD. For verification, I ejected my SD before booting into recovery, and attempted another /data wipe, which still "hot rebooted" my recovery.

AndyYan said:
Hmm, my problem can be triggered simply by attempting to wipe /data, so I'm pretty sure this is not relevant to my SD. For verification, I ejected my SD before booting into recovery, and attempted another /data wipe, which still "hot rebooted" my recovery.
Click to expand...
Click to collapse
Probably I'm talking about another problem.
Sorry, I was not sure and noticed my problem to be on the safe side.

Loader009 said:
Probably I'm talking about another problem.
Sorry, I was not sure and noticed my problem to be on the safe side.
Click to expand...
Click to collapse
I'm not sure if you're familiar with linux at all. But there's a simple fix to this solution. I had the same problem when I was using CM7 with my second OG Droid. But basically you use the following commands. If it's a problem with wiping the /Data clean out, and then rebuilding from a previous backup where the /Data directory is in tact, this is what you do. (WARNING! IF YOU ARE NOT COMFORTABLE ISSUING THESE COMMANDS, THEN DON'T.)
open up cmd prompt
Click to expand...
Click to collapse
navigate to your adb folder where the actual adb.exe file is located. Then make sure your phone is booted into recovery.
adb shell
Click to expand...
Click to collapse
that will put you in a linux environment while your phone is in recovery
ls
Click to expand...
Click to collapse
that will list all directories and files in the root of your phone make sure there is a directory called data. as long as there is, do the following.
rmdir data
Click to expand...
Click to collapse
that will delete the entire current /data structure on your phone. If you don't feel safe doing this, then don't. From there just do the recovery again.
ENJOY!

dslinfreak said:
I'm not sure if you're familiar with linux at all. But there's a simple fix to this solution. I had the same problem when I was using CM7 with my second OG Droid. But basically you use the following commands. If it's a problem with wiping the /Data clean out, and then rebuilding from a previous backup where the /Data directory is in tact, this is what you do. (WARNING! IF YOU ARE NOT COMFORTABLE ISSUING THESE COMMANDS, THEN DON'T.)
navigate to your adb folder where the actual adb.exe file is located. Then make sure your phone is booted into recovery.
that will put you in a linux environment while your phone is in recovery
that will list all directories and files in the root of your phone make sure there is a directory called data. as long as there is, do the following.
that will delete the entire current /data structure on your phone. If you don't feel safe doing this, then don't. From there just do the recovery again.
ENJOY!
Click to expand...
Click to collapse
You really sure this could deal with my issue, since you're replying to HIM instead of ME in MY question post?
EDIT: I actually risked my phone and attempted this - I think I already know ADB commands pretty well - and although /data is totally deleted, after a reboot to recovery, wiping /data still causes "hot reboot".
AND the actions also totally wiped my internal storage (because internal storage is /data/media and deleting /data also deleted it)! Thank god I don't have anything important in there...
Sent from Google Nexus 4 @ CM11

Yes, that's what I was thinking after reading his post.
It is also a little bit different problem than the one discussed here.
In your case AndyYan I simply would flash a stock ROM with RSDLite and then redo the flash recovery and ROM steps.
Because your data is already lost, this might be the fastest way.
But this way we wouldn't figure out what the current problem is. It's your choice since I don't know how fast you need the phone. I don't know if you are able to get a shell (with OpenRecovery you surely are) but what do you get if you enter "mount"? (Search for a line with /data)
With "mount" you'll get plenty of lines so it might be better to do it on the PC with "adb shell mount".
edit: With mount you get only the mounted partitions. I forgot that nothing of that is mounted. Theoretically we should be able to mount the data partition manually and format it with the right filesystem...
But I really don't know what might break, what happens to the media folder and other soft-/hardlinks.

Loader009 said:
flash a stock ROM with RSDLite and then redo the flash recovery and ROM steps.
Because your data is already lost, this might be the fastest way.
But this way we wouldn't figure out what the current problem is. It's your choice since I don't know how fast you need the phone. I don't know if you are able to get a shell (with OpenRecovery you surely are) but what do you get if you enter "mount"? (Search for a line with /data)
With "mount" you'll get plenty of lines so it might be better to do it on the PC with "adb shell mount".
edit: With mount you get only the mounted partitions. I forgot that nothing of that is mounted. Theoretically we should be able to mount the data partition manually and format it with the right filesystem...
But I really don't know what might break, what happens to the media folder and other soft-/hardlinks.
Click to expand...
Click to collapse
As said in the OP, RSD'd already but problem remains. As for mounting problems, I assume I can attempt to manually mount it, but I don't know the right command (Linux n00b).
I don't have any important data on the phone (it's not my primary device, as my signature says), everything's on the SD card, so feel free to throw suggestions/commands at me, as long as it doesn't have the risk of hard-bricking!
Sent from Google Nexus 4 @ CM11

AndyYan said:
You really sure this could deal with my issue, since you're replying to HIM instead of ME in MY question post?
EDIT: I actually risked my phone and attempted this - I think I already know ADB commands pretty well - and although /data is totally deleted, after a reboot to recovery, wiping /data still causes "hot reboot".
AND the actions also totally wiped my internal storage (because internal storage is /data/media and deleting /data also deleted it)! Thank god I don't have anything important in there...
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Edit: Now that /data is gone, do an advanced recovery, don't wipe data, just flash it on. this might avoid the 'hot reboot' issue. i'm about to attempt to replicate this problem on my emulator.

dslinfreak said:
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Click to expand...
Click to collapse
/sdcard is just a symlink to /data/media...

I read the thread from the beginning to be sure what has already been tried.
It looks like the /data partition is corrupted, probably even more, the partition table (which we cannot rewrite afaik).
But I give my best suggestions I have to help.
As you might imagine, I won't be able to solve your problem but I can try to search where the actual problem is.
Please correct me if I am saying something wrong!
The following commands should be entered inside "adb shell" and the output should be posted here:
mount
ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/mmcblk0p39
The first command tells us what has been mounted within the recovery. /data should be there somewhere.
The second command tells us what partitions are available. userdata is the /data partition and should be listed.
The third command is actually a confirmation. If userdata is not in the output of the second command, then this command tells us if the actual partition exists.
In the last case (userdata is not shown in the second command but the partition exists), there might be a naming issue. Theoretically a format of this partition and give it the name "userdata" should solve it.
How? Actually I know on linux the command "mkfs.ext4 /path/to/partition" with which it is possible to format a partition into the ext4 filesystem.
But how do we give it a name? I don't know. Actually this is done in the partition table and not in the partition itself.

arrrghhh said:
/sdcard is just a symlink to /data/media...
Click to expand...
Click to collapse
well, color me purple now. Not a great thing for me and now I look like an absolute retard. I think I'm gonna go back to hs now and retake linux OS.

dslinfreak said:
I appoligize that you did this. i really was just talking to him. as for the fix, was there a stock rom already on the phone? or had you put cm10 or 11 on there? i know for a fact that their internal storage for files, pictures, music, and dowloads are stored in /sdcard on the photon q. i did enough digging on adb for the past week to memorize that file structure.
Edit: Now that /data is gone, do an advanced recovery, don't wipe data, just flash it on. this might avoid the 'hot reboot' issue. i'm about to attempt to replicate this problem on my emulator.
Click to expand...
Click to collapse
It's okay, if there were any important data there I would have backed it up before you say it. And yes, /sdcard simply symlinks to /data/media.
As I described, I can flash ROMs all I want, yet I can't backup or wipe my /data, which is needed for backup ops.
Loader009 said:
I read the thread from the beginning to be sure what has already been tried.
It looks like the /data partition is corrupted, probably even more, the partition table (which we cannot rewrite afaik).
But I give my best suggestions I have to help.
As you might imagine, I won't be able to solve your problem but I can try to search where the actual problem is.
Please correct me if I am saying something wrong!
The following commands should be entered inside "adb shell" and the output should be posted here:
mount
ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/mmcblk0p39
The first command tells us what has been mounted within the recovery. /data should be there somewhere.
The second command tells us what partitions are available. userdata is the /data partition and should be listed.
The third command is actually a confirmation. If userdata is not in the output of the second command, then this command tells us if the actual partition exists.
In the last case (userdata is not shown in the second command but the partition exists), there might be a naming issue. Theoretically a format of this partition and give it the name "userdata" should solve it.
How? Actually I know on linux the command "mkfs.ext4 /path/to/partition" with which it is possible to format a partition into the ext4 filesystem.
But how do we give it a name? I don't know. Actually this is done in the partition table and not in the partition itself.
Click to expand...
Click to collapse
Here's the full output:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
[B]/dev/block/mmcblk0p39 on /data type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)[/B]
/dev/block/mmcblk0p39 on /sdcard type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-05-18 00:52 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-05-18 00:52 abootBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-05-18 00:52 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-05-18 00:52 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2014-05-18 00:52 carriercust -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2014-05-18 00:52 cdrom -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2014-05-18 00:52 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-05-18 00:52 devtree -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-05-18 00:52 dhob -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-05-18 00:52 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-05-18 00:52 hob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-05-18 00:52 kpan -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-05-18 00:52 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-05-18 00:52 mbl -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-05-18 00:52 misc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-05-18 00:52 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-05-18 00:52 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-05-18 00:52 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-05-18 00:52 padA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-05-18 00:52 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-05-18 00:52 pds -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-05-18 00:52 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-05-18 00:52 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-05-18 00:52 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-05-18 00:52 rpmBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-05-18 00:52 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-05-18 00:52 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-05-18 00:52 sbl2Backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-05-18 00:52 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-05-18 00:52 sbl3Backup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-05-18 00:52 sp -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-05-18 00:52 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-05-18 00:52 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2014-05-18 00:52 tombstones -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2014-05-18 00:52 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-05-18 00:52 tzBackup -> /dev/block/mmcblk0p14
[B]lrwxrwxrwx root root 2014-05-18 00:52 userdata -> /dev/block/mmcblk0p39[/B]
lrwxrwxrwx root root 2014-05-18 00:52 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-05-18 00:52 utagsBackup -> /dev/block/mmcblk0p15
~ # ls -al /dev/block/mmcblk0p39
ls -al /dev/block/mmcblk0p39
brw------- root root 259, 7 2014-05-18 00:52 mmcblk0p39
As you can see, /data and userdata both exists.
Furthermore, using TWRP, I can even use its file manager to delete files, modify permissions, etc. in /data, just can't wipe it or back it up (backing up /data usually takes 20+ seconds, but now it's completed in a flash).

For me everything looks ok.
The partition is mounted and the recovery can access the partition.
It should work but it doesn't.
I am kind of clueless.
If I remember correctly, there was in TWRP an option to wipe data/internal storage (or something like that).
Could you try this one? (And post the last_log again.)
I think that it wipes in a blink of an eye because there is nothing to delete.
With the wipe data/internal storage I think it formats the partition instead of doing a "rm -R" (wipe data) on several folders. (I think it is rm -R, I don't actually know it.)
I have problems if I backup data from (external) sdcard. I have to move my backup to the internal storage (not in a recovery!) to successfully restore my backup.
It is annoying, but I haven't found a solution to be 100% sure that the recovery reads the backup correctly from the (external) sdcard.

What about a recovery.log after the failed attempt?

He already has:
AndyYan said:
Here is the last_log from TWRP 2.7.0.1: http://d-h.st/TKb.
[...]
And here's the last_log from CWM 6.0.4.8 (I built it via ClockworkMod Builder myself): http://d-h.st/zvK.
[...]
Something even more strange is, although TWRP "hot reboots" / CWM "fast skips" when wiping /data, /data gets wiped anyways.
Click to expand...
Click to collapse

Loader009 said:
If I remember correctly, there was in TWRP an option to wipe data/internal storage (or something like that).
Could you try this one? (And post the last_log again.)
I think that it wipes in a blink of an eye because there is nothing to delete.
With the wipe data/internal storage I think it formats the partition instead of doing a "rm -R" (wipe data) on several folders. (I think it is rm -R, I don't actually know it.)
I have problems if I backup data from (external) sdcard. I have to move my backup to the internal storage (not in a recovery!) to successfully restore my backup.
It is annoying, but I haven't found a solution to be 100% sure that the recovery reads the backup correctly from the (external) sdcard.
Click to expand...
Click to collapse
I tried the "format data" option like you said, and it seems to go nicely - the log says it recreated filesystem properly - until it "hot reboots" again. Bang it. Log attached: http://d-h.st/chh
I have always been backing up to/restoring from external SD card without any flaws. Now I can't restore my backup, but only because restoring backup involves wiping /data...

Loader009 said:
He already has:
Click to expand...
Click to collapse
I kept looking for recovery.log... haha.
Nothing brilliant is coming to me at the moment, I will ask some people (much) smarter than I...

[Q] Freescale Tablet Problem

Hi,
I have a Zenithink C-94 tablet running ICS on it. I have compiled a JB rom and a KK rom for it, but have not been able to get the tablet to even come on. I contacted Zenithink and requested the kernel source since it is under GPL, but have had no luck. I managed to come up with the proprietaries (ex. cameras, codecs, etc.) and either obtain or write drivers for them. I have compiled the kernel, but this tablet has two kernels. Yes, two kernels; one for the boot.img and one for the "uImage_update". This writes to the vendor partition (mmcblk0p8). The kernel I have compiled is for the boot.img. I am now working on the uImage_update kernel. This one the CPIO is customized big time. See the ICS_CPIO.zip (attached). I am working on the scripts in this to update them to JB /KK. These scripts involve the partitions and recovery.fstab, etc. The partitions have changed from ICS to JB / KK. ICS was like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- MEDIA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DATA
mmcblk0p8 ------- Vender
mmcblk0p9 ------- MISC
JB / KK are like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- DATA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DEVICE (AKA Vender)
mmcblk0p8 ------- MISC
Boot, recovery, system, and cache have not changed. Data which was on mmcblk0p7 is now on mmcblk0p4. Device, which was known as vender, was on mmcblk0p8 is now on mmcblk0p7. Misc which was on mmcblk0p9 is now on mmcblk0p8. ICS had Media and Data separate, now they are together on the same partition. I know to change the partitions in the scripts, but I am having trouble with the recovery.fstab part. ISC is like this:
Code:
/boot emmc /dev/block/mmcblk0p1
/recovery emmc /dev/block/mmcblk0p2
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/data ext4 /dev/block/mmcblk0p7
## /misc emmc /dev/block/mmcblk0p9
# UBI support is under below:
#/system ubifs /dev/ubi1_0
#/data ubifs /dev/ubi1_2
#/cache ubifs /dev/ubi1_1
/sdcard vfat /dev/block/mmcblk0p4
JB / KK are like this:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/devices/platform/sdhci-esdhc-imx.2/mmc_host/mmc1 /mnt/extsd vfat defaults voldmanaged=sdcard:auto
/devices/platform/fsl-ehci /mnt/udisk vfat defaults voldmanaged=sdcard:auto
/dev/block/mmcblk0p5 /system ext4 ro wait
/dev/block/mmcblk0p4 /data ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic wait,encryptable=footer
/dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,nomblk_io_submit wait
/dev/block/mmcblk0p7 /device ext4 ro,nosuid,nodev wait
/dev/block/mmcblk0p1 /boot emmc defaults defaults
/dev/block/mmcblk0p2 /recovery emmc defaults defaults
/dev/block/mmcblk0p8 /misc emmc defaults defaults
In the sbin folder of the CPIO is the "product_tool.sh". It has this line:
Code:
if mount -t vfat /dev/block/mmcblk1p1 /sdcard
How would I rewrite this for JB / KK according to the recovery.fstab? Would this stay the same? Please help.

Elephone P6000 mtk6732 64bit Recovery & SP Flash Tool

Elephone P6000 Recovery​
SPFlashtool Video is now removed due to possible confusion. I will make a new more concise video for making backup's of specific partitions very soon​
Here is a couple of tut's for those who have windows 8.1 64bit problems Drivers etc.
Uninstall any previous attempts to install drivers then reboot the PC do not insert your phone yet!!
Follow these guides step by step.
This first Driver Signature Verification
Then follow this down to step 9 Installing Vcom Drivers windows 8.1
Thanks to the authors of these tuts
Note: If you do not name your readback eg boot.img and leave the ROM_0 the flashtool will just do a complete ROM dump of your entire phone 12.8gb which cannot be processed by droid tools :silly:
PLEASE READ and post in the Q&A Tab which is above my name over < there also hit the THANKS Button bottom Left corner if I helped it costs you no money but cost me many hours
Recommended Viewing
See @rnovino more detailed and excellent general SPFlashTool TuTs with all the mtk drivers links . Thanks to him for these.
Here and Here
Please NO NOOBS asking how to install drivers etc just use google as these questions have been answered a million times over and I really don't have the time to spoon feed everyone :crying: You will probably brick your phone if you don't know what you're doing so read read and read again. :silly:
Recovery​
UPDATE: bigrammy CWM port is now retired. Good news is that @carliv has compiled a CWM Recovery Specifically for the P6000 :victory: Dont be just a Leech and please show him your respect and appreciation by visiting his thread and hitting his THANKS button HERE at the very least.
a bigammy Thanks to all the dev's and testers involved with this project :highfive:
Offcial: Compiled recovery-CWM-Modd-P6000 Download here
HERE
Thanks to @carliv for the recovery module to fix this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All the menu screenshots are HERE They are of the version before the font was fixed. I will update these when I get the time.
Credits To.
@carliv Without whom the Recovery would not have been possible so hit his THANKS button at the very least or better still buy him a coffee Here
@yuweng For his continued support and Advice Thanks bro :highfive:
@rua1 For his awesome DroidTools that saves everyone this headache if their device is lucky enough to be supported Please come back!! :laugh:
There are so many more people that should be mentioned but I would run out of thread so to all who have helped and educated MANY THANKS
It should go without saying all is at your own risk and I take No, None, Zero, Nada, Zip, Responsibility.
SPFlashtool and Recovey are powerful tools and can either revive your phones or kill them forever so you have been warned. !!!!!
Regards bigrammy.
Guys PLEASE!! do not post my links on other websites or forums This is only so that the proper people get the credit and support is available for the user. It is just as easy to post a link to this thread HERE My links are spam free and I earn zero money from them so why do it :silly:
TWRP LOLLIPOP VERSION v2.8.7.0
HERE​
Hit Thanks before you leave.

Recovery
New CWM Recovery is now ported to the p6000.
It's the None Touch Versions and I ported it over from the mt6595 version made by carliv :angel: over Here so full credit goes to him for his Awesome work.
The recovery supports Aroma File Manager also so get over to carliv's thread for the Aroma File Manager zip and hit his THANKS button because without him we would still be stuck with zero support. Link to Aroma FM and all information about how to use it and install Aroma FM is in the thread there so read it please. Again Here
Use google first then ask if not sure.
Post any questions in the Q&A's at the top of this thread.
Here is the recovery Removed see OP
Use the normal ways to install it. adb, spflashtool, If rooted just get the flashify.apk https://play.google.com/store/apps/details?id=com.cgollner.flashify
Thanks and enjoy!!!

TWRP is HERE!!!! YEEEHAAA
Well at long last we have working TOUCH Recovery​
First we must thank all the dev's who have spent many many many Hours and Days trying to fix this problem thats confounded the best of us ​ @carliv @yuweng @codelover @Santhosh M @BachMinuetInG @HypoTurtle
The eventual fix came by way of @NiksSkersts and @yuweng who are working on the P6000 sister/rebranded phone the "Just5 Blaster" Thread Here Please visit and hit his thanks button Also Go HERE and Hit yuweng's Thanks Button for all his work he never gave up trying to fix our problem
All those listed need to be Thanked at the very least EVERYONE!!!
In the end the problem was with the KERNEL or the drivers for the kernel anyway the Just5 Kernel works fine for our recovery needs :good:
I have used a Early carliv TWRP test build for the first release I have had to make quite a lot of changes to the init.rc fstab etc as it was just a test build carliv made to see if the touch could be made to work So go over to @carliv thread and hit his THANKS Button or buy him a coffee because as said none of this would be possible without him :angel:
Quick Note: These are all based on KK so far Android L is still a work in progress
TWRP V2 Now added:
Fixes:
1, Added Custom Partition to Mounts/Backup :good:
Tips:
1. To prevent problems when data_sd and external_sd are mounted to the PC goto TWRP settings/screen and uncheck the sleep function so the screen does not sleep this will ensure a stable connections
2. To view your Internal_SD on device using the TWRP File Manager in Advanced make sure Data is Mounted then got to /data/media/0 you will now see all your internal_sd files so can edit copy etc on device.
3. Performing Backups with TWRPV2 . When you backup large partitions like Data or System PLEASE make sure to only select 1 one partition at a time to backup. You can select multipule small ones like boot, recovery, nvram and they will all backup fine but for some reason System and Data must be done one at a time on their own!!
Please verify any previous backups you have made.
You can double check them by moving the system/data.ext4.win file to your pc then rename it system/data.tar and use winrar to view the files inside. Rename it back to the ext4.win to use with twrp again.
TWRPV2 HERE
More Choice bigrammy I hear you say Well here you go all in one HIT!!
These are all the work of @carliv and have been compiled by him for the P6000 so make sure you thank him PLEASE!!!
I have not had time to test them all to destruction but I am sure they will be fine Enjoy!!
Carliv Touch Recovery V3.0 HERE
PhilzP6000 by Carliv Here
Carliv CWM V2 Touch Kernel Here Same as in the OP but with touch working
TWRP V2 Screenies
Here is the PhilzJust5 made by @yuweng and @NiksSkersts I confirm it works on our phone too but again not fully test by me Philz Recovery Here
TWRP Screenies here HAPPY BACKUPS EVERYONE!! & Dont forget hit the thanks button for all involved and me too

Ok, i m a noob with Mtk devices..but i've experience on modding with other android phone..... proc/partinfo give me the same result on partion size ecc...
but
Only one thing I did not understand,
I have to connect the device without a battery, right?
Connecting the device without battery, despite having installed the drivers Vcom, I see that the device is recognized for 2 seconds then disconnects automatically, then again recognized .. is this normal behavior?
thx for your work :good::good:

enr88 said:
Ok, i m a noob with Mtk devices..but i've experience on modding with other android phone..... proc/partinfo give me the same result on partion size ecc...
but
Only one thing I did not understand,
I have to connect the device without a battery, right?
Connecting the device without battery, despite having installed the drivers Vcom, I see that the device is recognized for 2 seconds then disconnects automatically, then again recognized .. is this normal behavior?
thx for your work :good::good:
Click to expand...
Click to collapse
I Missed your post
In Future please use the Q&A bro just read the OP above.
To answer your question: When the progress bar in flashtool turns red put in your battery quickly I have mine ready and just slightly away from the contacts.
When done it will now hold it on until the end of the read backs.
I will copy this to the Q&A HERE

New ft rom available, r. 8.4 9th january
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=2026#lastpost
bigrammy, i note that backup from cwm creates file size of boot, recovery of about 12Mb , have you tried to restore?
also another issue is that the backup folder is not in external sd, but in internal memory!
Thanks

megthebest said:
New ft rom available, r. 8.4 9th january
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=2026#lastpost
bigrammy, i note that backup from cwm creates file size of boot, recovery of about 12Mb , have you tried to restore?
also another issue is that the backup folder is not in external sd, but in internal memory!
Thanks
Click to expand...
Click to collapse
12MB? sure it's not 16MB (full partition size)...
@bigrammy in int.rc of the Carliv recovery doing this:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard1
export SECONDARY_STORAGE /storage/sdcard0
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0​should switch it so that internal sdcard (/data/media/0) and external sd card switch places so that backup is added to removable card - only downside being it may not boot if there's no sdcard present.

HypoTurtle said:
12MB? sure it's not 16MB (full partition size)...
@bigrammy in int.rc of the Carliv recovery doing this:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard1
export SECONDARY_STORAGE /storage/sdcard0
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0​should switch it so that internal sdcard (/data/media/0) and external sd card switch places so that backup is added to removable card - only downside being it may not boot if there's no sdcard present.
Click to expand...
Click to collapse
My boot.img backup size is 16mb (16,777,216 bytes) to be exact bro so not sure what's happened with yours
Did you use the stock scatter for a backup or flash? maybe double check your partition sizes on the phone /proc/partinfo
As for the storage problem i am working on this right now
I am full of cold so I don't think my brain is working properly :crying:
We have some strange paths for the cards and I am struggling to define them correctly so all works as it should.
In recovery we should be able to view our sdcard when plugged into the PC with the USB cable
I am not 100% sure if we have emulated or none emulated internal sdcard even.
This Elephone ROM is very poor with none existant files :crying: making my job even harder eg: the stock fstab's says the internal sd card is at [email protected] which does not exist
Even the paths are not correctly defined so it's a process of trial and error.
I don't wish to bother @carliv until I am 100% sure I can go no further .
For now the recovery does what it's supposed to do which is backup and flash all though it's to and from the internal sd
I am back at work tomorrow so no further debugging for 4 days from me.
You're more than welcome to have a go at fixing it if you wish just be sure to give carliv the credit :good:

bigrammy said:
This Elephone ROM is very poor with none existant files :crying: making my job even harder eg: the stock fstab's says the internal sd card is at [email protected] which does not exist
Even the paths are not correctly defined so it's a process of trial and error.
Click to expand...
Click to collapse
Ah, thought the fstab was taken from the boot.img, my mistake... Still waiting on mine to arrive (3 weeks and counting), will wait til then before attempting anything. Regarding the fstab it's actually /devices/mtk-msdc.0/11230000.MSDC0 that is claimed to be the internal sdcard, not quite sure how it can be it's own partition though, anyone care to post the outcome of mount and df?
Edit. The internal sdcard is set by the service sdcard in init.ssd_nomuser.rc
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_start​not sure if the fstab lines are an error or are used while in (adv)meta mode or something.

HypoTurtle said:
Ah, thought the fstab was taken from the boot.img, my mistake... Still waiting on mine to arrive (3 weeks and counting), will wait til then before attempting anything. Regarding the fstab it's actually /devices/mtk-msdc.0/11230000.MSDC0 that is claimed to be the internal sdcard, not quite sure how it can be it's own partition though, anyone care to post the outcome of mount and df?
Edit. The internal sdcard is set by the service sdcard in init.ssd_nomuser.rc
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_start​not sure if the fstab lines are an error or are used while in (adv)meta mode or something.
Click to expand...
Click to collapse
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.

bigrammy said:
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.
Click to expand...
Click to collapse
TCL Meme da 3N M2M MT6752
Cofface recovery
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Recovery here

hanuma said:
TCL Meme da 3N M2M MT6752
Cofface recovery
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Recovery here
Click to expand...
Click to collapse
Thanks bro I will check how he has defined things. Is it in english do you know? It maybe easier to port this. :laugh:

bigrammy said:
:laugh: Yeah thats what I thought too
/devices/mtk-msdc.0/11230000.MSDC0 the path seems not to be correct according to what I have on the phone itself which is /sys/devices/mtk-msdc.0/11230000.MSDC0/
and for the other card is /sys/devices/mtk-msdc.0/11240000.MSDC1/ ?/??? maybe we need to drill down further as I see in some of carliv examples it goes to /mmc_host/mmc0 1 for MSDC1
I have drilled all the way down and can confirm on 11230000.MSDC0 = Type = MMC and for 11240000.MSDC1 = Type = SD so I guess these are the correct ones
Your Thoughts Welcome.
Click to expand...
Click to collapse
My thinking is that perhaps the /devices/mtk-msdc.0/11230000.MSDC0 is for use with META mode as it points to a device rather than a partition, i.e. the whole NAND memory. Not 100% about that... it doesn't make much sense that META mode is controlled by boot.img but that seems to be the case (~ half the .rc's are for meta mode (factory and meta ones)), which would mean that a bad boot.img flash (and recovery.img), would result in a true brick - there isn't a mask mode/drivers for
MTK afaik.

HypoTurtle said:
My thinking is that perhaps the /devices/mtk-msdc.0/11230000.MSDC0 is for use with META mode as it points to a device rather than a partition, i.e. the whole NAND memory. Not 100% about that... it doesn't make much sense that META mode is controlled by boot.img but that seems to be the case (~ half the .rc's are for meta mode (factory and meta ones)), which would mean that a bad boot.img flash (and recovery.img), would result in a true brick - there isn't a mask mode/drivers for
MTK afaik.
Click to expand...
Click to collapse
@hanuma
The cofface recovery is a e3 recovery and yes it seems that a lot of meta stuff is in there too.
The meta stuff is probably to accommodate OTA updates maybe (Just a guess )
I think we should be able to define things how we want.......
cofface has this for one of the volds.
Code:
/devices/platform/mt_usb auto auto defaults voldmanaged=usbdisk:auto
Here are the full readouts. mount, df, etc for your info.
Code:
[email protected]_e:/ # mount
mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered
0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0
0
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,comm
it=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,comm
it=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/customimg /custom ext4 rw,seclabel,relatime,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:129 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=00
07,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,al
low_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]_e:/ #
[email protected]_e:/ # ls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
brw-rw---- root system 179, 0 2015-01-26 17:24 mmcblk0
brw-rw---- root system 179, 32 2015-01-26 17:24 mmcblk0boot0
brw------- root root 179, 64 2015-01-26 17:24 mmcblk0boot1
brw-rw---- root system 179, 1 2015-01-26 17:24 mmcblk0p1
brw-rw---- root system 179, 10 2015-01-26 17:24 mmcblk0p10
brw-rw---- root system 179, 11 2015-01-26 17:24 mmcblk0p11
brw------- root root 179, 12 2015-01-26 17:24 mmcblk0p12
brw------- root root 179, 13 2015-01-26 17:24 mmcblk0p13
brw------- root root 179, 14 2015-01-26 17:24 mmcblk0p14
brw------- root root 179, 15 2015-01-26 17:24 mmcblk0p15
brw------- root root 179, 16 2015-01-26 17:24 mmcblk0p16
brw------- root root 179, 17 2015-01-26 17:24 mmcblk0p17
brw------- root root 179, 18 2015-01-26 17:24 mmcblk0p18
brw------- root root 179, 19 2015-01-26 17:24 mmcblk0p19
brw-rw---- root system 179, 2 2015-01-26 17:24 mmcblk0p2
brw------- root root 179, 20 2015-01-26 17:24 mmcblk0p20
brw------- root root 179, 3 2015-01-26 17:24 mmcblk0p3
brw------- root root 179, 4 2015-01-26 17:24 mmcblk0p4
brw-rw---- root system 179, 5 2015-01-26 17:24 mmcblk0p5
brw------- root root 179, 6 2015-01-26 17:24 mmcblk0p6
brw-r----- root system 179, 7 2015-01-26 17:24 mmcblk0p7
brw-rw---- root system 179, 8 2015-01-26 17:24 mmcblk0p8
brw-r----- root system 179, 9 2015-01-26 17:24 mmcblk0p9
brw------- root root 179, 96 2015-01-26 17:24 mmcblk0rpmb
brw------- root root 179, 128 2015-01-26 17:24 mmcblk1
brw------- root root 179, 129 2015-01-26 17:24 mmcblk1p1
brw------- root root 179, 130 2015-01-26 17:24 mmcblk1p2
[email protected]_e:/ #
[email protected]_e:/ # df
df
Filesystem Size Used Free Blksize
/dev 958.1M 128.0K 958.0M 4096
/sys/fs/cgroup 958.1M 12.0K 958.1M 4096
/mnt/secure 958.1M 0.0K 958.1M 4096
/mnt/asec 958.1M 0.0K 958.1M 4096
/mnt/obb 958.1M 0.0K 958.1M 4096
/system 1.2G 951.9M 318.9M 4096
/data 12.5G 1.8G 10.7G 4096
/cache 105.3M 712.0K 104.6M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 116.0K 4.7M 4096
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/custom 290.6M 45.5M 245.1M 4096
/storage/sdcard1 12.5G 1.8G 10.6G 4096
/mnt/media_rw/sdcard0 25.0G 4.2G 20.8G 32768
/mnt/secure/asec 25.0G 4.2G 20.8G 32768
/storage/sdcard0 25.0G 4.2G 20.8G 32768
[email protected]_e:/ #
[email protected]_e:/ # ls -al /dev/block/platform/mtk-msdc.0/by-name
ls -al /dev/block/platform/mtk-msdc.0/by-name
lrwxrwxrwx root root 2010-01-01 08:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2010-01-01 08:03 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2010-01-01 08:03 custom -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2010-01-01 08:03 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2010-01-01 08:03 flashinfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2010-01-01 08:03 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2010-01-01 08:03 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2010-01-01 08:03 metadata -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2010-01-01 08:03 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2010-01-01 08:03 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2010-01-01 08:03 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2010-01-01 08:03 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2010-01-01 08:03 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2010-01-01 08:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2010-01-01 08:03 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2010-01-01 08:03 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2010-01-01 08:03 system -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2010-01-01 08:03 tee1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2010-01-01 08:03 tee2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2010-01-01 08:03 userdata -> /dev/block/mmcblk0p19
Things to do:
1. Make external_sd = mmcblk1p1 = sdcard0 default for the backups.
2. add sd_ext = mmcblk1p2 to backup options
3. Get sdcard1 defined as internal_sd
4. Mount Both if possible to upon connection to PC . (If only one then external_sd is preferred by me) Thoughts welcome on this.
5. I really need sleep !!!! lol

bigrammy said:
@hanuma
The cofface recovery is a e3 recovery and yes it seems that a lot of meta stuff is in there too.
The meta stuff is probably to accommodate OTA updates maybe (Just a guess )
Things to do:
1. Make external_sd = mmcblk1p1 = sdcard0 default for the backups.
2. add sd_ext = mmcblk1p2 to backup options
3. Get sdcard1 defined as internal_sd
4. Mount Both if possible to upon connection to PC . (If only one then external_sd is preferred by me) Thoughts welcome on this.
5. I really need sleep !!!! lol
Click to expand...
Click to collapse
Could be for FOTA I suppose... tried to look though /system/bin/fotabinder; but couldn't see much other than a reboot call.
/devices/platform/mt_usb is a usb device I believe (usb drive attached to microusb).
So for reference.
From boot.img
External SDcard
/dev/block/vold/179:129 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=00
/mnt/media_rw/sdcard0 25.0G 4.2G 20.8G 32768
/storage/sdcard0 25.0G 4.2G 20.8G 32768
Internal SDcard (data/media)
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data 12.5G 1.8G 10.7G 4096
/storage/sdcard1 12.5G 1.8G 10.6G 4096
These are set in ramdisk.
fstab (unsure if used for normal boot - but might be used by vold)
Code:
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
Bits and pieces from .rc's
Code:
on post-fs-data
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0770 media_rw media_rw
chown media_rw media_rw /data/media
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib:/custom/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-tablet.jar:/system/framework/dolby_ds.jar
export BOOTCLASSPATH_EX /system/framework/mediatek-op.jar
mkdir /mnt/media_rw/sdcard0 0700 media_rw media_rw
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard0 0700 root root
mkdir /storage/sdcard1 0700 root root
export EXTERNAL_STORAGE /storage/sdcard0
# Support legacy paths
symlink /storage/sdcard0 /sdcard
symlink /storage/sdcard0 /mnt/sdcard
symlink /storage/sdcard1 /mnt/sdcard2
on fs
mount_all /fstab
setprop ro.crypto.fuse_sdcard true
service sdcard /system/bin/sdcard -u 1023 -g 1023 -d /data/media /storage/sdcard0
class late_start
service fuse_sdcard0 /system/bin/sdcard -u 1023 -g 1023 -d /mnt/media_rw/sdcard0 /storage/sdcard0 <<<
class late_start <<<
disabled <<<
<<< These two are disabled
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1 <<<
class late_start <<<
disabled <<<
on boot
chown root /remount.sh <<<
chmod 700 /remount.sh <<< Not sure why this is here
exec /remount.sh <<<
service met_log_d /system/bin/met_log_d
class main
# Refer to http://source.android.com/devices/tech/storage/index.html
# It said, "Starting in Android 4.4, multiple external storage devices are surfaced to developers through
# Context.getExternalFilesDirs(), Context.getExternalCacheDirs(), and Context.getObbDirs().
# External storage devices surfaced through these APIs must be a semi-permanent part of the device (such as an SD card slot in a battery compartment).
# Developers expect data stored in these locations to be available over long periods of time."
# Therefore, if the target has the SD card slot in a battery compartment, we need to specify SECONDARY_STORAGE (*** UN-Comment the following command ***)
#
# export SECONDARY_STORAGE /storage/sdcard1
From recovery.img
init.rc
Code:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard1 0700 root root
symlink /storage/sdcard1 /mnt/sdcard2
on boot
service vold /sbin/minivold
socket vold stream 0660 root mount
ioprio be 2
seclabel u:r:recovery:s0
# virtual sdcard daemon running as media_rw (1023)
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled
fstab (line probably not used by recovery)
Code:
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto

Well, I came here by chance and saw you've ported a recovery
Good to see this. Bad that those guys from taiwan101 or so, didn't keep my credential in recovery.
I helped SevenMaxs to solve mounting both sdcards in his device (a mt6752) and that one has same sdcard paths. So if you replace this:
Code:
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
with this:
Code:
/devices/mtk-msdc.0/11240000.MSDC1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
in fstab and recovery.fstab it will work (both sdcards not only the internal).
No change in init.rc. I mean on this (which is my solution for mt6595 taken by those guys):
Code:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /storage/sdcard0
export SECONDARY_STORAGE /storage/sdcard1
symlink /system/etc /etc
symlink /data/media/0 /storage/sdcard0
mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
mkdir /storage/sdcard1 0700 root root
symlink /storage/sdcard1 /mnt/sdcard2
on boot
service vold /sbin/minivold
socket vold stream 0660 root mount
ioprio be 2
seclabel u:r:recovery:s0
# virtual sdcard daemon running as media_rw (1023)
service fuse_sdcard1 /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1
class late_start
disabled
And you should know that you can't switch sdcard0 with sdcard1 (internal with external) in CWM if internal is emulated. As you saw it doesn't have to be defined on fstab at all (if you define it as in stock recovery it won't work), and by default CWM will asign it to sdcard0, and you can't change that. If you want to place backups in external sdcard, just select "backup to /storage/sdcard1" from menu. I guess you are too much used with the "old" cwm, jellybean version with sftab1 Well things are changed now for kitkat using fstab2, and to be honest I don't understand why they did it. Twrp still uses fstab1 and is doing just fine
Later edit: Guys you can't relay on stock recovery or other one based on stock. The CWM works different (no fstab or init.rc from stock recovery will help you). One other thing you should know, if you define the usbdisk or otg or whatever its name is in CWM fstabs, you will loose the USB Mass Storage mounting to PC function, because CWM only allow one USB connection. All these are already explained by me in my thread for porting recoveries, and more exactly in the new guide composed of only with pictures.

carliv said:
Well, I came here by chance and saw you've ported a recovery
in fstab and recovery.fstab it will work (both sdcards not only the internal).
No change in init.rc. I mean on this (which is my solution for mt6595 taken by those guys):
And you should know that you can't switch sdcard0 with sdcard1 (internal with external) in CWM if internal is emulated. As you saw it doesn't have to be defined on fstab at all (if you define it as in stock recovery it won't work), and by default CWM will asign it to sdcard0, and you can't change that. If you want to place backups in external sdcard, just select "backup to /storage/sdcard1" from menu. I guess you are too much used with the "old" cwm, jellybean version with sftab1 Well things are changed now for kitkat using fstab2, and to be honest I don't understand why they did it. Twrp still uses fstab1 and is doing just fine
Later edit: Guys you can't relay on stock recovery or other one based on stock. The CWM works different (no fstab or init.rc from stock recovery will help you). One other thing you should know, if you define the usbdisk or otg or whatever its name is in CWM fstabs, you will loose the USB Mass Storage mounting to PC function, because CWM only allow one USB connection. All these are already explained by me in my thread for porting recoveries, and more exactly in the new guide composed of only with pictures.
Click to expand...
Click to collapse
Thanks for that @carliv ... still waiting for my device to run this recovery was wasn't sure what version CWM it was.
I'm guessing minivold is why you can't simply switch SECONDARY_STORAGE with EXTERNAL_STORAGE... It is a moot point though if as you say "backup to /storage/sdcard1" is there as an option.
Edit. @carliv is the symlink /storage/sdcard1 /mnt/sdcard2 bit right? Or should it be /mnt/sdcard1 ?

HypoTurtle said:
Thanks for that @carliv ... still waiting for my device to run this recovery was wasn't sure what version CWM it was.
I'm guessing minivold is why you can't simply switch SECONDARY_STORAGE with EXTERNAL_STORAGE... It is a moot point though if as you say "backup to /storage/sdcard1" is there as an option.
Edit. @carliv is the symlink /storage/sdcard1 /mnt/sdcard2 bit right? Or should it be /mnt/sdcard1 ?
Click to expand...
Click to collapse
First CWM will check for sdcard0 on fstab to see if matches any defined voldmanaged entry and if it's not it will assume is a data/media sdcard and assign it sdcard (aka storage/sdcard0) path. To change that you need to build the recovery and to do that in source code. I guess all this fuss was started by google when they designed kitkat for their devices without external sdcard.
Yes, /mn/sdcard2 is right for /storage/sdcard1 because /mnt/sdcard (<<<no 0 here) is for /storage/sdcard0 - at least that's in all the phones I saw, but maybe yours is different. If you open the mnt folder with a root explorer do you see any sdcard1 there? That will be a first for me to hear such thing.

carliv said:
First CWM will check for sdcard0 on fstab to see if matches any defined voldmanaged entry and if it's not it will assume is a data/media sdcard and assign it sdcard (aka storage/sdcard0) path. To change that you need to build the recovery and to do that in source code. I guess all this fuss was started by google when they designed kitkat for their devices without external sdcard.
Yes, /mn/sdcard2 is right for /storage/sdcard1 because /mnt/sdcard (<<<no 0 here) is for /storage/sdcard0 - at least that's in all the phones I saw, but maybe yours is different. If you open the mnt folder with a root explorer do you see any sdcard1 there? That will be a first for me to hear such thing.
Click to expand...
Click to collapse
Would I be right in thinking then that the backup location is hardcoded in the recovery to something like /storage/sdcard0? I was thinking that it might have been backup => $EXTERNAL_STORAGE (if that's even possible) so that a simple switch external/secondary in init.rc would point the backup to /storage/sdcard1 instead, it's been a while since I've compiled anything, might poke through the code though.

HypoTurtle said:
Would I be right in thinking then that the backup location is hardcoded in the recovery to something like /storage/sdcard0? I was thinking that it might have been backup => $EXTERNAL_STORAGE (if that's even possible) so that a simple switch external/secondary in init.rc would point the backup to /storage/sdcard1 instead, it's been a while since I've compiled anything, might poke through the code though.
Click to expand...
Click to collapse
This is only for phones with internal sdcard on data/media. If you have a phone with internal sdcard as a "fat" partition (as I do) you can switch them as much as you like, but not from EXTERNAL and SECONDARY storage; it has to be done in fstabs switching voldmanaged:sdcard0 to external and sdcard1 to internal. In kitkat cwm those defines EXTERNAL and SECONDARY STORAGE can be removed and the recovery will work, or you can let only EXTERNAL to sdcard as in CWM official init.rc. The reason I added those modifications, including mnt/sdcards and other from init.rc was for USB Mass Storage mount to PC. Stock CWM init.rc will work with right fstabs but on connecting to PC it will mount only the external sdcard; my modds make it possible to mount both sdcards.