Nexus 7 problems - Nexus 7 (2013) Q&A

Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help

Is your AndroidSDK up to date? Try different cables and USB ports?

nhizzat said:
Is your AndroidSDK up to date? Try different cables and USB ports?
Click to expand...
Click to collapse
im having the exact same problem.. im using the nexus root toolkit ive updated, uninstalled, cleared, restarted.. about all i can handle..
ive succesfully unlocked my device but adb driver/nexus 7 always cant be found or doesnt work in windows 7

nhizzat said:
Is your AndroidSDK up to date? Try different cables and USB ports?
Click to expand...
Click to collapse
Trying SDK now, and yes I tried different cables and usb ports

DjTawmeh said:
Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help
Click to expand...
Click to collapse
This is what I use and it works with all versions of Android that I have used..
Its a universal driver for most Android devices.. It has never failed me
https://www.dropbox.com/s/t6x8szvi4kjun6n/latest_usb_driver_windows.rar?dl=0
Install this driver in Your Device Manager.. First Uninstall the old or current one your using..
then install the driver.. it also works on my Windows 10 test machine...
Edit: You might want to disable Device Driver Signing.. In case the driver refuses to install.

DjTawmeh said:
Hey everyone! My second post here!
So my nexus 7 is having a bit of trouble being recognized by my PC. Ive tried to change between PTP & MTP with nothing, I've also tried turning debugging off. As well as trying to update/reinstall drivers. Didn't work :c
So please help
Click to expand...
Click to collapse
I had exactly the same problem even after re-installing drivers etc nothing appeared to work. Prior to updating to Lollipop I did a factory reset (set up from new) and since then my PC has no problems seeing the Nexus 7. So as painful as it is you could always try a factory reset.

Sounds like you may have the wrong drivers in Windows.
The WUG toolkit has a script that you can follow that will walk you through manually removing all the drivers in Windows. That usually will get you straightened out.

Related

[Q] Epic Fully Bricked???

Hello Everyone,
Captivate owner/user here, but had a question regarding a buddy's Epic. I have looked all over the forums, but have not found anyone else who has encountered this problem, so I apologize if this is a repeat thread. I believe my friend was running BakedSnack v1.6 with the DK28 modem. He went ahead and tried flashing ViperRom Trinity, and got stuck at the Samsung screen. I'm not familiar with flashing on this device, so I dont know the correct methods. I did however try to Odin his phone, and have failed to get my pc/odin to recognize his phone. I've tried every driver file I could find and nothing works. He has access to CWM so I hope it's not fully bricked. I figured his pc would recognize it, having has the drivers previously installed, but nothing. Any feedback is greatly appreciated, thanks.
Try a different cable and a different USB port on the computer. These phones can be picky with the cables.
You are not bricked if you can get to CWM.
Neckberg said:
Try a different cable and a different USB port on the computer. These phones can be picky with the cables.
You are not bricked if you can get to CWM.
Click to expand...
Click to collapse
Originally, we kept trying on my Captivate's cable to no luck. My pc would not even beep or see it. Then we tried another micro usb cable, and this time my pc saw it, but couldnt identify it, due to drivers im assuming. That was as close as I got unfortunately...
Torridred04 said:
Originally, we kept trying on my Captivate's cable to no luck. My pc would not even beep or see it. Then we tried another micro usb cable, and this time my pc saw it, but couldnt identify it, due to drivers im assuming. That was as close as I got unfortunately...
Click to expand...
Click to collapse
get the driver from here: http://www.multiupload.com/O9ZLS8GZP8. This was posted in this thread: http://forum.xda-developers.com/showthread.php?t=963652
amosher13 said:
get the driver from here: http://www.multiupload.com/O9ZLS8GZP8. This was posted in this thread: http://forum.xda-developers.com/showthread.php?t=963652
Click to expand...
Click to collapse
Tried that driver already, still no luck. At first i was thinking my pc wasn't installing the driver correctly until he installed it on his computer and had no luck as well. I installed it multiple times and uninstalled it, still never recognized the phone.
might want to install the android sdk, i actually remember having issues as well on my win7 pc until i did that. then look for adb in C:\Program Files\android-sdk-windows\platform-tools or that relative to where you install it.
Torridred04 said:
I did however try to Odin his phone, and have failed to get my pc/odin to recognize his phone. Any feedback is greatly appreciated, thanks.
Click to expand...
Click to collapse
In order to Odin the phone you MUST be in Download Mode. Turn the phone off the press the 1 key while pressing the Power key.
Appreciate the replies everyone. I did have the phone in download mode when trying to Odin but it failed to show the COM message indicating its been recognized. Download & CWM work & boot up, but the computers don't recognize the device and every driver I've tried installing has had no effect.
Sent from my Captivate
If no com on the screen your drivers not installed correctly, try unplugging and plugin the cable back in. Try different pc with WinXP if u can cuz Win7 is a real pain unless u doing the drivers right after windows installation. Hope this helps.
Sent from my SPH-D700 using XDA App
The same thing happens with my Epic and new roms...
To solve it, I pull the battery, replace the battery and boot with the Samsung "three finger salute"...
Just hold power+camera+volume down and it will boot direct to recovery. Just reboot from recovery and it should work OK.

win7 won't recognize device

I am not rooted. Have yet to figure it out. I have rooted everything I had but this device. Followed albert wertz method for my last device. It was fine but maybe its a samsung update or a win update; I am not sure what the issue is. I am just trying to transfer files from cell>pc vice versa. Drivers are installed and trying the samsung toolkit too but it apparently thinks that debugging mode isn't checked cause it gets stuck there everytime.
bocaccio said:
I am not rooted. Have yet to figure it out. I have rooted everything I had but this device. Followed albert wertz method for my last device. It was fine but maybe its a samsung update or a win update; I am not sure what the issue is. I am just trying to transfer files from cell>pc vice versa. Drivers are installed and trying the samsung toolkit too but it apparently thinks that debugging mode isn't checked cause it gets stuck there everytime.
Click to expand...
Click to collapse
go to development and install the tool kit connect your phone with adb
and it should install drivers
Dreamlogix said:
go to development and install the tool kit connect your phone with adb
and it should install drivers
Click to expand...
Click to collapse
Did it and it says they're already installed.
It shows up in device manager in Windows then?
Your not gonna like my solution
Dreamlogix said:
It shows up in device manager in Windows then?
Your not gonna like my solution
Click to expand...
Click to collapse
It does not show up in the dvc manager. I simply wanna put my pics from my deployment to afghanistan on my pc. I can't figure this out for the life of me cause it was working fine til i did something to my laptop that ended up messing my my wifi driver; ever since then nada for "laptop driver" or the gs3
Reboot to download mode while connected to a adb?
Sent from my SPH-L710 using xda app-developers app
What I did was turn off my phone then plug in the usb cable then power the phone on. That's what worked for me.
das_webos_transformer said:
Reboot to download mode while connected to a adb?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I'm a lil behind. I dont understand what being in dl mode has to do with my pc recognizing the device.
Lancerz said:
What I did was turn off my phone then plug in the usb cable then power the phone on. That's what worked for me.
Click to expand...
Click to collapse
Didn't work. Just booted back up and is as it was before. Only showing charging and the lookout security icon.
bocaccio said:
Didn't work. Just booted back up and is as it was before. Only showing charging and the lookout security icon.
Click to expand...
Click to collapse
I had this same problem the other day bro. Make sure you have the updated drivers that was my problem. What version of the drivers are you using?
cbass15 said:
I had this same problem the other day bro. Make sure you have the updated drivers that was my problem. What version of the drivers are you using?
Click to expand...
Click to collapse
Hope I'm giving the right answer. this is what i found in the C drive under the samsung toolkit folder
Samsung_USB_Driver_1.5.15.0
drivers
I can't post links yet, but do a search on google "samsung l710 drivers" and hit the first link. It should take you to Samsung's website and you can get the drivers there.
Also, check if the device is in the right mode by doing the following:
On the dialer, dial *#7284# (*#PATH#).
Set the UART to PDA.
Click on Qualcomm USB Settings and change it to MTP+ADB.
If it was set to RMNET + DM + MODEM for example, checking the USB Debugging option will not enable debugging.

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...

[Q] USB Device Not Recognized

I bought a Korean Note II (SHV-E250S) and my computer wasn't able to recognize it from the get-go. Now, I installed a rom that caused my phone to be stuck at the first screen and I can't connect my phone in download mode to restore it. I tried a different cord (supposedly OEM), reinstalling kies, downgrading kies, installing just Samsung USB drivers, uninstalling the unknown device driver, shutting down the computer, installing updates, reupdating kies, emergency software recovery/upgrade, switching USB ports, USB debugging on/off (when the phone still worked). I'm literally out of things to try. Any help will be appreciated.
upacreekwithoutapaddle said:
I bought a Korean Note II (SHV-E250S) and my computer wasn't able to recognize it from the get-go. Now, I installed a rom that caused my phone to be stuck at the first screen and I can't connect my phone in download mode to restore it. I tried a different cord (supposedly OEM), reinstalling kies, downgrading kies, installing just Samsung USB drivers, uninstalling the unknown device driver, shutting down the computer, installing updates, reupdating kies, emergency software recovery/upgrade, switching USB ports, USB debugging on/off (when the phone still worked). I'm literally out of things to try. Any help will be appreciated.
Click to expand...
Click to collapse
Tried checking if ODIN recognises it on computer?
bunglebp said:
Tried checking if ODIN recognises it on computer?
Click to expand...
Click to collapse
Yes. It doesn't recognize it either.
upacreekwithoutapaddle said:
Yes. It doesn't recognize it either.
Click to expand...
Click to collapse
Do u have a nandroid backup?
Sent from my AweSoMe ☆♥Note2♥☆
mannyvinny said:
Do u have a nandroid backup?
Sent from my AweSoMe ☆♥Note2♥☆
Click to expand...
Click to collapse
No. Sorry. I made a back up in clockwork recovery but I get an error MD5 mismatch.
Device Descriptor Request Failed (Code 43)
The phone is now soft bricked and I get Device Descriptor Request Failed (Code 43 I sold it to someone with a T-Mobile rom and N7100 clockworkrecovery. They updated clockworkrecovery and now the phone just boots into recovery and then restarts. I cannot get the phone to connect to the computer at all. I get an error. I have tried talking with support but they tell me to try everything that I have already done, such as; different usb ports, cords, computers, had the usb port replaced, reinstalling software (all of them), and restarting download mode.
any development?
I have the same problem, device descriptor request failed.
Luckily, im not bricking the phone yet.
Nothing
I gave up on that phone. What have you tried?
upacreekwithoutapaddle said:
I gave up on that phone. What have you tried?
Click to expand...
Click to collapse
Some search on google told me that we need to fix the usb pin.
Im not yet trying it. Im afraid it will cause another problem. So i leave the phone as it. Even though i cant do anything to update the phone. (Maybe i do have change to update the phone, but it will take a risk)
Try to fix your usb port pin.
On the phone? I had the pins on the USB port replaced and I bought a new USB port from China with no help. I also tried 5 different computers (both mac and pc) as well as different oem USB cords.
Sent from my SM-N900T using XDA Free mobile app
upacreekwithoutapaddle said:
On the phone? I had the pins on the USB port replaced and I bought a new USB port from China with no help. I also tried 5 different computers (both mac and pc) as well as different oem USB cords.
Have you solved it yet? I have the same problem here please send the Fix for this.
Thank You!
Click to expand...
Click to collapse

please help..moto 360 not recognized on computer

Trying to root, I made cable and computer says device not recognized. I have installed, uninstalled drivers multiple times. I have tried 3 different computers. Any ideas what the problem can be??? I really want root!
suzook said:
Trying to root, I made cable and computer says device not recognized. I have installed, uninstalled drivers multiple times. I have tried 3 different computers. Any ideas what the problem can be??? I really want root!
Click to expand...
Click to collapse
have you found a fix?? i really want to root...

Categories

Resources