I am in need of assistance as my Nexus 5 running Android L recently froze up on me at the lock screen. Not being able to unlock it, i restarted the device only to find it stuck at the Google logo. I figured i could just reflash the phone to stock android 4.4.4 via fastboot, but when connected to my pc in bootloader mode, it isnt recognized as Nexus 5, rather as Android Device. I deleted the drivers and re-installed them but no such luck, i ran out of options. I searched some threads and couldn't find a solution to my problem, so i was hoping to get some help. I'm still kind of a noob with this kind of stuff, so please excuse me if this doesn't make any sense. Is there anything else i can try?
Use proper drivers...
Or simply use a different pc
doctor_droid said:
Use proper drivers...
Or simply use a different pc
Click to expand...
Click to collapse
I installed the drivers using Android SDK but it still doesnt show up.
I haven't got another pc but if you think that could help, i could maybe get to one, but i was hoping i could fix it with this one.
Jaimes214 said:
I installed the drivers using Android SDK but it still doesnt show up.
I haven't got another pc but if you think that could help, i could maybe get to one, but i was hoping i could fix it with this one.
Click to expand...
Click to collapse
I would rather suggest u too use fastboot drivers only (not from sdk)..wait will give u link. ..
Use this
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
All L related questions go here: http://forum.xda-developers.com/google-nexus-5/help/android-l-developer-preview-help-t2796217
Closed.
Related
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.
aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Same here. Any help for us would be great. Thanks.
shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.
Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html
doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow
Did you install those libraries properly?
Freshly baked from my Nexus 5
This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.
Lately i ve been having issues transfering files via USB to my Moto G 1st Gen (XT1034), so i looked through the web and i found out that if i changed my rom maybe i could fix it, so i decided to update my Moto G to Android 5.0 using Cyanogenmod 12, but i accidentally flashed a cwm version built for 2nd Gen Moto G and installed a rom built for 2nd Gen too that i had previously downloaded. After flashing and installing the rom it just bootlooped and now i cant transfer a Moto G 1st Gen rom to fix it!!! I ve tryed adb but i got "error: device not found", i ve also tryed manually installing those android USB drivers from a youtube video (Called How to Copy Files Over to your Android In a Bootloop with No OS using ADB!) but when i select the inf file i get a message telling me that those drivers are not supported on my 64 bit system.
Help me please im freaking out.
Hi, thank you for using XDA Assist. It sounds to me like you need to return your device to stock at this point. See if this helps, http://forum.xda-developers.com/showthread.php?t=2542219 Check Motorola's web sit to see if you can find the firmware there. If not, see if anyone here can help, http://forum.xda-developers.com/moto-g/help Just make sure the firmware you download is for your specific model number.
Don't forget to register on XDA to ask questions in that forum.
Good luck!
jd1639 said:
Hi, thank you for using XDA Assist. It sounds to me like you need to return your device to stock at this point. See if this helps, http://forum.xda-developers.com/showthread.php?t=2542219 Check Motorola's web sit to see if you can find the firmware there. If not, see if anyone here can help, http://forum.xda-developers.com/moto-g/help Just make sure the firmware you download is for your specific model number.
Don't forget to register on XDA to ask questions in that forum.
Good luck!
Click to expand...
Click to collapse
Thank you for replying. I ve already checked that, but i didnt tryed it because the files were uploaded to filefactory and it would take 2 hours to download the file, but it guess i ll just have to wait for it. My biggest problem is that adb isnt recognizing my device and i dont know how to fix it.
OK, try this. With your device connect to you PC via USB go into device manager. Do you see an icon with a yellow exclamation mark? If so right click and go to where it lets you chose from a driver from a list on your computer. Chose the Android composite ADB interface,
jd1639 said:
OK, try this. With your device connect to you PC via USB go into device manager. Do you see an icon with a yellow exclamation mark? If so right click and go to where it lets you chose from a driver from a list on your computer. Chose the Android composite ADB interface,
Click to expand...
Click to collapse
It appears as it is already installed, but my pc still doesnt recognize it
The only other thing I can tell you is see if this helps, http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396 Also try different usb ports and cables.
jd1639 said:
The only other thing I can tell you is see if this helps, http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396 Also try different usb ports and cables.
Click to expand...
Click to collapse
Thanks for everything. Someone is helping me in the Moto G section that seems to know how to fix it. About the USB driver issues, i ve tryed everything explained in that thread
I'm glad you're getting the help you need. I'll close this thread then.
I bought a nexus 5 as a gift for someone and wanted to do some personalizing. I made a custom boot animation, converted it through the "Boot animations" app on google play, but now it hangs on the animation. I tried connecting the device through adb but I can't get my drivers to work, says that nothing is connected. I tested the connection with MY N5 as well and I receive the same result. The reason I tried to connect it though adb was that I read you could change the boot animation through there. Any help would be appreciated... thanks guys :crying:
Are u using Linux? And have u tried using fastboot?
Aurey24 said:
Are u using Linux? And have u tried using fastboot?
Click to expand...
Click to collapse
I'm on windows, and when in fastboot the console on my PC says that it can't detect the phone.
Go to device manager on your pc with the device connected. Do you see anything with a yellow !? If so right click on it and update the driver. Go to let me choose a driver from the pc. Find the adb composite interface driver.
Sent from my Nexus 9 using XDA-Developers mobile app
Jiharu Ikumiya said:
I'm on windows, and when in fastboot the console on my PC says that it can't detect the phone.
Click to expand...
Click to collapse
Yep as u can see it's the drivers that isn't making it happen, typically why I use Linux, just dual boot some light Ubuntu distro like lxde using a USB and use the terminal, the nexus will definitely get recognized and u can save it, I'm almost 100% positive this is the easiest way unless u know how to troubleshoot the drivers in windows, or u don't want to in which case I can get Windows installed onto my PC and figure out how to get it working to help you if u really want to stick with it.
Aurey24 said:
Yep as u can see it's the drivers that isn't making it happen, typically why I use Linux, just dual boot some light Ubuntu distro like lxde using a USB and use the terminal, the nexus will definitely get recognized and u can save it, I'm almost 100% positive this is the easiest way unless u know how to troubleshoot the drivers in windows, or u don't want to in which case I can get Windows installed onto my PC and figure out how to get it working to help you if u really want to stick with it.
Click to expand...
Click to collapse
A friend of mine found the Nexus 5 toolkit on here, I didn't know it existed. We're up and running now, sorry guys... just a bit of a scare. I appreciate the offer of your help though, means a lot to me!
Jiharu Ikumiya said:
A friend of mine found the Nexus 5 toolkit on here, I didn't know it existed. We're up and running now, sorry guys... just a bit of a scare. I appreciate the offer of your help though, means a lot to me!
Click to expand...
Click to collapse
NP, glad u good it working, I thought u knew about the toolkit and that's what u used to flash the phone. I'm glad u figured it out.