Related
Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.
I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...
Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.
If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck
My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...
Thanks for your time. I appreciate it.
bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...
it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.
I face this problem too. Please someone give us the solution.
Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.
More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.
strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/
Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0
Hello guys,
I recently installed CWM on my GoClever device.
Booting into recovery from Android using ROM Manager didn't work, so I tried
Code:
su "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
And I booted in CWM right after it rebooted
but when I tried to boot the device back to Android, it booted to CWM.
Also the CWM is unable to mount any of the directories.
Code:
CWM-based Recovery v6.0.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /open/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
ADB should work I guess
Could anyone help me please? I guess it's not hard to fix this, probably some file modifying, but I don't really know what exactly to do... :/
EDIT: A recovery image that boots into Android instead of recovery would be a neat solution, but I'm not sure if it's possible
LAST EDIT [SOLVED] :
hajdulak said:
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
-> [SOLVED] pretty please
Click to expand...
Click to collapse
Well, i guess A13's will never get some solid support... At least I got my 10 posts... Weeee!
Guys, what's with all the views and no answers?
After some googling, I found out it's quite a frequent issue, but none of the googled threads helped in any way... Damn it...
Also, A13 devices have SOOOOO low support...
And an important thing
I got a dumped stock recovery img on the /sdcard/, just need to know if I can flash it and how to flash it using ADB, I'm quite afraid of doing anything now
Soooo...
When the device is plugged in, it identifies itself as "MID08"
Seems i installed a wrong recovery image
Now I need drivers for my TAB, as it can't appear in the
Code:
adb devices
menu... :/
If anyone can really help, this is a list of my blockdevices:
Code:
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 nandf ram0 ram1
And this is my fstab
Code:
/dev/block/nandh /cache ext4 rw
/dev/block/nande /data ext4 rw
/dev/block/nandi /emmc auto rw
/dev/block/nandd /system ext4 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
And this is recovery.fstab
Code:
# mount point fstype device
/boot emmc /dev/block/nandc
/cache ext4 /dev/block/nandh
/data ext4 /dev/block/nande
/emmc auto /dev/block/nandi /dev/block/nandi1
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/nandd
/recovery emmc /dev/block/nandg
Also when I try to cd to some dirs i get can't cd to XXX
I guess there's some script that does the mounting stuff, but I still don't know what it is... I just need to access my sdcard and get the recovery image outta there...
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
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
but, in /etc/ there has two files i think are in conflict:
the first is fstab:
Code:
/dev/block/mtd/by-name/cache /cache ext4 rw
/dev/block/mtd/by-name/userdata /data ext4 rw
/dev/block/mtd/by-name/system /system ext4 rw
/dev/block/mtd/by-name/user /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
/dev/block/mmcblk0p1 /external_sd vfat rw
second is recovery.fstab:
Code:
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
so, if there is 2 files that would to mount the paths, one of them are blocking other.
i say this cause i think "recovery.fstab" is the correct to mount in recovery mode.
but in this recovery mode isn't! /etc/fstab is mounting!
see like this.
i am in CWM and there a log in bottom with:
Code:
CWM-based Recovery modified by androtab.info v6.0.3.1
E:Can't find misc
E:Can't mount /cache/recovery/command
E:Can't find misc
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
and when i go to install zip from sdcard>choose zip from sdcard(internal storage, not is the removable sdcard):
E:Can't mount /sdcard/
but external sdcard (removable) it mount and open!
and when i go to mount /sdcard, or /cache, /data, /sd-ext, /system, it says: Error mounting /cache!, Error mounting /data!...
i don't know what can i do, cause, even sdcard can mount, /system cannot, and install a custom ROM cannot be done, even not backup the actual rom!
to finish, i say that i think is a conflict cause in ADB i go to mount /mnt (that is the path of sdcard, external_sd (...)) and it return:
mount: can't find /mnt in /etc/fstab
but if i am in recovery mode i would be in /etc/recovery.fstab
can someone help me?
my device is a DL 3003 (RK30x) is a brazilian product. and sorry for my bad english!
Hi to all, I hope to be posting in the right section...otherwise...punish me plz
It's a long story, so i hope that someone has time and want to put some effort to help me understand what i'm doing wrong.
By the way i work in IT field and have some knowledge about linux (let's say 5 on 10) but not so many on how android really works, but i'm confortable with custom recovery and roms, i'm still using an s4 mini (GT-I9195) with mine android 9 custom rom and i'm super happy with it.
Now that presentation are done , here is the matter.
I've found an old zp980 32GB (NOT the "plus one") that some years ago i've rooted it flashed with recovery and custom rom. all was working, but at some point i started playing with fdisk and parted and i messed up things.
Honestly i don't remember what exactly i was doing, but now the status of the phone is:
System not booting
I can enter into Recovery (custom TWRP by dezmen3 v2.4.4.0)
I can connect to adb into recovery
I cannot flash rom trough recovery due the actual system partition (589 MB)
I cannot flash the original rom trough SP flash tool due "SFT enable dram failed (4032)" error
The partitions actually are (what i can see from recovery):
System (589 MB)
Data (54MB)
Boot (6 MB)
Recovery (6MB)
Cache (4 MB)
uboot(0 MB)
nvram (5 MB)
Free space: 27412 MB
Actually, I've tried to reformat the memory using SP flah tool, but i got the same error "SFT enable dram failed (4032)", all drivers are ok, i can see COM port in deivce manager tried win 10 and even win 7.
SP tool ver. used v5 1720 more updated version tells me that the brick i'm tringo to flash in not supported anymore xD
Here a dump of fdisk -ul /dev/block/mmcblk0 from adb shell
Bash:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 4869120 1022 2145049599+ 83 Linux
if i make a print from parted (pushed with adb) I get:
Error: Can't have a partition outside the disk!
Before i was also having an error saying that there was an extended partition into a logical one (don't ask me how I do it), but i removed it
So, now....what to to to rescue this device?
by the way honestly except for the instinct of "recover things that doesn't work" my main purpose is understand:
What I've messed on the partitions
Why sp flash tool can't reformat/flash the memory (i haven't tried to manually modify it again)
no brave person hat want to help me to brick it in a bad way?
EDIT NEW INFO
i've understtod that the problem was caused by
/dev/block/mmcblk0p1
and
/dev/block/mmcblk0p6
start and end were inverted , them were overflowing.
Now i used fdisk to remove part 1 (the extended), so i've lost also 5 and 6 (system and cache) and i have recreated them using 1 GB for each and using correct sector order.
now SD and try to flash a ....random compatible rom....see u later for info.
Cross your finger for me xD
flash failed it cant mount system and emmc.....
and now
~ # cat /etc/fstab
/cache ext4 rw
/data ext4 rw
/emmc vfat rw
/system ext4 rw
/sdcard vfat rw
/sd-ext auto rw
if someone has a zp980/c2 working can please post me the result of
cat /etc/fstab
from adb shell??
and a fdisk -ul?