Hello guys,
My nexus 5x is not working, it only shows a black screen and the Google logo.
I can't go into recovery mode and my nexus is not showing in LGUP.
What should I do?
Mine did this and now fails to power up, just spontaneously bricked itself and I haven't used custom ROMs on it or unlocked the bootloader either.
neo158 said:
Mine did this and now fails to power up, just spontaneously bricked itself and I haven't used custom ROMs on it or unlocked the bootloader either.
Click to expand...
Click to collapse
the phone is auto brick he did that to me
just throw it and never wast your money to repair it this phone is like this
the phone has a limited life time no matter what
Related
Hi,
I have a really tough problem with my Verizon Galaxy Nexus. After I boot it up it shows the Google logo and then the screen goes black. It is still on because I have left it there hoping it would pass this screen but the battery died eventually. If I put the phone into a computer I get the charging screen and it will charge. I can get into fastboot mode. I have tried unlocking the device so I could flash a new ROM but as soon as I use the Gnex toolkit to unlock it, the fastboot mode reboots and it is locked again. When the device is plugged into the computer in fastboot mode Windows is constantly giving the noise that something is plugged in than unplugged then plugged in, on and on and on. I have put it in Odin mode and flashing the 4.04 image ROM looked like it worked but still after the phone reboots it just shows the Google Logo and then goes black. I have gotten into the stock recovery and wiped data and cache and that did not help either. Any help would be appreciated!
Nick
PS
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
I followed that and afterwards my screen still comes up black after the Google logo.
I just tried to install TWRP recovery to see if that would help. I went through all of the fastboot commands and they said they completed successfully. When the phone rebooted the stock android recovery was still on the device... so for some reason this phone is taking the commands and they are getting returned as successful but they are not successful... super strange.
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
My Gnexi said:
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
Click to expand...
Click to collapse
Correct, seems highly likely his eMMC deep fried. If unlocking bootloader doesn't even work, I would try nothing else and get its mainboard replaced.
Thanks. Now that I know, I can stop wasting my time trying to fix this.
My screen froze today so I rebooted. It immediately went into a bootloop. Ive been running Pure Nexus ROM with no problems for months now so I have no idea what happened. I can get into fastboot mode however it will not reboot nor boot into recovery. Wusfresh toolkit detects my phone in fastboot but no commands work. I tried booting into recovery then I even tried to flash stock. It went thru the whole flash procedure but goes right back into the bootloop. I am unable to manually flash stock because as I stated nothing works past fastboot mode and since it flashed stock now my usb is not enabled. Bootloader IS unlocked. I have no idea what to do at this point. Ive been messing around with Nexus phones for years and have never been unable to at least flash stock to fix any problems. Its been months since Ive messed around with my phone and its killing me that out of the blue it does this and I might have to spend Christmas money to replace my phone. Any help would be greatly appreciated!
Variant-LGH790 32GB
HW Version- rev_1.0
Bootloader Version-M8994F-2.6.36.2.20
It's a HW problem, because LG used some ****ty solder for the emmc and cpu. So the connection between the cpu and the motherboard is weak after some time, especially if you do stuff on your phone that heats up the cpu. You can try to put in in the freezer for like 10 minutes, then it started working for some people. Or you can open your 5x, and then take a heatgun or hair dryer and heat up the cpu for some time and press on it (you can find a picture of each chip on the motherboard on ifixit). This isn't a fix that will work for years, but at least, you can backup your data, flash stock and then send it to the repair centre.
Sent from my Nexus 5X using Tapatalk
When the phone bootloops, did you try pressing the volume down button? If it launches recovery then it means bootloop is caused by stuck power button.
Thanks for the suggestions guys. Nothing worked so I'm just going to call LG and see about a refund.
Hello everyone,
I need help !!
I have a nexus 5x for 1 year and a half, root with the bootloader unlocked.
But this afternoon, I used it normal, and it freeze and it is set to restart. Except that it starts constantly on the google logo, sometimes more but that's all. And after 5, 6 times it power off.
Sometimes it gets stuck on the google logo indefinitely
It is also very slow to pass the warning that my bootloader is unlocked
I specify that I have access to the bootloader and it reboot when I try to decrypt my data in recovery (twrp)
I tried the tutorial here https://forum.xda-developers.com/nexus-5x/general/tool-unblod-fix-nexus-5x-thats-bootloop-t3718388, but it's even worse since I does not even exceed the Google logo.
Any idea ?
I specify that I am under the stock rom (8.1 december)
Thanks
You probably have a hardware issue but have you tried flashing the factory image with fastboot?
Sent from my [device_name] using XDA-Developers Legacy app
Greetings!
My girlfriend's Nexus 5X recently got stuck into boot loop. What I tried to fix it:
- Completely discharging it and charging it again
- Get into recovery mode - after going to the bootloader and choosing recovery mode, the phone reboots to the google logo
- I tried reflashing system, boot and recovery with TWRP - still the phone reboots when trying to get into recovery mode
What else can I try, having in mind that I can't get into recovery or boot it at all? The bootloader is unlocked, so I can try flashing anything.
You could try the BLOD-fix boot/recovery images on other threads in this forum.
If the phone is still in warranty (and even if it's not), I'd suggest getting in touch with your local LG repair people.
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Squealor said:
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Click to expand...
Click to collapse
No point contacting google, you have to go to the manufacturer LG wherever they happen to be in your country. A simple replacement phone will only potentially have the same issue - its a hardware problem and the PCB/motherboard must be replaced. I had a brand new phone (well 'brand new' as bought in 2016 but only unboxed last Tuesday lol) which didn't last 6 hours before getting overly hot and going into bootloop...tried a factory reset and got into setup but it shutdown and bootlooped again halfway through. Fortunately it was within the 2 year warranty period, so LG authorised the replacement motherboard on Thursday (1 hour wait as a walk-in service) and it has been fine (and cool!) ever since.
As a bonus, they upgraded it from 6.0 to 7.1.2, which LG considers the "latest" stable version for the 5x.
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
pamack said:
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
Click to expand...
Click to collapse
You didn't relock the bootloader did you? After unlocking it?
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
pamack said:
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Click to expand...
Click to collapse
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
pamack said:
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
Click to expand...
Click to collapse
Still probably worth flashing via adb to check?
mikefnz said:
Still probably worth flashing via adb to check?
Click to expand...
Click to collapse
He means fastboot.