Google Nexus 5 :: Bootloop And USB Error - Device Descriptor Request Failed
Aug 6, 2015
A friend gave me his nexus 5 because it have a problem, one day the phone was stuck on boot screen (the flying balls of lollipop) and to add difficulty (can't be easy right?) windows doesn't recognize the phone but it recognize my nexus 5 with the same cable on the same usb port....
I get a "Device Descriptor Request Failed"(the usb port on the nexus seems to be ok) but my nexus get none ... Is it a hardware issue ? I heard that there is issues with nexus 5's motherboard...
I can enter the fastboot and recovery but after a wipe, still stuck..... Not rooted and booloader locked....
Since the last windows update from this week windows cant detect my nexus 5. I tried everything. It keeps showing up like "Unknown USB Device (Device Descriptor Request Failed)" And i doesn't show up immediately when i plug in the phone. It takes like 10 seconds, then it shows that with a yellow triangle.
I've been using Nexus 5 since Nov '13, but this is the first time i'm facing a serious issue in my device.I was browsing through Chrome and my Battery was 73%, all of a sudden my device rebooted and here comes the main issue/problem.My device is suffering a boot loop only displaying the google logo for 3-5 seconds and again it reboots.Occasionally the boot animation starts but no success, again it reboots.
I tried to enter fastboot menu, it enters but it doesn't stay there for not more than 2 seconds. So I can't make any choice over there.I tried all the combinations (VOL UP+ Power, VOL DOWN+Power, pressing all the buttons), but its of no use.My device is out of power now.Even when I plug my device to charger/computer its not showing the battery charging animation instead the reboot loop occurs.I suspect it can be a problem with the power button in the board.
My device details: I'm running Stock Android 4.4.4 with stock kernel.(not modified any system files) TWRP recovery V 2.7.1.1 UNLOCKED ( @present Locked) ROOTED. @present Unrooted)
My Nexus 5 is stuck at the flying dots after Lollipop OTA update. Already try factory reset. Cant connect to my Lap (running Windows 10) because it says in the device manager: Unknown USB Device (Device Descriptor Request Failed), so I cant manually update the driver and cant access it with ADB and Fastboot tool. The device has no USB debugging enabled. In the old computer where I used to connect the device and has the drivers installed says the same thing in device manager as my new laptop.
I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: [URL] .... After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission).
Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Nexus on bootloop tried every method ,most of them . Flashing new factory image is also of no good. Cleared cache , factory reset and still on bootloop. On flashing lollipop factory image it gets stuck on boot loop and on flashing KitKat factory image or using any custom ROM like cyanogenmod it gets through boot but is unable to detect sim and apps like play store and camera keep crashing and refuses to open.
A colleague of mine (yes honestly it wasnt me) reported that his Nexus 5 was stuck with as he put it "the wee android man in the middle of the screen" Then, before he give the phone to me to look at he said that he had tried some things with images to get it to work but it didnt work. so truthfully i am not sure what he has done or not done but the phone is stuck as follows:
When you turn the phone on you have the android robot which looks like it is doing an update.
I have gone into bootloader where I have the option to Start, Recovery Mode, Restart Bootloader and Power Off. The lock state in the Fastboot mode shows unlocked.
No matter which option you take (Even Recovery) it just goes back to the android screen that looks like it is trying to update....i cant get to the android with the exclamation mark that would allow me to do a factory reset. At this stage of the game im not worried about any lost data etc.
Well as the title says, I modified framework-res.apk to change navbar dpi (using apktool and copying original META-INF folder and Manifest in my compiled apk). The problem is that when I push the framework to the N5, it wont boot.
Code:
adb reboot recovery adb shell mount system adb push framework-res.apk /system/framework/framework-res.apk adb -d shell chmod 644 /system/framework/framework-res.apk adb reboot
And I also tried to take a logcat when in bootloop (idk if it's stupid or not):
Failed to parse /system/framework/framework-res.apk: Failed to collect certificates from /system/framework/framework-res.apk
I used adb to install TWRP onto my Nexus 5. Now it is in a bootloop, and TWRP does not seem to be able to mount anything. When it reboots it looks like it automatically goes to the TWRP where it says it is running OpenRecoveryScript but it is unable to mount anything. I tried a boot start to Recovery and it worked but when i tried a factory reset it says the same thing.
I had a new nexus 5 running on android 6.0 ,I was planning on rooting my phone , had the oem bootloader unlocked - the twrp installed , however after flashing the elementalx and beta supersu , my phone was in a bootloop for 4 hours. I did everything as told in the tutorial video for rooting and now i think that by flashing the nexus 5 stock rom it might be useful in recovering my phone... How to flash stock rom on nexus... when I tried getting into the recovery mode it was still in twrp ...
I was using the Cataclysm Rom for months without any problems. Today I restarted my phone (I do this every other day, when it gets a little bit slow) and it stuck in bootloop.
I tried wiping dalvik/cache, doing a factory reset, reflashing Cataclysm, nothing worked. So I decided to go back to stock (using [URL] ....) and I'm still stuck in a bootloop every time. I can access and use fastboot/stock recovery in the normal way, but it won't boot.. What I could do?
My unlocked Nexus 5 during kingroot rooting process my laptop shut down and now its in a boot loop stuck at logo. I can bring up bootloader and ADB but no back up or recovery on phone hard drive.exactly what do I do?
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Got notification that my OTA had downloaded last night, started the install process only for it to fail part way through, Had the android man with red triangle with 'error' underneath it. Since I booted back into 5.1.1 I can't start the process again to upgrade
My mum's N5 is completely stock - I can't believe i'm having issues with the only non-rooted device in my house!
I applied the OTA 6.0 update but when starting the phone i get a never-ending loop of "unfortunately ... has stopped" about lots of apps, and google services framework, process.acore, play services, etc
I got into stock recovery and cleared cache, no change
Any way to fix it without wiping data/factory reset?
I'm running Cataclysm ROM (the Sept. 10 beta), Franco kernel, and I'm rooted and use Xposed. I receive this error when I try to add a card in Android Pay: "Android Pay cannot be used: Google is unable to verify that your device of the software running on it is Android compatible". I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. Wallet still works as it always has.
Okay so I've just received a refurbished Nexus 5 from Google as my old one had a hardware power button fail. Anyway I've decided this time round I'm not going to root and wanted the phone completely stock so thought I would do all the OTA updates it gives me before I start messing around with it but have a slight problem.
The phone came installed with 4.4.2 and did an over the air update to 4.4.4 it now wants to upgrade to 5.0.1 however whenever I download the update which is 479.5MB it downloads it and tries to 'verify' install and then I get a 'verification failed' every time and it doesn't install? (may I add I have literally not touched the phone it's come straight from Google, the only thing I've done is logged into my Google account and updated whatever stock apps needed updating in the play store)
All my new contacts fail to save. When I enter the name and number, then hit Done, I get the "New contact saved" msg. But, a few minutes later, the contact is gone.
When I restart the phone, I get a black box in the middle of the screen "Autorization Failed" - with no reference to which app it is. Is there anyvway to tell which app is throwing this message?
I just bought a Nexus 6 phone recently. I tried connecting to the Wi-Fi where I work but it keeps saying Authentication Problem beside the WiFi name and will not connect. I just updated to Lollipop 5.1.1 thinking this would work but I am still having this issue. I don't want to have to use my data whilst at work all the time!
I flashed a custom ROM to my nexus 5 and was using it for the last few months. But today, I decided to rollback to latest stock ROM. And I double clicked "flash-all.sh" and it failed after few seconds. I could not see what happened so I again ran the executable under terminal and seen it failed again. I just remmebered that I hadn't unlocked the bootloader before running the script. Now, the phone is not turning on at all. It only vibrates if I hold the power button for some seconds, 6 seconds actually and if I hold the button for longer times, it keeps vibrating every 6 seconds.
I am not even getting the Google logo thing.
root@localhost:~/Hammerhead/hammerhead-lmy48b# nexus-fastboot flash bootloader bootloader-hammerhead-hhz12h.img < waiting for device > target reported max download size of 1073741824 bytes sending 'bootloader' (3119 KB)...
I have been trying to connect my nokia n900 to my pc that runs windows 7. I am using usb cable that came with the phone. I get an error messege on the computer when using mass storage mode that says "failed to install device driver'. I downloaded PC suite and tried PC suite mode. I got an error message saying "your phone is in file transfer mode. quit file tranfer mode to proceed" how do I quit file transfer mode?
Am trying to update my bb but when the module is been download, it always stop on the way. The report is "An error has occur when dowloading software for your device.lease, check your internet connection or try later, if the problem persist". I have a very good working internet connection. I have tried everything posible but still having the same. The whole module to download is 821 and the module already downloaded is 710.
I was wondering how to resolve an issue I've been having with my Bold 9700. I'm placing it in this forum since it doesn't appear to be a model specific issue. When a geolocation request is made (BB Maps, GPS settings in options, etc) the device tries to use aGPS first. When it does I get messages in the device log saying it tried various transports (BIS,WAP,WIFI,TCP) and they all failed. It seems to be failing due to a dns issue. I've tried using it on my home wifi to rule out blocking of the DNS by my carrier (AT&T) and it still has the same issue. The device is on BESX with an IT Policy that is set to allow most everything and BIS.
The specific log entries are: Geolocation START Geolocation - Transport failed: BIS Geolocation - Transport failed: MDS Geolocation - Transport failed: WLAN Geolocation - Insufficient Coverage
Then it cycles through a few times: net.rim.udp open net.rim.dns DnsQ 2 net.rim.dns DnsQ 2 net.rim.dns - RefQ (which I think means the query was refused) net.rim.tunnel - Clos-wap.cingular
Until it gets to: net.rim.dns - MaxQ net.rim.tcp - DNSx -1 Geolocation - Transport failed: TCP Geolocation - FAILURE: All transports failed
I've taken out some log entries that didn't seem to be significant (tunnel opening, etc). GPS works fine after this fails but I'd like to be able to get a fix when indoors or in low coverage which doesn't seem to happen unless I use a 3rd part app that has it's own aGPS data.
