Unable to install chainfire drivers on Calks Rom 2.8, 2.81

Unable to install chainfire drivers on Calks Rom 2.8, 2.81 - Samsung Epic 4G Touch

anyone have this problem? I get stuck on boot logo screen every time. restore is only way to get it to boot. It seems to install fine with other all other roms.. I tried installing the cf3d driver only without the egl and still no go. Different kernels.. No luck
never had this problem with any of Calks roms.
fixes or condolences, anyone? ;p
Sent from my SPH-D710 using Tapatalk

Heres my recovery.log... If it can help.
Starting recovery on Sat Jan 1 00:00:20 2000
framebuffer: fd 4 (480 x 800)
Rogue ET Recovery 1.1.2 (CWM v5.0.2.7)
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/cyasblkdevblk0p1 /dev/block/cyasblkdevblk0
8 /emmc vfat /dev/block/mmcblk0p11 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
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=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=12
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=running
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Sent from my SPH-D710 using Tapatalk

Related

[Q] Error processing ROM Manager script

Since I just created this account XDA won't let me post this in the appropriate place (which would be http://forum.xda-developers.com/showthread.php?t=1175842).... regardless.
I am trying to flash Nil's Business Gingersense 3.0. I have successfully rooted and flashed multiple ROMs in the past. When trying to flash this ROM CWM comes up saying Error processing ROM Manager Script.
Here is the CWM log.
Starting recovery on Thu Sep 8 19:53:39 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /misc mtd misc (null)
2 /recovery mtd recovery (null)
3 /boot mtd boot (null)
4 /system yaffs2 system (null)
5 /datadata yaffs2 datadata (null)
6 /data ext3 /dev/block/mmcblk0p1 (null)
7 /cache ext3 /dev/block/mmcblk0p2 (null)
8 /emmc vfat /dev/block/mmcblk0p3 (null)
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
10 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
I:Completed outputting fstab.
Irocessing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=FRF91
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.koush.20110905.104341
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 5 10:44:06 PDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=release-keys
ro.product.model=ADR6300
ro.product.brand=verizon_wwe
ro.product.name=inc
ro.product.device=inc
ro.product.board=inc
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.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=inc
ro.build.description=3.26.605.1 CL264707 release-keys
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
wifi.interface=eth0
wifi.supplicant_scan_interval=45
mobiledata.interfaces=rmnet0
ro.com.android.dataroaming=true
ro.com.google.locationfeatures=1
ro.sf.lcd_density=240
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
settings.display.autobacklight=1
settings.display.brightness=143
ro.phone_storage=1
dalvik.vm.heapsize=32m
ro.cdma.data_retry_config=max_retries=infinite,0,0,60000,120000,480000,900000
ro.cdma.home.operator.numeric=310012
ro.cdma.home.operator.alpha=Verizon
ro.config.htc.nocheckin=1
ro.HorizontalVVM=true
ro.HorizontalBUA=true
ro.ril.enable.prl.recognition=1
ro.additionalmounts=/mnt/emmc
ro.opengles.version=131072
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.google.clientidbase=android-verizon
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.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.config.vc_call_vol_steps=7
ro.cdma.otaspnumschema=SELC,1,80,99
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.url.safetylegal=http://www.htc.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.media.dec.jpeg.memcap=20000000
ro.media.enc.jpeg.quality=95,85,70
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.product.version=3.26.605.1
ro.modversion=CyanogenMod-7.1.0-RC1-Inc-KANG
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=HT09HHJ18316
ro.bootmode=recovery
ro.baseband=2.15.00.07.28
ro.carrier=COMMON
ro.bootloader=0.92.0000
ro.hardware=inc
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
0e32a451006c45b253cb68e516ffb9c2
e32a451006c45b253cb68e516ffb9c2
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
Oh, and I have verified I am on v4.4.0.0 or higher (currently 5.0.2.0) I have also verified I am using the correct recovery of 3.0.0.8 (since I am SLCD).

Try reinstall the recovery and redownload the rom
Sent From My Optimized HTC Incredibly Dinc

Kratz17 said:
Try reinstall the recovery and redownload the rom
Sent From My Optimized HTC Incredibly Dinc
Click to expand...
Click to collapse
If the above didn't work you might also want to downgrade from the 5.0.2.0 version. There have been reports here and there of problems with the new version.

Any solutions to this yet?
I've got basically the same problem where I cannot restore my backup. I get the same errors as here.
SOLUTION???

GreatMoloko said:
Since I just created this account XDA won't let me post this in the appropriate place (which would be http://forum.xda-developers.com/showthread.php?t=1175842).... regardless.
I am trying to flash Nil's Business Gingersense 3.0. I have successfully rooted and flashed multiple ROMs in the past. When trying to flash this ROM CWM comes up saying Error processing ROM Manager Script.
Here is the CWM log.
Starting recovery on Thu Sep 8 19:53:39 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
Oh, and I have verified I am on v4.4.0.0 or higher (currently 5.0.2.0) I have also verified I am using the correct recovery of 3.0.0.8 (since I am SLCD).
Click to expand...
Click to collapse
Your ClockworkMod Recovery is version 5.0.2.0. ROM Manager version you need to get from when you open ROM Manager itself, as it'll say at the top. These are two different things. I'm using verison 4.5.0.1. Update ROM Manager in the Market (or uninstall it from your current ROM, then re-install from the Market).
Try performing the following in ROM Manager: Open it, hit Menu - Settings - turn on Advanced Mode - turn on Erase Recovery - hit back arrow - select Flash ClockworkMod Recovery.
Then try flashing the ROM in question.
EDIT: I have had issues with ClockworkMod Recovery verision 5.0.2.0 initially, but after turning on the Erase Recovery feature and re-flashing it, things were fine. Every once in a while it won't backup, so I just reboot and re-flash recovery, do the backup, and it works fine.

[email protected] said:
I've got basically the same problem where I cannot restore my backup. I get the same errors as here.
SOLUTION???
Click to expand...
Click to collapse
I have the same problem... I happen after I flash abyss kernel 4.2 to my galaxy note and now I cannot restore my backup, when I boot to CWM it freeze.
Please if someone can help.

Still a problem- No Erase Recovery found in ROM Manager Premium
RMarkwald said:
Your ClockworkMod Recovery is version 5.0.2.0. ROM Manager version you need to get from when you open ROM Manager itself, as it'll say at the top. These are two different things. I'm using verison 4.5.0.1. Update ROM Manager in the Market (or uninstall it from your current ROM, then re-install from the Market).
Try performing the following in ROM Manager: Open it, hit Menu - Settings - turn on Advanced Mode - turn on Erase Recovery - hit back arrow - select Flash ClockworkMod Recovery.
Then try flashing the ROM in question.
EDIT: I have had issues with ClockworkMod Recovery verision 5.0.2.0 initially, but after turning on the Erase Recovery feature and re-flashing it, things were fine. Every once in a while it won't backup, so I just reboot and re-flash recovery, do the backup, and it works fine.
Click to expand...
Click to collapse
Using ROM Manager ptremium 5.0.2.4. Turned on Advance Features a waring window came OK'd it but no new feature cropped up!!! Don't know where this Erase Recovery" feature is to be found

unknowners said:
Using ROM Manager ptremium 5.0.2.4. Turned on Advance Features a waring window came OK'd it but no new feature cropped up!!! Don't know where this Erase Recovery" feature is to be found
Click to expand...
Click to collapse
Menu - settings, 7th option down. Advanced mode has nothing to do with the erase recovery feature.

Log report
cmlusco said:
Menu - settings, 7th option down. Advanced mode has nothing to do with the erase recovery feature.
Click to expand...
Click to collapse
Log report says this:
Starting recovery on Sat Nov 24 08:00:52 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p5 (null)
2 /boot emmc /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p2 (null)
4 /data ext3 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /emmc vfat /dev/block/mmcblk0p8 (null)
7 /system ext3 /dev/block/mmcblk0p1 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Got arguments from /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery" "--update_package=CACHE:update.zip"
(replacing path "CACHE:update.zip" with "/cache/update.zip")
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.fitsnugly.20111120.085104
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Nov 20 08:51:42 EST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=fitsnugly
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=LG-P999
ro.product.brand=lge
ro.product.name=lge_lge_star
ro.product.device=p999
ro.product.board=p999
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p999
ro.build.description=lge_star-user 2.3.3 GRI40 41fdc8a2 release-keys
ro.build.fingerprint=lge/lge_lge_star/p999:2.3.3/GRI40/lgp999-V21e.41fdc8a2:user/release-keys
rild.libpath=/system/lib/librilswitch.so
rild.libargs=-d /dev/ttyspi0
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.sf.lcd_density=240
mobiledata.interfaces=gannet0,vsnet0,vsnet1,vsnet2,vsnet3
dalvik.vm.heapsize=32m
dalvik.vm.dexopt-flags=m=y,u=n
ro.additionalmounts=/mnt/emmc
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.opengles.version=131072
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.telephony.call_ring.absent=true
ro.telephony.ril_class=lgestar
ro.hardware.respect_als=true
ro.bt.bdaddr_path=/sys/devices/platform/star_bd_address/bdaddr_if
dalvik.vm.dexopt-data-only=1
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
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.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-G2x-KANG
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=tegra
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
Finding update package...
I:Update location: /cache/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
Replacing stock recovery with ClockworkMod recovery...
about to run program [/sbin/busybox] with 4 args
rm: /etc: is a directory
about to run program [/sbin/busybox] with 4 args
sh: invalid number 'root'
sh: can't kill pid 3344: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/adbd'
sh: invalid number 'recovery'
sh: can't kill pid 994: No such process
sh: invalid number 'root'
sh: can't kill pid 1764: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/adbd'
sh: invalid number 'root'
sh: can't kill pid 9420: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
sh: can't kill pid 998: No such process
sh: invalid number 'root'
sh: can't kill pid 1764: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]
Starting recovery on Sat Nov 24 08:00:57 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p5 (null)
2 /boot emmc /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p2 (null)
4 /data ext3 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /emmc vfat /dev/block/mmcblk0p8 (null)
7 /system ext3 /dev/block/mmcblk0p1 (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=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.fitsnugly.20111120.085104
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Nov 20 08:51:42 EST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=fitsnugly
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=LG-P999
ro.product.brand=lge
ro.product.name=lge_lge_star
ro.product.device=p999
ro.product.board=p999
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p999
ro.build.description=lge_star-user 2.3.3 GRI40 41fdc8a2 release-keys
ro.build.fingerprint=lge/lge_lge_star/p999:2.3.3/GRI40/lgp999-V21e.41fdc8a2:user/release-keys
rild.libpath=/system/lib/librilswitch.so
rild.libargs=-d /dev/ttyspi0
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.sf.lcd_density=240
mobiledata.interfaces=gannet0,vsnet0,vsnet1,vsnet2,vsnet3
dalvik.vm.heapsize=32m
dalvik.vm.dexopt-flags=m=y,u=n
ro.additionalmounts=/mnt/emmc
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.opengles.version=131072
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.telephony.call_ring.absent=true
ro.telephony.ril_class=lgestar
ro.hardware.respect_als=true
ro.bt.bdaddr_path=/sys/devices/platform/star_bd_address/bdaddr_if
dalvik.vm.dexopt-data-only=1
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
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.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-G2x-KANG
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=tegra
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
449dfc3bd9a686a32d1b8be35bcdd0d7
e04b109f5e4c6e595fcece40d2b9a984
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.

Are you s-off, or bootloader unlocked? If so try reflashing cwm thru hboot or fastboot. Also, are you trying to install this rom thru rom manager? Why not just go straight to recovery your self and flash it from there. Rom manager is known to have issues flashing things.

[CWM][RELEASE] Clockworkmod recovery for P1010

First CWM - Based recovery for Samsung Tablet P1010 by Skin1980
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

HOWTO:
1- Reboot your device in download mode;
2- open Odin;
3- Select the attached file in the PDA field;
4- Flash it.
Skin1980_P1010_CWM-RECOVERY-BETA-1.tar ---> this is for froyo only
Skin1980-P1010-NEW-CF-ROOT-GB.tar ----> this is for Gingerbread
Thanks to:
RussianDeveloper: Great tester and great person... without him you don't have the CWM Recovery
Drockstar, chris41g, koush: for the CWM source
Supercurio: for the explanation about RFS corruption
Chainfire: for the CF-ROOT files/code

EXT4 - Conversion
STATUS: Untested
1st: Flash the new kernel attached that have the ext4 support;
2nd: Install this zip file in recovery ---> http://www.multiupload.com/CSZBZDL1F3
ATTENTION!!!! This will wipe all your data! Make a backup with titanium or similar so then you can restore it!
REMEMBER Also to do a nandroid backup before the zip installation so, if it doesn't work, you can restore easily.

It's great to see this post! I was starting to lose all hope. I just want to let you know that I'm up for testing... only that my Girlfriend has borrowed my Tab for a trip so I won't have it available for a week or so. I just wanted to post so you can see there is people interested.
In the mean time, could you please tell more of what's in the PDA file? Is it only a custom kernel? or does it already contain a CWM attempt?

splattx_x said:
It's great to see this post! I was starting to lose all hope. I just want to let you know that I'm up for testing... only that my Girlfriend has borrowed my Tab for a trip so I won't have it available for a week or so. I just wanted to post so you can see there is people interested.
In the mean time, could you please tell more of what's in the PDA file? Is it only a custom kernel? or does it already contain a CWM attempt?
Click to expand...
Click to collapse
For now it's only the stock kernel with CWM.... when it will work i will add more features like OC, lagfix, init.d support, custom bootanimation etc...

A member called Agafonoff tested it and said that works.... need to test every function like backup and restore...
And please somebody post also the output of:
Code:
mount

It boots on my p1010. I have FROYO.XWKM2 installed.
After booting, kernel version is 2.6.32.9 [email protected] #1
Booting to recovery, it is ClockworkMod Recovery v3.0.0.5.
I see the following output:
Code:
E:Missing bitmap icon_clockwork
(Code -1)
ClockworkMod Recovery v3.0.0.5
E:failed to open /etc/recovery.fstab (No such file or directory)
Checking for ext4 partitions...
Checking /system...
E:unknown volume for path [/system]
E:unknown volume for path [/system]
E:Unable to process volume! Skipping...
Checking /data...
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:Unable to process volume! Skipping...
Checking /cache...
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:Unable to process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
mount output
Code:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gi
set=utf8 0 0
/dev/block/mmcblk0p3 /mnt/apk vfat ro,nodev,noatime,nodiratime,f
0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,err
0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw
d/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,c
rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,ch
wx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check
iocharset=cp437 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,n
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=002
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Unable to do a backup. can't find /sdcard either.

try with alpha 3 please and for every test please post the output like shilob have done.... thanks and sorry but without the device is more and more longer...

Alpha 2 works, missing icon message gone.
Alpha 3 stuck at Galaxt Tab Boot screen

shilob said:
Alpha 2 works, missing icon message gone.
Alpha 3 stuck at Galaxt Tab Boot screen
Click to expand...
Click to collapse
Ok... i understand some thing... but now i have to go... when i have some free time i will patch it
Inviato dal mio GT-I9100 usando Tapatalk

@Skin1980 I have sent you 5$ (USD) via your paypal donate link as good will for your initial work on getting CWM working on the p1010. If/when we get a working backup & recovery, I will be sure to send a larger donation. - thank you for your time and effort sir!
---------- Post added at 07:36 PM ---------- Previous post was at 07:16 PM ----------
Not that it should be any different but accessing the adb shell, running su and then mount on un-modified tab (i.e. no cwm beta/alphas) returns this:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/
rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=cp437 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#

Please somebody post here the file vold.fstab that can be found under tge etc folder
Inviato dal mio GT-I9100 usando Tapatalk

Is this the file you are looking for?
-p.s thank you!!

Exactly!
Inviato dal mio GT-I9100 usando Tapatalk

ok willing beta tester here atlast and if you need any help just ask

Another beta tester here. I don't have much time available, but am willing to help. I was researching how to port ICS for us, but didn't have the time and hardware needed. Thanx!

I can test too, i have a ujkm5 froyo.

Please someone that test the alpha 4 and also the alpha 5 and also alpha 6.
Need that the issue will be reported here.
Like i said in the OP i don't have this device so i need more tester as possible. Please test every of the three version (4 - 5 - 6) and report what works and what not. If you can post also the file /temp/recovery.log or the terminal output.
Thanks
P.S.: after we have a working CWM i promise you some tweaks to get 2000+ on quadrant

Alpha 4
boots
Bad mounts
Alpha 5
boots
Code:
ClockworkMod Recovery v3.0.0.5
Checking for ext4 partitions...
Checking /system...
Checking /data...
E:failed to mount /data (No such device)
/data may be rfs. Checking...
Checking /cache...
E:failed to mount /cache (No such device)
/cache may be rfs. Checking...
Done!
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
tried to backup
Code:
SD Card space free: 12928MB
Backing up boot image...
Error while backing up boot image!E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
Can only mount /sdcard and /system. Other mounts repeat in mount menu.
Code:
# cat recovery.log
cat recovery.log
Starting recovery on Tue Dec 13 04:21:57 2011
framebuffer: fd 4 (1024 x 600)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system ext4 /dev/block/stl9 (null)
3 /system rfs /dev/block/stl9 (null)
4 /cache ext4 /dev/block/stl11 (null)
5 /cache rfs /dev/block/stl11 (null)
6 /data ext4 /dev/block/mmcblk0p2 (null)
7 /data rfs /dev/block/mmcblk0p2 (null)
8 /dbdata ext /dev/block/stl10 (null)
9 /dbdata rfs /dev/block/stl10 (null)
10 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
E:failed to mount /data (No such device)
/data may be rfs. Checking...
32512
Checking /cache...
E:failed to mount /cache (No such device)
/cache may be rfs. Checking...
32512
Done!
I:Processing arguments.
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=c16090d04b4792e
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=p1lite
ro.revision=4
dpm.allowcamera=0
ro.build.id=FROYO
ro.build.display.id=FROYO.XWKM2
ro.build.version.incremental=XWKM2
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Mon May 23 12:36:47 KST 2011
ro.build.date.utc=1306121807
ro.build.type=user
ro.build.user=root
ro.build.host=SE-S608
ro.build.tags=release-keys
ro.product.model=GT-P1010
ro.product.brand=samsung
ro.product.name=GT-P1010
ro.product.device=GT-P1010
ro.product.board=GT-P1010
ro.product.cpu.abi=armeabi-v7a
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=omap3
ro.build.product=GT-P1010
ro.build.description=GT-P1010-user 2.2.1 FROYO XWKM2 release-keys
ro.build.fingerprint=samsung/GT-P1010/GT-P1010/GT-P1010:2.2.1/FROYO/XWKM2:user/r
elease-keys
ro.build.PDA=P1010XWKM2
ro.build.hidden_ver=P1010XWKM2
ro.build.changelist=1012194
ro.build.buildtag=
ro.sf.lcd_density=240
ro.sf.hwrotation=90
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttyS0
wifi.interface=tiwlan0
jpeg.libskiahw.decoder.enable=0
jpeg.libskiahw.decoder.thresh=100000
ro.opengles.version=131072
dalvik.vm.heapsize=48m
keyinputqueue.use_finger_id=true
windowsmgr.max_events_per_sec=60
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.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
media.stagefright.enable-record=false
keyguard.no_require_sim=true
ro.config.ringtone=Minimal_tone.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
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
W:Can't unlink /cache/recovery/command
#
Alpha 6
boots
Code:
ClockworkMod Recovery v3.1.0.1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
tried to backup
Code:
SD Card space free: 12928MB
Backing up system...
Then nothing...
Can only mount /sdcard and /system

shilob said:
Alpha 4
boots
Bad mounts
Alpha 5
boots
Code:
ClockworkMod Recovery v3.0.0.5
Checking for ext4 partitions...
Checking /system...
Checking /data...
E:failed to mount /data (No such device)
/data may be rfs. Checking...
Checking /cache...
E:failed to mount /cache (No such device)
/cache may be rfs. Checking...
Done!
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
tried to backup
Code:
SD Card space free: 12928MB
Backing up boot image...
Error while backing up boot image!E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
Can only mount /sdcard and /system. Other mounts repeat in mount menu.
Code:
# cat recovery.log
cat recovery.log
Starting recovery on Tue Dec 13 04:21:57 2011
framebuffer: fd 4 (1024 x 600)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system ext4 /dev/block/stl9 (null)
3 /system rfs /dev/block/stl9 (null)
4 /cache ext4 /dev/block/stl11 (null)
5 /cache rfs /dev/block/stl11 (null)
6 /data ext4 /dev/block/mmcblk0p2 (null)
7 /data rfs /dev/block/mmcblk0p2 (null)
8 /dbdata ext /dev/block/stl10 (null)
9 /dbdata rfs /dev/block/stl10 (null)
10 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
E:failed to mount /data (No such device)
/data may be rfs. Checking...
32512
Checking /cache...
E:failed to mount /cache (No such device)
/cache may be rfs. Checking...
32512
Done!
I:Processing arguments.
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=c16090d04b4792e
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=p1lite
ro.revision=4
dpm.allowcamera=0
ro.build.id=FROYO
ro.build.display.id=FROYO.XWKM2
ro.build.version.incremental=XWKM2
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Mon May 23 12:36:47 KST 2011
ro.build.date.utc=1306121807
ro.build.type=user
ro.build.user=root
ro.build.host=SE-S608
ro.build.tags=release-keys
ro.product.model=GT-P1010
ro.product.brand=samsung
ro.product.name=GT-P1010
ro.product.device=GT-P1010
ro.product.board=GT-P1010
ro.product.cpu.abi=armeabi-v7a
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=omap3
ro.build.product=GT-P1010
ro.build.description=GT-P1010-user 2.2.1 FROYO XWKM2 release-keys
ro.build.fingerprint=samsung/GT-P1010/GT-P1010/GT-P1010:2.2.1/FROYO/XWKM2:user/r
elease-keys
ro.build.PDA=P1010XWKM2
ro.build.hidden_ver=P1010XWKM2
ro.build.changelist=1012194
ro.build.buildtag=
ro.sf.lcd_density=240
ro.sf.hwrotation=90
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttyS0
wifi.interface=tiwlan0
jpeg.libskiahw.decoder.enable=0
jpeg.libskiahw.decoder.thresh=100000
ro.opengles.version=131072
dalvik.vm.heapsize=48m
keyinputqueue.use_finger_id=true
windowsmgr.max_events_per_sec=60
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.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
media.stagefright.enable-record=false
keyguard.no_require_sim=true
ro.config.ringtone=Minimal_tone.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
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such device)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such device)
W:Can't unlink /cache/recovery/command
#
Alpha 6
boots
Code:
ClockworkMod Recovery v3.1.0.1
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
tried to backup
Code:
SD Card space free: 12928MB
Backing up system...
Then nothing...
Can only mount /sdcard and /system
Click to expand...
Click to collapse
On Alpha 6:
And the file /temp/recovery.log ?
menù works?

Hi, Skin1980. I'll download and check it out.
UPD. File temp/recovery.log on sdcard not present.

HELP!! Having troubles doing NANDROID BACKUP via Clockwork Recovery (sd c

I have a rooted GNexus running AOKP M3 and Franco Kernel #16. Today before updating the kernel I attempted to do a nandroid backup via ROM Manager (newest version: 5.0.0.6). I've done this successfully on a couple occasions but not after I updated ROM Manager. Anyways heres the log:
Starting recovery on Tue Feb 7 02:28:41 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.5.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (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 /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:fail
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=ICS_MR0
ro.build.display.id=full_maguro-userdebug 4.0.1 ICS_MR0 eng.koush.20111123.115422 test-keys
ro.build.version.incremental=eng.koush.20111123.11 5422
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Wed Nov 23 11:54:46 PST 2011
ro.build.date.utc=1322078086
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Full AOSP on Maguro
ro.product.brand=Android
ro.product.name=full_maguro
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=maguro
ro.build.description=full_maguro-userdebug 4.0.1 ICS_MR0 eng.koush.20111123.115422 test-keys
ro.build.fingerprint=Android/full_maguro/maguro:4.0.1/ICS_MR0/eng.koush.20111123.115422:userdebug/test-keys
ro.build.characteristics=nosdcard
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
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
ro.factorytest=0
ro.serialno=01498FC30D018007
ro.bootmode=unknown
ro.baseband=I9250XXKK6
ro.carrier=unknown
ro.bootloader=PRIMEKK15
ro.hardware=tuna
ro.revision=9
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
de969e6d3606553b5a17eed6b595c2dd
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
I:using /data/media, no /sdcard found.
help?

Hmm.. funny. I just successfully did a backup by manually going into recovery and doing it from the menu. I still got a message saying sd card missing or something but it said backup complete and I can see the backup file in ROM Manager.

Unable to install radio

Hi there, I installed CM9 successfully however when it rebooted, there was no radio. I downloaded the file 403radios_btldr.zip and tried to apply it via CWM recovery and keep getting the following error.. i have also downloaded it twice from different sources. Is that the correct radio? Any ideas?
Code:
Starting recovery on Sat Mar 24 15:43:56 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (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 /sdcard 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.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=ICS_MR0
ro.build.display.id=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.version.incremental=eng.koush.20111215.170401
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Thu Dec 15 17:04:31 PST 2011
ro.build.date.utc=1323997471
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_toro
ro.product.device=toro
ro.product.board=toro
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=toro
ro.build.description=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.fingerprint=Android/full_toro/toro:4.0.1/ICS_MR0/eng.koush.20111215.170401:eng/test-keys
ro.build.characteristics=default
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
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=0146975B0401F00E
ro.bootmode=unknown
ro.baseband=��������������������
ro.carrier=unknown
ro.bootloader=PRIMEKL01
ro.hardware=tuna
ro.revision=9
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
5a8985a48c9f5d61b0f5440da38a35c4
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.6");
ui_print("March 24, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/403radios_btldr.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.6
March 24, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/403radios_btldr.zip
Finding update package...
I:Update location: /sdcard/Download/403radios_btldr.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
installing samsung updater extensions for toro
Writing bootloader...
Writing LTE radio...
Writing CDMA radio...
Unable to open modem device (No such file or directory)
IOCTL_MODEM_GOTA_START failed: (-1)
script aborted: assert failed: samsung.update_cdma_modem(
package_extract_file("radio-cdma.img"))
assert failed: samsung.update_cdma_modem( package_extract_file("radio-cdma.img"))
E:Error in /sdcard/Download/403radios_btldr.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/403radios_btldr.zip")
I:using /data/media, no /sdcard found.

It looks to me that your baseband is showing up as unknown and the assert failed because of that.
I would try flashing back to stock (starting from scratch) in fastboot with the official images from google. http://code.google.com/android/nexus/images.html

First I will give you the usual response (not trying to be a douche though lol ) : should've put this in Q&A section, should've checked for other threads about this first since I'm sure there are others, look through development section for the appropriate radios thread that will answer your questions, etc. etc...
Now to answer, I'm assuming by "no radio" you mean no functioning signal i.e. no data/sms/calls? if so I'd recommend looking in the development section either here or at Rootzwiki (recommend there first since they have a sticky thread with all current radios/roms) for a flashable zip... if you want to do it a better way I would suggest learning about ADB and Fastboot and doing it through those means, it does require a little bit of computer savvy to set up but is immensely helpful in many ways... also I don't believe the zip you are trying to flash is the correct one, or you may be flashing it wrong... I am on the go on my GNex but can give links if you can't find anything
blazing through on my Nexus Prime via XDA app

seems to me that the cwm zip you're using is not doing it right. attach that cwm zip for us to look at it, or a link to it.
better yet, use fastboot as suggested.

doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip

nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
thx for posting your solution.. i hate it when people find a solution and abandon the thread

nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
Those are commands for GSM images.
So... According to your OP you had flashed a CDMA rom on a GSM device. Then were trying to flash CDMA radios?
That is the reason why you had no service and the .zip file wouldn't flash.
Make sure you flash the correct ROM's the future.

[Q] can't access userdata partition

Hi all,
i am desperatly trying to fix a gnex refusing to erase/format/write userdata partition (tried odin and fastboot)
i finally managed to get a recovery to work (twrp), so this allows me to connect with adb.
i can now get the partitions:
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name/
lrwxrwxrwx 1 root root 20 Jan 1 20:49 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 20:49 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 1 20:49 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 20:49 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 20:49 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 1 20:49 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 20:49 param -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 20:49 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 1 20:49 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 20:49 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 1 20:49 system -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 20:49 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 1 20:49 xloader -> /dev/block/mmcblk0p1
then tried to check for error on userdata
Code:
~ # e2fsck -c /dev/block/mmcblk0p12
e2fsck 1.41.12 (17-May-2010)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p12
Could this be a zero-length partition?
this seems strange... but partition size seems not null:
Code:
~ # cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
beside, there is really not much in the fstab, is this normal ?
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p10 /system ext4 rw
/dev/block/mmcblk0p11 /cache ext4 rw
/dev/block/mmcblk0p3 /efs ext4 rw
/usb-otg vfat rw
shouldn't it mount the userdata paritition too ?
anyway, if someone with a working gnex could check against the same commands, this would help me big time !

riferez and
auto-answering... the fstab must be the one from the recovery, not the one from system... don't know where to find that one though
and still doesn't explain the e2fsk error

julienvt said:
auto-answering... the fstab must be the one from the recovery, not the one from system... don't know where to find that one though
and still doesn't explain the e2fsk error
Click to expand...
Click to collapse
tried to fdisk the partitions to get info, no success... can't anybody try from adb ?
Code:
/sbin # fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error

julienvt said:
tried to fdisk the partitions to get info, no success... can't anybody try from adb ?
Code:
/sbin # fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
Click to expand...
Click to collapse
Give me 10mins, I'll connect my device and give you those command outputs.
a maguro wrote this.

i got parted on the recovery, and tried access the disk that way
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Error: /dev/block/mmcblk0: unrecognised disk label
(parted) quit
this doesn't bode very well for the emmc.. although i don't understand why i can flash bootloader, recovery, system, etc, and not userdata. Is this parttion somehow physically separated ?
(i previously used omap without errors as well)

i tried on another android phone, got the same messages, so it's just a wrong method

julienvt said:
Hi all,
i am desperatly trying to fix a gnex refusing to erase/format/write userdata partition (tried odin and fastboot)
i finally managed to get a recovery to work (twrp), so this allows me to connect with adb.
i can now get the partitions:
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name/
lrwxrwxrwx 1 root root 20 Jan 1 20:49 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 20:49 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 1 20:49 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 20:49 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 20:49 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 1 20:49 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 20:49 param -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 20:49 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 1 20:49 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 20:49 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 1 20:49 system -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 20:49 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 1 20:49 xloader -> /dev/block/mmcblk0p1
then tried to check for error on userdata
Code:
~ # e2fsck -c /dev/block/mmcblk0p12
e2fsck 1.41.12 (17-May-2010)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p12
Could this be a zero-length partition?
this seems strange... but partition size seems not null:
Code:
~ # cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
beside, there is really not much in the fstab, is this normal ?
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p10 /system ext4 rw
/dev/block/mmcblk0p11 /cache ext4 rw
/dev/block/mmcblk0p3 /efs ext4 rw
/usb-otg vfat rw
shouldn't it mount the userdata paritition too ?
anyway, if someone with a working gnex could check against the same commands, this would help me big time !
Click to expand...
Click to collapse
on TWRP:
Code:
~ # cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p10 /system ext4 rw
/dev/block/mmcblk0p11 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p3 /efs ext4 rw
/usb-otg vfat rw
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p12 on /data type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
you can see /data aka userdata is mounted, and so is /system (which you can use 'mount' or TWRP > Mount > /system).
Try to unmount the partitions then run 'e2fsck'.
julienvt said:
tried to fdisk the partitions to get info, no success... can't anybody try from adb ?
Code:
/sbin # fdisk -l /dev/block/mmcblk0p1
fdisk: can't open '/dev/block/mmcblk0p1': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p9
fdisk: can't open '/dev/block/mmcblk0p9': I/O error
/sbin # fdisk -l /dev/block/mmcblk0p3
fdisk: can't open '/dev/block/mmcblk0p3': I/O error
Click to expand...
Click to collapse
these are the radio, efs and x-loader.. why are you trying to mess with them?

bk201doesntexist said:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p12 on /data type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
you can see /data aka userdata is mounted, and so is /system (which you can use 'mount' or TWRP > Mount > /system).
Try to unmount the partitions then run 'e2fsck'.
Click to expand...
Click to collapse
in fact for me mount only show the first 5 entries, not /data and followings.
pls, in twrp log, i get:
Code:
E: unable to ount '/system'
E: unable to ount '/efs'

julienvt said:
in fact for me mount only show the first 5 entries, not /data and followings.
pls, in twrp log, i get:
Code:
E: unable to ount '/system'
E: unable to ount '/efs'
Click to expand...
Click to collapse
mate, i think your emmc fried or has bad blocks or something. Or your partition table is all screwed up. The fact parted can't read it (the device should be using GPT, i believe) also is not a good sign, right?

bk201doesntexist said:
mate, i think your emmc fried or has bad blocks or something.
Click to expand...
Click to collapse
seems like it... i'll try to see if i can try to format.
other than that, it requires to swap the motherboard, right ?
anyway, thanks for your help

i think i'll look into this:
http://forum.xda-developers.com/showthread.php?t=1644364

julienvt said:
i think i'll look into this:
http://forum.xda-developers.com/showthread.php?t=1644364
Click to expand...
Click to collapse
Might be related.
a manta wrote this.

i just ran the eMMC scanner from this thread:
http://forum.xda-developers.com/showthread.php?t=1823918
and all partitions seem fine !
Code:
~ # chmod 0755 /sbin/emmc-scan
~ # emmc-scan
partition /dev/block/mmcblk0p1
/dev/block/mmcblk0p1
scanned 0 MiB = 0 MB completed --> OK
partition /dev/block/mmcblk0p2
/dev/block/mmcblk0p2
scanned 3 MiB = 4 MB completed --> OK
partition /dev/block/mmcblk0p3
/dev/block/mmcblk0p3
scanned 20 MiB = 21 MB completed --> OK
partition /dev/block/mmcblk0p4
/dev/block/mmcblk0p4
scanned 8 MiB = 9 MB completed --> OK
partition /dev/block/mmcblk0p5
/dev/block/mmcblk0p5
scanned 4 MiB = 5 MB completed --> OK
partition /dev/block/mmcblk0p6
/dev/block/mmcblk0p6
scanned 4 MiB = 5 MB completed --> OK
partition /dev/block/mmcblk0p7
/dev/block/mmcblk0p7
scanned 8 MiB = 9 MB completed --> OK
partition /dev/block/mmcblk0p8
/dev/block/mmcblk0p8
scanned 11 MiB = 12 MB completed --> OK
partition /dev/block/mmcblk0p9
/dev/block/mmcblk0p9
scanned 16 MiB = 17 MB completed --> OK
partition /dev/block/mmcblk0p10
/dev/block/mmcblk0p10
scanned 654 MiB = 686 MB completed --> OK
partition /dev/block/mmcblk0p11
/dev/block/mmcblk0p11
scanned 432 MiB = 453 MB completed --> OK
partition /dev/block/mmcblk0p12
/dev/block/mmcblk0p12
scanned 13865 MiB = 14539 MB completed --> OK
partition /dev/block/mmcblk0p13
/dev/block/mmcblk0p13
scanned 0 MiB = 0 MB completed --> OK
it's... interesting ! But i don't really know where to go from there

another thing to note, is that twrp is asking me for password when starting... does this mean that the data is encryted ? could this explain why i can't mount/format the partition ?

here is the twrp recovery log
Code:
~ # cat /tmp/recovery.log
Starting TWRP 2.5.0.0 on Sun Jan 2 18:47:30 2000
BOARD_HAS_NO_REAL_SDCARD := true
I:Internal path defined: '/data/media'
I:External path defined: '/usb-otg'
I:Mount: Unable to find partition for path '/data'
SP1_NAME := efs
RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true
TW_INCLUDE_CRYPTO := true
Starting the UI...Pixel format: 720x1280 @ 32bpp
Pixel format: BGR_565
framebuffer: fd 3 (720 x 1280)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/system'
I:Processing '/cache'
I:Recreating /cache/recovery folder.
I:Processing '/data'
I:Can't probe device /dev/block/mmcblk0p12
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p12', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p12
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p12', current file system: 'ext4'
I:Backup folder set to '/data/media/TWRP/BACKUPS/0A3BDBBB0B01F015'
I:Settings storage is '/data/media'
I:Processing '/misc'
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/sbl'
I:Processing '/xloader'
I:Processing '/radio'
I:Processing '/efs'
I:Created '/efs' folder.
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p10
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p10', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p3
E:Unable to mount '/efs'
I:Actual block device: '/dev/block/mmcblk0p3', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unmounting main partitions...
Partition Logs:
/system | /dev/block/mmcblk0p10 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/cache | /dev/block/mmcblk0p11 | Size: 425MB Used: 7MB Free: 418MB Backup Size: 7MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p12 | Size: 13865MB
Flags: Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Has_Data_Media Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: emmc
Fstab_File_System: ext4
Backup_Method: dd
/misc | /dev/block/mmcblk0p5 | Size: 4MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p7 | Size: 8MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p8 | Size: 11MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl | /dev/block/mmcblk0p2 | Size: 3MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: sbl
Storage_Name: sbl
Backup_Path: /sbl
Backup_Name: sbl
Backup_Display_Name: sbl
Storage_Path: /sbl
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/xloader | /dev/block/mmcblk0p1 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: xloader
Storage_Name: xloader
Backup_Path: /xloader
Backup_Name: xloader
Backup_Display_Name: xloader
Storage_Path: /xloader
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/radio | /dev/block/mmcblk0p9 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p9
Display_Name: radio
Storage_Name: radio
Backup_Path: /radio
Backup_Name: radio
Backup_Display_Name: radio
Storage_Path: /radio
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/efs | /dev/block/mmcblk0p3 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: EFS
Storage_Name: EFS
Backup_Path: /efs
Backup_Name: efs
Backup_Display_Name: EFS
Storage_Path: /efs
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB-OTG
Storage_Name: USB-OTG
Backup_Path: /usb-otg
Backup_Name: usb-otg
Backup_Display_Name: USB-OTG
Storage_Path: /usb-otg
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
I:Loading package: TWRP (/res/ui.xml)
I:Loading resources...
I:Loading variables...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page clear_vars
I:Loading page confirm_action
I:Loading page action_page
I:Loading page singleaction_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page wipe
I:Loading page advancedwipe
I:Loading page formatdata
I:Loading page formatdata_confirm
I:Loading page backup
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/data/media/TWRP/BACKUPS/0A3BDBBB0B01F015'
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page selectstorage
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page reboot
I:Loading page settings
I:Loading page timezone
I:Loading page screen
I:Loading page advanced
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageracction
I:Loading page decrypt
I:Loading page trydecrypt
I:Loading page terminalfolder
I:Loading page terminalcommand
I:Loading page sideload
I:Loading page installsu
I:Loading page fixsu
I:Switching packages (TWRP)
E:Cannot load volume /misc!
E:Cannot load volume /misc!
Startup Commands: ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76L
ro.build.display.id=cm_maguro-eng 4.0.4 IMM76L eng.dees_troy.20130408.213053 test-keys
ro.build.version.incremental=eng.dees_troy.20130408.213053
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Mon Apr 8 21:31:04 UTC 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=dees_troy
ro.build.host=ded1.ktechnology.net
ro.build.tags=test-keys
ro.product.model=Galaxy Nexus
ro.product.brand=Google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
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=omap4
ro.build.product=maguro
ro.build.description=yakju-user 4.0.4 IMM76I 330937 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76I/330937:user/release-keys
ro.build.characteristics=nosdcard
ro.cm.device=maguro
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
ro.telephony.call_ring.multiple=0
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=9.0.0-RC0-maguro-UNOFFICIAL
ro.modversion=9.0.0-RC0-maguro-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=0A3BDBBB0B01F015
ro.bootmode=unknown
ro.baseband=I9250XXLA2
ro.carrier=unknown
ro.bootloader=PRIMELA03
ro.hardware=tuna
ro.revision=9
ro.emmc=0
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Failed closing /dev/block/mmcblk0p5
(I/O error)
E:Unable to set emmc bootloader message.
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:Cannot find file /nobrightness

more data, parts of result of dmesg when recovery is starting
Code:
<6>[ 3.077697] mmc0: new high speed MMC card at address 0001
<6>[ 3.078124] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 3.078277] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 3.078491] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 3.084991] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
<6>[ 3.085418] sr_class1p5_calib_work: iva: Calibration complete: Voltage Nominal=1140000 Calib=974860
<6>[ 3.087158] mmcblk0boot1: unknown partition table
<6>[ 3.088012] mmcblk0boot0: unknown partition table
<6>[ 4.788635] mms_ts 3-0048: could not find firmware file 'mms144_ts_rev32.fw'
<6>[ 4.788940] mms_ts 3-0048: Melfas MMS-series touch controller initialized
<3>[ 4.804687] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
<3>[ 4.826416] HDCP: failed to load keys
<6>[ 4.939514] EXT4-fs (mmcblk0p11): recovery complete
<6>[ 4.939666] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 5.093933] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 5.098724] android_work: sent uevent USB_STATE=DISCONNECTED
<3>[ 7.358123] mmcblk0: error -110 transferring data, sector 5611464, nr 8, cmd response 0x900, card status 0xb00
<4>[ 7.358306] mmcblk0: retrying using single block read
<6>[ 7.377777] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 7.378784] android_usb gadget: high speed config #1: android
<6>[ 7.379333] android_work: sent uevent USB_STATE=CONFIGURED
<3>[ 9.773437] mmcblk0: error -110 transferring data, sector 5611464, nr 8, cmd response 0x900, card status 0x0
<3>[ 9.773803] end_request: I/O error, dev mmcblk0, sector 5611464
<3>[ 10.836090] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
<3>[ 10.836151] mmcblk0: command error, retrying timeout
<3>[ 13.250854] end_request: I/O error, dev mmcblk0, sector 5611465
<3>[ 13.251190] Buffer I/O error on device mmcblk0p12, logical block 1615844
<3>[ 14.312896] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
<3>[ 14.312957] mmcblk0: command error, retrying timeout
<3>[ 16.727355] musb_g_ep0_irq 709: SetupEnd came in a wrong ep0stage out/status
<3>[ 16.727691] mmcblk0: error -110 transferring data, sector 5611466, nr 6, cmd response 0x900, card status 0x0
<3>[ 16.728057] end_request: I/O error, dev mmcblk0, sector 5611466
<3>[ 21.208526] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
<3>[ 21.208587] mmcblk0: command error, retrying timeout
...

julienvt said:
more data, parts of result of dmesg when recovery is starting
Code:
[ 3.077697] mmc0: new high speed MMC card at address 0001
[ 3.078124] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
[ 3.078277] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
[ 3.078491] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
[ 3.084991] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
[ 3.085418] sr_class1p5_calib_work: iva: Calibration complete: Voltage Nominal=1140000 Calib=974860
[ 3.087158] mmcblk0boot1: unknown partition table
[ 3.088012] mmcblk0boot0: unknown partition table
[ 4.788635] mms_ts 3-0048: could not find firmware file 'mms144_ts_rev32.fw'
[ 4.788940] mms_ts 3-0048: Melfas MMS-series touch controller initialized
[ 4.804687] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
[ 4.826416] HDCP: failed to load keys
[ 4.939514] EXT4-fs (mmcblk0p11): recovery complete
[ 4.939666] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
[ 5.093933] android_work: sent uevent USB_STATE=CONNECTED
[ 5.098724] android_work: sent uevent USB_STATE=DISCONNECTED
[ 7.358123] mmcblk0: error -110 transferring data, sector 5611464, nr 8, cmd response 0x900, card status 0xb00
[ 7.358306] mmcblk0: retrying using single block read
[ 7.377777] android_work: sent uevent USB_STATE=CONNECTED
[ 7.378784] android_usb gadget: high speed config #1: android
[ 7.379333] android_work: sent uevent USB_STATE=CONFIGURED
[ 9.773437] mmcblk0: error -110 transferring data, sector 5611464, nr 8, cmd response 0x900, card status 0x0
[ 9.773803] end_request: I/O error, dev mmcblk0, sector 5611464
[ 10.836090] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
[ 10.836151] mmcblk0: command error, retrying timeout
[ 13.250854] end_request: I/O error, dev mmcblk0, sector 5611465
[ 13.251190] Buffer I/O error on device mmcblk0p12, logical block 1615844
[ 14.312896] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
[ 14.312957] mmcblk0: command error, retrying timeout
[ 16.727355] musb_g_ep0_irq 709: SetupEnd came in a wrong ep0stage out/status
[ 16.727691] mmcblk0: error -110 transferring data, sector 5611466, nr 6, cmd response 0x900, card status 0x0
[ 16.728057] end_request: I/O error, dev mmcblk0, sector 5611466
[ 21.208526] mmcblk0: timed out sending r/w cmd command, card status 0x400b00
[ 21.208587] mmcblk0: command error, retrying timeout
...
Click to expand...
Click to collapse
Either partition table is damaged.. Or emmc has fried/bad blocks on that partition. It can't r/w mmcblk0p12, which is the same issue from the beginning. I imagine that, somehow, you could repartition it - maybe through omapflash/sectors or through a custom PIT file or maybe even through parted, after creating a new label (which will erase the partitions). Where's sector 5611466?
Have you tried getting feedback from the twrp team on this, see if they ever encountered this?
a manta wrote this.

bk201doesntexist said:
Either partition table is damaged.. Or emmc has fried/bad blocks on that partition. It can't r/w mmcblk0p12, which is the same issue from the beginning. I imagine that, somehow, you could repartition it - maybe through omapflash/sectors or through a custom PIT file -
a manta wrote this.
Click to expand...
Click to collapse
yeah, i tried to use parted or mkfs, see if i could format, but to no avail...
Code:
~ # parted /dev/block/mmcblk0p12 mkfs ext2
Error: /dev/block/mmcblk0p12: unrecognised disk label
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Error: /dev/block/mmcblk0: unrecognised disk label
(parted)
Code:
~ # mkfs.ext2 /dev/block/mmcblk0p12
mkfs.ext2: lseek: Value too large for defined data type
although fastboot format -u userdata works until it tries to 'write userdata', and still, the emmc brick test runs smoothly.
I am about to sell it for pieces on ebay, but this is bugging me not to find a proper solution

julienvt said:
yeah, i tried to use parted or mkfs, see if i could format, but to no avail...
Code:
~ # parted /dev/block/mmcblk0p12 mkfs ext2
Error: /dev/block/mmcblk0p12: unrecognised disk label
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Error: /dev/block/mmcblk0: unrecognised disk label
(parted)
Code:
~ # mkfs.ext2 /dev/block/mmcblk0p12
mkfs.ext2: lseek: Value too large for defined data type
although fastboot format -u userdata works until it tries to 'write userdata', and still, the emmc brick test runs smoothly.
I am about to sell it for pieces on ebay, but this is bugging me not to find a proper solution
Click to expand...
Click to collapse
mkfs.ext4 isn't available? Gives the same result? Can you create a new label in Parted?
a manta wrote this.

bk201doesntexist said:
mkfs.ext4 isn't available? Gives the same result?
a manta wrote this.
Click to expand...
Click to collapse
no, only mk2fs. maybe because it's twrp ?

Develop Bugs

welcome