Database Info

[Q] HELP NEEDED galaxy s2 (i9100g),cannot mount emmc

when i try to install a rom with cwm,installation is aborted , and when i go to mount and storage menu,and try to mount emmc storage then it says :error cant mount emmc,the log file of error during flashing a rom was :
Starting recovery on Sat Apr 21 16:28:46 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.3
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p5 (null)
2 /recovery emmc /dev/block/mmcblk0p6 (null)
3 /efs ext4 /dev/block/mmcblk0p1 (null)
4 /cache ext4 /dev/block/mmcblk0p7 (null)
5 /system ext4 /dev/block/mmcblk0p9 (null)
6 /data ext4 /dev/block/mmcblk0p10 (null)
7 /sdcard vfat /dev/block/mmcblk0p11 (null)
8 /emmc vfat /dev/block/mmcblk1p1 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0NAL_DEFAULT_PROPERTIES
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=cff1930417fc1ae
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=t1
ro.revision=7
ro.emmc=0
dpm.allowpolicy=1
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.build.id=GINGERBREAD
ro.build.display.id=juffo.v2.DZKJ2
ro.build.version.incremental=DZKJ2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Fri Oct 21 19:47:33 KST 2011
ro.build.date.utc=1319194053
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-30
ro.build.tags=release-keys
ro.product.model=GT-I9100G
ro.product.brand=samsung
ro.product.name=GT-I9100G
ro.product.device=GT-I9100G
ro.product.board=omap4sdp
ro.product.cpu.abi=armeabi-v7a
ro.build.PDA=I9100GDZKJ2
ro.build.hidden_ver=I9100GDZKJ2
ro.build.changelist=679669
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=GT-I9100G
ro.build.description=GT-I9100G-user 2.3.6 GINGERBREAD DZKJ2 release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:2.3.6/GINGERBREAD/DZKJ2:user/release-keys
ro.tether.denied=false
ro.flash.resolution=1080
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=250
dalvik.vm.heapsize=64m
persist.service.usb.setting=0
com.ti.omap_enhancement=true
media.camerahal.test-esd1=false
media.camerahal.test-esd2=false
media.overlay.cloneStatic=false
media.overlay.cloneDynamic=false
persist.sys.HDMICableConnected=no
persist.sys.GfxRotation=0
opencore.asmd=1
wifi.interface=tiwlan0
debug.video.rotateoverlay=0
omap.audio.mic.main=AMic0
omap.audio.mic.sub=AMic1
omap.audio.power=PingPong
ro.com.google.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=false
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tv.hdmi.uicloning.enable=true
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.pvrsrvinit=stopped
init.svc.geomagneticd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
Script Asserts: Enabled
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
-- Installing: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
also i had wiped cache partition by mistake , i am new to xda and flashing roms,so i am a bit inexperienced any help would appreciated

Format emmc from inside cwm. Copy roms u wish to install to external SD card and install from there. Never install from internal memory

Emmc
Ok will try and reply thanks for help though

not able to install?!!
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing

same problem !!!
I am having the same problem i cant flash a rom and stuck with incompatable ics theme help plzz anyone

Dragon Hunter @666 said:
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing
Click to expand...
Click to collapse
this is the solution for your device: http://forum.xda-developers.com/gal...-pit-files-creating-larger-partition-t2552738

Tf700 blocked in 4.4.20

Hi guys,
i'm french, so sorry for my english!
I will try to explain what big problem i have with my tf700,
I was root with Bootloader LOCKED, and when i received last OTA update (4.4.23) I had a droid green belly open with an exclamation point above!
This is what i've got with the last_log:
Starting recovery on Mon Dec 10 19:22:26 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.fw.camera.status=1
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
persist.sys.Nvidia.didim=0
persist.sys.timezone=Europe/Brussels
persist.sys.NV_STEREOAPP=0
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/app/Browser.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
and next i would try to downgrade in ICS maj and again I had a droid green belly open with an exclamation point above!
I am helpless!
Just give me some help please! :/

BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
Click to expand...
Click to collapse
Did you somehow modify your Browser.apk?

_that said:
Did you somehow modify your Browser.apk?
Click to expand...
Click to collapse
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?

BinaryLover said:
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?
Click to expand...
Click to collapse
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.

_that said:
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.
Click to expand...
Click to collapse
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/

BinaryLover said:
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/
Click to expand...
Click to collapse
If you have some Linux knowledge, you can do the following:
- download the full 10.4.4.20 firmware from the firmware thread
- unzip twice
- get blobtools from https://github.com/AndroidRoot/BlobTools and compile
- run blobunpack on the blob
- mount -o loop blob.APP /mnt/some/dir
- copy whatever you need from the mounted directory.
If you only need Browser.apk, download this and unzip:
View attachment Browser.zip

Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/

BinaryLover said:
Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/
Click to expand...
Click to collapse
You cannot install this apk (it's a system app and also missing the odex file), you need to replace the existing file. To do that, become root and remount the system partition writable - either with your preferred root file manager, or with the command "mount -o remount,rw /system".

Thnak you i success to remplace apk
and now when i try to downgrade, bug... with droid again
last_log:
Starting recovery on Fri Dec 28 18:42:59 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Boot command: launcher-boot-recovery
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Finding update package...
I:Update location: /sdcard/ASUS_BUNDLE.zip
Opening update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installation aborted.
I:result_code: 80000002
Check and format /storage to vfat if needed...
Done.

BinaryLover said:
and now when i try to downgrade, bug... with droid again
Click to expand...
Click to collapse
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
BinaryLover said:
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
Click to expand...
Click to collapse
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?

_that said:
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?
Click to expand...
Click to collapse
i want to be in 10.4.4.23 root.
ok now i tryed to upgrade with dlpkgfile to 4.4.23 and.. droid belly open with an exclamation point above!
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/lib/libwebrtc_audio_preprocessing.so" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
Yes it's not the Browser.apk who make bug! we move forward!!

BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
Click to expand...
Click to collapse
OK. You know the drill ... replace your file with the one in the attached zip: View attachment libwebrtc_audio_preprocessing.zip
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.

_that said:
OK. You know the drill ... replace your file with the one in the attached zip: View attachment 1598826
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.
Click to expand...
Click to collapse
Ho God you are the best!!!
It's work!!! I'm in 4.4.23!! Thank you very much!!
I ask myself the question why were corrupted apk!But now it's work!!!
Bravo tu m'as bien aidé pour mon problème!, je te remercie!

[Q] Status 7 Error Pacman Rom

Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me

thekool11 said:
Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
Click to expand...
Click to collapse
Have you checked md5sum?

glevitan said:
Have you checked md5sum?
Click to expand...
Click to collapse
Did you really need to quote all of that just to say that?
Sent from a dream.

I believe you're trying to flash a Saga ROM.

bananagranola said:
I believe you're trying to flash a Saga ROM.
Click to expand...
Click to collapse
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded

thekool11 said:
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
Click to expand...
Click to collapse
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?

A ROM for a different device: the Desire S, codenamed Saga. We are the forum for the Desire HD/Inspire 4G, codenamed Ace.

williamrazmy said:
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
Click to expand...
Click to collapse
here is a noob fiendly way to solve it
http://forum.xda-developers.com/showthread.php?t=2302599

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] How to fix My Devices Stuck At animation Boot Alcatel One Touch 4011x

Devices One Touch 4011x MT6575
Flashing CMW V5.5.0.4 and do nandroid backup for safety....im wrong edit some word in build.prop ,restart devices then got stuck at animations boots,im trying restore but still stuck at animations boots..btw the backup has work before..how to fix this problem in cmw?btw my devices still can go cwm..
PHP:
Starting recovery on Sun Jan 1 01:24:30 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (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!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

hello someone please help

techpowering said:
hello someone please help
Click to expand...
Click to collapse
you can't go to cwm?

thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help

techpowering said:
thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help
Click to expand...
Click to collapse
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings

FSadino said:
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings
Click to expand...
Click to collapse
Thank for Reply i have a question can we replace the original file build.prop in update.zip?because my devices has damage usb port ( some small damage on board i/c ) so my devices cant be detected anymore at computer..it because im plug charger usb on car.. btw i was doing factory reset,clean cache,davlik,restore ,clean again now reboot and wait..i will update how it work...uuh i hope build.prop can replace with zip file

seems not work how to replace build.prop zip file?

i believe there is not much you can do without usb connection. you have to get your usb working again before you can fix the phone.
Sent from my ONE TOUCH 4011X using XDA Free mobile app

techpowering said:
seems not work how to replace build.prop zip file?
Click to expand...
Click to collapse
I agree with @HadpeH, without USB we can not do anything. First fix this problem then it will be easier to help you

im request the stock build.prop for devices One Touch 4011x ( alcatel )..my usb devices cannot repair because the small i/c board has broken

you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app

hey
HadpeH said:
you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app
Click to expand...
Click to collapse
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m

moonbutt74 said:
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m
Click to expand...
Click to collapse
Thank you i will try as soon...and will update how works

Bump! already replace with new build.prop using Aroma file manager...and set to rw-r--r-- still not work..stuck at animation boots..tried nandroid restore..and reboot still stuck on animations boots what the problem of this? can someone help read this log what cause problem on my devices
HTML:
Starting recovery on Sun Jan 1 01:00:47 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (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!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

bump for help