8042 run tablet from sdcard.

[vampirefo.]

So I need to start over from the beginning and reformat my sd card and make sure all partitions are primary?

yes, that is what you need to do.

 

[magicmaker]

Ok I will try again and see what happens.

Thanks for your help

This is what I have now

93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 1572864 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 524288 nandh
93 64 1183744 nandi
179 0 15558144 mmcblk0
179 1 1305600 mmcblk0p1
179 2 3957728 mmcblk0p2
179 3 10288128 mmcblk0p3

 

[vampirefo.]

Ok I will try again and see what happens.

Thanks for your help

This is what I have now

93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 1572864 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 524288 nandh
93 64 1183744 nandi
179 0 15558144 mmcblk0
179 1 1305600 mmcblk0p1
179 2 3957728 mmcblk0p2
179 3 10288128 mmcblk0p3

Ok that is correct, you now have a data and a system partition.

 

[magicmaker]

I think I got everything right but now when I restart the Coby it get stuck on the Coby screen and will not do anything. It has been like that for at least 30 minutes.

 

[vampirefo.]

I think I got everything right but now when I restart the Coby it get stuck on the Coby screen and will not do anything. It has been like that for at least 30 minutes.

then you have a problem, at most 5 minutes.

adb shell

logcat

 

[magicmaker]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\Windows\system32>cd C:\androidadb\sdk\platform-tools


C:\androidadb\sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # logcat
logcat
/sbin/sh: logcat: not found

 

[vampirefo.]

adb shell

ls

Your are running these commands while the tablet is stuck at Coby screen?

 

[magicmaker]

adb shell

ls

Your are running these commands while the tablet is stuck at Coby screen?

I am running them back at the CWM Recovery screen

 

[magicmaker]

Does all of this look right?
I tried doing it all from the start.

C:\Windows\system32>cd C:\androidadb\sdk\platform-tools


C:\androidadb\sdk\platform-tools>adb push 2012-12-23.18.59.10 /sdcard/clockworkm
od/backup/2012-12-23.18.59.10
push: 2012-12-23.18.59.10/system.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-
12-23.18.59.10/system.ext4.tar.a
push: 2012-12-23.18.59.10/system.ext4.tar -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/system.ext4.tar
push: 2012-12-23.18.59.10/recovery.img -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/recovery.img
push: 2012-12-23.18.59.10/nandroid.md5 -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/nandroid.md5
push: 2012-12-23.18.59.10/data.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/data.ext4.tar.a
push: 2012-12-23.18.59.10/data.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-2
3.18.59.10/data.ext4.tar
push: 2012-12-23.18.59.10/cache.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-1
2-23.18.59.10/cache.ext4.tar.a
push: 2012-12-23.18.59.10/cache.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-
23.18.59.10/cache.ext4.tar
push: 2012-12-23.18.59.10/boot.img -> /sdcard/clockworkmod/backup/2012-12-23.18.
59.10/boot.img
9 files pushed. 0 files skipped.
3038 KB/s (457484166 bytes in 147.021s)


C:\androidadb\sdk\platform-tools>adb shell
~ # mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p2 /data
~ # mount -t ext4 /dev/block/mmcblk0p3 /system
mount -t ext4 /dev/block/mmcblk0p3 /system
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
tar: can't open '/sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.tar':
No such file or directory
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
tar: short read
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
tar: short read
~ #

 

[vampirefo.]

I am running them back at the CWM Recovery screen

No run at Coby screen,

but
run this in cw recovery

mount -t ext4 /dev/block/mmcblk0p2 /data

mount -t ext4 /dev/block/mmcblk0p3 /system

busybox df -h

ls /system

ls /data

 

[magicmaker]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\Windows\system32>cd C:\androidadb\sdk\platform-tools


C:\androidadb\sdk\platform-tools>adb push 2012-12-23.18.59.10 /sdcard/clockworkm
od/backup/2012-12-23.18.59.10
push: 2012-12-23.18.59.10/system.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-
12-23.18.59.10/system.ext4.tar.a
push: 2012-12-23.18.59.10/system.ext4.tar -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/system.ext4.tar
push: 2012-12-23.18.59.10/recovery.img -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/recovery.img
push: 2012-12-23.18.59.10/nandroid.md5 -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/nandroid.md5
push: 2012-12-23.18.59.10/data.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/data.ext4.tar.a
push: 2012-12-23.18.59.10/data.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-2
3.18.59.10/data.ext4.tar
push: 2012-12-23.18.59.10/cache.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-1
2-23.18.59.10/cache.ext4.tar.a
push: 2012-12-23.18.59.10/cache.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-
23.18.59.10/cache.ext4.tar
push: 2012-12-23.18.59.10/boot.img -> /sdcard/clockworkmod/backup/2012-12-23.18.
59.10/boot.img
9 files pushed. 0 files skipped.
3038 KB/s (457484166 bytes in 147.021s)


C:\androidadb\sdk\platform-tools>adb shell
~ # mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p2 /data
~ # mount -t ext4 /dev/block/mmcblk0p3 /system
mount -t ext4 /dev/block/mmcblk0p3 /system
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
tar: can't open '/sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.tar':
No such file or directory
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
tar: short read
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
tar: short read
~ # mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p2 /data
mount: mounting /dev/block/mmcblk0p2 on /data failed: Device or resource busy
~ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 48.0K 407.1M 0% /dev
/dev/block/nandh 503.9M 8.4M 495.6M 2% /cache
/dev/block/mmcblk0p2 1.2G 8.0M 1.1G 1% /data
/dev/block/mmcblk0p3 3.6G 8.0M 3.4G 0% /system
~ # ls /system
ls /system
lost+found
~ # ls /data
ls /data
lost+found

 

[vampirefo.]

The commands and recovery in this thread are old.

The best way for you to do this today would be

reboot into cw recovery

use cw recovery to mount /system and /data

adb shell

rm -r /sdcard/clockworkmod/backup/2012-12-23.18.59.10/*

busybox tar -cvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.tar /data

busybox tar -cvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4.tar /system

in cw recovery
unmount /system
unmount /data

mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p3 /system

busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.tar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4.tar

adb push boot_ds.img.zip /sdcard

use cwm to install it.

 

[magicmaker]

Not trying to be dumb but do i just need to close out the command prompt and start over doing the steps above?

 

[vampirefo.]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\Windows\system32>cd C:\androidadb\sdk\platform-tools


C:\androidadb\sdk\platform-tools>adb push 2012-12-23.18.59.10 /sdcard/clockworkm
od/backup/2012-12-23.18.59.10
push: 2012-12-23.18.59.10/system.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-
12-23.18.59.10/system.ext4.tar.a
push: 2012-12-23.18.59.10/system.ext4.tar -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/system.ext4.tar
push: 2012-12-23.18.59.10/recovery.img -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/recovery.img
push: 2012-12-23.18.59.10/nandroid.md5 -> /sdcard/clockworkmod/backup/2012-12-23
.18.59.10/nandroid.md5
push: 2012-12-23.18.59.10/data.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-12
-23.18.59.10/data.ext4.tar.a
push: 2012-12-23.18.59.10/data.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-2
3.18.59.10/data.ext4.tar
push: 2012-12-23.18.59.10/cache.ext4.tar.a -> /sdcard/clockworkmod/backup/2012-1
2-23.18.59.10/cache.ext4.tar.a
push: 2012-12-23.18.59.10/cache.ext4.tar -> /sdcard/clockworkmod/backup/2012-12-
23.18.59.10/cache.ext4.tar
push: 2012-12-23.18.59.10/boot.img -> /sdcard/clockworkmod/backup/2012-12-23.18.
59.10/boot.img
9 files pushed. 0 files skipped.
3038 KB/s (457484166 bytes in 147.021s)


C:\androidadb\sdk\platform-tools>adb shell
~ # mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p2 /data
~ # mount -t ext4 /dev/block/mmcblk0p3 /system
mount -t ext4 /dev/block/mmcblk0p3 /system
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.t
ar
tar: can't open '/sdcard/clockworkmod/backup/2012-06-15.17.02.23/data.ext4.tar':
No such file or directory
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/data.ext4.t
ar
tar: short read
~ # busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
busybox tar -xvf /sdcard/clockworkmod/backup/2012-12-23.18.59.10/system.ext4
.tar
tar: short read
~ # mount -t ext4 /dev/block/mmcblk0p2 /data
mount -t ext4 /dev/block/mmcblk0p2 /data
mount: mounting /dev/block/mmcblk0p2 on /data failed: Device or resource busy
~ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 48.0K 407.1M 0% /dev
/dev/block/nandh 503.9M 8.4M 495.6M 2% /cache
/dev/block/mmcblk0p2 1.2G 8.0M 1.1G 1% /data
/dev/block/mmcblk0p3 3.6G 8.0M 3.4G 0% /system
~ # ls /system
ls /system
lost+found
~ # ls /data
ls /data
lost+found

as you can see your data and system are empty, that's why stuck at Coby screen.

 

[vampirefo.]

Not trying to be dumb but do i just need to close out the command prompt and start over doing the steps above?

best to just reboot into recovery