Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,771,526 Members 49,990 Now Online
XDA Developers Android and Mobile Development Forum

Hard Brick, Stuck on Boot logo!!!!

Tip us?
 
AlexFG
Old
#1  
AlexFG's Avatar
Senior Member - OP
Thanks Meter 18
Posts: 116
Join Date: Apr 2009
Location: Miami, FL
Tablet 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.
 
AlexFG
Old
#2  
AlexFG's Avatar
Senior Member - OP
Thanks Meter 18
Posts: 116
Join Date: Apr 2009
Location: Miami, FL
Any ideas? Anyone????
 
tanker32
Old
(Last edited by tanker32; 12th April 2014 at 05:24 AM.) Reason: typos
#3  
tanker32's Avatar
Member
Thanks Meter 25
Posts: 58
Join Date: Jul 2013
Location: Frydek-Mistek

 
DONATE TO ME
Lightbulb Seems like a EFS problem.

Quote:
Originally Posted by AlexFG View Post
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.
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/show....php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/show....php?t=2682004

Everything is about EFS problem or corrupted NAND partition.

I hope your device will be fine!
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


Peter "The Bestguy" Tanker
The Following User Says Thank You to tanker32 For This Useful Post: [ Click to Expand ]
 
AlexFG
Old
#4  
AlexFG's Avatar
Senior Member - OP
Thanks Meter 18
Posts: 116
Join Date: Apr 2009
Location: Miami, FL
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.
Tags
bad partition table, cwm, hard brick, omni rom, recovery
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes