KYROS MID1125 Stuck at android screen

[qpeter]

Hello,
I have spent some time looking at previous posts and trying stuff.

My tablet boots first with the COBY screen and then the Android screen, at this point nothing else happens. I have done a reset using a paper clip.

I suspect it got in this state when i was restoring a backup from an app, the files were meant to go to removable storage but i think they may have gone to the internal drive by mistake. This is only hypothesis though !!

What i have done so far:-
1) installed usb driver to communicate to the tablet from pc. That was an ordeal as using the android sdk drivers do not install unless the ID strings are tweaked to match the ones expected from the tablet.

from "android_winusb.inf"

[Google.NTx86]


;Coby MID-1125
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01



2)Reset the tablet into its debug mode by holding the volume button down on reset. I get the prompt at the bottom left of the screen.

3)Run "Fastboot" . This communicates with the device. I can reboot it and clear the user/cache ok.

4)Used the "Patch_1125_v2" to use fastboot to install a "Unsecure_1125.img" and reboot. This works ok

5)After reboot i run the adb program but get "device not found"


D:\ANDROID STUFF\Patch_1125_v2>fastboot flash boot Unsecure_1125.img
sending 'boot' (5616 KB)... OKAY
writing 'boot'... OKAY

D:\ANDROID STUFF\Patch_1125_v2>fastboot flash recovery Recovery_1125.img
sending 'recovery' (6760 KB)... OKAY
writing 'recovery'... OKAY

D:\ANDROID STUFF\Patch_1125_v2>fastboot reboot
rebooting...


D:\ANDROID STUFF\Patch_1125_v2>adb devices
List of devices attached


D:\ANDROID STUFF\Patch_1125_v2>adb start-server


What can i do now ?? I emailed COBY usa and have received diddly squat.
The hardware must surely be ok to get this far.

I am now stuck, i can't believe how fiddly it is to get back to a known state. On a pc you can boot from another device when all else fails.
I wondered if it is a simple matter to open up the back, take the sdcard out and re-create an image on it using a basic device like a camera or dictaphone ?

thanks in advance.

 

[qpeter]

Got a bit further ..............................

Once the tablet has booted, looked at PC device manager and "gingerbread adb" was shown in yellow - needs a driver.
Checked the ID and it is slightly different to what i assumed. Changed the inf file and driver installed ok.

Fastboot is PID_D00D and ADB is PID_DEED



;Coby MID-1125
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01


So now ADB is communicating:-

D:\ANDROID STUFF\Patch_1125_v2>adb devices
List of devices attached
0123456789ABCDEF device



What do i do next folks ???

 

[qpeter]

did "adb reboot recovery"

got a CWM menu with various options. Used vol + - control to select options.

Chose factory reset one

 

[qpeter]

did "adb bugreport" and gives me a whole screed of stuff. Could anyone decipher the meaning of this ?

Especially :

------ KERNEL LOG (dmesg) ------

ecksum_loop = 0,coor checksum error!

<4>[ 205.230000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.240000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.250000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.270000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.270000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.280000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.280000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.320000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.330000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.340000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.350000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.360000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.370000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.380000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.380000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.410000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.430000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.440000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.450000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.510000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.520000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.530000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.5400

etc. etc.

 

[vampirefo.]

during bootup

adb shell logcat

what os are you running, you posted a lot of info but none is of any help.

start by posting the version of android you are using, what app you restored and if the device was rooted, and how it was rooted, did you use CW recovery to make a backup?

 

[vampirefo.]

did "adb bugreport" and gives me a whole screed of stuff. Could anyone decipher the meaning of this ?

Especially :

------ KERNEL LOG (dmesg) ------

ecksum_loop = 0,coor checksum error!

<4>[ 205.230000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.240000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.250000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.270000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.270000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.280000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.280000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.320000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.330000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.340000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.350000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.360000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.370000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.380000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.380000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.410000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.430000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.440000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.450000] check_sum = 253,checksum_loop = 3,coor checksum error!

<4>[ 205.510000] check_sum = 253,checksum_loop = 0,coor checksum error!

<4>[ 205.520000] check_sum = 253,checksum_loop = 1,coor checksum error!

<4>[ 205.530000] check_sum = 253,checksum_loop = 2,coor checksum error!

<4>[ 205.5400

etc. etc.

unless you are building a kernel and what to debug the kernel the above has no use.

logcats are important debugs aren't

 

[qpeter]

Hello Vampirefo,

I am a total noob with tablets. in fact i deserve a chocolate medal to get this far.
I have sparse linux knowledge.


I am not trying to root the device, it just stopped working and i am try to get back to using it.
I think the android version is icecream. I had no backups of the system when i got the device (i have now!).
If you tell me what to do, i can run the commands.


D:\ANDROID STUFF\Patch_1125_v2>adb shell logcat
/sbin/sh: logcat: not found

 

[vampirefo.]

Hello Vampirefo,

I am a total noob with tablets. in fact i deserve a chocolate medal to get this far.
I have sparse linux knowledge.


I am not trying to root the device, it just stopped working and i am try to get back to using it.
I think the android version is icecream. I had no backups of the system when i got the device (i have now!).
If you tell me what to do, i can run the commands.


D:\ANDROID STUFF\Patch_1125_v2>adb shell logcat
/sbin/sh: logcat: not found

you got lots of problem then, Unsecure_1125.img is a 2.3 kernel (gingerbread) and it's unable to boot 4.0 (icecream)

post output of below

adb shell

cat /system/build.prop

 

[qpeter]

D:\ANDROID STUFF\Patch_1125_v2>adb shell
root@android:/ # cat /system/build.prop
cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CaribbeanSunset_v1.1
ro.build.display.id=CaribbeanSunset_v1.1.0009
ro.build.version.incremental=0009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue May 15 17:06:30 CEST 2012
ro.build.date.utc=1337094390
ro.build.type=user
ro.build.user=marvin
ro.build.host=heartofgold
ro.build.tags=test-keys
ro.product.model=MID1125
ro.product.brand=Coby
ro.product.name=coby_mid1125
ro.product.device=em102
ro.product.board=em102
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Coby
ro.product.locale.language=de
ro.product.locale.region=DE
ro.wifi.channels=
ro.board.platform=tcc88xx
# ro.build.product is obsolete; use ro.product.device
ro.build.product=em102
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=coby_mid1125-user 4.0.3 CaribbeanSunset_v1.1 0009 test-keys

ro.build.fingerprint=Coby/coby_mid1125/em102:4.0.3/CaribbeanSunset_v1.1/0009:use
r/test-keys
ro.build.characteristics=tablet
# end build properties
ro.system.hdmi_max_resolution=fullhd
ro.system.hdmi_active=true
ro.system.hdmi_portable=true
tcc.hdmi.720p.fixed=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.system.hdmi_max_resolution=fullhd
ro.system.hdmi_active=true
ro.system.hdmi_portable=true
tcc.hdmi.720p.fixed=0
ro.media.dec.jpeg.memcap=20000000
ro.media.dec.vid.max_width=1920
ro.media.dec.vid.max_height=1088
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.ra.enabled=1
ro.media.dec.vid.rv.enabled=1
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
persist.sys.output_mode=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
persist.sys.timezone=Europe/Amsterdam
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
root@android:/ #

 

[vampirefo.]

You need to get a 4.0 kernel and flash it.

 

[qpeter]

Where do i get a 4.0 kernel and how do i flash it ??

 

[vampirefo.]

Where do i get a 4.0 kernel and how do i flash it ??

I am looking you flash it via fastboot, just like you flashed Unsecure_1125.img

 

[qpeter]

ok, so it is a ".img" file and i would do a "fastboot flash boot xxxx.img" ??

 

[vampirefo.]

ok, so it is a ".img" file and i would do a "fastboot flash boot xxxx.img" ??

yes

coby_mid1125-seed-0009.zip


this appears to be the version you have the boot.img is inside the zip, flash at your own risk.

came from here

http://www.androidtablets.net/forum...s-coby-kyros-1125-firmware-flash-img-etc.html

 

[qpeter]

That has worked, i have got the tablet working again and i am restoring my apps again.

THe tablet was initially set to german language but i soon rectified that on the settings page

That's excellent, thank you very much for your assistance