I'm trying to get adb to detect my Electrify on Windows 8, it would seem rooting and/or installing ROMs is impossible without adb, I have my phone plugged in and all the drivers installed except one "Motorola ADB Interface" of course. The manual driver installer errors out on "Cannot detect Operating System" is there anyway around this, either forcing the driver in, or not using ADB to root?
Use a linux live cd and install the android sdk, or use something like vmware, or try to extract the driver and force it to install in device manager, or dual boot an os that isnt in beta...
Sent from my MB855
The linux live cd should actually work I didnt think about that
I found this
http://forum.xda-developers.com/showthread.php?t=741824
It says its for use with HTC phones but could it possibly work with mine?
Its a year and a half old
Will the driver for my phone be installed/available?
I would post this there but its kind of a dead thread
If you have a spare thumb drive of 4gb or larger laying around you can do a persistent install of ubuntu (or just about any other distro) using LinuxLive USB Creator, which can be found here: http://www.linuxliveusb.com/
If you're not very familiar with linux, persistence is like having your linux operating system on a thumb drive with the advantage over a live cd being that any changes you make (such as installations or saved files) are not lost upon shutdown. So you could install the android sdk (which is all you should need) and then whenever you needed it you could just boot from your thumb drive. If you need help setting up (such as installing the sdk and setting the path and what not) let me know.
-devx
Related
Hi.
I'm trying to make some custom native software for android but I need some help getting started.
What I have done so far is getting a HTC Hero, GSM version.
Flashed a custom rooted ROM. update-hero-generic-2.73.405.38-rooted-signed.zip
Installed the sdk and ndk on Windows.
Downloaded and built the open source android project in a VMWare ubuntu image.
What I'm trying to do now is to get ADB talking to my Hero.
I have USB debugging on in the applications->development menu on in the Hero.
When I attach the phone to my XP PC it detects it and asks for drivers, I point it to drivers in android-sdk-windows\usb_driver, windows won't load them because they do not match the hardware.
I can install the driver manually but eventhough the device manager lists it as working (android phone with android composite ADB interface) adb cant find it.
adb devices just give me an empty list.
I tried this on a Windows 7 box and it seemed to work there, is there something special I need to do to get it working on XP?
Installing HTC Sync (drivers included) should resolve.
Thanks!
I actualy tried that before posting but it did not seem to work.
I now tried it again and this time I manually installed the driver in the HTC directory and now it works.
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
If you want to install Debian, just follow this step:
1. Download this : megaupload.com/?d=EV1SOKWJ
In the debian folder you should change the installer.sh and bootdeb files by this one
Download them:
installer.sh : mediafire.com/file/6j99zi0g1lu4oxq/ashu11x_installer.rar
Bootdeb : mediafire.com/file/osshm94mo1qhd65/ashu11x_bootdeb.rar
2. After that, copy the debian folder unzipped to the root of your sd-card
3. Than open Terminal and type:
Code:
su
cd /sdcard/debian
sh installer.sh
bootdeb
cd /scripts/onetime.sh
sh onetime.sh
That's it!
Credits:
ashu11x
An other way to install it
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
Download Linux Installer here:
uk.androlib.com/android.application.com-galoula-linuxinstall-tFjz.aspx
Install it
Press "Menu" button and choose "Setup".
The configuration apper, the defaults settings work without touch anithing : Debian Leny into a 500M loop file named "Linux.loop" in th sdcard. for lunch this Linux, the script name is "linuxboot".
Detailled functions :
- Install into LOOP file
Check to box if you want use an loop file, a loop file, is a virtual disk, same as image of hard drive. The loop file can be in any directory. I recomand to put this loop file into sdcard with an extension ".loop".
- Server
Name or IP of download server. If this option is empty, the default server is used. To install ubuntu, leave emtpy.
- Distribution type
Type of distibutions, actualy, Debian or Ubuntu.
- Distribution version
Version in type distribution. Warning ! Please check your version with a real type ! Debian can be Lenny or Squeeze, but no Dapper or Jaunty ! This two end, is Ubuntu version !
- Script to lunch Linux
The command to lunch Linux. you can choose own command to lunch. It permit to install Lenny into file Lenny.loop with script name bootLenny and install. after that install debian squeez or Ubuntu Jaunty into a partition of your SD card, and use an JauntyBoot to lunch jaunty. You have two Linux distributions on the same phone !
- Install into (loop)
Enter full path for the filename used as loop. I recommend to /sdcard/myfile.loop
- File size
The size of file allowed for loop. The size is alocated directly, no possible to change or have an dynamic size !
Click to expand...
Click to collapse
The full site with pictures
android.galoula.com/en/LinuxInstall/
where is the /scripts/onetime.sh
http://forum.xda-developers.com/showthread.php?t=1129803
http://forum.xda-developers.com/showthread.php?t=996746
http://forum.xda-developers.com/showthread.php?t=954807
ccownu said:
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
The full site with pictures
android.galoula.com/en/LinuxInstall/
Click to expand...
Click to collapse
on My P500 that one sucks, it worked on 2 gb not on 8 gb, but as told its an rc
Or just do this: ← How to Build CHROOT ARM Ubuntu Images for Android! (UBUNTU ONLY) SHALL WORK ON DEBIAN I THINK!
How to Install Busybox on your Android! →
How to Install Ubuntu on Android!
Posted on February 1, 2011 by admin
For those of you who want to install Ubuntu on your Android smartphone or tablet device, here’s our universal guide on how to do it. (This guide is based off my original guide at NexusOneHacks.net)
*Note – This guide should work on most “rooted” Android smartphones/tablets with no further modification.
We will be running Ubuntu “chrooted” under Android OS, which just means that we will be running a “virtual” Ubuntu OS that runs on top of the Android OS. Your Android OS will work fully (e.g. your phone will keep working normally) while the Ubuntu runs on top of it.
First of all, you should have your Android device “rooted” because you need root access to run Ubuntu off your Android.
Second, your Android OS must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it.
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
How do you know this? Just try installing Ubuntu and if it doesn’t boot, your Android device needs a kernel with loop device support. Otherwise you are fine.
How to Install Ubuntu on Android! (Windows)
First, download the following Ubuntu.zip file (from a preferred mirror), unzip and copy over the whole ubuntu directory to the SD card of your Android smartphone/tablet device:
Download ubuntu.zip http://downloadandroidroms.com/files/get/Nhi9EJWSw7/ubuntu.zip
(Turn USB storage ON then copy over the Ubuntu folder to the root directory of your SD card.)
(What it looks like after copied over to the SD Card)
1) Again, make sure you have your Android smartphone/tablet “rooted”!
2) You must have Android SDK installed or have access to adb.exe.
3) Make sure your Android phone/tablet is in debugging mode. Go to Settings->Applications->Development and make sure USB Debugging is checked ON.
4) Connect your Android device to your computer via USB cable and set the USB mode to “Just Charge”.
5) Your Android device should be recognized as “ADB Device” under Device Manager. If not, install appropriate drivers.
For all HTC Android smartphones/tablets (such as G2 Phone, Nexus One), you can download Windows drivers here:
HTC Windows 64-bit driver download – Click Here to Download Driver
HTC Windows 32-bit driver download – Click Here to Download Driver
6) Open up a command prompt by typing “cmd” under Start->Search programs and files.
7) Browse to your SDK directory where you installed the Android SDK:
8) Then go into platform-tools directory:
9) Type “adb devices” to double-check your Android device is recognized.
In this example, I used an HTC G2 Phone, which shows up at “HT09SR204261″. This is fine. However, if you get an empty device, that means you didn’t install the drivers for your phone/tablet correctly. (Go back to #5)
10) Type “adb shell” to enter the Android shell.
Then type “su” to enter super user mode, then type “cd /sdcard” and “cd ubuntu” to enter the ubuntu directory in your SD card of your Android device.
11) Next, type “sh ubuntu.sh” to run the script which will basically get your Ubuntu image ready to run on your Android smartphone/tablet.
If you get error messages, don’t worry and keep going.
12) Type “bootubuntu” to enter Ubuntu. (Next time you enter Ubuntu, you just need to type “bootubuntu” from your /sdcard/ubuntu directory, no need to run ubuntu.sh again.
If you got “[email protected]” at this point, congratulations! This means your Android OS comes with loop device support and Ubuntu is now running “chrooted” on top of your Android OS!!!
However, if you failed at this point, your Android OS probably doesn’t support loop devices, try installing another ROM or compiling your own kernel with loop device support.
How to Install Programs on your Ubuntu!
Once you’ve got Ubuntu running on your Android device, it’s time to install some Ubuntu packages(or programs).
Type “apt-get update” to update, this is the first thing you will need to do before installing any new programs.
How to Install OpenSSH-server on your Android Ubuntu!
Type “apt-get install openssh-server” to install OpenSSH-server. What is OpenSSH-server? If you want to connect to your Android Ubuntu via an IP address (and SSH into it), you will want to do this.
How to Install TightVNCServer on your Android Ubuntu!
If you want to access the GUI of your Android Ubuntu, you can install TightVNCServer, which allows you to access the Android Ubuntu via Android VNC app on your Android smartphone/tablet or even access it remotely from your desktop computer.
Type “apt-get install tightvncserver” to install.
How to Fix Language Issues
Above is after I connected to my Android Ubuntu via SSH2. Well, for some reason my default language switched to German. To fix that, just type “export LANG=en_US.UTF-8″:
How to Install LXDE!(optional)
Next, we will install LXDE (Lightweight X11 Desktop Environment). Although we can use Ubuntu’s default GNOME (and trust me I love that), LXDE takes up less memory so our GUI access will be faster.
If you like GNOME, you can skip this step though.
Type “apt-get install lxde”
Next, let’s setup xstartup file so that when TightVNCServer is started, the LXDE runs instead of GNOME:
Type “cat > /root/.vnc/xstartup”
Then type:
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then hit Ctrl+D twice and enter to save the file.
How to Start TightVNCServer!
Next, let’s start the TightVNCServer and connect to it from our Android phone and my Windows 7 desktop:
Type “export USER=root” and “vncserver -geometry 1024×800″.
Here, you can change the resolution settings 1024×800 to the resolution of your liking.
Now your TightVNCServer is ready to accept any incoming connections from your phone or computer. Just point to the correct IP address and use port number 5901 to connect.
On your Android smartphone, just download the free app “Android-VNC-Viewer” and set the IP address to “127.0.0.1″ and port number 5901 to connect.
And you should be able to get into your Ubuntu like this:
You can also use desktop software like TightVNC Viewer and connect to your phone.
Do “ifconfig” to find out what your IP address is in your Android Ubuntu.
In this example, mine was connected to “192.168.1.131″.
Then connect to “192.168.1.131:5901″ on your TightVNC Viewer:
Here’s LXDE running on my desktop off my G2 Phone’s Ubuntu:
Troubleshooting
Ubuntu not running?
Try typing “cp” under Android shell and if you get an error message, it means you need to install Busybox. Install Busybox and try again.
Final Thoughts
As said in the video, there will be a lot of improvements in the speed of Android devices in the near future. This year, there will be a slew of dual-core 1Ghz processor-equipped Android devices being introduced. Which just means our Android Ubuntu will run faster and faster.
A tutorial for how to get ADB and DroidExplorer up and running for your Rhodium in Windows Vista.
All this information exists in bits and pieces of posts throughout this (and other) forums, though I felt it would be helpful to compile it in one place.
If you’re running a different version of windows, the differences should generally be fairly minor. Please let me know if there’s any mistakes or modifications I should make here.
ADB refers to the Android Debug Bridge, a tool put out by google, which lets you access your android device via the USB connection for the purposes of debugging it. One particularly useful component is the ability to access your phone from your PC via a terminal window (similar to a command prompt). While not necessarily intended for this purpose, it may be used for a rudimentary level of USB access to transfer files to and from your device. It will NOT let you have any of the advanced functions that a native driver would.
Optional First Step: Download ADB from Google:
You may choose to install the SDK yourself, but this will be incorporated in your installation of DroidExplorer in step 4 if you don't already have the SDK installed.
ADB is part of the Android SDK (Software Development Kit), which you can download from:
http://developer.android.com/sdk/index.htmlInstall the most recent version for windows. For simplicity sake, I suggest you extract/install it to the root, so for example, to
C:\android-sdk-windows\
Optional:
To make your life easier, it’s a good idea to add the folder containing adb to your system environment path, so you can use adb from anywhere on your drive.
To do this, right click on My Computer, click ‘Advanced System Settings’, and then click on ‘Environment Variables’.
Choose one of the PATH variables (either for your user, or the system wide one), and add the path containing the adb.exe file. For example, if you extracted the sdk to the root of C drive as I had suggested, the path would be:
[blah blah, preceding path values] ;C:\android-sdk-windows\platform-tools\
Make sure you remember to have a semicolon preceding the path you’re adding, so windows knows it is separate from the previous entry.
Second Step: Remove previous drivers:
If you have tried to connect your phone (in android mode) to your PC, you may need to go to the device manager and remove the incorrectly-installed drivers.
Third Step: Install Drivers:
The key obstacle here is that there is no driver made by HTC (or others) specifically to connect the Rhodium in Android mode to a PC. While there may eventually one day be such a driver, we need to resort to a work-around.
Drivers Option #1:
A product called PDANet installs software on your android phone and your windows PC that then functions as a PC and device driver set. (The application has other intended uses, as you can read on their website, but these are secondary to our purpose).
Download and install the latest version of PDANet, on both your android Rhodium (via marketplace) and your PC (via the below link):
http://www.junefabrics.com/android/index.php
You will then need to follow the prompts to connect your phone, select the manufacturer (HTC), and the HTX XDA Driver will be installed. Windows security may require you to approve the installation, as the driver is unsigned. After installing, you will need to restart your computer before the drivers will work.
As part of the install, you will be asked to connect your RHOD phone to your computer via the USB cable. The new hardware wizard should pop up, and you should choose to install the driver automatically (given that you’ve previously placed the driver onto your system with PDANet – if you’ve managed to locate the specific driver file as I’ve heard rumors of, then browse to that file).
USB Debugging needs to be enabled on your device, which it is in the stock builds provided here (Settings->Applications->Development->USB debugging).
Drivers Option #2:
Install the HTC Sync Drivers - this has been described for Windows 7, although there are mixed reports as to the success. Information is in the below links:
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
Optional:
To check that your phone is working, type ‘adb devices’ into your command prompt. If you see your device, you’re good to go. (if you didn’t set the environment path to include the location of adb.exe, you’ll have to either cd to the directory first, or type
C:\android-sdk-windows\platform-tools\adb devices(if you installed the sdk elsewhere, then modify the expression appropriately
What can you do now? To see a list of commands you can use, simply type adb from the command prompt.
To use adb to send a file ‘picture.jpg’ to your sd card, in your command prompt, go to the location of the picture, and then type :
adb push picture.jpg /sdcard/to see the contents of /sdcard , type:
adb shell ls /sdcard/Read more about ADB here: http://developer.android.com/guide/developing/tools/adb.html
And for more details on setting up and using ADB, see this (the source for this workaround):
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
--
Fourth Step: Install Droid Explorer
Now that this is working, you may appreciate an application called DroidExplorer, which gives you a GUI that lets you navigate your device in a manner similar to windows explorer. From here, you can copy, move and delete files, as well as install and uninstall applications.
Download and install DroidExplorer from here:
http://de.codeplex.com/
Startup DroidExplorer, and you’re finished. Do read up on ADB and DroidExplorer on their respective pages so that you know both what you can do as well as what you might inadvertently break by blindly playing with options.
As has been said frequently on this website, if you want safe, stick to the default ‘stable’ XDAndroid install for the Rhodium, and keep your windows mobile running as a backup. If you want more, know that you’ll have lots of learning to do, and potentially may loose all the data on your phone and need to spend hours learning and fixing it. You may even brick your phone (make it unusable and unsalvageable – make it about as valuable as a brick).
Helpful Links:
The wiki for ADB on XDAndroid:
http://xdandroid.com/wiki/FAQ#What_is_ADB_.2F_How-To_ADB
Original xda thread on getting USB to work on the rhodium:
http://forum.xda-developers.com/showthread.php?t=849718
If you have any additional comments/changes to suggest, please let me know, and I’ll modify this initial post.
Heh, I always meant to turn that "original XDA thread" into an ADB tutorial for Windows users... but I just never got around to it.
Thanks for putting this together - do you mind if I reference it in the FAQ?
Just skimmed over the how-to - perhaps you should mention that in lieu of the Android SDK, you can simply download Droid Explorer. It usually takes care of the nitty gritty stuff, but pdanet seems to fill in the gaps with driver issues...
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
AkumaX said:
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
Click to expand...
Click to collapse
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
arrrghhh said:
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
Click to expand...
Click to collapse
I installed Droid Explorer and was left w/ 3 (!) Drivers missing, CDC abstract control model ACM x 2, and XDA. After I installed the HTC Sync drivers, it found the driver for XDA and then that gave the ability to let Droid Explorer install the other two *shrugs*
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
slycker said:
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
Click to expand...
Click to collapse
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
AkumaX said:
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
Click to expand...
Click to collapse
That's what VirtualBox is for! lol.
yes i can install usb drivers thank you !
Hello All,
So there is very little documentation on the PX102 online as of yet, let alone AOCOS products in general (at least on english sites which I have scoured). First off, I'm currently using OSX 10.6.8 and have the current Android developer tools package that was downloaded from their site about three hours ago (just to be clear). The PX102 is running 4.1.1 and the tablet is a fresh restore (I had a number of apps downloaded but considered that some may have been interfering...).
I will be attempting to root via psneuter exploit from SuperOneClick v2.3.3, however in the terminal when I execute "adb devices" it returns "List of devices attached" with blank space underneath...
I have tried to kill/restart server, run "adb usb", and a couple other small things to no avail.
Yes, usb debugging mode is enabled as well.
I would really like to attempt/execute this all via OSX, however name an OS and I have it at my disposal...
I admit- I am a noob in various ways, especially to android as this is my first android device. Hoever, I also consider myself to be rather self sufficient in terms of sourcing knowledge and troubleshooting, which is why I humbly ask for guidance in this endeavor.
Also, feel free to ask me any questions about the PX102 (via PM only please! I dislike threads being fuddled with asides...).
I'm not seeing too many people claiming to have these tablets though there is quite a bit of interest in them.
Anyone?
For windows you can try rkbatchtool v1.5 to get the correct drivers
Rooted mine
I rooted mine, wasn't easy though.
First problem, you need a adb driver that works on this rockchip tablet that doesn't have a built in ADB driver. Also I didn't have much luck on the chinese language AOCOS forum.
The only way I found to get one is:
1) download and install the morborobo phone manager software from moborobo.com. Yes this is a risk to your pc. God knows what else it did to my pc.
2) let IT find a driver. It will download and install two unsigned drivers.
3) those drivers aren't enough. You need to generate adb_usb.ini in c:/Users/%username%/.android/adb_usb.ini (if you're on windows 7)
Installing the SDK does that automatically otherwise you need to run "android update adb" or something to generate it
4) put the vendor id at the end of adb_usb.ini in the case of AOCOS the vendor is 0x2207
I tried using a premade adb_usb.ini with all of the vendor ids. That didn't work. It worked when I put the right on only.
NOTE, that vendor ID exists nowhere online. I had to find it by reading it directly from the device using USBVIEW from http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
5) Now you should have a working adb driver. Plug the machine in and type "adb devices". It should see yours
6) now comes the rooting.
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1886460
The script is here: http://uploaded.net/file/0fpyh5c5
the videos showing how are here http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Note there IS a hacked adb driver that doesn't need a vendor ID, BUT it doesn't work for rooting, it's too old to have the restore feature you need for a jelly bean root.
The PX102 is cool, but mine has some problems:
1) the keyboard charge connector is bad, I have to send it back
2) the battery sucks... I'm sending back the tablet too, hopefully that will fix it
3) never drop one of these, mine only fell a couple feet and it's flaky now. :/
4) the camera is fake. It's not the 2mega pixels it says. It's super low quality and maybe vga. They put in bull**** fractal interpolation software to try to fake higher res
The keyboard is no where near as nice as a transformer, the tablet only rests on the keyboard and can fall off.
Still it's a nice machine. I have my memory cards formatted ext2 (from a previous tablet). I can mount them but the machine won't boot with an ext2 card plugged in. I have to take the card out, boot the machine, then plug it in and mount it.
I even managed to install GNU Gcc/ gnu tools
You can also try this: http://www.androidtablets.net/forum/rockchip-rk3066-tablets/46964-root-your-rockchip-3066-a.html
Or this: http://valentijn.sessink.nl/?p=382