Develop Bugs

[Q] EVO Unrecognized - WTF??

Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.

buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App

EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...

perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes

Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.

Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.

Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...

What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.

try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST

Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.

I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.

Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever

It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.

buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip

No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.

**BUMP**
Anyone care to take a shot??

holy crap ADB

http://forum.xda-developers.com/showthread.php?t=865685
i followed that very first post step by step....and i still cannot get ADB to work to connect to my device, in fact, HTC sync does not even connect.
any help? i went thru all of those steps twice...not sure what im missing here.
im running windows 7 home premium 64bit. using HTC cable, on brand new 3 hour old G2. it connects to the computer, charges, and works in mass storage mode.

tackleberry said:
http://forum.xda-developers.com/showthread.php?t=865685
i followed that very first post step by step....and i still cannot get ADB to work to connect to my device, in fact, HTC sync does not even connect.
any help? i went thru all of those steps twice...not sure what im missing here.
im running windows 7 home premium 64bit. using HTC cable, on brand new 3 hour old G2. it connects to the computer, charges, and works in mass storage mode.
Click to expand...
Click to collapse
Did you download and install the Android SDK yet?

Heres a ADB set up Tutorial Video you can check out on how to get ADB up and running.

I use mini-adb since I have had complications setting it up on Windows 7. You can find the download link on this post http://forum.xda-developers.com/showthread.php?t=926486
You will just put the files you need to push inside of the folder you set up for it. Eaaaaasy!

simplyTravis said:
I use mini-adb since I have had complications setting it up on Windows 7. You can find the download link on this post http://forum.xda-developers.com/showthread.php?t=926486
You will just put the files you need to push inside of the folder you set up for it. Eaaaaasy!
Click to expand...
Click to collapse
That's exactly what I used.
1.Make sure USB debugging is enabled under settings>applications>applications settings>development on your phone.
2. Connect your phone to your computer using usb.
3 Hold down on the shift key and then right click on the folder where you have adb.exe installed. From the menu select 'open command window here'.
4. A DOS Window will appear and after the prompt type: adb devices
5. This should give you a readout that says that daemon has started and then list your device.
6. if successful, you're ready to go. place/unzip all current and future files to be adb 'd into this folder and follow the commands provided from whatever you are trying to adb.

ok, ill try that soon. for some reason ADB does not like me or win7...ill feel better if it hates win 7 lol.
i did install sdk, just like the link i posted stated to do.

tackleberry said:
ok, ill try that soon. for some reason ADB does not like me or win7...ill feel better if it hates win 7 lol.
i did install sdk, just like the link i posted stated to do.
Click to expand...
Click to collapse
lol...I remember when I first got started I was so intimidated by adb. Its really simple once you get past that first success. It will be one of those forehead in hand moments.

EdKeys said:
lol...I remember when I first got started I was so intimidated by adb. Its really simple once you get past that first success. It will be one of those forehead in hand moments.
Click to expand...
Click to collapse
i dont feel intimidated by it, im more pissed off that the damn thing wont connect...now im just determined to get it to work, even if i never use the damn program lol

tackleberry said:
i dont feel intimidated by it, im more pissed off that the damn thing wont connect...now im just determined to get it to work, even if i never use the damn program lol
Click to expand...
Click to collapse
The only other thing I can think of at this time is to go into device manager on your computer and see if one of the drivers is throwing an error. If it error'd out before you installed the drivers from htc you might have to delete/uninstall in device manager and have your computer once again "find" your phone and install the correct drivers which are now on your computer.

ADB doesn't like me either. I have tried setting it up six times. Twice from fresh Ubuntu installs. I don't like to think that I'm retarded, but it might be the case. I was never so happy as the day that the no ADB root thread appeared in the development forum.

[AlphaRevX] Public Beta 2 for dInc2

Hi guys,
The day has arrived:
AlphaRevX now includes support for the Droid Incredible 2 (HBOOT 0.97).
Hop on over to http://alpharev.nl/x/beta/
We'll use this as a support thread.
This version will also download and flash custom recovery if you want to, after getting S-OFF.
Note: the very first download missed some DLLs for the windows version, that should be included now.

USB Drivers here: http://www.multiupload.com/2OFYWZFCCR
EDIT: Currently does NOT work in Windows. Use Linux.
Small Linux distro here: Download Puppy Linux
Download that, burn it to a CD or put it on a flash drive with UNetbootin.
Boot up and download/make a new key for Linux. Extract it and run as root. (open terminal and run "sudo ./alpharevx")
I couldn't get it to work in vmWare.

mines stuck on waiting for fastboot...im on window 7 64 bit, im gonna try reinstalling the drivers, but nothing else ive tried works
after reinstalling drivers....it now says failed

I am testing with my friend phone's , mine was off with xtc clip .
Thanks for work

Hell. YEAH. I'll be attempting this tomorrow!

Praise the lord, the dream is alive.
Many thanks to all the hard working folks out there. Y'all rock.
Happy rooting to all.
Sent from my ADR6350 using XDA App

It keeps on disconnecting and reconnecting, and that makes it get stuck. I uninstalled the htc sync and drivers and reinstalled the linked driver here. Going to try again. It just flat out failed the first time, got all the way to rebooting the bootloader x2 the second time, but then failed. Both times I heard the bu-dunk of a device being unconnected from my computer. Windows 7 Pro 64 bit
Edit: I tried downloading the alpharev file again, and it had more stuff in it this time. Going to try again. Will post results.
Edit 2:Still no joy. Failed in the same spot. Tried on xp and same thing. Will dig around for my old ubuntu cd and see what happens.

I keep getting stuck at waiting for fastboot also, win7 pro 64 also, might boot into linux and see if it works that way

Are there specific system requirements for this to run?

logan4434 said:
mines stuck on waiting for fastboot...im on window 7 64 bit, im gonna try reinstalling the drivers, but nothing else ive tried works
after reinstalling drivers....it now says failed
Click to expand...
Click to collapse
devator22 said:
It keeps on disconnecting and reconnecting, and that makes it get stuck. I uninstalled the htc sync and drivers and reinstalled the linked driver here. Going to try again. It just flat out failed the first time, got all the way to rebooting the bootloader x2 the second time, but then failed. Both times I heard the bu-dunk of a device being unconnected from my computer. Windows 7 Pro 64 bit
Edit: I tried downloading the alpharev file again, and it had more stuff in it this time. Going to try again. Will post results.
Click to expand...
Click to collapse
TheWh0leTruth said:
I keep getting stuck at waiting for fastboot also, win7 pro 64 also, might boot into linux and see if it works that way
Click to expand...
Click to collapse
Let's put a error summary here:
- Windows 7 32/64bit (or all Windows OS?)
- HTC Sync not installed.
- HTC Drivers (provided by Alpharev) installed.
- switching USB ports tried
- two fastboot attempts
+ specifically for those without .dll problems (resolved).
Also, could a mod possibly merge the three Alpharevx threads..? :/

On Windows 32 it makes it up to the Fastboot process. Enter the key, everything works good, then it gets to the section trying to change the Fastboot and fails each time.

Do I need Android sdk for this, for adb.

jkhonea said:
On Windows 32 it makes it up to the Fastboot process. Enter the key, everything works good, then it gets to the section trying to change the Fastboot and fails each time.
Click to expand...
Click to collapse
Added to summary.

instructions?

jkhonea said:
On Windows 32 it makes it up to the Fastboot process. Enter the key, everything works good, then it gets to the section trying to change the Fastboot and fails each time.
Click to expand...
Click to collapse
this is where mine is ATM, reinstalling the drivers provided seemed to fixed the hang up issue, now it tries to go to fastboot twice and then says failed.
still windows 7 64 bit, i have an XP pc too if that works for anyone let me know plz.

jcampos719 said:
instructions?
Click to expand...
Click to collapse
logan4434 said:
this is where mine is ATM, reinstalling the drivers provided seemed to fixed the hang up issue, now it tries to go to fastboot twice and then says failed.
still windows 7 64 bit, i have an XP pc too if that works for anyone let me know plz.
Click to expand...
Click to collapse
For now there's only the Linux option. Seems like drivers and .dll problems don't happen there.

When i try it it says (Beta key accepted - thank you for participating!) but nothing happens my phone doesnt do anything. any help would be great.

i failed in windows numerous times, went downstairs to use my linux server and worked first time.

jcampos719 said:
instructions?
Click to expand...
Click to collapse
+1 Please

so if linux is the only way right now, am i able to run a VM using linux to use alpharev?

Win7 64bit pc does not Recognize A100 tab

I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.

I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yes, I did download from Acer. I finally went back and reviewed the paper work that came with Tab and found that the company that refurbished for Walmart has a 90 day warranty. I have emailed there warranty support service, hopefully I will hear something from them tomorrow. The only thing I have not tried is a different usb cable which I will pick up tomorrow at good old Radio Shack. If that does not fix the problem then the problem must be in the Tab. I have installed drivers for 3 other android device on the same pc's and never had a problem. Tomorrow is going to be a busy day for me. Dealing with this issue, going to the dentist and I am suppose to get the new Vizio Co-Star so I will be setting that up and then learning how to operate it and seeing what its potential is.

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.

lartomar2002 said:
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.
Click to expand...
Click to collapse
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.

pio_masaki said:
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Da*n, Oh well, back to the drawing board.

lartomar2002 said:
I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.
Click to expand...
Click to collapse
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !

Izzyb914 said:
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !
Click to expand...
Click to collapse
I was at Radio Shack and bought a cable for $20.00, what a rip-off I could have gotten the same cable for $4.95 from Monoprice. Anyways that was the problem and now the pc sees the device.

You can download an Ubuntu Live CD for free, and boot from it without needing to reformat / repartition your hard disk. In other words you don't need to install it, just reboot run the commands you need, take the disc out, boot back to windows and done.
I put together this package that simply includes adb and fastboot, it will install them automatically and allow you to run them with ease.
Download here:
android-cmdline-tools.zip
Instructions:
Boot into your Live Ubuntu CD (or other distro)
Download the above package
Open your terminal emulator (i.e. Gnome Terminal, Konsole, Terminator, etc) do the following:
Code:
cd /tmp && unzip ~/Downloads/android_cmdline_tools.zip
*If you downloaded to a different location you need to correct the path, I used ~/Downloads as it is the typical download location on linux for Chrome and Firefox.
After the file is unzipped you should have the android-cmdline-tools directory in /tmp/android-cmdline-tools
Now lets install adb and fastboot:
Code:
cd android-cmdline-tools && sudo bash ./install-linux.sh
(may request your password if you are on a live cd then it shouldn't, however if it does leave it blank, otherwise you should type your users password)
This will prompt you to make sure you wish to install. Enter Y to install, any other key to abort
If this succeeds, you will now have adb and fastboot ready to run on your device
On linux you shouldn't need any special drivers for these tools to work with the A100 so this package is a small convenient download that is quick to install and use the tools, and should come in handy for usage via Live CD/DVD to access your A100 or most other android devices through adb/fastboot
Good luck and hope this helps!

linuxsociety said:
One quick solution would be to grab an Ubuntu Live CD download and reboot your computer into the Live installation, download the adb and fastboot files for linux. You usually can get them in packages aimed at flashing recovery so you don't have to download the entire Android SDK. Ubuntu shouldn't have a problem seeing your A100 without the need for any drivers or modifying any .ini files. This is an alternative, so that you don't have to wipe your Win7 install. just keep a Live CD for linux laying around, they usually come in handy!!
Actually now that I am thinking of it I'll just make a package named A100-cmdline-tools.zip that contains both adb and fastboot for both windows and linux. Maybe it will come in handy for some of you guys
Click to expand...
Click to collapse
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks

lartomar2002 said:
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks
Click to expand...
Click to collapse
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .

linuxsociety said:
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .
Click to expand...
Click to collapse
Where do I d/l from?

lartomar2002 said:
Where do I d/l from?
Click to expand...
Click to collapse
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179

linuxsociety said:
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179
Click to expand...
Click to collapse
Duh! Sometimes I can be so dense.

[Q] Cant transfer files to my nexus 7 2013

Ok guys I am pretty new to this all this so please bear with me with my bad words. I decided to install a custom rom on to my nexus 7 http://nexus7root.com/nexus-7-roms/c-rom-for-nexus-7-android-4-4-4multi-window/ (mind you I had a rooted kitkat os installed on my tablet before hand) I installed it and everything went fine. Porblem is when I plug my nexus 7 into my computer, the 26 gigs of space I should have (you know so you can do file management droping pics and vids and such) was not there. I dont understand, no matter what computer I was using ANYWHERE I was always able to simply plug my tablet in and start file management. What am I doing wrong? do i need to install drivers ON the nexus 7? if you say I need to install drivers on to my p.c then please explain (weather it was linux or windows I could do file management on there computer with out having to install anything ahead of time.) so what gives? please help.

Simplest first, under Settings>Storage>Menu (upper right on stock)>USB computer connection, is MTP still checked? I'm not familiar with that rom so not sure about locations.
Based on what you said, it seems the PC is recognizing the N7. Check device manager to make sure there are no exclamation marks. You can also "update driver software" or even uninstall it. Windows should then install the device the next time you connect.
After those ideas:
Have you done several reboots? Was it a clean install? You can always run the install again but try wiping cache in recovery first.
You'll get other replies if someone knows the exact situation for your rom.

ritchea said:
Simplest first, under Settings>Storage>Menu (upper right on stock)>USB computer connection, is MTP still checked? I'm not familiar with that rom so not sure about locations.
Based on what you said, it seems the PC is recognizing the N7. Check device manager to make sure there are no exclamation marks. You can also "update driver software" or even uninstall it. Windows should then install the device the next time you connect.
After those ideas:
Have you done several reboots? Was it a clean install? You can always run the install again but try wiping cache in recovery first.
You'll get other replies if someone knows the exact situation for your rom.
Click to expand...
Click to collapse
YOU ARE ****ING AWSOME. I am pretty savy with computer's but never did I know there was a actual option to flick mtp on and off. that said I never ever would have guess to check there. I was stuck up in the developers mode trying to figure out if my usb setting was off. THANK YOU THANK YOU THANK YOU. now I dont have to go back to my old rom.

Thanks. Glad I helped.
Sent from my Nexus 5 using Tapatalk