FORUMS

A Helpful Guide to Music Streaming Services

With the launch of Apple Music, music streaming services have recently gained a lot of … more

An Inside Look at the Redesign of Business Calendar

The much-acclaimed calendar app, Business Calendar, underwent a major design … more

New Android One Device Dead On Arrival

Today, Google announced the second generation of Android One devices, with the new Lava Pixel … more

OnePlus 2 Leaked, Actually Prettier Than Expected

The OnePlus 2 launch event is mere hours away, and we have been treated to clear, … more

[Q] Creative ZiiO doesn't appear on adb devices list

3 posts
Thanks Meter: 1
 
By Stawonog, Junior Member on 21st December 2010, 01:15 PM
Post Reply Subscribe to Thread Email Thread
Our company bought new shiny ZiiO 7" to test some mobile aplications, but we are having trouble getting started. 'adb devices' shows empty list, but the device appears on 'lsusb' list (Bus 002 Device 007: ID 2350:0102) and we can access files by USB connection. We tried to set it up using standard steps (enable debugging, list devices, add vendor id, set permissions and restart adb server). We also tried several systems (Ubuntus and Windowses) and PCs. It's our first Creative device and first device with such problem.

So, is it known problem or maybe the device is broken? How to set up adb and device to work together on Ubuntu 10.04?

There's no ZiiO forum, so I posted here - hope it's ok.
 
 
30th December 2010, 05:51 PM |#2  
Junior Member
Thanks Meter: 0
 
More
i have the some problem, any ideas?
4th January 2011, 08:25 AM |#3  
OP Junior Member
Thanks Meter: 1
 
More
We managed to solve the problem. Here is what you should do on Ubuntu:
- add to xx-android.rules flowing line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="2350",SYMLINK+= "android_adb",MODE="0666"
- restart udev
- add folowing line to ~/.android/adb_usb.ini:
0x2350
- restart server
We also have the solution for Windows and Mac.
4th January 2011, 06:01 PM |#4  
Junior Member
Thanks Meter: 0
 
More
this work fine with MAC OSx too.
7th January 2011, 10:04 PM |#5  
Junior Member
Thanks Meter: 0
 
More
Sorry to be a newb, can you tell me how I can edit the file? I am a bit rusty with this stuff. Thanks!
19th January 2011, 12:46 AM |#6  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Stawonog

We managed to solve the problem. Here is what you should do on Ubuntu:
- add to xx-android.rules flowing line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="2350",SYMLINK+= "android_adb",MODE="0666"
- restart udev
- add folowing line to ~/.android/adb_usb.ini:
0x2350
- restart server
We also have the solution for Windows and Mac.

Could you please outline the solution for Windows?

Thanks in advance.
19th January 2011, 08:31 AM |#7  
OP Junior Member
Thanks Meter: 1
 
More
here you go:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart server
The Following User Says Thank You to Stawonog For This Useful Post: [ View ]
20th January 2011, 02:03 PM |#8  
Member
Flag Köln
Thanks Meter: 0
 
More
you seem to be quite knowledgeable
so might be you know how to get permanent root on the ziio, I only get till temp root then tried this

F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit

But I always get su: unknown id: root in adb shell and su: must be suid to work properly in terminal emulator
20th January 2011, 03:28 PM |#9  
dbzfanatic's Avatar
Senior Member
Thanks Meter: 282
 
Donate to Me
More
If you have an xbin or sbin folder try moving su there, then chmodding it. That's the method I used to root the android emulator. Link is in my sig if you think it might help you out/give you some ideas. The emulator lost root on reboot but that's because it was a virtual device, pretty sure a real phone wouldn't lose root on reboot.
21st January 2011, 01:39 PM |#10  
Member
Flag Köln
Thanks Meter: 0
 
More
OK gave it a shot but didn't work either. No x or sbin on the ziio to begin with. will try some more later..
25th January 2011, 06:16 AM |#11  
Junior Member
Thanks Meter: 0
 
More
Is there anyway we can hack the ZiiO and root it with Android 2.2 ourselves?

Read More
Post Reply Subscribe to Thread

Tags
adb, creative, ubuntu, ziio
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes