Requesting Firmware Dumps from Coby Generation 3 Devices

Status
Not open for further replies.
I have a Coby Kyros MID7036 that I am trying to get the Google Play framework on it. I am stuck trying to get the firmware dump as the root file is not working for the 4.0.3 OS and 3.0.8 kernal. Any thoughts on how to get it rooted?
 
vampirefo. said:
http://www.androidtablets.net/forum...ating-system-dump-coby-kyros-mid7034-4-a.html

http://www.androidtablets.net/forum...-coby-kyros-mid-7034-4-root-gapps-script.html
Click to expand...


this is what I was able to pull:

Mount


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
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/mtdblock2 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/240:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/240:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=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:1 /mnt/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0


cat /proc/partitions


major minor #blocks name


179 0 30702592 mmcblk0
179 1 30698496 mmcblk0p1
31 0 10240 mtdblock0
31 1 5120 mtdblock1
31 2 389120 mtdblock2
31 3 4096 mtdblock3
31 4 524288 mtdblock4
31 5 1572864 mtdblock5
31 6 10240 mtdblock6
31 7 1024 mtdblock7
31 8 1024 mtdblock8
240 0 1421312 ndda
240 1 1421296 ndda1


cat /proc/mtd


dev: size erasesize name
mtd0: 00a00000 00100000 "boot"
mtd1: 00500000 00100000 "kpanic"
mtd2: 17c00000 00100000 "system"
mtd3: 00400000 00100000 "splash"
mtd4: 20000000 00100000 "cache"
mtd5: 60000000 00100000 "userdata"
mtd6: 00a00000 00100000 "recovery"
mtd7: 00100000 00100000 "misc"
mtd8: 00100000 00100000 "tcc"


busybox df -h


/system/bin/sh: busybox: not found


lsmod


wlan 523226 0 - Live 0xbf26b000
vpu_encoder 4955 0 - Live 0xbf266000
vpu_decoder_ext 6938 0 - Live 0xbf261000
vpu_decoder 6896 0 - Live 0xbf25c000
vpu_manager 432530 3 vpu_encoder,vpu_decoder_ext,vpu_decoder, Live 0xbf1ed000
ufsd 378330 0 - Live 0xbf17e000 (P)
tcc_ndd 7292 2 - Live 0xbf178000 (P)
tcc_mtd 7058 6 - Live 0xbf173000
tcc_nand 1471169 2 tcc_ndd,tcc_mtd, Live 0xbf000000 (P)


C:\Users\AVDIII\Desktop\coby_root3>adb shell
shell@android:/ $ mkdir /sdcard/dump
mkdir /sdcard/dump
mkdir failed for /sdcard/dump, File exists
255|shell@android:/ $ busybox tar -cvzf /sdcard/dump/7036_system.tar /system
busybox tar -cvzf /sdcard/dump/7036_system.tar /system
/system/bin/sh: busybox: not found
127|shell@android:/ $ push busybox /data/local/busybox
push busybox /data/local/busybox
/system/bin/sh: push: not found
127|shell@android:/ $ chmod 755 /datalocal/tmp/busybox
chmod 755 /datalocal/tmp/busybox
Unable to chmod /datalocal/tmp/busybox: No such file or directory
10|shell@android:/ $ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
shell@android:/ $ /data/local/tmp/busybox cp /data/local/tmp/busybox /system/bin
/busybox
ta/local/tmp/busybox /system/bin/busybox <
cp: can't create '/system/bin/busybox': Read-only file system
1|shell@android:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|shell@android:/ $
C:\Users\AVDIII\Desktop\coby_root3>adb shell
shell@android:/ $ cat /dev/mtd/mtd > /sdcard/dump/recovery.img
cat /dev/mtd/mtd > /sdcard/dump/recovery.img
/dev/mtd/mtd: No such file or directory
1|shell@android:/ $ cat /dev/mtd/mtd6 > /sdcard/dump/recovery.img
cat /dev/mtd/mtd6 > /sdcard/dump/recovery.img
/dev/mtd/mtd6: Permission denied




getevent -p
add device 1: /dev/input/event4
name: "GT80X"
events:
ABS (0003): 0000 : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
0001 : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
0018 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
002f : value 0, min 0, max 254, fuzz 0, flat 0, resolution 0
0030 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0032 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 5, fuzz 0, flat 0, resolution 0
003a : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
input props:
INPUT_PROP_DIRECT
add device 2: /dev/input/event3
name: "telechips remote controller"
events:
KEY (0001): 0002 0003 0004 0005 0006 0007 0008 0009
000a 000b 000c 000e 000f 001c 0034 003c
003d 0044 0057 0058 0067 0068 0069 006a
006b 006c 006d 0071 0072 0073 007f 009e
00a4 00a6 00a7 00a8 00ac 00d0
input props:
<none>
add device 3: /dev/input/event2
name: "tcc-gpiokey"
events:
KEY (0001): 0072 0073 009e
input props:
<none>
add device 4: /dev/input/event1
name: "tcc-accel"
events:
ABS (0003): 0000 : value -1, min -32, max 31, fuzz 0, flat 0, resolution 0
0001 : value 1, min -32, max 31, fuzz 0, flat 0, resolution 0
0002 : value 21, min -32, max 31, fuzz 0, flat 0, resolution 0
0006 : value 0, min -128, max 128, fuzz 0, flat 0, resolution 0


input props:
<none>
add device 5: /dev/input/event0
name: "axp202 power-key"
events:
KEY (0001): 0074
input props:
<none>

Is this helpful?
 
I tried with a script from XDA by Bin4ry and it here are the results twice:
C:\Users\AVDIII\Desktop\Root>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (22.11.2012) v17 =
======================================================================


Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)


x) Unroot


Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.


Normal Mode enabled!
.


Pushing busybox....
900 KB/s (1085140 bytes in 1.177s)
Pushing su binary ....
761 KB/s (91980 bytes in 0.118s)
Pushing Superuser app
674 KB/s (996704 bytes in 1.443s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .


C:\Users\AVDIII\Desktop\Root>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (22.11.2012) v17 =
======================================================================


Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)


x) Unroot


Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.


Normal Mode enabled!
.


Pushing busybox....
1010 KB/s (1085140 bytes in 1.049s)
Pushing su binary ....
781 KB/s (91980 bytes in 0.115s)
Pushing Superuser app
781 KB/s (996704 bytes in 1.245s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .

then I ran the CobyADB script for root and dump, managed to get a recovery file, but it is 0 kB.
 
CobyADB is intended for tablets using Allwinner CPUs. Your tablet uses a Telechips processor which puts boot.img, bootloader.img, and recovery.img in different places. You'll have to search a little bit, but I believe Vampirefo has already posted the correct commands to make a dump for your tablet.

Until we get the new tablets all sorted out I won't be updating CobyADB to account for the new tablets using the Telechips processor.
 
I think I have a dump for a 7036-4 but I installed gapps. Is that ok or is there a way to remove gapps?
 
Post it as is. If it's a valid dump then I'll note that it has the Google apps included when I add it to the dump index.
 
Finally gained root and have a much needed dump for the MID8048-4 .zip includes boot.img, recovery.img and system compressed in the tar.gz format. Had to manually dd as the dump script in utility pointed to nandc and nandg whereas /proc/mtd listed the images in mtd0 and mtd6 on my device.:D


#####sorry about the prior corrupt file i think something happened while uploading either way here is the new zip https://www.dropbox.com/s/u8rm6zvj58xce2h/dump8048.zip ..... check out on my end.
 
Last edited:
DaSnOoTeRKiNG said:
Finally gained root and have a much needed dump for the MID8048-4 .zip includes boot.img, recovery.img and system compressed in the tar.gz format. Had to manually dd as the dump script in utility pointed to nandc and nandg whereas /proc/mtd listed the images in mtd0 and mtd6 on my device.:D


https://www.dropbox.com/s/u8rm6zvj58xce2h/dump8048.zip
Click to expand...
Yes I pointed this out already /proc/mtd I use cat rather dd same thing though, So these tablets are already kernel rooted? I suspect so.
Current dump script is for allwinner, your tablet is telechips.

just checked your dump, it's corrupt, did you check before upload? corrupt dumps are of no use, redo dump test and upload.
 
Last edited:
These files that are being uploaded here... do they contain user/app cache/data, e.g. gmail account names, passwords, financial app data, sms, call logs, etc.?
A typical nandroid backup would, and as such, should never be distributed publicly.
 
Status
Not open for further replies.

Similar threads

Traveller
  • Sticky
Requesting Firmware Dumps For Coby Generation 3 Devices, Part II
2 3
Replies
32
Views
47K
chrisautrey
C
S
All things 7042
Replies
1
Views
20K
Traveller
Traveller
tpaine
Requesting Touchscreen Drivers for Restoring Development Repairing All Coby Gen3 Tabs
Replies
9
Views
6K
matedaks
M
S
  • Locked
[ROM] Custom ROM for Coby Kyros 9742 - rooted, deodexed, Google Play
6 7 8
Replies
118
Views
158K
Traveller
Traveller
S
  • Locked
[ROM] Custom ROM for Coby Kyros 7042 - Rooted, Deodexed, Google Play
10 11 12
Replies
173
Views
154K
Traveller
Traveller
Back
Top