Database Info

mtd_utils

Curently I trying to cross compile mtd utils but without success. But I starting Debian again under phone and I will compile it under phone and will post utils here when finish. P.S. tried to write to mtd without luck so I think mtd utils will give me permisions to write. If you have another idea how to write to flash, please post solution here. Currently I want to change rsa modulus inside spl but not know how to access flash (with haret I done this but after restarting phone all is back to previous state, so I need another way)

Succesfully compiled! I think it will be useful to someone

No way to write to flash, only can read Some info:
Code:
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin# ls
doc_loadbios flash_lock flashcp mkfs.jffs2 nanddump nftldump serve_image ubidetach ubinize ubiupdatevol
docfdisk flash_otp_dump ftl_check mkfs.ubifs nandtest recv_image sumtool ubiformat ubirename
flash_erase flash_otp_info ftl_format mtd_debug nandwrite rfddump ubiattach ubimkvol ubirmvol
flash_eraseall flash_unlock jffs2dump mtdinfo nftl_format rfdformat ubicrc32 ubinfo ubirsvol
localhost:~/mtd/install/sbin# ./nandtest
usage: nandtest [OPTIONS] <device>
-h, --help Display this help output
-m, --markbad Mark blocks bad if they appear so
-s, --seed Supply random seed
-p, --passes Number of passes
-o, --offset Start offset on flash
-l, --length Length of flash to test
-k, --keep Restore existing contents after test
localhost:~/mtd/install/sbin# ./ftl_check
usage: ftl_check device
localhost:~/mtd/install/sbin# ./ftl_check /dev/mtd0
Memory region info:
Region size = 512 mb Erase block size = 128 kb
No valid erase unit headers!
localhost:~/mtd/install/sbin# ./flash_otp_info /dev/mtd0
Usage: flash_otp_info [ -f | -u ] <device>
localhost:~/mtd/install/sbin# ./flash_otp_info -f /dev/mtd0
OTPSELECT: Inappropriate ioctl for device
localhost:~/mtd/install/sbin# ./mtd_debug
usage: mtd_debug info <device>
mtd_debug read <device> <offset> <len> <dest-filename>
mtd_debug write <device> <offset> <len> <source-filename>
mtd_debug erase <device> <offset> <len>
localhost:~/mtd/install/sbin# ./mtd_debug info /dev/mtd00
open(): No such file or directory
localhost:~/mtd/install/sbin# ./mtd_debug info /dev/mtd0
mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CAP_NANDFLASH
mtd.size = 536870912 (512M)
mtd.erasesize = 131072 (128K)
mtd.writesize = 2048 (2K)
mtd.oobsize = 64
regions = 0
localhost:~/mtd/install/sbin# ./nandwrite /dev/mtd0 /root/ttt/mtd.img
Writing data to block 0 at offset 0x0
libmtd: error!: cannot write 2048 bytes to mtd0 (eraseblock 0, offset 0)
error 5 (Input/output error)
Erasing failed write from 00000000 to 0x01ffff
libmtd: error!: bad eraseblock number 131072, mtd0 has 4096 eraseblocks
nandwrite: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Data was only partially written due to error
: Invalid argument
localhost:~/mtd/install/sbin# ./mtdinfo /dev/mtd0
mtd0
Name: msm_nand
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 4096 (536870912 bytes, 512.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 64 bytes
Character device major/minor: 90:0
Bad blocks are allowed: true
Device is writable: true
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin# cat /root/ttt/mtd.img > /dev/mtd0
cat: write error: Input/output error
localhost:~/mtd/install/sbin# ./mtd_debug erase /dev/mtd0 0x200000 0x20000
MEMERASE: Input/output error
localhost:~/mtd/install/sbin# ./flash_erase -N -u /dev/mtd0 0x200000 0x20000
Erasing 128 Kibyte @ 200000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 16 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 220000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 17 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 240000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 18 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 260000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 19 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 280000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 20 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 2a0000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 21 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 2c0000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 22 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 2e0000 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 23 (mtd0)
localhost:~/mtd/install/sbin# ./flash_erase --help
Usage: flash_erase [options] MTD_DEVICE <start offset> <block count>
Erase blocks of the specified MTD device.
Specify a count of 0 to erase to end of device.
-j, --jffs2 format the device for jffs2
-N, --noskipbad don't skip bad blocks
-u, --unlock unlock sectors before erasing
-q, --quiet do not display progress messages
--silent same as --quiet
--help display this help and exit
--version output version information and exit
localhost:~/mtd/install/sbin# ./flash_erase -N -j /dev/mtd0 0x200000 0x20000
flash_erase: error!: /dev/mtd0: unable to get NAND oobinfo
error 22 (Invalid argument)
localhost:~/mtd/install/sbin#
localhost:~/mtd/install/sbin# ./flash_erase -N /dev/mtd0 0x200000 0x20000
Erasing 128 Kibyte @ 200000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 16 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 220000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 17 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 240000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 18 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 260000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 19 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 280000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 20 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 2a0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 21 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 2c0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 22 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 2e0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 23 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 300000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 24 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 320000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 25 (mtd0)

If I could I would like to help you, but you write something in Japanese ...
whatever good luck!

Good job pal, hope nand android will be ready suddenly, thanks you're a great dev!!

After new nand driver I am able to write to flash chip but one problem is first 0x59bffff bytes is protected! Some offsets I erased sucessfully (83%)! And succesfully writing to flash (83%) but could not write to memory where is spl I think (maybe need special access to unlock it?) Or only solution is jtag? But, maybe, I seen in kernel option in nand driver (errase call and reset call... I will try)
Code:
localhost:~/mtd/sbin# cat /proc/mtd
dev: size erasesize name
mtd0: 20000000 00020000 "msm_nand"
localhost:~/mtd/sbin# ./mtdinfo /dev/mtd0
mtd0
Name: msm_nand
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 4096 (536870912 bytes, 512.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 64 bytes
Character device major/minor: 90:0
Bad blocks are allowed: true
Device is writable: true
localhost:~/mtd/sbin# ./flash_erase /dev/mtd0 0 4096
Erasing 128 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 0 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 20000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 1 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 40000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 2 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 60000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 3 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 80000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 4 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ a0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 5 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ c0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 6 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ e0000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 7 (mtd0)
error 22 (Invalid argument)
error 22 (Invalid argument)
Erasing 128 Kibyte @ 41a0000 -- 12 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 525 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 41c0000 -- 12 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 526 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 41e0000 -- 12 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 527 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 4200000 -- 12 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 528 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 4220000 -- 12 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 529 (mtd0)
error 22 (Invalid argument)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 22 (Invalid argument)
Erasing 128 Kibyte @ 59c0000 -- 17 % complete flash_erase: Skipping bad block at 059e0000
Erasing 128 Kibyte @ 70a0000 -- 21 % complete flash_erase: Skipping bad block at 070c0000
Erasing 128 Kibyte @ b6e0000 -- 35 % complete flash_erase: Skipping bad block at 0b700000
Erasing 128 Kibyte @ 11460000 -- 53 % complete flash_erase: Skipping bad block at 11480000
Erasing 128 Kibyte @ 116c0000 -- 54 % complete flash_erase: Skipping bad block at 116e0000
Erasing 128 Kibyte @ 14660000 -- 63 % complete flash_erase: Skipping bad block at 14680000
Erasing 128 Kibyte @ 1f820000 -- 98 % complete flash_erase: Skipping bad block at 1f840000
Erasing 128 Kibyte @ 1ffe0000 -- 100 % complete
localhost:~/mtd/sbin#

Writing only from offset 0x59c0000 and good news I think I cid unlocked my device!!! (offset 0x1FEE0000)
Code:
localhost:~/mtd/sbin# ./nandwrite -s 0x59c0000 -m --pad /dev/mtd0 ../mtd.img
Writing data to block 718 at offset 0x59c0000
Writing data to block 719 at offset 0x59e0000
Bad block at 59e0000, 1 block(s) from 59e0000 will be skipped
Writing data to block 720 at offset 0x5a00000
Writing data to block 721 at offset 0x5a20000
Writing data to block 722 at offset 0x5a40000
Writing data to block 723 at offset 0x5a60000
Writing data to block 724 at offset 0x5a80000
Writing data to block 725 at offset 0x5aa0000
Writing data to block 726 at offset 0x5ac0000
Writing data to block 727 at offset 0x5ae0000
Writing data to block 728 at offset 0x5b00000
Writing data to block 729 at offset 0x5b20000
Writing data to block 730 at offset 0x5b40000
Writing data to block 731 at offset 0x5b60000
Writing data to block 732 at offset 0x5b80000
Writing data to block 733 at offset 0x5ba0000
Writing data to block 734 at offset 0x5bc0000
Writing data to block 735 at offset 0x5be0000
Writing data to block 736 at offset 0x5c00000
....
....

good work munjeni,it's a good news!!
i will Expected for another good news.
i have a one questios:what is cid unlocked??are you test nand in your device??!!
you're the best dev

Milane, ne nisam napravio jos uvek nista, hehe no, I curently testing nand driver, and nand booting will be "only" when bootloader be unlocked (when I get access to first 0x59bffff bytes)! After that I will try something

hahahaha #define PROTECT_BLOCK_NUM (0x212)
Maybe changing to 0x0 ...DONE! Huh I have one chance to try and to write to flash hmmm... must be 100% sure to have good nand backup without bad blocks if something go bad my device will be bricked (I not care becouse I will by new phone, our phone will be for playing with jtag)

For developers here is working nand driver

munjeni said:
For developers here is working nand driver
Click to expand...
Click to collapse
Cool Man Munjeni.
You are The King of HD MINI Android and
Gabana Is The King of HD MINI WM.
Thank All of You......

Simple bootloader I think will be good now:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/tinboot.git;a=summary
Some interested links:
http://forum.xda-developers.com/showthread.php?t=614275

hi munjeni,good work ,you're the best development in the xda.

MOUNTED!!!
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,noatime,nodiratime,fmask=0111,dmask=0000,al
low_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=re
mount-ro 0 0
/dev/block/loop0 /data ext2 rw,sync,noatime,nodiratime,errors=continue 0 0
/dev/block/loop1 /system ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block/loop2 /cache ext2 rw,sync,noatime,nodiratime,errors=continue 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 /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,nosuid,nodev,noexec,relatime,fmask=011
1,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed
,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,fmas
k=0111,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=
mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.jcwp.Txwy-1 vfat ro,dirsync,nosuid,nodev,noexec,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.jcwp.I3Dbz-1 vfat ro,dirsync,nosuid,nodev,noexec,r
elatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.jcwp.S4305-1 vfat ro,dirsync,nosuid,nodev,noexec,r
elatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.demo.android.waterfallwallpaper-1 vfat ro,dirsync,
nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[COLOR="Red"][B][SIZE="6"]/dev/block/mtdblock0 /mnt/sdcard/flash yaffs2 rw,relatime 0 0[/SIZE][/B][/COLOR]#

I have good news, nand driver is now able to write to region at 0x2820000 (there is master boot record, partition table, imgfs ...etc) I think we will be able now to create android nand rom creating new MBR and partition table (not 100% sure)!!!
Here is erase block offsets http://pastebin.com/xAhnEXBU
I confirm I sucessfully erased mbr and my partitions but no way to unlock spl (start offset 0x2400000) and I don't know why:
Code:
localhost:~/mtd/sbin# ./flash_erase /dev/mtd0 0x2400000 1
Erasing 128 Kibyte @ 2400000 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 288 (mtd0)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd0: MTD Erase failure
error 5 (Input/output error)
Erasing 128 Kibyte @ 2400000 -- 100 % complete
If someone have skills hex editing mbr it will be good! In attachment is mbr and msflsh dump... I waiting expert with ideas and my device will be testing device!

Great job! looks great! also there must be another partition maps, for example in computer GUI Partition map, Apple Partiton, and MBR (known also as Microsoft's Master Boot Record)
& also you still need JAG picture? right?

Other partition table? MBR contains a partition table describing the locations, sizes, and other attributes of linear regions referred to as partitions! We have mbr and we have all needed to create nand rom but I need to learn now how to do it. I think will not be hard (maybe I will create linux partition layout)

I Checked some info.
I just think you should do with MBR Partition Table.
I saw EBR Scheme it's says for Linux. (not sure), but it's not famous now, looked at HD2, nothing says about MBR .. Partition Maps it's specially for computers between Mac, Linux and Windows now.
Also I checked about Linux Partition Layout that you said.. I didn't see in Mobile Phones right now (maybe future), not famous.
Anyway, seems MBR is the Default and the Famous for Mobiles right now.
Try MBR Partition Map Scheme

First I will map all wince partition tables, all offsets, all sizes, and will resize one wince partition and to free space will create one yaffs2, then I will try to see that partition from android becouse I not know if nand driver is good for reading (yes it is good for writing now but from android I see only 2 mtd - one is mtd0 and seccond is mtd0ro, but I not see partition layout from android, it is problem now)... will try to create one yaffs2 and mount it under android, if all go ok than I will delete all layouts and try creating new layout for android boot!
If you want to help, please ask some guys to hd2 forums about how to create custom android layout in nand for android, maybe someone will help. Only good thing is: I am able to edit/delete mbr, table, imgfs...
EDIT:
hmmm I have idea. Maybe puting modified spl (hex edited spl with my rsa modulus) to memory regions where it will be executed? And than signing rom with my rsa key and using regular htc utility to install all (install nbh with modified spl)

external sdcard wont mount

Ok guys I know I'm behind the times, but I'm running Tiamat 3.2 (Xoom of course).
Suddenly my external sd card isnt mounting. I has previously mounted.
Firing up adb and looking at dmesg, I see the following:
mmcblk0: 14.9 Gb <---Which should be external sdcard
mmcblk1: 29.7 Gb <---Internal sdcard
mount only shows the following:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs 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 /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/pdsb /pds ext2 ro,noatime,nodiratime,barrier=1,data=writeback 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm also finding this on searching dmesg:
sh-4.1# dmesg | grep mmc
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: [email protected] [email protected]
00 video=tegrafb [email protected] console=ttyS0,115200n8 usbcore.old_scheme_fi
rst=1 tegraboot=sdmmc gpt gpt_sector=0x03b6efff mot_prod=1 androidboot.serialno=
170061c241615357 hw_rev=p3 androidboot.modelno=MZ604 product_type=w lp0_vec=8192
@0x1e7f1020 androidboot.bootloader=1045 androidboot.carrier=wifi-only lcd_manfid
=AUO mem_vid=0x101 mem_pid=0x5454 androidboot.carrier=wifi-only product_type=w
<4>[ 12.376571] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376592] mmc0: no vmmc regulator found
<7>[ 12.376680] Registered led device: mmc0::
<6>[ 12.376763] mmc0: SDHCI controller on tegra [sdhci-tegra.1] using ADMA
<4>[ 12.376835] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376856] mmc1: no vmmc regulator found
<7>[ 12.376943] Registered led device: mmc1::
<6>[ 12.377030] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 12.377141] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 12.377158] mmc2: no vmmc regulator found
<7>[ 12.377243] Registered led device: mmc2::
<6>[ 12.377340] mmc2: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<6>[ 12.518127] mmc1: new high speed SDHC card at address b368
<6>[ 12.518364] mmcblk0: mmc1:b368 H1510 14.9 GiB
<6>[ 12.521455] mmcblk0: p1
<6>[ 12.620506] mmc2: new high speed MMC card at address 0001
<6>[ 12.620792] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<6>[ 12.627027] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpani
c) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 12.718736] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode
. Opts: (null)
<7>[ 15.302617] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570874
<7>[ 15.302724] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570873
<7>[ 15.302760] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570851
<6>[ 15.302792] EXT4-fs (mmcblk1p10): 3 orphan inodes deleted
<6>[ 15.302805] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 15.313298] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mod
e. Opts: noauto_da_alloc
<6>[ 20.318570] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 20.319437] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode
. Opts: noauto_da_alloc
<6>[ 20.324635] EXT4-fs (mmcblk1p2): mounted filesystem without journal. Opts:
(null)
<6>[ 42.616835] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.213691] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.215912] EXT4-fs (mmcblk1p10): re-mounted. Opts: (null)
<6>[ 46.020452] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.054467] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.085089] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<4>[ 119.330601] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 119.330686] mmc0: new high speed SDIO card at address 0001
<3>[ 125.914203] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1660.225502] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1665.431378] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1673.260399] FAT: Filesystem error (dev mmcblk0p1)
Obviously there is a Filesystem error on the device. What do I do to rectify the error?
I've tried to mount manually but this is what I get:
sh-4.1# mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
<v/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
mount: I/O error

Really, why don't you upgrade? I think you will be much happier. An upgrade to an EOS ICS build will probably fix your sd mounting problem, unless, of course, the sd card is bad or not seated properly.

Cannot access external SD card

Hi everbody,
Yesterday I received two Transcend 8GB microSDHC cards (Class 4, TS8GUSDHC4) and I wanted to use them with my rooted EEE pad transformer. I've formatted the card using fdisk (with fat32, "c" in fdisk). Then, I copied a jpg to the SD card, but my tablet couldn't open it.
I've checked /Removable but it was empty. I went into the adb shell as root. "dmesg" gave me the following:
Code:
<6>[ 4545.116710] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.117412] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.117802] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.118197] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.118870] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.138425] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.139115] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.139476] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.142621] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.142997] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.143644] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.281748] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.282439] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.282814] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.288602] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.289014] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.290014] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.292451] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.292846] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.293509] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.293896] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.294568] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.294955] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.295618] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.296006] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.296677] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.298838] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.299529] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:0
<6>[ 4545.299896] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.304242] [mmc]:carddetect_irq:272 mmc1: gpio_69:0
<6>[ 4545.304627] [mmc]:carddetect_irq:272 mmc1: gpio_69:1
<6>[ 4545.305003] [mmc]:mmc_detect_change:1368 mmc1: gpio_69:1
<6>[ 4545.305677] [mmc]:mmc_schedule_delayed_work:84 mmc1: delay 20
<6>[ 4545.327467] [mmc]:mmc_rescan:1786 mmc1: gpio_69:1 rescan_disable 0
<6>[ 4545.482018] [mmc]:mmc_rescan:1868 mmc1: extend_wakelock 1
Not sure what is happening here, but no device seems to be mounted. With the card inserted, I also ran "df ":
Code:
Filesystem Size Used Free Blksize
/dev 360M 32K 360M 4096
/mnt/asec 360M 0K 360M 4096
/mnt/obb 360M 0K 360M 4096
/system 503M 459M 44M 4096
/data 13G 7G 5G 4096
/cache 521M 22M 498M 4096
/Removable 360M 0K 360M 4096
/mnt/sdcard 13G 7G 5G 4096
And "mount":
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs 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 /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /data ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=1,nodelalloc,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Can somebody help me getting my SD card to work? Is this card simply not compatible or is something else wrong?
I've searched the forums, but I couldn't find the answer anywhere.
Thanks a bunch!

May be try that MMC in some other device like a phone...
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
May be try that MMC in some other device like a phone...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.

chronozphere said:
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.
Click to expand...
Click to collapse
Thanks, I needed a good laugh
Everyone starts some-where, MicroSDHC cards are evil in that respect

I have the sameproblem...icant mount sd card...howto
Enviado desde mi Transformer TF101 usando Tapatalk 2

chronozphere said:
Aah.. this is so stupid.
I don't have any experience with SD cards so far. So I thought it would be OK if it was partially sticking out. After all you need to be able to pull it out. But apparently one should insert it fully into the tablet.
Click to expand...
Click to collapse
I used to think the SD card reader on my laptop was poorly designed as i needed tweezers to pull out the card, then one day i pushed it in and it clicked then the thing flew out, good times :laugh:

Bootloop & Dalvik Cache Wipe failed

Hello friends,
I'm stumped. Don't know what to do anymore.
Im am not new to rooting/modding but I am at a point now where I can't help myself.
I had CM10 running on my HOS and wanted to go back to Stock. So I relocked the Bootloader and started flashing my device. Unfortunately it didn't work and ended with the Errorcode 155 (as far as i can remember).
From there on nothing worked anymore. I think i got the HTC logo and then a black screen.
So i unlocked the Bootloader again and put CWR on it. I wanted to put CM ROM on it via adb put but didn't work. "Device not found".
So, after that i flashed TWRP and mounted my external storage so i could put the ROM on it. But didn't work. Windows said I had to format it. So i formatted it with FAT32. After that i was able to put ROM and gapps on it. Finally I was able to flash the ROM and gapps. That did work. I wanted to wipe Dalvik Cache but it said "Failed". Rebooted into Fastboot and did fastboot flash boot boot.img
I took boot.img out of the CM-Zip File.
Wiping external storage also failed.
Does anyone have a clue what is going on? How can i fix it?
I got a log from clockwork. Hope anyone can do something with it.
Code:
Starting recovery on Tue Feb 19 09:05:09 2013
framebuffer: fd 4 (540 x 960)
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p22 (null) 0
2 /boot emmc /dev/block/mmcblk0p21 (null) 0
3 /cache ext4 /dev/block/mmcblk0p34 (null) 0
4 /data ext4 /dev/block/mmcblk0p35 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p36 (null) 0
6 /system ext4 /dev/block/mmcblk0p33 (null) 0
7 /misc emmc /dev/block/mmcblk0p23 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.koush.20120429.134456
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 13:45:32 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=ville
ro.product.brand=htc
ro.product.name=cm_ville
ro.product.device=ville
ro.product.board=ville
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=ville
ro.build.description=cm_ville-userdebug 4.0.4 IMM76D eng.koush.20120429.134456 test-keys
ro.build.fingerprint=htc/cm_ville/ville:4.0.4/IMM76D/eng.koush.20120429.134456:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=ville
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=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-ville-UNOFFICIAL
ro.modversion=9.0.0-RC0-ville-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=SH24KW405401
ro.bootmode=recovery
ro.baseband=1.11.50.05.28
ro.carrier=HTC-GER
ro.bootloader=2.15.0000
ro.hardware=ville
ro.revision=128
ro.emmc=1
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
-- Wiping cache...
Formatting /cache...
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
Creating filesystem with parameters:
Size: 268431360
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65535
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65535 blocks
warning: wipe_block_device: Discard failed
Cache wipe complete.
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
Couldn't open directory.
No files found.
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
-- Wiping cache...
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
Formatting /cache...
Creating filesystem with parameters:
Size: 268431360
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65535
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65535 blocks
warning: wipe_block_device: Discard failed
Cache wipe complete.
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0

looks like it's not mounting mmpcblk0p35 which is /data. I'm curious about the line '/datadata'..
You can cause some pain with TWRP and wiping, you can wipe a mount point. Maybe a contributing factor to a failed install? I would boot to TWRP and install the ROM again and then reboot.

I tried several times installing the ROM from scratch via both CWM and TWRP. Didn't work. Still stuck on CM animation.

So I finally got my phone running again. However no stock rom, "just" CM10.1.
I did a factory reset with TWRP to do a formatting of the partitions. After that I flashed CM10.1-Nightly and the corresponding boot.img
...I tried again to install the stock RUU (with relocked bootloader) but still getting Error-155.
So i'm on CM10.1. Not too bad

tonestar81 said:
So I finally got my phone running again. However no stock rom, "just" CM10.1.
I did a factory reset with TWRP to do a formatting of the partitions. After that I flashed CM10.1-Nightly and the corresponding boot.img
...I tried again to install the stock RUU (with relocked bootloader) but still getting Error-155.
So i'm on CM10.1. Not too bad
Click to expand...
Click to collapse
great job. as you get more devious in breaking your phone, you get better at fixing it CM10.1 rocks, everything is working for me on it.
Unless your planing on selling the phone, I'm not sure why you'd want to use any RUU's (or any OTA/Vendor stuff). Your now managing the software on your phone not the telco/HTC. For sure you do a better job!

Got Stuck into BOOTLOOP
I am running Noir A2 Lite, with Spreadtrum chip SP8810. I am stucked into Bootloop, and I am fully sure it is due to not clearing Dalvik-cache.
I was setting up the low internal memory issue with ext3 partition of Sdcard method using Pimk Rom, BusyBox etc. Everything was fine and in the end I got the internal memory increased but the phone was working slow so I thought to get back to the previous state where my genuine internal phone memory was existing. So I just done the RESET FACTORY from Settings of phone. After that it rebooted and still keeps rebooting again and again. I searched on the causes of BOOTLOOP and came to know it might happen due to not clearing DELVIK-CACHE.
Phone is rooted D Of course), and I can't boot into Recovery Mode, I don't know why because since I rooted I wasn't able to get into recovery mode by pressing any key combinations. But I can go into fastboot by pressing VOL+ and POWER button together.
Can you suggest me any way to resolve this problem?
Regards!!

[Q] Cache partition seems to have disappeared

LG Optimus 2x (P990), Stock ROM, Android 2.3.4, rooted, ROM Manager and CWM Recovery installed.
My phone seemed to be getting rather slow so I decided to clear the cache and the Dalvik cache, from the recovery menu, to see if it would speed up the phone a little. Both processes completed without errors and I rebooted the phone.
The phone now works faster and is completely normal except for one thing. I find that I cannot now download any apps from Google Play as I get an error 498. If I look at a DF listing in a terminal there is no /cache listed. If I look at the results of 'mount' in the terminal I cannot see a cache partition either.
I have tried clearing the cache 3 times now with no success. I have also tried Cache Fixer but that gives errors if I try to move the cache 'Cache has NOT been moved'. I assume that may be because there isn't a cache partition now. I also tried restoring the cache using a partial restore from a nandroid backup which completed successfully but hasn't cured the problem - I still don't seem to have a cache.
EDIT: I've just had a look at the partition using fdisk and this is what I see:
Disk /dev/block/mmcblk0p2: 4 heads, 16 sectors, 2048 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 00 0 0 0 0 0 0 0 0 00
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00
Doesn't look good!
FURTHER EDIT: That bit about fdisk above is wrong. I thought that I was looking at a device but it was a partition.
Using fdisk on the proper device I get:
Disk /dev/block/mmcblk0: 7996 MB, 7996440576 bytes
1 heads, 16 sectors/track, 976128 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 129 44928 358400 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 44929 53120 65536 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 53121 53376 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 53377 946432 7144448 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 53441 54464 8192 83 Linux
/dev/block/mmcblk0p6 54529 54848 2560 83 Linux
/dev/block/mmcblk0p7 54913 57472 20480 83 Linux
/dev/block/mmcblk0p8 57537 254144 1572864 83 Linux
/dev/block/mmcblk0p9 254209 946432 5537792 83 Linux
So the cache partition is still there (/dev/block/mmcblk0p2) but it doesn't appear in the mount list:
rootfs / rootfs ro,noatime 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,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext3 ro,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,data=ordered 0 0
tmpfs /mnt/extasec tmpfs rw,nodev,noatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p6 /lgdrm ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,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/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,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/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:17 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,noexec,noatime,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:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexec,noatime,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/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.MultitaskingDrawer-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/org.englishheritage.app-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/uk.agiletech.forestcomm-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.mxdata.tube.Market-1 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
If I try and unmount, mount or remount the cache partition I get 'Invalid argument'.
I have run a file system check on that partition and it shows 'clean'. So, to summarise, the cache partition is there, the file system is clean but it isn't being mounted and I can't mount it either. I'm baffled.
I would be really grateful for some suggestions.

I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.

I have the same problem on motorola defy (jordan)
BarrySamuels said:
I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.
Click to expand...
Click to collapse
Did you manage to solve it?

KfirSolomon said:
Did you manage to solve it?
Click to expand...
Click to collapse
Sorry for the very late reply but I've only just seen your post.
Yes I did solve it. It was because the partition had been formatted ext4 which my current OS didn't recognise. It used ext3 so I reformatted it manually via a terminal and all was well.