Hey XDA users,
This is my first attempt at flashing an android device (I'm a recent convert from Apple). Needless to say, things aren't going particularly smoothly.
I can't get the Nexus 7 ToolKit V4.0.0 to recognize my device in ADB mode, even though it shows my serial number in Fastboot mode.
I followed all of the troubleshooting suggestions provided by the guide, and nothing seems to work.
I'm terrible stumped.
Any help would be greatly appreciated!
Thanks,
-Foxgrin
Have you installed the drivers correctly? It seems that the ADB drivers were not properly installed. Use a program called USBdeview and delete anything that pertains to your Nexus 7. Then plug your nexus 7 again and have it install the drivers.
Related
I have been having a difficult time getting the right usb drivers for my 2013 nexus 7. I have tried the manual download fron SDK, various toolkits available (wugfresh, etc.) with no success. The furthest I got was when I tried to unlock with the "fastboot oem unlock" command, i got a "waiting on device" message.
Is there a problem with Windows Vista loading these drivers.
Please help!! I'm about to throw this tablet through the window!!
BamaRalph said:
I have been having a difficult time getting the right usb drivers for my 2013 nexus 7. I have tried the manual download fron SDK, various toolkits available (wugfresh, etc.) with no success. The furthest I got was when I tried to unlock with the "fastboot oem unlock" command, i got a "waiting on device" message.
Is there a problem with Windows Vista loading these drivers.
Please help!! I'm about to throw this tablet through the window!!
Click to expand...
Click to collapse
For adb and bootloader, use these drivers direct from Google:
http://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
You might have previous attempts at install or previous drivers blocking the proper install.
Use Nirsoft USBDeview to get rid of any old Nexus 7 entries
I did that on the wugfresh toolkit, but still have issues loading a good driver that will let me unlock!
Even worse trying to find a driver which works across multiple devices..
what makes the android USB driver situation so unstable? shouldn't the devices just meet the MTP spec and no driver updates would be needed?
(obviously that is not true, but)
It has been a painful process, at least in my case. By watching the videos it seems simple. I have seen where Samsung drivers have worked in some cases. I'm wondering if Vista has something to do with it. I couldn't get any of the wugfresh toolkit drivers to work, which even had Samsung drivers. Then, finally windows loaded a Composite Android Device driver that let me get all the way to the unlocking command then said "waiting for device"??? I really want to root this tablet!!
BamaRalph said:
I did that on the wugfresh toolkit, but still have issues loading a good driver that will let me unlock!
Click to expand...
Click to collapse
Did you try all of them I had problems to with wugfresh but I used the PDA drivers and it worked for me make sure all previous drivers are deleted.
sent from my Nexus 7 2nd gen using tapatalk 4
zim2dive said:
what makes the android USB driver situation so unstable? shouldn't the devices just meet the MTP spec and no driver updates would be needed?
Click to expand...
Click to collapse
The devices don't alway advertise themselves as MTP compatible so the OS doesn't know to use the MTP drivers. It is a bug in the implementation on those particular devices.
For example, Nexus 7 2013 advertises MTP compatibility when USB debugging is turned off, but stops doing so when USB debugging is turned on.
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!
Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!
When I plug in my phone to my PC the only thing that happens is it begins charging. Doesn't show signs of adb working, only thing that happens beside charging is my pc says it's an Unknown Device.
I tried all sorts of things, like USB Debugging on and off, MTP on and off, PTP on and off, I think even fastboot doesn't work. I tried to install all kinds of drivers (official, unofficial, uninstalling them afterwards if they didn't work ofc), I tried Wug's toolkit, nothing. I tried killing adb server then restarting it - nope. I even tried all of my USB ports, both 2.0 and 3.0. Also tried 3 different roms/kernels (L dev preview, Purity and Mahdi), didn't work aswell.
Things seem pretty hopeless at this point :/
Download wugfresh toolkit... look In the section of driver installation... They'll help you out
Sent from my Nexus 4 using XDA Free mobile app
driver installation...
As I said, I already tried the driver thing in Wug's Toolkit. Also my Windows allows unsigned drivers.
Bump :/
monitobeko said:
Bump :/
Click to expand...
Click to collapse
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
venu123 said:
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
Click to expand...
Click to collapse
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
monitobeko said:
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
Click to expand...
Click to collapse
Might be windows 8/8.1 giving you driver signature grief. Try the Universal adb drivers:
http://www.koushikdutta.com/post/universal-adb-driver
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .