So, this morning my son (who has a Nexus 5X) says his phone is bootlooping. I said "gimme that!..you don't know what you're doing." Lol
Thought I could fix it, but an hour later, a dozen google searches and trying a bunch of different things I can't get ADB mode to work on this phone!!
I'm using a Windows 10 PC that works fine with my Nexus 6P and ASUS tablet. I reinstalled USB drivers just in case but that's not it. I've tried different cables with no luck either.
I can get the 5X to boot into recovery mode where I see the dead Android robot with 'no command' under him. I then press the power button + volume up to get to ADB sideload menu. I can hear the "da da" music of the PC seeing something on the other end of the USB cord but no matter what I do, no ADB/Fastboot. I've even tried the LGUP tool, that even says no device attached.
I was hoping someone may have some way to restore the device. It boots up the Google logo then reboots Google logo then just shuts itself off. Every once in a while I can get it to boot to the Android boot animation for about 2 seconds before it freezes and shuts itself off. The device is about 11 months old (one year warranty?) and has never been rooted.
Thanks for any info... **I called Project Fi, going to get a replacement**
Sorry, I totally missed the last part before replying.
It could be a hardware failure. Since you're so close to 12 months, I would contact Google (or LG if not from google) and let them try to troubleshoot. That's the best way to get warranty repair. They will run you through any steps that might work. You just don't have much time to troubleshoot.
Sent from my Nexus 9 using Tapatalk
Mine does not appear at all on Windows or any operating system I'm guessing none if the init files should be zero bytes either I have no idea wth happened I check the root system with root browser and got this and my 5x is bootlocked I reset it dozens of times and still no recognition set mtp manually via devel options and nothing
Don't know about these files but re-installing (updating) all drivers seems to work for me. I've had to do this many times in the past 4 months for rooted N5, & N9, not rooted but bl-unlocked N5X, and virgin N5X. Never had to do this before and could use multiple devices interchangeably with Windows 10 which I've had since its beginning. Wugfresh has a driver install/repair section on his NRToolkit that can be helpful.
Sent from my Nexus 9 using Tapatalk
Sorry this is old thread. but I have same issue with nexus 5x. though it recently experienced BLOD and flashed 4cores. did you find a solution to your problem? mine however only recognized in adb on ubuntu. but no where else. no windows 10. and on ubuntu mtp didn't work
are you guys checking your adb device drivers in windows?
Related
Hey Everyone,
I'm hoping someone can help me find a way to un-brick my Galaxy Nexus GSM 16GB (GT-I9250M). Before you call me an idiot, I'll have you know I wasn't flashing it or anything. I was simply listening to music when the screen went all glitchy and the sound started looping. Then the phone attempt to restart, but mid way through booting, it would glitch out again. It would repeat this until I finally pulled the battery. When I got home, I tried to get it into Fastboot mode or Download/Odin mode. Neither of which worked. I was running the stock version of android. If I recall correctly, it was running 4.0.2.
So in a nutshell, here's the status of the phone:
Regardless of what I do, Fastboot mode and Download/Odin are not accessible.
No matter what combination of buttons I press, the screen always shows: Phone ... Yellow Alert Triangle ... Computer
Using Galaxy Nexus Toolkit or Wug's Toolkit, the phone is not listed under Fastboot or ADB devices.
While the phone is plugged in via USB without a battery, I see device manager adding and releasing an OMAP4440 device every second or so.
When I plug in the phone (with the battery) in via USB while its off, it will turn itself on showing the alert screen mentioned above.
ODIN is about the only app/toolkit I've used that "sees" the device.
Using ODIN, I have tried various stock images mentioned in the forums. All of them have either failed or get stuck on "NAND Write Start!!"
I've read dozens of posts on various forums but I could not find a concrete solution, so I'm appealing to you guys for help. Any help would be great appreciated.
Thank you!
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
1. first off you need to download "Odin 3 v1.85" here
2. also download CF-Root-GGN_YAKJU_ICL53F-v5.1 here
3. open Odin in your computer
4. where it says PDA put CF-Root-GGN_YAKJU_ICL53F-v5.1
5. Power on the device and when you have the "phone triangle pc screen" connect it to your PC.
6. ???
7. PROFIT!!!
kmdub said:
Based on what you have described, even if I could get it working again, I would try to get a warranty replacement, provided that is an option. Sounds like a hardware failure. Like I said, even if it somehow started working again, I wouldn't trust it.
Click to expand...
Click to collapse
You're probably right. I still have my Nexus S which I can fall back to resort to this. I will try what nonione has suggested, and if that doesnt work, I will likely look to replace the phone.
I've never seen a samsung phone that couldn't be recovered (other than physical or water damage).
You can easily get the phone back with odin (no you do not have to be in odin mode on the phone).
Study up on it....tons of threads, use search.
Never seen a bricked Samsung....ever...and I've had at least 6 or 8 different models.
(edit)
There;s quite a bit more to it than nonione tried to walk you thru.
You will need the correct drivers on your computer first...buncha other steps too.
Study hard before you try odin.
Google, "Galaxy Nexus OMAP Unbricker". Download it and when the OMAP devices comes up in the Device Manager quickly right click on it and install the driver includes with the OMAP download. Once the driver has installed run the .bat file in the download. Should go to Fastboot now.
Then:
http://forum.xda-developers.com/showthread.php?p=27160425
Download the .pit file here:
http://forum.xda-developers.com/showthread.php?p=27152659
Sent from my SGH-T769 using Tapatalk 2
That's easy to repair, dude
That's not a brick, that's just telling you, that the firmware files are corrupt, all you need, is a jig, a Windows PC, Odin and chainfires ODin files
I can walk you through, on Teamviewer, if you want. I've had this problem quite a lot (Not on the GNex, though) I jope I get it, so I get a GS 3 ^^
I do have the same phone with the same problem..but currently out of the country, so cant get it replaced.. I get no yellow triangle my phone is completely dead..I tried the omap flash no luck..please let me know if the omap flash tool worked for you..
Hey guys,
So a bit of an update. I tried using Odin to flash. None of the files suggested worked for me. I also tried the OMAP flasher. While it "did something" without erroring out, it did not switch to fastboot mode for me. My phone is simply stuck in that yellow alert state. So now, i'm going to try using a Jig as familyguy59 has suggested. I saw a video of one guy use one to fix the exact same issue as I'm having, albeit with his Samsung Galaxy 2, but it looks promising. I purchased one a couple days ago and it should come soon. I'll let you guys know how it goes.
Hey Guys,
So I tried the jig i bought. No dice. I'm pretty disappointed. : / I guess off to Samsung it goes... I just don't have any luck with Samsung products.
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Steepgnomeking said:
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Click to expand...
Click to collapse
Have the same issue. I am trying fr a work computer, internet restricted, no kies. Now can only recognize note 2 as a camera. When I switch thw usb settings in android, I get the not supported box. Same thing happens at the home computer. I left bb for this??
This is a simple hardware fail and needs to be taken in for warranty repair. The fact that it's bricked, we'll you're just gonna have to cross your fingers and hope they don't charge you for a new one.
Or you can try a jig to get it into download mode and try to push a rom through.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Thats what i'm going to do take it in and see if they can fix it but i want to get it back to stock firmware before but not being able to plug it in to update it is kinda ruining that plan.
Well I turned in 3 notes with custom roms that were rooted and I never got charged, but I always run a stockist rom.
What rom did you flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Are u able to boot in recovery?
PM me if u need help
Sent from MOON......
Can you boot into recovery? If so then you can push a file to your SD card using adb. If your having problems with Samsung drivers or what ever good way to test is connecting your phone to a Linux box and setting up udev and adb. Then you can do a adb device command and see if it sees it.
If you have the time to install Linux on a extra hard drive or duel boot you can connect using adb.
Nice thing about Linux is that you can connect directly to the USB device using udev and the device id and with ADB you can push a file onto your phones SD card. Here's a good how to
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Sent from my SGH-I317 using xda app-developers app
Phone: VZW Galaxy Nexus, Rooted, TWRP Recovery, Lean Kernel
For the first (and last) time in my life I decided to dirty flash a ROM (4/16 build of Project Elite) to my phone (from an earlier build of PE). My phone apparently hated that. It has created an odd world of problems for my phone that I am hoping someone may be able to see a trend with and offer up some suggestions for escaping this odd world.
Here are my phone's symptoms:
(1) Earpiece on phone stopped working: During phone calls, I can only hear audio when using speakerphone. I was able to remedy this by getting the SoundAbout App from the Play store. This tool allows you to manually change how the audio is routed. My phone thinks a headphone is plugged in and tries to route the audio through the headphone jack. This app allows me to fix that problem.
(2) USB File Transfer Mode stopped working: When connecting my phone to the computer it will charge (sometimes, see #3) but my computer will not recognize it as a device. Consequently, adb (and wireless adb), fastboot and ODIN all will not connect to my phone because the phone is not recognized. I have uninstalled, updated and re-installed just about every driver set I can find for the Galaxy Nexus/ I know it is not a driver issue because my wife's Nexus connects to the CPU just fine.
(3) Phone Charging is Intermittent: I have trouble finding a trend with this one. If I toggle Fast Charge (Off or On), my phone will no longer charge. This is fixed by powering off the phone with the cable plugged in. At that point the white battery icon appears and the phone begins charging. If I power the phone back on, the phone will continue to charge but will not be recognized as a USB device.
Here is what I have tried over the past 2 days:
(1) Both GNEX Toolkits: With no USB connectivity, adb and fastboot are not options. This option becomes unavailable with no usb. Have tried both.
(2) ODIN: Phone is not recognized by ODIN tool.
(3) Cleaning USB/Headphone Ports: This produced some interesting black stuff, but no results.
(4) Clean Flash of PE 4/16 Build: Wipe data/cache/dalvik and re-flash. Same problem.
(5) Clean Flash of Stock Rooted Build: Wipe data/cache/dalvik and flash. Same problem.
(6) Mobile ODIN: Cannot locate the tar balls for a stock 4.2.2 factory flash. Have found the necessary files for 4.0.2, but these will not flash in Mobile ODIN. I have read that you have to be on the same android version as the ODIN tar files you are trying to flash. I think this is my best option at this point, but I cannot for the life of me figure out how to get Mobile ODIN to work.
As far as I can tell this is a software problem that is baked somewhere deep in the phone. Since the USB and headphone problem started at the same time, I do not believe it to be hardware. My theory is that somehow fast-charge is locked on (?) and my phone is locked to routing the audio to the headset. If I can find a way to completely wipe everything off and start fresh, I believe my problem will be solved.
Does anybody have any ideas what may be going on here and how I may be able to get this phone back to Stock?
tldr; no usb, no headset audio after dirty flash, how do i get back to stock??
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
bk201doesntexist said:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
7ontheline said:
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
Click to expand...
Click to collapse
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
bk201doesntexist said:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
Click to expand...
Click to collapse
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
7ontheline said:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
Click to expand...
Click to collapse
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.
You've done this? Sure the USB port doesn't have a bent pin or something?
Sent from my Nexus
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
tdf666 said:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.
I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.
I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
Sent from my Galaxy Nexus using xda app-developers app
Hello everyone
Got Nexus 7 (2013) few days ago and now tried to root manually (from this thread: http://forum.xda-developers.com/showthread.php?t=2382051)
and everything was fine untill I tried to flash TWRP in command (fastboot flash recovery recovery-twrp.img) and flashing didn't end, had to close cmd or unplug USB to stop it, once unplugged it said "Too many links" or something like that, tried doing it bunch of times with older versions and what not, nothing worked.
Then found out about Nexus Root Toolkit by WugFresh and again, everything was fine, drivers checked and working, but once it got to the spot where it had to boot .img file it just never ended, as seen on tutorial videos it takes about half a second to load it, I waited for 10 minutes but nothing.
This part - http://imgur.com/QU5Ic0R
So I guess its something wrong with transfering files to Nexus 7 ? Even tho I was able to import few files to it before. Maybe something on my PC is blocking it ? :silly:
Frustrated and exhausted Would appreciate any help, Im new at android stuff so please detailed answers
Thanks.
Cactulus said:
Hello everyone
Got Nexus 7 (2013) few days ago and now tried to root manually (from this thread: http://forum.xda-developers.com/showthread.php?t=2382051)
and everything was fine untill I tried to flash TWRP in command (fastboot flash recovery recovery-twrp.img) and flashing didn't end, had to close cmd or unplug USB to stop it, once unplugged it said "Too many links" or something like that, tried doing it bunch of times with older versions and what not, nothing worked.
Then found out about Nexus Root Toolkit by WugFresh and again, everything was fine, drivers checked and working, but once it got to the spot where it had to boot .img file it just never ended, as seen on tutorial videos it takes about half a second to load it, I waited for 10 minutes but nothing.
This part - http://imgur.com/QU5Ic0R
So I guess its something wrong with transfering files to Nexus 7 ? Even tho I was able to import few files to it before. Maybe something on my PC is blocking it ? :silly:
Frustrated and exhausted Would appreciate any help, Im new at android stuff so please detailed answers
Thanks.
Click to expand...
Click to collapse
Are you running it in admin mode? Right click>run as admin? And have you tried chainfire autoroot? http://forum.xda-developers.com/showthread.php?t=2467014
oliver4xhd said:
Are you running it in admin mode? Right click>run as admin? And have you tried chainfire autoroot? http://forum.xda-developers.com/showthread.php?t=2467014
Click to expand...
Click to collapse
Just tried running in admin mode, didn't work, still wont boot boot.img, and it would be same with chainfire on any other root method
I have a really strange problem that none of the other threads in this forum have described. 5X running 7.0 Build NBD90W - Unlocked Bootloader
The 5X was working just fine and I was able to connect to both of my PCs and change the mode from Charging to MTP or PTP from the pull down. Now when I connect, I can see that phone is being charged when connected to the PC, but the pull down is not showing up. If I go into DEVELOPER Options under Networking and try to change it to one of the other settings, nothing happens. My PC does not show the 5X connected in the Device Manager.
I have also tried booting into the Bootloader and using fastboot or adb and neither is able to see the phone. This is happening on multiple PCs.
It's like something is broken inside the phone that it is not communicating. I have tried everything in the forums, I even reinstalled the SDK Toolkit but nothing is working. My last option was to factory reset the phone.
I have also tried to get into Stock Recovery and when I push the power and up button, it gives the message the bootloader is unlocked and then restarts the phone. -- EDIT -- I am able to get into Stock Recovery, I wiped cache and rebooted, still no luck.
Also tried booting into Safe Mode, didn't make a difference.
Any ideas? Thanks....
You didn't mention if you've tried a different cable.
kirkgbr said:
You didn't mention if you've tried a different cable.
Click to expand...
Click to collapse
Good point, I have tried multiple different cables. Same cables work fine with my Nexus 6P.
Got the OTA for N5D91L this afternoon, it was able to successfully update to the November security and after the reboot, still not able to connect to the PC. :crying:
Bump it up!
Oh, i see, i'm not the one with the same problem. i have two 5x with the same problem. both unlocked, rom installed, both started not being detected at some point.
faulty cable
Ok, brought phone to warranty center. They could see a phone and restored OS to original.
Bought another cable to check and it works now ok. Old Nilkin cable still doesn't work (only charges). So, i guess, the problem was with cable in my case.
Good luck finding what's wrong with yours phone.