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
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
JogibaerNr1 said:
Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
Click to expand...
Click to collapse
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
madhouse24 said:
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
Click to expand...
Click to collapse
This worked for me.
Sent from my VS996 using Tapatalk