odin in linux via virtual box - Captivate Q&A, Help & Troubleshooting

i use linux on my home pc and i have not seen a thread or qestion answered about flashing odin from linux so i tried it myself, forgive me if it has been covered before.
i was able to successfully flash with odin using windeows running inside a vm. my vm software is sun virtual box.
before you do this read the instructions for running odin in widows as i dont go into odin specific detail here.
1. created virtual machine.
2. installed windows XP sp2 on virtual machine
3. installed the newwest version of .net framework(i read that helps but it may have been in reference to kies)
4. dowloaded odin and the proper windows drivers and .pit file and jh2
5. shut down the virtual machine
6. put phone into download mode
7. plugged phone into usb port
8. went into virtual box without the VM running and select
machine>settings>usb
9. clicked the add device icon on the right and clicked on samsung_android[0400]
10. started virtual machine
11. started odin and added the proper .pit file and .tar file
12. pulled batery from phone and put into download mode again and connected the usb and selected devices from the top of the window, selected "samsung_android [0400]"
at this point odin should see the device. if not you may need to reselect the phone in the vm window, do this quickly as there seems to be a time window to start the conection.
simply click start!
this may work in vmware and other vm type software for mac and linux as long as you can mount usb devices to the vm as soon as they are hooked up. if it can be done by com port and not device that may be even better.
i have only done this with virtual box 3.2 running widows XP inside mint 9
if it fails i am not responsible for damage to your device. and in the event it doesn't work go find a friend with windows and run it the proper way! windows machines aren't hard to find!
this worked for my iphone with itunes but was trickier as the driver changes halfway through and that is why i thought this would work.
wine does not work, i have not been able to use wine with software for any device that need drivers when running in widows. so please dont ask!

Not running Linux except for my G1 theme dev,but thanks for the info.
Sent from my SAMSUNG-SGH-I897 using XDA App

I can verify VirtualBox works great for this. Qemu didn't, afaict none of the host USB access options work as documented.

Vmware also works perfectly.
Sent from my GT-I9000 using XDA App

Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.

I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.

ponack said:
Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.
Click to expand...
Click to collapse
wine will not work. it doesn't support USB plugging

Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App

Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Click to expand...
Click to collapse
Yeah, I figured that out after I posted - I was like wait, there's drivers that need to be installed. Oops.

Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Couldn't have said it better, I have tried wine with lots of software but never got the usb end of things to work. Odin does open under wine but I have no idea how to tell it to see the phone as it would see a windows driver that sees the phone.if that makes sense.
There are things I can try but if feel I'd be wasting my time as I don't know enough to be sure I'm on the right path.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

TimF said:
I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.
Click to expand...
Click to collapse
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Dani897 said:
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...

pietro_spina said:
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...
Click to expand...
Click to collapse
well I can see it in download mode now... It was just the stupid front ports on my computer. Seems to prefer the back ones...
so now a device is visible in my windows VM but it is called "Gadget Serial"
When it is in "recovery" windows VM can see it as Samsung etc.. and Odin can connect... But obviously odin needs it to be in "download" not "recovery" for it to work.

I've problems trying it...
In normal mode all works and VM detects correctly...
But when I put the phone in Download Mode, "lsusb" freezes...
any ideas?

Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?

Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.

Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
mystichobo said:
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.
Click to expand...
Click to collapse
this thread was risen from the dead.....
for no reason as you have mentioned. look at the date of the OP, and realize that heimdall wasnt always available

Related

trouble with ADB

I've been following mrkite38's nice guide here:
http://forum.xda-developers.com/showpost.php?p=5096501&postcount=17
I understand it completely, and have done similiar operations before. However I cannot get my phone to popup in device manager in any form. I here the bell that tells you a device has been connected, but nothing ever shows up, no notification, nothing.
Any ideas? thanks guys
Is USB debugging enabled inside android?
mrkite38 said:
Is USB debugging enabled inside android?
Click to expand...
Click to collapse
Yes and also stay awake
I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL
Reddog80p said:
I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL
Click to expand...
Click to collapse
same - maybe it's win7 is the problem. I've had problems with it on winmo as well. I'll try my parents pc sometime (xp)
i cant get it to work right on vista either. never have.
does your device ever show up in device manager? I can't even do that...
berardi said:
does your device ever show up in device manager? I can't even do that...
Click to expand...
Click to collapse
I got it to work on win 7 64 bit. It was a pain, actually I only got it to work on my laptop and not my desktop both with win 7 64 bit.
So normally when you plug in the android phone, 2 things pop up in device manager as Android phone, however one of them always trys to load a driver of a disk drive (probably set up to transfer stuff) however whenever that device is enabled with the driver adb wont work. So what I had to do was, especially b/c win 7 is a bit odd for automatically installing any driver it want with out input from up I had to disable that.
Start run gpedit.msc
in there go to Admin Templates > system > Driver installation > Driver instillation restriction. Enable both "Allow admin to override device installation restriction policies" and "Prevent installation of devices not described by other policy settings"
Ok after doing that you want to get rid of the drivers it tried to put in, so in device manager uninstall them, also download and run usbdeview, and remove the HTC drivers from there too. Might have to restart?
Now the drivers i used for adb was from proxoid, there are 32 bit and 64-bit versions there for you and it seemed to work
So d/l that, plug you phone in and in device manager manually set the drivers, you know right click deceive, update drivers, let me choose, choose form list, have disk etc.
Now the only pain with this method is that when you plug in another device, you have to go to device manager and install the driver from there either by using windos update or manually. If you take off those policies we changed earlier, windows in its great wisdom will reinstall non-working drivers.
Like i said worked on 1 comp not the other.
Good luck.

[HELP]cmd adb error msg...

I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum
Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!
SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
This IS in the wrong forum.
Moved.
Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...
And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )
the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb
The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.
virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that
Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,
I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis

windows 7 usb help

First off sorry I'm sure flammage is coming but I've looked and looked through google and through xda my last ditch effort is to make a post.
I can not get windows 7 to recognize my I've downloaded the latest SDK with usb drivers but each time I try and update drivers I get "windows has determined he driver software for your device is update. Please help me
Go look for the PDANet drivers. You may have to actually install PDANet, but it's painless. Install those drivers, and adb will work for you.
This is mentioned in various stickies and other guides around the board.
This option didn't work please help pda install but didn't overwrite the driver
You need to reboot and hit f8 I believe, then choose the option to allow installation of unsigned drivers. Then try to reinstall the drivers when you boot
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
disgustip8ted said:
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
Click to expand...
Click to collapse
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
codesplice said:
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Click to expand...
Click to collapse
Thank you so much for this help all I had to do was download usbdeview the actual program it self told win 7 what to do so now my nexus one works on win 7, thank you!
No problem! Glad I could help
codesplice said:
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
Click to expand...
Click to collapse
well played, i think youre correct.
ill have to grab that util for work...
disgustip8ted said:
well played, i think youre correct.
ill have to grab that util for work...
Click to expand...
Click to collapse
DSEO is a pretty nifty utility for sure. Provides easy one-click (okay, a few clicks, actually) access to disabling the driver signature enforcement - and even an easy way to eliminate the "Test Mode" watermark that would appear in the bottom-right of the desktop while operating in Test Mode.
There are other methods to bypass the signature enforcement without turning on Test Mode, but I've found that to be the best option. Other approaches use a boot-time hook to basically insert the F8 (and other keys as appropriate - down, down, enter or something like that) keystrokes to "automanually" disable driver signature enforcement for that boot. Any third-party application that accesses things that early in the boot process makes me a bit nervous!

Nexus 7 Driver Failure

Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Works fine for me after about 10 minutes of searching and reading. No need to add to the thread clutter.
RajanB said:
Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Click to expand...
Click to collapse
Follow instructions in the Nexus 7 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1766475
Remember to scroll all the way down in each individual window of the guide to setting up the drivers. I drove myself crazy before I realized that I had missed something important. Also if your desktop is 64bit, you have to use the 64bit drivers. Good luck!
RajanB said:
Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Click to expand...
Click to collapse
Have you downloaded these yet they are new out.
http://forum.xda-developers.com/showthread.php?t=1796165
Install the android sdk. Go to device manager and find your nexus, right click and update driver software. Search computer, select all locations (or something like that) then have disk and browse to your installation. Uh underneath extras there is a folder with the driver you're going to select.
I'm at work so that's a general idea, Google "cyanogenmod adb driver install" and skip the part about replacing the file with a custom one since the nexus is included by default.
Sent from my LG-P999 using xda app-developers app
mi7chy said:
Works fine for me after about 10 minutes of searching and reading. No need to add to the thread clutter.
Click to expand...
Click to collapse
Sorry. Where did you search and read apart from Google? Links please?
Ok, so I done what you guys recommended, in order of when you posted, and non of the suggestions worked.
A screenshot of what happens is attached.
Thanks.
The image didn't attach :S
Wow... user has 4 total posts, all in this one thread and saying nothing worked.
Did you try
Rock-&-Roll-Hedgehog said:
Have you downloaded these yet they are new out.
http://forum.xda-developers.com/showthread.php?t=1796165
Click to expand...
Click to collapse
That will get your the ASUS drivers which will should work on your computer.
All of the root kits also include drivers and they are not that hard to install.
krelvinaz said:
Wow... user has 4 total posts, all in this one thread and saying nothing worked.
Did you try
That will get your the ASUS drivers which will should work on your computer.
All of the root kits also include drivers and they are not that hard to install.
Click to expand...
Click to collapse
Yep. Tried that aswell... if it had worked I wouldn't of come back to ask if anyone had any other ideas as to why it doesn't work..
I thought it was possible to ask questions on here without people saying stuff like that...
clearly you are doing something wrong because the drivers work.
If you need help, you need to provide more details on what you are trying and what the issue is when you try to install... Not just an image of what happens when you plug the device in. That part is obvious that you don't have the drivers installed.
So of the various methods of getting drivers, which ones did you try and what did they say when you tried loading them?
krelvinaz said:
clearly you are doing something wrong because the drivers work.
Click to expand...
Click to collapse
Ok, let me run you through what I'm doing here...
I opened up the zip containing the files.
These are the files that I am greeted with;
amd64
i386
android_winusb
androidwinusb86
androidwinusb64
source.properties
Now what? (=
Those are the drivers... now you need to load them.... Not using Vista for many years... did a simple google search and found...
Code:
Windows Vista
To install the Android USB driver on Windows Vista for the first time:
Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
Select Locate and install driver software.
Select Don't search online.
Select I don't have the disk. Show me other options.
Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.) As long as you specified the exact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to install the driver.
Or, to upgrade an existing Android USB driver on Windows Vista with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane.
Locate and expand ADB Interface in the right pane.
Right-click on Listed Nexus 7 Device, and select Update Driver Software.
When Vista starts updating the driver, a prompt will ask how you want to search for the driver software. Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.) As long as you specified the exact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista might prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to upgrade the driver.
Change the location in the instructions to where you unloaded those USB drivers and you should be on your way...
Try pdanet drivers, just Google pdanet install the proper one(can't remember if they have a 32 bit or 64 bit)
I used their drivers to root the n7. If they don't have asus drivers just.click I don't know. Don't remember exactly the installation step by step, but.its easy enough to get through
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Try pdanet drivers, just Google pdanet install the proper one(can't remember if they have a 32 bit or 64 bit)
I used their drivers to root the n7. If they don't have asus drivers just.click I don't know. Don't remember exactly the installation step by step, but.its easy enough to get through
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Tried that. It all installed correctly, it just won't show up in Computer so I can view my files.
I have unlocked my bootloader... if that helps, which means that Nexus Root Kit 1.5.2 can detect that the Nexus 7 is plugged in.
RajanB said:
Tried that. It all installed correctly, it just won't show up in Computer so I can view my files.
I have unlocked my bootloader... if that helps, which means that Nexus Root Kit 1.5.2 can detect that the Nexus 7 is plugged in.
Click to expand...
Click to collapse
So your having an issue with mtp stuff. Go into setting then click on storage then hit the three dots on the top right corner. Just make sure media device is checked.
Reboot the computer and try a different USB port. These are just so basic steps just do that and see what happens
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
So your having an issue with mtp stuff. Go into setting then click on storage then hit the three dots on the top right corner. Just make sure media device is checked.
Reboot the computer and try a different USB port. These are just so basic steps just do that and see what happens
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ok. Done all that, still the same.
And it now comes up with what you can see in the attached image.
RajanB said:
Sorry. Where did you search and read apart from Google? Links please?
Click to expand...
Click to collapse
search and read the same forums you posted your question in. try the nexus 7 development forum to start.
Sent from my Nexus 7 using xda premium
RajanB said:
Ok. Done all that, still the same.
And it now comes up with what you can see in the attached image.
Click to expand...
Click to collapse
ok seriously..... search these forums for nexus root toolkit 1.5. install that and follow the prompts for installing drivers
Sent from my Nexus 7 using xda premium
uberNoobZA said:
ok seriously..... search these forums for nexus root toolkit 1.5. install that and follow the prompts for installing drivers
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The driver he is having issues with is mtp. This might be a windows error.
I sent you a pm OP
Sent from my Nexus 7 using Tapatalk 2

[Q] ADB Not Working

Hi all. I'm trying to get ADB to work. I installed SDK x86. However, I have a 64bit system. Someone told me the x86 works better. The tf701t connects fine to view files, but when I turn on usb debugging, it plays the sound like it didnt detect properly. Also, in device manager, I have the yellow ! triangle next to K00C and base system device. Any suggestions?
kuthedude said:
Hi all. I'm trying to get ADB to work. I installed SDK x86. However, I have a 64bit system. Someone told me the x86 works better. The tf701t connects fine to view files, but when I turn on usb debugging, it plays the sound like it didnt detect properly. Also, in device manager, I have the yellow ! triangle next to K00C and base system device. Any suggestions?
Click to expand...
Click to collapse
If you are talking about windows, Isnt it a MTP driver issue usually? I thought you had to reinstall that. I wouldnt expect that the x86 version is going to be better. Maybe it is! Either way its a mess. You could try linux on a stick. Its easy!
YayYouFixedIt said:
If you are talking about windows, Isnt it a MTP driver issue usually? I thought you had to reinstall that. I wouldnt expect that the x86 version is going to be better. Maybe it is! Either way its a mess. You could try linux on a stick. Its easy!
Click to expand...
Click to collapse
How do you do "Linux on a stick"?
kuthedude said:
How do you do "Linux on a stick"?
Click to expand...
Click to collapse
Im not sure if you can use it for production off the stick, but you can put it on a usb stick and try them without harming you system. Then install it if you like it and possibly dual boot it if you like it.
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
http://manjaro.org/get-manjaro/
http://www.linuxmint.com/
http://distrowatch.com has a good list of other linux distros.

Categories

Resources