Related
I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?
Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.
OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.
OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739
Already been done that road multiple times.
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root
I did OTA update to 4.3 of my N7 3G which was rooted and unlocked (I know now I shouldn't have done it...).
I got an error at the end of the update (when was installing radio).
Rebooted, and got stuck in the google loop...
NOW, I CAN ENTER FASTBOOT MODE, BUT THE PROBLEM IS THAT THE USB DEVICE IS NO MORE DETECTED BY THE PC (I tried Windows XP, Windows 7, Linux), so I cannot re-flash it... It's not a driver's issue, because at USB level the N7 is not even detected when connected to the PC (for instance, dmesg shows nothing in ubuntu and windows does not "beep").
Is it possible that that was corrupted only the "USB stack" of the bootloader??? I could not find a similar issue in this or other forums (??).
Is there any chance to get the USB working again?
Is there any chance to send it for repair to ASUS (I bought it one month ago) with this described symptoms and with the "unlocked" icon on power on?
Is there a payed service to flash it with JTAG?
Thanks to anyone who can give me a clue...
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
c0ldblooded said:
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
Click to expand...
Click to collapse
I solved by sending it to assistance. Excellent service by ASUS... I did not have to pay although the tablet was unlocked/rooted.
Andrea.
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
dilldoe said:
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
Click to expand...
Click to collapse
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
Exactly the case. Unfortunately I can't send it to ASUS
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
dilldoe said:
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
Click to expand...
Click to collapse
That's the point: I could boot into fastboot but 'fastboot device' was not detected by the PC (so I could not re-flash it). Now if I boot into fastboot the PC correctly detects the device...
What I find very, very strange is that an OTA update to 4.3 caused the USB port to stop working!! From what I read googling around, even with a problem during a system update going to fastboot mode (on + volume down) should always allow a connection to the PC for reflashing, or, at least, you could enter APX mode (on + volume up), which is an even lower level mode that is detected by the PC with different drivers (for direct programming, but need encryption key and SW not yet available for Nexus 7).
Maybe it was just a coincidence: an USB hardware failure just before I did the OTA update, which I realized only afterwards, when I needed USB for reflashing...
However the ASUS Service Repair Report states:
Problem/Symptoms: Pad Battery can't be charged. OS ERROR
Replaced Part:
ME370TG BAT COSLI-POLY FPAC
ME370TG MAIN_BD.1G/T30L/NFC
The first one looks the battery (????)
The second sounds like the mainboard...
Andrea
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!
my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.
I've had it working for a long time, then my PC quit recognizing my N7 2012 intermittently. I thought it was a buggy ROM so I tried another. Same problem, so I wiped it and flashed stock 5.0. Same problem
It doesn't recognize it at all anymore, but I can plug in my N5 and N9 and they work great. Has this happened to anyone?
liquidsuspension said:
I've had it working for a long time, then my PC quit recognizing my N7 2012 intermittently. I thought it was a buggy ROM so I tried another. Same problem, so I wiped it and flashed stock 5.0. Same problem
It doesn't recognize it at all anymore, but I can plug in my N5 and N9 and they work great. Has this happened to anyone?
Click to expand...
Click to collapse
Did you try reinstalling the drivers? Download official Google ADB/USB drivers and install them through Device Manager.
Yep, did all that. The same driver runs my other nexus devices fine. I wish I could remember what the Windows error message says...something like 'unplug and plug it in again, if that doesn't work then replace the device'.
Make sure you enable USB debugging on your tablet. And first time you do that and connect it to PC, it should ask you for sth like RSA fingerprint. Accept that and it should work.
stuck in boot loop
Fobos531 said:
Make sure you enable USB debugging on your tablet. And first time you do that and connect it to PC, it should ask you for sth like RSA fingerprint. Accept that and it should work.
Click to expand...
Click to collapse
I see where on a lot of replies that the tablet needs to be in USB debugging. If it's in boot loop, how can you do that? My Vista won't even recognize the tablet any more!
Ok it started working again, so I quickly downloaded the 5.1 image to flash. I got through it but now it just shows the google logo forever. I can get into the bootloader via the hardware keys, but the n7 isn't recognized as a fastboot device, so I can do nothing else with it....
What Windows tells me when I plug it in is this: "The last USB device you plugged in to this computer malfunctioned, and Windows does not recognize it"
In device manager it says this: "Unknown USB Device (Device Descriptor Request Failed)"
I can get it into recovery, but it just shows our little android friend laying on his back with a red triangle.
billycrashed said:
I see where on a lot of replies that the tablet needs to be in USB debugging. If it's in boot loop, how can you do that? My Vista won't even recognize the tablet any more!
Click to expand...
Click to collapse
Try getting into Fastboot. Hold Power button to turn it off. Hold Power + Volume Down button to get to bootloader. Try using Nexus Root Toolkit when you get there or try getting into recovery and flashing something.
---------- Post added at 05:37 AM ---------- Previous post was at 05:35 AM ----------
liquidsuspension said:
Ok it started working again, so I quickly downloaded the 5.1 image to flash. I got through it but now it just shows the google logo forever. I can get into the bootloader via the hardware keys, but the n7 isn't recognized as a fastboot device, so I can do nothing else with it....
What Windows tells me when I plug it in is this: "The last USB device you plugged in to this computer malfunctioned, and Windows does not recognize it"
In device manager it says this: "Unknown USB Device (Device Descriptor Request Failed)"
I can get it into recovery, but it just shows our little android friend laying on his back with a red triangle.
Click to expand...
Click to collapse
Why can't you get into the bootloader with the hardware keys? To get into recovery in your situation, Hold Power Button + Volume Up(for one second only) and the recovery should pop up.
I can get into the bootloader. Just can't get the device to be recognized bu the pc, so O never succeed at flashing anything.
liquidsuspension said:
I can get into the bootloader. Just can't get the device to be recognized bu the pc, so O never succeed at flashing anything.
Click to expand...
Click to collapse
Try using a different USB cable or port, or even try doing all this on an alternative PC.
Its the same on my laptop and desktop, all usb ports, 3 different cables...
I'm starting to think the n7's usb port is going bad perhaps.
liquidsuspension said:
Its the same on my laptop and desktop, all usb ports, 3 different cables...
I'm starting to think the n7's usb port is going bad perhaps.
Click to expand...
Click to collapse
It could be, try taking it to the local service.
Hi guys,
i knew this topic was dicussed a few times, but i didn´t find a solution which fits for me.
Unfortunately i wiped my OnePlus 2 using twrp and since then i can´t used it, it only says "no OS installed".
No USB connection is found, i can not find it as an adb device (daemon not running. starting it now on port 5037) and USB OTG isn´t working either.
I tried different drivers for the device (actually i uses a qualcomm 9008 driver) but nothing helps.
Is there a change to rescue the phone?
Many thanks in advance!
Were you able to get into recovery mode by pressing and holding Volume Up, then pressing Power once? How about Fastboot mode by pressing and holding Volume Down, then pressing Power once?
Also, what recovery do you have?
Tristan Phan said:
Were you able to get into recovery mode by pressing and holding Volume Up, then pressing Power once? How about Fastboot mode by pressing and holding Volume Down, then pressing Power once?
Also, what recovery do you have?
Click to expand...
Click to collapse
I am able to get into both modes, as well Fastboot mode as recovery. But i am not able to get a connection to my pc or other devices.
Using TWRP 3.0.2-2 as Recovery.
try to connect usb storage with otg
chxei said:
try to connect usb storage with otg
Click to expand...
Click to collapse
Unfortunately usb otg is a big problem at the Oneplus 2. Until now i didn´t find an adapter that works.
Seesternfan said:
Hi guys,
i knew this topic was dicussed a few times, but i didn´t find a solution which fits for me.
Unfortunately i wiped my OnePlus 2 using twrp and since then i can´t used it, it only says "no OS installed".
No USB connection is found, i can not find it as an adb device (daemon not running. starting it now on port 5037) and USB OTG isn´t working either.
I tried different drivers for the device (actually i uses a qualcomm 9008 driver) but nothing helps.
Is there a change to rescue the phone?
Many thanks in advance!
Click to expand...
Click to collapse
Hi I had the same problem a few months ago, my phone wasn´t recognized by my pc because I was using the official charging cable so I bought a cheap USB-C cable and I was able to connect it to my pc and reinstall the OS. Hope this helps.
So your device isn't recognized in Fastboot mode? Do you have any ROMs downloaded on your phone already?
coderch123 said:
Hi I had the same problem a few months ago, my phone wasn´t recognized by my pc because I was using the official charging cable so I bought a cheap USB-C cable and I was able to connect it to my pc and reinstall the OS. Hope this helps.
Click to expand...
Click to collapse
My original cable doesn´t work anyway, so i was forced to try another cable. Unfortunately this didn´t work either.
Tristan Phan said:
So your device isn't recognized in Fastboot mode? Do you have any ROMs downloaded on your phone already?
Click to expand...
Click to collapse
I´m not able to get a ROM on my device, this is my problem.
When I try to connect my phone using adb this is happening:
"C:\Users\Seesternfan>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *"
I tried different tips from the internet but i wasn´t able to get a connection with my phone.
Seesternfan said:
I´m not able to get a ROM on my device, this is my problem.
When I try to connect my phone using adb this is happening:
"C:\Users\Seesternfan>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *"
I tried different tips from the internet but i wasn´t able to get a connection with my phone.
Click to expand...
Click to collapse
If you can get your hands on a USB-OTG cable, definitely do so to get a ROM onto your phone. Have you tried MTP? If you enable MTP under Mount in TWRP, does your PC recognize it in Windows Explorer?
Tristan Phan said:
If you can get your hands on a USB-OTG cable, definitely do so to get a ROM onto your phone. Have you tried MTP? If you enable MTP under Mount in TWRP, does your PC recognize it in Windows Explorer?
Click to expand...
Click to collapse
I have two USB-OTG cables at home. The problem is that the OnePlus 2 USB C port is no ordinary USB C port. Till now i didn´t find a cable that works, except the original one which is out of stock.
MTP is enabled but there is no difference to before.
Have tried reinstalling the drivers?
@Seesternfan
Can it be possible to get remote access to your PC, so that I can help you?
Is your USB-OTG cable a USB-C one? I use a Micro-USB USB-OTG cable with an Anker Micro-USB to USB-C adapter.