I never thought I'd have to go as far as create a thread pleading for help, but after a lot of Google searching I still cannot find someone with the same problem.
I will explain:
I am trying to use fastboot, which I (don't think) I've any problems with in the past.
I can issue commands in normal use via adb from my PC fine.
I can adb reboot bootloader ok, and can get into the bootloader any other way just fine.
I can use the volume keys to navigate the options in the bootloader just fine.
The problem comes with I connect the USB to my PC whilst in fastboot.
Windows fails to recognise the device, and says it may have malfunctioned.
It won't allow me to reinstall the drivers successfully it seems, and seems to have a problem with the USB Host Controller too.
Fastboot immediately freezes, and I'm unable to even navigate using the volume keys, let alone issue commands from my PC.
My question then is twofold:
1. Is there likely to be a problem with the USB port on my device, or some sort of bootloader corruption?
2. Is it possible to return to stock Android without using fastboot?
Finally, I would like to stress that I've seen plenty of similar looking threads, but it seemed that the posters of those threads merely had problems getting in to the bootloader or recovery.
I haven't got that problem, the problem only arises when a USB is connected to the PC, the tablet becomes unresponsive only in bootloader mode.
If anyone has any advice to offer at all, I'd greatly appreciate it.
Additionally, if the problem is solved, I will post a detailed set of instructions in case anybody else should encounter a similar problem in the future.
__________________________________________________________
Update for anyone who happens to read this in the future:
[This guide](http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html) has a useful FAQ at the bottom which helped a little.
I think I managed to determine the problem was likely a duff usb connection, either on my Nexus or on my computer.
I was able to just about hobble through by keeping the cable in the same place.
In case it wasn't just this, this is what I did:
1. Flashed TWRP recovery from their app.
Went into bootloader and failed to do anything
2. Flashed CWM recovery.
Managed to be recognised in fastboot.
I still had problems with my Nexus 'malfunctioning' -- possible the USB.
I updated the drivers using the ones from [this thread](http://forum.xda-developers.com/showthread.php?t=2588979).
3. Flashed a new bootloader image immediately (there were rumours that a dodgy version had been released accidentally). [This](http://www.androidfilehost.com/?fid=23060877489996594) is the one I used.
Then I managed to get the stock ROM flashed, and the bootloader locked up again.
Fastboot freezes whenever USB plugged in
I'm having a problem with this step...
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options.
however, whenever the usb is NOT plugged in (and rebooted bootloader) the button work just fine.
I don't have a recovery currently installed.
The issue is not with drivers on the computer,
happens while usb plugged in both windows and linux or simply just plugged into a wall outlet to charge and with different USB cables.
I need to load fastboot but i'm having this issue. Is the device bricked without hope?
any help would be appreciated.
Nexus 7 2012 Model (grouper)
Boatloader version 3.34
Related
Anyone else here with the bootloader problem of not being able to select anything if the usb is plugged in?
Saw the same behavior on two N7's so there's probably a reason for it.
anyone know how to fix this?
From what ive been able to gather, through trial and error, is that if you have the bootloader drivers installed and visible through fastboot , it should enable you to choose which you want and even boot into recovery. booting into the bootloader not plugged in allows me to switch through the options. however when i plug into usb it freezes until the computer recognizes it as an android bootloader device. attempting to reboot into recovery through the bootloader without USB plugged in has always failed for me.
I can let my n7 sit there for hours and my computer still can't use it. It detects it but it says its not working, and i can't use volume controls to change selection.
A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
Got myself a google LG Nexus 4.
Connecting via USB - 2 different cables, 2 computers, 3 different operating systems (archlinux, debian, windows vista ) - i get nothing (*).
the phone does not acknowledge that it is connected to a computer, but it charges ok.
the computers do not recognize the phone in any way, not even in dmesg (or device manager in windows).
i have tried changing options inside the phone (debugging on/off, mtp/ptp...), even a full factory reset, and going into recovery and wiping cache/dalvik cache. - nothing.
wiggling the cable and such does not help.
i even replaced the usb connector, no change whatsoever.
so something tells me that it is not a hardware problem.
the phone has been upgraded to android 5.0 (before i became the owner).
my endless searches show that nobody knows what's going on, it might be hardware fatigue, it might be related to the upgrade to 5.x, it might be a firmware problem...
any helpful pointers, including downgrading & softbricking the system would be helpful (i just want to install ubuntu phone onto it).
(*) my other android phone connects ok with both cables, to all machines and operating systems.
With the phone in fastboot or recovery mode, is it recognized?
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Go into device manager with your phone connected and uninstall the drivers. Then install "universal adb driver"(google it it's from Koush) with your phone NOT connected.
audit13 said:
With the phone in fastboot or recovery mode, is it recognized?
Click to expand...
Click to collapse
i tried adb, the device list is empty.
booting into recovery, replugging the usb cable, i still get nothing. it's like there's nothing to communicate to, both from the computer's and the phone's point of view.
i will have to play with fastboot (i gather it works only while the phone is booted into recovery?), but i doubt it'll change anything.
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Click to expand...
Click to collapse
do you mean the connector from the usb port, that flat cable snap-on thingy (far right on this image)?
is it realistic to try to fix that?
PS:
meanwhile the battery drained completely and i had a "Red light of death" which i managed to fix like this. i think it will take a while to recharge properly.
Adb commands will work with the phone booted into the rom. Use fastboot commands with the phone in fastboot mode.
Yes, the flat part at the it her end of the USB cable is what connects to the motherboard and is not worth fixing if that is causing the charging problem.
With a red LED, just connect it to a 2.0 amp charger using the original charging cable and let it charge for a few hours.
thanks again.
next thing i realized that the volume rocker isn't working (anymore?).
so i can't boot into recovery.
i don't know how, but once i managed to get into recovery, but couldn't make any choices in there.
anyhow, that sort of cinches it: i'm done with this phone. project failed.
(nevermind, it was a cheap ebay shot)
ubuntu phone will have to wait.