Hi,
So I have had a good experience with the Kogan Agora 7" a couple of years ago. I flashed a new ROM and my 6 year old still idolizes it. It's perfect for games and movies while traveling and cost bugger all.
I was considering getting my kids a console unit for games but came across the new Quad core HDMI Dongle. I though to myself there is the ticket, When traveling i could use it as a smart TV (plug and play is King) Or it may be possible to replace or augment my Media-portal HTPC system.
I bought one and on the face of it it appears to do all that I require from an Android device like web surfing, mail checking and video streaming fine, except when it came to installing the Playstation controller.
I needed Root access and it was a bit of a pain to get it done. BUT I found it!
I used RK3188_ROOT for CX-919 FW0715 MOD by Everal. found here.
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Enjoy.
So if anyone decides to purchase one of these to play with, you will be glad to know that it is a Rockchip RK188. Weather you think that hardware is good or not is irrelevant but it is useful to know as I tried many methods to gain root but once I had this bit of info it became easy.
Those infinity Pocket PC's may be the same although I can't be sure.
I managed to pair a sixaxis controller and am working on getting it running in a game. I will post if i have any more issues and or success.
Raskern said:
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Click to expand...
Click to collapse
Thanks for posting this info. However I'm not able to get this to work. My PC doesn't recognise the device when it's in "USB Debugging" mode. In the device manager it just appears in "Other Devices" as "KHSTVQCDONA". I've tried updating the software, selecting the "usb_drivers" folder containing drivers provided in the downloading Zip file, and also tried downloading the "Google USB Drivers" directly from Google, but Windows doesn't find the drivers for this device.
If I disable "USB Debugging" the device does connect successfully under "Portable Devices", but clearly that's not much use.
I can't seem to figure it out.
Below are the steps I took in trying to get it to work. I was going to write it as a guide for dummies, but I never got it working...
Download the software from the link above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the bit "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC.
Make sure the Micro-USB port of the device is connected to a power source (either your PC or the provided AC adapter). The port doesn't seem to transfer data.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open the Windows "Device Manager".
In the "Device Manager", expand "Other Devices", then right-click on "KHSTVQCDONA" and click on "Update Driver Software".
Click "Browse my computer for driver software".
Navigate to the "usb_drivers" folder of the software you extracted earlier, select it, and click "OK".
Click "OK". THIS DIDN'T WORK, stating that "Windows was unable to install your KHSTVQCDONA" and "Windows could not find driver software for your device".
[*] Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator".
[*]C:
[*]cd RK3188_ROOT
[*]TPSparkyRoot.bat
At this point I see the following:
*---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
--- Plug in your device, make sure debugging is enabled in Developer Options
--- This script will now copy files over to your N101 II
error: device not found
error: device not found
error: device not found
--- Reboot 1/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
error: device not found
error: device not found
--- Reboot 2/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
--- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and star
t over
Press any key to continue . . .
Click to expand...
Click to collapse
I terminate at this point
I've also done the following
Un-ticked "Verify apps over USB"
In "Security", ticked "Unkown sources", and un-ticked "Verify apps"
At this point I'm totally at a loss.
I had already started using the device initially, so I did a factory reset, but this hasn't helped at all.
Can you see anything I'm missing, or point me in the right direction?
Many thanks in advance! :good:
Ok So I know i messed around with many drivers installing and uninstalling before it worked. I Thought it was the last set that came with the Root method but I may be wrong.
Also I cant remember exactly now but I am pretty sure if you activate the connect to computer you bypass the ROM and connect to the SD card and the U SD. So that would not help when accessing the root files.
Try re-installing the drivers after connecting without the box checked in settings or try the ones from super oneclick 2.3.3 or even the pocket pC ones. you may also need to uninstall the device then reconnect to get a clean run at it. Windows likes hanging onto what it thinks is the best driver even when they don't work or are completely wrong.
Also I ran the batch file form within windows not in console, Just right clock to run as administrator.
I have just used it for a couple of weeks in Japan get let the Kids watch Aview (iView) and it worked a treat. Also the latest sixaxis updates made the controller even better than before. I can probably have a tool around with it later this week but I am busy before then so wont be able to help any. It can be done!
PM me if you cant find the drivers mentioned above I can email them to you.
Thanks for the quick response.
Can you just confirm that you were connecting using the blue Male-Male USB cable, and not a USB-Micro-USB cable?
When I connect to the Micro-USB port it doesn't see a device at all. It just seems to provide power.
When I connect with the blue Male-Male USB cable, unless I have "Connect to PC" ticked, it also doesn't see a device.
I don't have a micro-SD card installed, but that doesn't matter right?
I'll try those drivers you suggest. Thanks.
I am quite keen to figure out what is different but I cant access it for a couple of days sorry.
I definitely used a full sized USB to Connect, I may have used another one, and powered it from the Micro USB direct to power supply. If you are connecting it to the PC for power it may cause problems.
I know that you cannot access the recovery menu unless you are powering through the Micro USB only. Another thing I meant to mention in my original post. I may have posted it elsewhere.
SUCCESS! After I got the SuperOneClick software to forcibly install the drivers the device was then recognised and I could root the device.
Thanks. I'll write up the full instructions.
Excellent!! Thanks for writing up the guide.
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
I had to do things differently......
Used rocketchip_batch_tool_1.7 for drivers, superoneclick didnt do anything.
I ran the batch from the folder on my desktop.
For EACH device re-boot i had to RE CHECK connect usb on cx919 settings.
I got a few errors about no more storage on my device when it tried to copy some stuff, although i have the super user and i tried sixaxis controller which requires root and it worked. Not sure what the files were.
update:
Hmm and it seems SSL websites dont work now as well as Netflix or the Store.
ill have to try something else!
Update:
did a factory wipe. all seems ok now.
TeqTeq said:
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
Click to expand...
Click to collapse
Worked fine since then. All a sudden same prob, no Netflix no store. Wtf?
Just wanted to post an updated root method since i got one of these second hand last week
1. get the universal rockchip drivers, or the latest generic google ones. both worked for me on two different PC's. (including windows 8.1 x64)
2. Enable USB Debug mode in developer options. you know the drill.
3. the kogan device has a "USB" menu in settings, that has a 'connect to PC' setting. turn that on or ADB cuts out shortly after the system boots - turn it off after rooting for it to work normally.
4. connect PC to kogan dongle via the USB port next to the power LED. The other one doesnt work.
5. root with whatever method you want - i used kingo root which rooted it flawlessly first time.
6. have fuuuuun!
3 and 4 stumped me for days til i figured out what was going on. not something i'd ever encountered before, and likely unique to this device and why some people cant figure it out.
Related
I've finally getting around to rooting my x10a, but I'm having a problem with step2.cmd. It echos it's schpeel that select option 6 or whatever, without any error (except for the normal "device not found"). I know that it's supposed to come up with a screen that you should select the 6th option on, but it's not showing up!
If anyone is wondering I do have USB debugging on and I have installed all the drivers.
EDIT: I did include the deviceid txt files inside both of the folders.
Actually, "device not found" is NOT normal. It shouldn't say that if it's working properly.
Steps 2 and 3 (and 5 for X10a) use ADB. There are a few things to check (I'll list everything I can think of, including ones you may have already done):
1. ADB doesn't require DeviceID.txt (it's for X10Flash), so it's not that.
2. Make sure USB Debugging is enabled on the phone (under Settings > Applications > Development).
3. Unplug the USB cable and plug it back in. On the phone, the notification bar should show "USB debugging enabled".
4. Make sure that the SD card is NOT mounted to your PC. The notification should show "USB connected", NOT "Turn off USB". If it does say "Turn off USB", then click it to turn it off.
5. In Windows, double-click on the Safely Remove Hardware icon in the system tray. There should be a device called "adb01 ADB Interface Driver". Don't remove it, just make sure it's there. Hit Cancel/Close.
6. Open Task Manager (Ctrl-Alt-Del) and look for a process called "adb.exe". Click it and hit "End Process". Next time you start adb, it should load up the daemon again.
7. Have you tried rebooting your PC? How about your phone?
8. ADB connects using TCP. If you have a software firewall (e.g. ZoneAlarm, Eset Smart Security, etc.), it may be blocking access. Either make an exception, or just disable the firewall for now (don't forget to turn it back on later). No, a router doesn't count (the phone is connected through USB, not your network).
9. There may be a problem with your Sony USB drivers. Uninstall Update Service and PC Companion (if you have them), reinstall them, and then plug in your phone again so that the drivers are reinstalled. I had to do this to fix a different problem (that second USB Mass Storage device kept connecting and disconnecting).
Did you allow unknown sources?
Sent from my X10a using XDA App
Grospolina said:
5. In Windows, double-click on the Safely Remove Hardware icon in the system tray. There should be a device called "adb01 ADB Interface Driver". Don't remove it, just make sure it's there. Hit Cancel/Close.
Click to expand...
Click to collapse
I've done everything but that, which is not there, what should I do about that?
You know what, the laptop I'm using right now really sucks in the spec department, so it might just be that. Is there anyway to reflash it to rogers x10a?
is your laptop using vista 64? If it is follow this post to fix it. http://forum.xda-developers.com/showthread.php?t=713457
to get through step2, i had to install sony ericsson pc companion, it has the drivers which step2 depends on
carmatic said:
to get through step2, i had to install sony ericsson pc companion, it has the drivers which step2 depends on
Click to expand...
Click to collapse
You are a freaking life-saver, going to try that now.
Mod. edit: not dev related, moved to general
plzz help ... when i enter to recovery mode i cannot do anything
it just come like this
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:unable preocess volume! Skipping...
Checking /cache
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:unable preocess volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
when i go into download mode by plugging usb cable on my phone after pressing vol up + vol down button . my com port does not show on ODIN and windows says - "USB DEVICE NOT RECOGNIZED"
what i have to dooo plzz help ???
i am waiting u
have you tryed reinstalling the usb drivers
got-petrol said:
have you tryed reinstalling the usb drivers
Click to expand...
Click to collapse
yes i have
Try installing the USB drivers on another PC if you have one available, preferably one that hasn't had the samsung connected to it before, then try putting the phone into download mode and re-flashing using Odin
bigdyl69 said:
Try installing the USB drivers on another PC if you have one available, preferably one that hasn't had the samsung connected to it before, then try putting the phone into download mode and re-flashing using Odin
Click to expand...
Click to collapse
i tried many pc and laptop
still same problem
Any help ??? I lost my phone ??? This is the end ????
When you used a diff PC or laptop, which USB drivers did you install? Where did you get them from?
Install the USB drivers from the Android SDK. Install the SDK, then from the SDK manager, choose Google USB drivers under extras/third party.
After this is downloaded, choose update driver to your unrecognized device in device manager and point to the SDK directory. You may get a new unrecognized device and will have to repeat this step.
After this Odin should work.
Sent from my GT-I9000 using Tapatalk
Pierreken said:
When you used a diff PC or laptop, which USB drivers did you install? Where did you get them from?
Click to expand...
Click to collapse
no diff
the one ehich come with kies and i inatall Android SDK as josteink said
still not work
plzz help sam problem
josteink said:
Install the USB drivers from the Android SDK. Install the SDK, then from the SDK manager, choose Google USB drivers under extras/third party.
After this is downloaded, choose update driver to your unrecognized device in device manager and point to the SDK directory. You may get a new unrecognized device and will have to repeat this step.
After this Odin should work.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
still not work with this way ,, plzz help
Why do you post this in "Galaxy S I9000 Q&A" and here?
elhennig said:
why do you post this in "galaxy s i9000 q&a" and here?
Click to expand...
Click to collapse
coz i need fast help ... I don't know what i have to do
i am getting crazy but for i will post here only
fhkal said:
still not work with this way ,, plzz help
Click to expand...
Click to collapse
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
tried to replace USB cale ??
tried to replace USB cale ??
I had a similar problem - resolved cable replacement
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
Not bad, but those drivers are old. It could be "better" to download latest and use those instead
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
Perfect guide, will work 100%
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
still not work mate ... after remove all thing belong to galaxy at the first i get like in the picture .... then done ur way still get USB DEVICE NOT RECOGINZE
THANKS FOR UR HELP
for ur info my bro have same phone and work normal in download mode in the pc and lap top which i worked with it
STILL NEED UR HELP
fhkal said:
still not work mate
...
for ur info my bro have same phone and work normal in download mode in the pc and lap top which i worked with it
Click to expand...
Click to collapse
Then I honestly have no idea. Really. best of luck.
Hi guys
any idea
i am sooo sad coz that ?? Mean lost my phone ?
connect pc to phone, go to devices and printers, delete all the unknown devices from there. Open device manager and remove all the unknown devices. Remove each and every samsung usb drivers and remove phone connection with pc then reboot. Then install fresh drivers from http://forum.xda-developers.com/showthread.php?t=961956 . "Dont connect your phone to pc during all this process!" Now get the phone to download mode and then connect the phone to pc and it will recognize the device. Remember that during all this process only connect phone to pc when in download mode!
Hi, when I plug in my device I can only see two folders and not all the folders I have on it. How do I bring up the dialog "Allow computer x..." again? I think I messed that up. Thanks ^_^
I had the same problem. After a reboot all the folders were visible.
Sent from my Nexus 4 using xda app-developers app
It might be a driver issue. If you haven't already installed the ADB drivers, do so by following this guide pulled from the Rooting sticky:
Jubakuba said:
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
[url="http://forum.xda-developers.com/showthread.php?t=1514942"]Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
Even after all of that, it might not work. Use MTP (Settings>Storage>...>USB Computer Connection. Try turning USB debugging on or turning it off (Settings>Developer Options>USB debugging). Try switching which USB port on your computer you are plugged into (that one gets me every time I plug my phone into a new computer).
Hopefully that helps somewhat. Depending on what else you need to do with your phone, you don't necessarily need the ADB drivers to see the folders, but I find that those drivers + that guide to be the easiest to install and follow.
I have used Nexus Root Toolkit twice successfully on two different computer, but on both occasions that has left the computer unable to connect to the Nexus 10 outside debugging mode.
I think it is "Step 1" in the driver install guide that tells me to:
2.) Launch Device Manager using the button bellow.
- Identify whatever device resembles your Nexus and right click it
- Select 'Uninstall'
- Check the box for 'Delete the driver software for this device'
- Select 'OK'
3.) Unplug your device and Launch USBDeview using the button bellow
- Use USBDeview to uninstall any;
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- ... or ANYTHING else you see that resembles your Nexus.
- In particular look for devices with Vendor ID
- "18d1" or... "04e8"
- Simply right click these devices, and select the option to:
- "Uninstall Selected Devices"
Click to expand...
Click to collapse
After doing this i can no longer connect the Nexus 10 as usb drive or/MTP. If i connect it, it simply says charging, and the Windows device manager doesn't list any new devices at all. Its like it isn't connected at all. If i enable usb debugging, i can use Nexus Root Toolkit without problem.
The computer in question is running Windows 8.1, and i first installed the Universal drivers that didn't work, and then got it to work with RAW drivers.
I assume that something got uninstalled that shouldn't have been, but i don't know what. Any help is appreciated, i don't fancy reinstalling windows
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.