I am trying to fix a faulty device, which bootloop very frequently, due to a faulty kernel / audio driver. I've found the problem checking logcats, as well as logcats during the boot sequence.
If anyone know how to fix the audio driver, here's the thread: http://forum.xda-developers.com/show...php?p=50961786
I would like to access ADB from this device, this might help, but I cannot get the device detected at all.
USB debugging is definitely enabled, and the device driver is also installed (Not even sure if I had to install a driver for this 2011 device in first place. Device is detected by computer without a problem).
If I type:
If I try:
error: device not found
The faulty device is a Creative ZEN Touch 2, but the name won't be of any help. Let's just pretend it's a generic Android device (Even thought no such Android exists) and forget about the name. The ROM installed on it (Froyo, 2.2.1) was customized by Creative, the manufacturer, since it's not a phone, just a multimedia device.
I was wondering if Creative "blocked" any access to ADB, if that's possible. I do know that Creative "does not encourage self-repair", according to the forums.
I also tried ADB wireless, I pressed the grey button that turned green, and then typed adb connect xxx.xxx.x.108 (IP). On the shell, I got the error:
unable to connect to xxx.xxx.x.108:5555
On the ZEN Touch 2, I found the file default.prop, which contain this:
# # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=1 ro.allow.mock.location=0 ro.debuggable=0 persist.service.adb.enable=0
I've read that this file is hard to modify, other than flash a new boot image.
What could I do to access ADB on this device ? Yes, the device is rooted.
EDIT: I have access to a Linux operating system, if that can make the detection easier. Although I do not have ADB installed on this OS, yet.