Develop Bugs

[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.

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 ?

I need advice!!

Ok im new here and i do know a little bit but definitly consider myself a noob still. My issue is this.......i bought my s3 2 weeks ago with the new OTA 4.3 pre installed searched high and low and was able to root and install a custom recovery..(philz cwm) and remove knox with the link provided in one of the forums. Then i tried to flash cm 10.2 and i got the status 7 error and looked it up and figured it would work after deleting the get prop lines to the semi colon so i did that and re flashed and then got the status 4 i believe...I couldnt find a solution to that so i tried a few other roms and couldnt flash those same status 7 error, then i came across beanstalk 4.4.1 and for whatever reason succesfully flashed it and ITS GREAT and everything is working smooth as can be however i am flash happy as im sure most of us are and love to try out different roms and pick my favorite one after a few days driving each and i CANT......I am seriously sorry if this has already been answered but legit i been searching days high and low to see what i could find and nothing. So i have no idea why i was able to flash beanstalk, but other roms will not work. The picture is my phones info.

Anything anyone lol? ....I read up on possibly flashing a new modem but I'm not sure if that will be the exact fix....thanks in advance everyone.

Are you running the latest Philz? You could also try twrp.

help
hello, am noob myself with little experience. and no offense to the seniors but have a att s3 rooted about six months now and have flashed several ROMs without a hitch using latest cwm. dont know what your using and have zero experience with any other recovery but has worked for me.
thanks again to a great community.
am learning, so one day will be able to contribute also.
yes, i use the thanks button, buy a beer/coffee when able, and purchase pro versions when available.
d2att
cm 11

That's the thing when I first rooted I had twrp but then flashed philz because I wanted a 4.4 ROM and so I flashed beanstalk and it worked great and I'm still running that one and whether it sounds stupid or not I like to test out a bunch and support these guys work but I can't flash anything else,..... maybe I'll try twrp again and see if I can flash with that, who knows though because I have seen a bunch of stuff about flashing a new modem. I just want to wait until I get a little more feedback, and by the way thank you guys for the ideas.

Does anyone have philz contact info? I stopped getting any status errors and now its just aborting installation all together and the message on Phil's cwm after its said band done logs and makes a file for me and tells me to email the developer( Phil) and that is a great idea however I can't private message him on here and I can't find his email ANYWHERE ......any help would be huge guys thank you in advance!!!!!

If status 7 error come up you have to definitely check version of your CWM, so update to latest. If you was able to flash BeanStalk, you should be able at least flash Quantum or Carbon rom. Some rom's have restrictions/problems with bootloader version that you have (MJB). But be very careful with flashing bootloader (or downgrading)... this is the easiest way of brick your device.

4b3ck said:
If status 7 error come up you have to definitely check version of your CWM, so update to latest. If you was able to flash BeanStalk, you should be able at least flash Quantum or Carbon rom. Some rom's have restrictions/problems with bootloader version that you have (MJB). But be very careful with flashing bootloader (or downgrading)... this is the easiest way of brick your device.
Click to expand...
Click to collapse
I know I can't mess with the boot loader or anything and I don't plan on trying it. But you made my point exactly if I was able to successfully flash bean stalk and it's running great with no issues and I do have philz latest cwm recovery installed I should be able to flash all of those but for whatever reason I can't....... I was getting the status 7 error at first and then I edited the updater script as that thread instructed step by step and then I got some message with a four the first time..... and since then anytime I try to flash anything I no longer get either of those errors now I get something like this which I have no idea about
'
I:command is: 'wipe' and I:value is: 'dalvik'
-- Wiping Dalvik Cache...
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': No such file or directory
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.
-- Dalvik Cache Wipe Complete!
I:script line: 'install /storage/emulated/0/goomanager/cm-10.2.0-d2att.zip
'
I:command is: 'install' and I:value is: '/storage/emulated/0/goomanager/cm-10.2.0-d2att.zip'
Installing zip file '/storage/emulated/0/goomanager/cm-10.2.0-d2att.zip'
E:unknown volume for path [/storage/emulated/0/goomanager/cm-10.2.0-d2att.zip]
-- Installing: /storage/emulated/0/goomanager/cm-10.2.0-d2att.zip
Finding update package...
I:Update location: /storage/emulated/0/goomanager/cm-10.2.0-d2att.zip
E:unknown volume for path [/storage/emulated/0/goomanager/cm-10.2.0-d2att.zip]
E:Can't mount /storage/emulated/0/goomanager/cm-10.2.0-d2att.zip
Installation aborted.
E:Error installing zip file '/storage/emulated/0/goomanager/cm-10.2.0-d2att.zip'
Done processing script file
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard

You still haven't answered, what version of the recovery are you using?
Sent from my SGH-I747 using xda app-developers app

SuperMidgetProductions said:
You still haven't answered, what version of the recovery are you using?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I'm using this one and I'm pretty sure this is the latest.
PhilZ Touch 6
CWM Base version: v6.0.4.5
I:Build version: 6.07.9 - cm_d2att

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
6.15.7 is the newest version

SuperMidgetProductions said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
6.15.7 is the newest version
Click to expand...
Click to collapse
Oh......lol .....thank you man I really appreciate that maybe that could be my issue....the only thing I'm still wondering about is that I was able to flash beanstalk by problems with the others.......I'm going to go ahead and flash the new one through Odin now though and just see for ha has if I'm able to flash something else. I will definitly check back in thanks alot brother.

swoopt25 said:
Oh......lol .....thank you man I really appreciate that maybe that could be my issue....the only thing I'm still wondering about is that I was able to flash beanstalk by problems with the others.......I'm going to go ahead and flash the new one through Odin now though and just see for ha has if I'm able to flash something else. I will definitly check back in thanks alot brother.
Click to expand...
Click to collapse
i may be wrong but it all has to do with the wording in the code of the zip getting flashed basically, if that dev adds in 1 extra line allowing it to be flashed with that then it will when the others won't. but thats just an idea

SuperMidgetProductions said:
i may be wrong but it all has to do with the wording in the code of the zip getting flashed basically, if that dev adds in 1 extra line allowing it to be flashed with that then it will when the others won't. but thats just an idea
Click to expand...
Click to collapse
I get It...totally makes sense especially when you unzip and look at what actually makes up a ROM....thank you again for real man.

swoopt25 said:
I get It...totally makes sense especially when you unzip and look at what actually makes up a ROM....thank you again for real man.
Click to expand...
Click to collapse
hope it works for you, good luck

SuperMidgetProductions said:
hope it works for you, good luck
Click to expand...
Click to collapse
Well I successfully flashed the later version but still not able to flash anything else and I tried two different ROMs......I logged it all but if I paste that whole log here it would probably be to much there is so much information and I literally don't know about 85% of it.

This is most of the log that in getting when trying to flash
bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on (UTC) Thu Feb 27 03:13:15 2014
framebuffer: fd 4 (720 x 1280)
PhilZ Touch 6
Clockworkmod v6.0.4.7
I:Build version: 6.15.7 - cm_d2lte
extra filesystem table (device2, fstype2, options2):
0 /storage/sdcard1 auto /dev/block/mmcblk1p1 0
1 /storage/usbdisk auto /dev/block/sda1 0
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
3 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
5 /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc1 0
5 /storage/sdcard1 auto /dev/block/mmcblk1p1 0
6 /storage/usbdisk auto /devices/platform/msm_hsusb_host/usb 0
6 /storage/usbdisk auto /dev/block/sda1 0
7 /modem emmc /dev/block/mmcblk0p1 0
8 /efs ext4 /dev/block/mmcblk0p11 0
9 /tmp ramdisk ramdisk 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 /preload 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!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:using /data/media/0 for /sdcard
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 1
I:110 0 usbdisk /storage/usbdisk 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:auto_restore_settings set to default (false)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:check_root_and_recovery set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:nandroid_compression set to default (low)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:twrp_backup_mode set to default (false)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:nandroid_md5sum set to default (1)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:show_nandroid_size_progress set to default (1)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:use_nandroid_simple_logging set to default (1)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:nand_prompt_on_low_space set to default (1)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:signature_check_enabled set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:set_brightness set to default (160)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_height set to default (24)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:show_virtual_keys set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:min_log_rows set to default (3)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:background_image set to default (default)
I:background_image set to default
Iefault stitch background loaded.
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:background_icon set to default (false)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:show_battery set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:show_clock set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_text_color set to default (8)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_background_color set to default (1)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_highlight_color set to default (7)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:normal_text_color set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_separator_color set to default (6)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:header_text_color set to default (8)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:batt_clock_color set to default (2)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_background_transparency set to default (102)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_highlight_transparency set to default (102)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:menu_separator_transparency set to default (102)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:show_menu_separation set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:dim_timeout set to default (60)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:blank_timeout set to default (180)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:scroll_sensitivity set to default (48)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:touch_accuracy set to default (7)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:touch_ui set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:enable_vibrator set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:enable_keyrepeat set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:wait_after_install set to default (true)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:slide_left_action set to default (5)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:slide_right_action set to default (3)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:double_tap_action set to default (2)
I:Cannot open /data/philz-touch/philz-touch_6.ini
Iress_lift_action set to default (4)
I:Cannot open /data/philz-touch/philz-touch_6.ini
Iress_move_action set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:time_zone set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:t_zone_offset set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:use_dst_time set to default (false)
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Current time: 2014-02-27 03:13:17 (UTC 0:00)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:use_qcom_time_daemon set to default (0)
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:use_qcom_time_offset set to default (0)
Command: "/sbin/recovery"
ro.cm.device=d2lte
ro.cm.display.version=11-20140215-UNOFFICIAL-d2lte
ro.cm.version=11-20140215-UNOFFICIAL-d2lte
ro.qc.sdk.audio.fluencetype=fluence
ro.sf.lcd_density=320
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.repeatable_keys=114,115
ro.cwm.enable_key_repeat=true
ro.ril.svdo=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.ril.transmitpower=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.boot.emmc=true
ro.boot.baseband=msm
ro.boot.hardware=qcom
ro.boot.serialno=0d934d63
ro.boot.bootloader=I747UCUEMJB
ro.boot.debug_level=0x4f4c
ro.boot.warranty_bit=1
ro.boot.boot_recovery=1
ro.boot.emmc_checksum=3
ro.boot.nvdata_backup=1
ro.boot.cp_debug_level=0x55FF
ro.boot.batt_check_recovery=1
ro.cdma.subscribe_on_ruim_ready=true
ro.emmc=0
ro.emmc.sdcard.partition=17
ro.hwui.text_cache_width=2048
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=msm8960
ro.build.id=KOT49H
ro.build.date=Sun Feb 16 00:36:16 CET 2014
ro.build.date.utc=0
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_d2lte-userdebug 4.4.2 KOT49H 31d5be565b test-keys
ro.build.product=d2lte
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.2
ro.build.version.codename=REL
ro.build.version.incremental=31d5be565b
ro.build.description=d2uc-user 4.1.2 JZO54K I747UCDMG2 release-keys
ro.build.fingerprint=samsung/d2uc/d2att:4.1.2/JZO54K/I747UCDMG2:user/release-keys
ro.build.characteristics=default
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.notification_sound=OnTheHunt.ogg
ro.secure=1
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=cm_d2lte
ro.product.board=MSM8960
ro.product.brand=samsung
ro.product.model=SGH-I747
ro.product.device=d2att
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=samsung
ro.baseband=msm
ro.bootmode=unknown
ro.hardware=qcom
ro.opengles.version=131072
ro.revision=16
ro.serialno=0d934d63
ro.telephony.call_ring.multiple=0
ro.telephony.ril_class=SamsungQualcommRIL
ro.telephony.default_network=10
ro.bootloader=I747UCUEMJB
ro.debuggable=1
ro.modversion=11-20140215-UNOFFICIAL-d2lte
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
ro.use_data_netmgrd=true
com.qc.hardware=true
lpa.decode=true
net.bt.name=Android
net.change=net.bt.name
ril.subscription.types=NV,RUIM
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
rild.libargs=-d /dev/smd0
rild.libpath=/system/lib/libril-qc-qmi-1.so
wifi.interface=wlan0
debug.sf.hw=1
debug.egl.hw=1
debug.mdpcomp.logs=0
media.aac_51_output_enabled=true
dalvik.vm.heapsize=512m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.hwc.mdpcomp.enable=true
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.audio.vr.enable=false
persist.audio.fluence.mode=endfire
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
persist.radio.add_power_save=1
persist.radio.mode_pref_nv10=1
persist.radio.apm_sim_not_pwdn=1
persist.radio.no_wait_for_card=0
persist.radio.snapshot_disabled=1
persist.timed.enable=true
persist.fuse_sdcard=true
persist.data_netmgrd_nint=16
service.adb.root=1
keyguard.no_require_sim=true
recovery.perf.mode=0
telephony.lteOnCdmaDevice=1
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Formatting /cache...
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
Formatting /sd-ext...
E:unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
I:setting up /data/media(/0) for /sdcard/.android_secure.
I:using /data/media/0 for /sdcard
Formatting /storage/sdcard1/.android_secure...
I:Formatting unknown device.
I:605 Volume sdcard1 /storage/sdcard1 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard1: Checking
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard1: Mounted
I:200 0 volume operation succeeded
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
I:605 Volume sdcard1 /storage/sdcard1 state changed from 4 (Mounted) to 5 (Unmounting)
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 5 (Unmounting) to 1 (Idle-Unmounted)
I:/storage/sdcard1: Idle-Unmounted
I:200 0 volume operation succeeded
Data wipe complete.
-- Wiping system...
Formatting /system...
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
Now flash a new ROM!
press any key to continue.
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Formatting /cache...
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
Formatting /sd-ext...
E:unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
I:setting up /data/media(/0) for /sdcard/.android_secure.
I:using /data/media/0 for /sdcard
Formatting /storage/sdcard1/.android_secure...
I:Formatting unknown device.
I:605 Volume sdcard1 /storage/sdcard1 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard1: Checking
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard1: Mounted
I:200 0 volume operation succeeded
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
I:605 Volume sdcard1 /storage/sdcard1 state changed from 4 (Mounted) to 5 (Unmounting)
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 5 (Unmounting) to 1 (Idle-Unmounted)
I:/storage/sdcard1: Idle-Unmounted
I:200 0 volume operation succeeded
Data wipe complete.
press any key to continue.
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
Formatting /system...
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
Done.
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Done.
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
Formatting /cache...
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
Done.
I:605 Volume sdcard1 /storage/sdcard1 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard1: Checking
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard1: Mounted
I:200 0 volume operation succeeded
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
-- Installing: /storage/sdcard1/newcm10.2 (2).zip
Finding update package...
I:Update location: /storage/sdcard1/newcm10.2 (2).zip
Opening update package...
Installing update...
Installation aborted.
I:setting up /data/media(/0) for /sdcard/clockworkmod/.last_install_path.
I:using /data/media/0 for /sdcard
press any key to continue.
I:set_brightness was set to 196
I:set_brightness was set to 232
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
/tmp/recovery.log copied to /sdcard/clockworkmod/philz_recovery.log
Send file to Phil3759 @xda

Figured it all out, I flashed back to my original touchwiz with root and Knox removed from beanstalk and then flashed from there. Now in running the latest cm11. Thanks to those who helped!

CWM recovery won't install

w w w.dropbox.com/sh/rsonn41mng31ggu/u5KYdN02kf
files: w w w.dropbox.com/s/bzleyayiza713g9/CWM%20ONLY%20for%20test%20for%20the%20wise%20people.rar
In standard. android recovery (3e) : recovery.zip gets this E:Error in /tmp/sideload/package.zip (status 0)
it is a std firmware 4.3 kernel 3.10 where junk is removed. and ota update linked to dummy link.
tryed installing image thrue different apps
there are more files. are they needed?
Please help

my tablet onda v975m is rooted SuperSu 1.94 latest busybox
tried to copy to root but after reboot it's gone
a Little help please
__bionic_open_tzdata: couldn't find any tzdata when looking for Asia/Shanghai!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Apr 19 18:36:03 2014
recovery filesystem table
=========================
0 /bootloader mtd bootloader 0
1 /boot_env mtd boot_env 0
2 /logo mtd logo 0
3 /aml_logo mtd aml_logo 0
4 /recovery mtd recovery 0
5 /boot mtd boot 0
6 /system ext4 /dev/block/system 0
7 /cache ext4 /dev/block/cache 0
8 /data ext4 /dev/block/data 0
9 /media vfat /dev/block/media 0
10 /sdcard vfat /dev/block/mmcblk0p1 0
11 /udisk auto /dev/block/sda1# 0
12 /tmp ramdisk ramdisk 0
stat /dev/nand_env OK
env device is /dev/nand_env erasesize=(0x00000) envsize=(0x10000)
E:Bad bootloader arguments
"(null)"
W:try mount /dev/block/mmcblk0p1 ...
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
E:failed to mount /udisk (No such device)
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
E:failed to mount /udisk (No such device)
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
E:failed to mount /udisk (No such device)
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
W:try mount /dev/block/sda11 ...
W:try mount /dev/block/sda12 ...
W:try mount /dev/block/sda13 ...
W:try mount /dev/block/sda14 ...
W:try mount /dev/block/sda1 ...
E:failed to mount /udisk (No such device)
E:cannot mount /udisk (No such device)
E:Can't mount /udisk/factory_update_param.aml
stat /dev/nand_env OK
env device is /dev/nand_env erasesize=(0x00000) envsize=(0x10000)
---void factory_reset_wipe_data(int*, char***),wipe_data=(null)
locale is [(null)]
I:loaded /etc/recovery.kl
I:recovery key map table
I:=========================
I: 0 type:select value:-4 key:28 15 116 104 158 -1
I: 1 type:down value:-3 key:108 114 109 -1 -1 -1
I: 2 type:up value:-2 key:103 115 -1 -1 -1 -1
I:
framebuffer: fd 4 (2048 x 1536)
installing_text: (1 x 1 @ 1896)
erasing_text: (1 x 1 @ 1599)
no_command_text: (1 x 1 @ 1599)
error_text: (1 x 1 @ 1599)
Command: "/sbin/recovery" "--show_text"
ro.serialno=12345678900
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.firstboot=0
ro.hardware=amlogic
ro.revision=11
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mass_storage
ro.build.id=JSS15J
ro.build.display.id=JSS15J.20140328
ro.build.version.incremental=20140328
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Fri Mar 28 18:35:08 CST 2014
ro.build.date.utc=1396002908
ro.build.type=user
ro.build.user=xiaoyang.huang
ro.build.host=droid10-sz
ro.build.tags=test-keys
ro.product.model=ONDA A9 Core4
ro.product.brand=MID
ro.product.name=k12_MA975M8_B
ro.product.device=k12_MA975M8_B
ro.product.board=k12_MA975M8_B
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=MID
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=11
ro.board.platform=meson8
ro.build.product=k12_MA975M8_B
ro.build.description=k12_MA975M8_B-user 4.3 JSS15J 20140328 test-keys
ro.build.fingerprint=MID/k12_MA975M8_B/k12_MA975M8_B:4.3/JSS15J/20140328:user/test-keys
ro.build.characteristics=tablet
ro.adb.secure=1
ro.sf.lcd_density=320
keyguard.no_require_sim=1
keyguard.enable=true
ro.statusbar.widget=true
ro.statusbar.button=true
ro.statusbar.yearmonthdayweek=true
hwui.render_dirty_regions=false
hw.nopm=false
hw.nobattery=false
hw.nophone=false
hw.novibrate=true
hw.hasethernet=true
ro.platform.has.touch=true
ro.sf.hwrotation=0
ro.ui.cursor=surface
sys.fb.bits=32
media.amsuperplayer.enable=true
media.amplayer.enable-acodecs=NULL
media.amplayer.enable=true
media.amplayer.support-exname=divx,h264,avi,ts,m2ts,mkv,mp4,mpg,mpeg,rm,rmvb,wmv,ts,dat,vob,vc1
media.amplayer.support-exname1=mp2,mp3,ac3
media.amsuperplayer.m4aplayer=STAGEFRIGHT_PLAYER
media.amsuperplayer.defplayer=PV_PLAYER
media.amplayer.thumbnail=true
media.amplayer.widevineenable=true
media.amplayer.dsource4local=1
media.amplayer.startmode=true
media.arm.audio.decoder=ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,cook,raac,amr,pcm,adpcm
media.wfd.use-pcm-audio=false
media.wfd.videoreolutiontype=0
media.wfd.videoreolutiongroup=5
media.wfd.videoframerate=30
media.html5videowin.enable=1
media.decoder.vfm.defmap=decoder ppmgr amvideo
gadget.nand.force_sync=true
ro.statusbar.widget.power=true
sys.rotation.settings=false
ro.hdmi480p.enable=true
audio.policy.digital.fixed=false
ro.app.optimization=true
ro.vout.dualdisplay3=true
ro.vout.player.exit=false
ro.has.cpu.setting=true
ro.cpumode.maxfreq=1200000,1320000,800000
audio.h2w.disconnect.delay=true
ro.usbstorage.cpumode=performance
ro.usbstorage.maxfreq=600000
ro.bootanimation.rotation=0
has.media.poll=true
media.libplayer.seek.fwdsearch=1
ro.flashplayer.surfacehack=1
libplayer.livets.softdemux=1
libplayer.netts.recalcpts=1
ro.audio.mapvalue=0,0,0,0
media.libplayer.modules=vhls_mod,dash_mod
ro.app.hdmi.allswitch=true
persist.sys.timezone=Asia/Shanghai
ro.osd2.size=64x64
ro.alarm.align=true
ro.permissions.settings=true
ro.statusbar.volume=true
ro.product.baseband=V1.1.0_V4
ro.product.firmware=00430001
ro.product.otaupdateurl=htt p://1 0.28.11.53:8080/otaupdate/update
ro.module.dualscaler=true
ro.media.partition.label=ONDA MID
ro.usb.vendor.string=ONDA
ro.usb.product.string=MID
ro.quickboot.enable=true
ds1.audio.multichannel.support=false
ds1.audio.effect.support=false
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
ro.config.alarm_alert=Alarm_Classic.ogg
ubootenv.var.firstboot=0
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
wifi.interface=wlan0
gps.enable=false
hw.cameras=2
ro.camera.orientation.front=0
ro.camera.orientation.back=0
drm.service.enable=true
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
ro.ubootenv.varible.prefix=ubootenv.var
init.svc.console=running
init.svc.recovery=running
-- Install /sdcard/Ny mappe ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:read key e=3
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 against key 0
I:verify_file returned 0
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 0)
Installation aborted.
-- Wiping cache...
start erase volume: /cache
Formatting /cache...
make_ext4fs_internal _directorynull) directorynull)
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
warning: wipe_block_device: Discard failed
format volume:/cache sucessed!,now fsync the format device:
Cache wipe complete.
W:try mount /dev/block/mmcblk0p1 ...
-- Install /sdcard/Ny mappe ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:read key e=3
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 against key 0
I:verify_file returned 0
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 0)
Installation aborted.
W:try mount /dev/block/mmcblk0p1 ...
-- Install /sdcard/Ny mappe ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:read key e=3
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
W:try mount /dev/block/mmcblk0p1 ...
-- Install /sdcard/Ny mappe ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:read key e=3
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 against key 0
I:verify_file returned 0
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 0)
Installation aborted.A