Android/Linux for CDMA Touch Pro 2

[locomariachi]

Originally Posted by 00_MACKIE_00

Got a walmart nearby? they have 8 giggers for less than 20 bucks

lol well i'm a lil short on cash (college status) but i might get another one soon. i'm using a 4gb one that i've had since i had my samsung slider. but that's neither here nor there. so basically get a new sd card and try it out and if not then what?

[slow4g63]

Originally Posted by locomariachi

just formatted my card but still getting the same thing.

Running an fsck on the SD Card
dosfsck 2.0.1, 23 Nov 2008, FAT32, LFN
Logical sectgor size is zero.
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the SD card. Cannot continue.
/bin/sh: can't access tty; job control turned off
/#

same here... I've read ALL of the posts talking about this and still no luck

[Boominsvx]

Delete your calibration file and use the stylus lightly on reboot. It's not going to be a perfect fix yet, but much less obtrusive. If you use a fingernail instead of a fingertip, you'll probably have more mistypes than others. There is no new rootfs as of yet.

[coolsilver]

Originally Posted by Boominsvx

Delete your calibration file and use the stylus lightly on reboot. It's not going to be a perfect fix yet, but much less obtrusive. If you use a fingernail instead of a fingertip, you'll probably have more mistypes than others. There is no new rootfs as of yet.

Thanks

I been using the stylus to calibrate.

[coolsilver]

Originally Posted by slow4g63

same here... I've read ALL of the posts talking about this and still no luck

Sounds like your card is biting the dust. Are you having any issues in winmo with reading it in file manager?

[slow4g63]

Originally Posted by coolsilver

Sounds like your card is biting the dust. Are you having any issues in winmo with reading it in file manager?

nope! it's all working fine, I use it daily to play my music stored on the card.
I just seen that it only had 8MB free so I thought maybe that it could of been trying to write files to the card so I cleared out 200MB and still get the errors.

here is the android txt, it goes through like it's going to load then it shows this at the bottom of the screen:

running an fsck on the sd card
dosfsck 3.0.1, 23 nov 2008, fat32, lfn
there are differences between boot sector and its backup.
differences: (offset: original/backup)
65:01/00
not automatically fixing this.
free cluster summary wrong (918 vs. really 36151)
auto-correcting.
performing changes.
/dev/block/mmcblk0p1: 964 files, 210761/246912 clusters
e2fsck 1.41.4 (27-jan-2009)
ext2fs_check_if_mount: no such file or directory while determining
whether /dev/block/loop0 is mounted.
e2fsck: superblock invalid, trying backup blocks...
e2fsck: bad magic number in super-block while trying to open /dev/block/loop0

the superblock could not be read or does not describe a correct ext2 filesystem. if the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck-b 8193 (device)
mount: mounting /dev/block/loop0 on /data failed: Invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty: job control turned off

... then it goes to say all these numbers and stuff and if I let it set for about 4-5mins it will scroll the same numbers and keeps looping every 4-5mins.

whewwwwwww... sorry about the super long post!

[00_MACKIE_00]

Originally Posted by slow4g63

nope! it's all working fine, I use it daily to play my music stored on the card.
I just seen that it only had 8MB free so I thought maybe that it could of been trying to write files to the card so I cleared out 200MB and still get the errors.

here is the android txt, it goes through like it's going to load then it shows this at the bottom of the screen:

running an fsck on the sd card
dosfsck 3.0.1, 23 nov 2008, fat32, lfn
there are differences between boot sector and its backup.
differences: (offset: original/backup)
65:01/00
not automatically fixing this.
free cluster summary wrong (918 vs. really 36151)
auto-correcting.
performing changes.
/dev/block/mmcblk0p1: 964 files, 210761/246912 clusters
e2fsck 1.41.4 (27-jan-2009)
ext2fs_check_if_mount: no such file or directory while determining
whether /dev/block/loop0 is mounted.
e2fsck: superblock invalid, trying backup blocks...
e2fsck: bad magic number in super-block while trying to open /dev/block/loop0

the superblock could not be read or does not describe a correct ext2 filesystem. if the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck-b 8193 (device)
mount: mounting /dev/block/loop0 on /data failed: Invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty: job control turned off

... then it goes to say all these numbers and stuff and if I let it set for about 4-5mins it will scroll the same numbers and keeps looping every 4-5mins.

whewwwwwww... sorry about the super long post!

sorry about your card not working, try a different one and it will work

[vernonlbrown]

Originally Posted by slow4g63

nope! it's all working fine, I use it daily to play my music stored on the card.
I just seen that it only had 8MB free so I thought maybe that it could of been trying to write files to the card so I cleared out 200MB and still get the errors.

here is the android txt, it goes through like it's going to load then it shows this at the bottom of the screen:

running an fsck on the sd card
dosfsck 3.0.1, 23 nov 2008, fat32, lfn
there are differences between boot sector and its backup.
differences: (offset: original/backup)
65:01/00
not automatically fixing this.
free cluster summary wrong (918 vs. really 36151)
auto-correcting.
performing changes.
/dev/block/mmcblk0p1: 964 files, 210761/246912 clusters
e2fsck 1.41.4 (27-jan-2009)
ext2fs_check_if_mount: no such file or directory while determining
whether /dev/block/loop0 is mounted.
e2fsck: superblock invalid, trying backup blocks...
e2fsck: bad magic number in super-block while trying to open /dev/block/loop0

the superblock could not be read or does not describe a correct ext2 filesystem. if the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck-b 8193 (device)
mount: mounting /dev/block/loop0 on /data failed: Invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty: job control turned off

... then it goes to say all these numbers and stuff and if I let it set for about 4-5mins it will scroll the same numbers and keeps looping every 4-5mins.

whewwwwwww... sorry about the super long post!

I had this problem too. Just reformat your card and only have the files for android on the card. Mine booted right up once I did that.

[Meanee]

I am getting an issue where phone went in a "deep sleep" and I couldn't get it out of it without hitting reset button. LED was Amber I believe, and no keys were responsive. Any guesses?

[steveholtam]

I always had perfect luck with Civic's files from the sub-folder. Now I have downloaded the new flyers all in one zip, and moved those files to my root, removing the old Android boot sub-folder.

My problem is the while trying to boot, I think the loading is stuck in a loop. I see a few things that look like errors, such as:

"task rpcrouter: 15 is blocked for more then 120 seconds" and "hung_task_timeout"

Any ideas? Thanks!