Dwco um700 destroyed?

[number79]

Hi All,

I have a DWCO UM700 - which seems like to be a clone of a Phecda U7 etc

Well, I think i've messed it up. While trying to get recovery working, I flashed a Phecda recovery image. It works, but the keys don't. But I can ADB SHELL. And when I do a cat /proc/mtd - the erasesize is 08000. whereas previously, it was 10000. Which probably explains why now, it doesn't boot normally. Won't let me go to ADB SHELL to see logcat etc.

So i tried using FWDN to flash the lk.rom as its there that sets MTD partitions, now, I can't boot normally - just get "COULD NOT DO NORMAL BOOT - REVERTING" and a fastboot error.

I can't find official firmware for this device, but I did copy my BOOT.IMG & RECOVERY.IMG before i started this sorry mess. But because they are as size 10000 and MTD is now 8000, they don't restore properly. What can I do?

Here is what I had:

# cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00100000 "boot"
mtd1: 00500000 00100000 "kpanic"
mtd2: 0b400000 00100000 "system"
mtd3: 00400000 00100000 "splash"
mtd4: 02800000 00100000 "cache"
mtd5: 10500000 00100000 "userdata"
mtd6: 00a00000 00100000 "recovery"
mtd7: 00100000 00100000 "misc"
mtd8: 00100000 00100000 "tcc"

# dd if=/dev/mtd/mtd6 of=/nand/recovery.img bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 1.427 secs (7348114 bytes/sec)
# dd if=/dev/mtd/mtd0 of=/nand/boot.img bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 2.780 secs (3771856 bytes/sec)

# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
tmpfs /tmp tmpfs rw,size=4096k 0 0
tmpfs /broadcasting tmpfs rw,size=512k 0 0
/dev/block/mtdblock2 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/sys/bus/usb /proc/bus/usb usbfs rw 0 0
/dev/block/ndda1 /nand vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#

and now:

cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 0b400000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 10500000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00100000 00080000 "misc"
mtd8: 00100000 00080000 "tcc"

~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)

 

[number79]

oh, and fwdn doesn't work. Just sits there with the message
UBS(USB Boot Supported) Load Complete!

and nothing else.

 

[number79]

Ok, I got fastboot working using fastboot in the SDK.

I used fastboot flash boot (with my old boot.img) and it got me to a boot up screen (no more COULD NOT DO NORMAL BOOT - REVERTING" and fastboot error.)

but when i try adb shell i get - exec '/system/bin/sh' failed: No such file or directory (2)

tried adb remount (remount succeeded) but adb shell gives same error

 

[number79]

Ok, i'll update my own thread.

I've been able to ascertain that Recovery.IMG from a COBY 7015 works fine. The boot.img is a bit screwy. But restoring recovery.img to boot partition works fine. So the kernel/ramdisk of COBY 7015 recovery.img is working well with this tablet.

1. TCC_MTD.IMG of HAIPAD - installed by FWDN, gets to the boot screen, but makes a part of the screen flicker after a few seconds
2. So that image rebuilds all the necessary components, but either the Haipad Kernel or the Haipad drivers aren't compatible with the tablet
3. But, the Coby 7015 recovery image kernel & drivers (albeit a stripped down set) work fine
4. So, unpacking TCC_MTD.IMG - replacing kernel from Coby & implementing the drivers into the previous image, and then repacking - might get a boot

I'll let you know!

 

[Blagus]

Does holding down menu or home buttons while resetting device gets you into fastboot? If yes, then simply flash recovery.img to boot.


I've had similar "reverting" problem, which after few resets became "entering fastboot mode" problem on my Joyplus M718 which seems to be a copy of Coby 7015.
But luckily, Joyplus offers their official 2.1, 2.2 and 2.3 updates for their devices.

 

[number79]

I'll close this thread once and for all. To cut a long story short, i ended up bricking it completely - or so I thought.

However, on slatedroid someone mentioned about forcing the TCC8902 Chip to go into USB Recovery mode by shorting one of the pins. Which worked.

Eventually, the device accepted a COBY Kyros MID7015 rom, and i've been running with that - minus the use of 2 hardware keys (which maybe are soft keys, since no program can detect their keypresses).

Moral of the story - I don't think any Tablet can be fully bricked. There is always a chance to get something working!