MID7035 CWM problem

Discussion in 'Coby Generation 3' started by jhax78, Jul 27, 2013.

  1. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    Hello peeps iam new here and would like some help if possible

    device: Mid7035


    i sucsefully used builder clockworkmod to build myself a cwm recovery image


    now the only problem i have is some mount points can't be found resulting in errors


    CWM log file


    Code:
    Starting recovery on Fri Jul 26 10:16:51 2013
    can't open /dev/tty0: No such file or directory
    framebuffer: fd 3 (800 x 480)
    ClockworkMod Recovery v6.0.3.4
    recovery filesystem table
    =========================
      0 /tmp ramdisk (null) (null) 0
      1 /boot mtd boot (null) 0
      2 /cache yaffs2 cache (null) 0
      3 /data yaffs2 userdata (null) 0
      4 /misc mtd misc (null) 0
      5 /recovery mtd recovery (null) 0
      6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
      7 /nand vfat /dev/block/ndda1 (null) 0
      8 /system yaffs2 system (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!
    W:Unable to get recovery.fstab info for /external_sd during fstab generation!
    I:Completed outputting fstab.
    I:Processing arguments.
    E:Can't find misc
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/command
    E:Can't find misc
    I:Checking arguments.
    Warning: No file_contexts
    Warning:  No file_contexts
    I:device_recovery_start()
    Command: "/sbin/recovery"
    
    
    ro.boot.serialno=0000130122211729126F
    ro.boot.wifimac=
    ro.boot.btaddr=00016C11B01E
    ro.boot.memtype=2
    ro.serialno=0000130122211729126F
    ro.bootmode=unknown
    ro.baseband=unknown
    ro.bootloader=unknown
    ro.hardware=m805_892x
    ro.revision=8194
    ro.emmc=0
    ro.boot.emmc=0
    ro.factorytest=0
    ro.secure=1
    ro.allow.mock.location=0
    ro.debuggable=1
    persist.sys.usb.config=adb
    ro.build.id=JDQ39E
    ro.build.display.id=cm_m805_892x-userdebug 4.2.2 JDQ39E eng.hudson.20130726.005010 test-keys
    ro.build.version.incremental=eng.hudson.20130726.005010
    ro.build.version.sdk=17
    ro.build.version.codename=REL
    ro.build.version.release=4.2.2
    ro.build.date=Fri Jul 26 00:50:45 PDT 2013
    ro.build.date.utc=0
    ro.build.type=userdebug
    ro.build.user=hudson
    ro.build.host=koushik-lion
    ro.build.tags=test-keys
    ro.product.model=m805_892x
    ro.product.brand=coby
    ro.product.name=cm_m805_892x
    ro.product.device=m805_892x
    ro.product.board=m805_892x
    ro.product.cpu.abi=armeabi-v7a
    ro.product.cpu.abi2=armeabi
    ro.product.manufacturer=coby
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=
    ro.board.platform=unknown
    ro.build.product=m805_892x
    ro.build.description=cm_m805_892x-userdebug 4.2.2 JDQ39E eng.hudson.20130726.005010 test-keys
    ro.build.fingerprint=coby/cm_m805_892x/m805_892x:4.2.2/JDQ39E/eng.hudson.20130726.005010:userdebug/test-keys
    ro.build.characteristics=default
    ro.cm.device=m805_892x
    ro.rommanager.developerid=cyanogenmod
    keyguard.no_require_sim=true
    ro.url.legal=removed link
    ro.url.legal.android_privacy=removed link
    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=10.1-20130726-UNOFFICIAL-m805_892x
    ro.modversion=10.1-20130726-UNOFFICIAL-m805_892x
    ro.config.ringtone=Orion.ogg
    ro.config.notification_sound=Argon.ogg
    ro.config.alarm_alert=Hassium.ogg
    ro.carrier=unknown
    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
    init.svc.ueventd=running
    init.svc.recovery=running
    
    
    I:Checking for extendedcommand...
    I:Skipping execution of extendedcommand, file not found...
    E:failed to find "userdata" partition to mount at "/data"
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/log
    E:Can't open /cache/recovery/log
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/last_log
    E:Can't open /cache/recovery/last_log
    E:Can't find misc
    E:failed to find "cache" partition to mount at "/cache"
    W:Can't unlink /cache/recovery/command
    E:failed to find "cache" partition to mount at "/cache"
    Error mounting /cache!
    E:failed to find "system" partition to mount at "/system"
    Error mounting /system!
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/log
    E:Can't open /cache/recovery/log
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/last_log
    E:Can't open /cache/recovery/last_log
    E:Can't find misc
    E:failed to find "cache" partition to mount at "/cache"
    W:Can't unlink /cache/recovery/command
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/log
    E:Can't open /cache/recovery/log
    E:failed to find "cache" partition to mount at "/cache"
    E:Can't mount /cache/recovery/last_log
    E:Can't open /cache/recovery/last_log
    E:Can't find misc
    E:failed to find "cache" partition to mount at "/cache"

    my devices recovery.fstab also used to build the recovery
    Code:
    # mount point    fstype        device            [device2]
    
    
    /boot            mtd            boot
    /cache      yaffs2       cache
    /data            yaffs2       userdata
    /misc        mtd            misc
    /recovery   mtd            recovery
    /sdcard      vfat            /dev/block/mmcblk0p1    /dev/block/mmcblk0
    /nand         vfat            /dev/block/ndda1
    /system     yaffs2      system



    please if anyone could help me resolve this or put me in the right direction i would be greatfull

    if any extra info files or anything is needed please say so and iĺl provide them
     
  2. vampirefo.

    vampirefo. Senior Member Developer

    Joined:
    Nov 8, 2011
    Messages:
    3,828
    Likes Received:
    1,389
    Trophy Points:
    655
    Location:
    Huntington WV
    Tablet / Device:
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    The builder isn't very good, or I guess I should say it's very limited, only some devices are supported, the best method to get a recovery is to build it from source, modify the source to the particular device you want the recovery to run on then compile the recovery.

    I don't have a Mid7035 but I pretty sure that recovery.fstab is wrong, doesn't look right, do you have your original stock recovery?
     
    • Like Like x 2
  3. vampirefo.

    vampirefo. Senior Member Developer

    Joined:
    Nov 8, 2011
    Messages:
    3,828
    Likes Received:
    1,389
    Trophy Points:
    655
    Location:
    Huntington WV
    Tablet / Device:
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    OK I downloaded Folken's 7035 dump, and as I thought your recovery.fstab is wrong, below is from Folken's 7035 dump.



    Code:
    # partition		mount_point		fs_type			device
    
    sdcard			/sdcard			vfat			/dev/block/mmcblk0p1
    system			/system			ubifs			/dev/ubi0_0
    userdata		/data			ubifs			/dev/ubi1_0
    cache			/cache			ubifs			/dev/ubi2_0
    misc			/misc			raw				misc
    kernel			/boot			mtd				boot
    recovery		/recovery		mtd				recovery
     
    • Like Like x 2
  4. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    hello vampirefo

    i can't thank you enough for helping me with this

    wierd thing is the recovery.fstab i used came fom my own stock recovery.img if that makes sense

    i have uploaded the stock recovery to stockrecovery.rar if you want to check it out
    i am breaking my head on this one please if i need to upload dump or do anything just say so and ill do it

    again i thank you for helping me out
     
  5. vampirefo.

    vampirefo. Senior Member Developer

    Joined:
    Nov 8, 2011
    Messages:
    3,828
    Likes Received:
    1,389
    Trophy Points:
    655
    Location:
    Huntington WV
    Tablet / Device:
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    OK that is weird the recovery you uploaded is for a telechips tablet, The original Coby 7035 is a VI Micro.
     
  6. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    ok that's wierd then it says coby mid7035 kyros on the back

    i have a strong feeling it's just some rebranded thing then

    i bought it from here Coby Kyros MID7035-4 Internet tablet 17,78 cm (7) zwart 1 GHz (Cortex 8) Android 4.0 Tablet-pc in de Conrad online shop

    any idea how to solve this?

    if i open a terminal on the tablet and use busybox df -h

    the output i get is

    Code:
    [/COLOR]Filesystem                Size      Used Available Use% Mounted on
    tmpfs                         188.9M     32.0K    188.8M   0% /dev
    tmpfs                         188.9M         0      188.9M   0% /mnt/asec
    tmpfs                         188.9M         0      188.9M   0% /mnt/obb
    /dev/block/mtdblock2    380.0M    247.3M    132.7M  65% /system
    /dev/block/mtdblock5       1.5G     762.5M    773.5M  50% /data
    /dev/block/mtdblock4    512.0M      9.3M    502.7M   2% /cache
    /dev/block/vold/179:1       1.9G    132.9M      1.8G   7% /mnt/ext_sd
    /dev/block/vold/240:1       1.4G      1.1G    285.3M  79% /mnt/sdcard
    [COLOR=#333333]
     
    Last edited: Jul 27, 2013
  7. vampirefo.

    vampirefo. Senior Member Developer

    Joined:
    Nov 8, 2011
    Messages:
    3,828
    Likes Received:
    1,389
    Trophy Points:
    655
    Location:
    Huntington WV
    Tablet / Device:
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    busybox df -h is useful for determining how full your partitions are, but doesn't help in your case.

    just use mount command to see how the partitions are mounted.

    Either way the recovery is going to have to be built manually, the builder isn't going to be able to build a working recovery for your device.
     
    • Like Like x 2
  8. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    Vampirefo thank you very much for the help so far

    iam happy i did read all those threads about compiling one and already have the tools installed in ubuntu to do so
    now i only have to wait till the kids go to bed so i can do my thing

    again thank you very much for this
     
    • Like Like x 2
  9. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    Argh im pulling my hairs now lol

    so i compiled a recovery from the latest CWM source and behold the same error sigh...

    btw this is what the mount command from adb shell tells me
    Code:
    rootfs / rootfs ro,relatime 0 0tmpfs /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
    tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 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/179:1 /mnt/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=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/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=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,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
     
  10. jhax78

    jhax78 Member

    Joined:
    Jul 27, 2013
    Messages:
    6
    Likes Received:
    1
    Trophy Points:
    62
    Location:
    Netherlands
    Tablet / Device:
    COBY MID7035
    ok after some digging around i decided to put the coby aside (for now ofc ) and have a look at this broken TOMTEC exelent 7" i have here too

    i thought lets dump the TOM TEC and check it's recovery.img out
    now i had a problem the touchscreen, charging part and the Wifi card is dead

    after some brainstorming i desoldered the Wifi card and soldered a USB hub in it's place
    and removed the battery and used a old pc PSU to power the hub and tablet

    after that i plugged in a mouse and keyboard and booted it up YESSS!! it works

    both devices work like a charm and i have still the mini usb connector to use for ADB tool and usb storage

    i found out it almost uses the same hardware except the CPU runs @ 1.2Ghz ( Coby MID7030 runs @ 1.0Ghz)
    Ram on the tomtec = 1Gb (Coby MID7035 = 512Mb) + the Tom Tec has hdmi

    it uses the same recovery.fstab and clockwork mod works
    i can make backups and such

    now i am trying to compile some drivers for a usb Wifi dongle i have so i can plug it in the hub and have Wifi again

    the ultimate goal now is to get a old hdmi monitor and buy a touch screen kit from ebay and built the TomTec hardware inside it
    so it will become a big tablet for my kids to play with

    ill try to make some pictures to show it but after i have cleaned the wires and such up a bit on this Franken Tablet

    Greets Jhax78
     

Share This Page

Search tags for this page

cannot mount sd card and misc on cwm

,

cwm for coby 7035

,

cwm recovery null

,

error cwm cannot link executi

,

source code cwm ubifs nand