Develop Bugs

[Q] Stuck at Unlock Bootloader screen

My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?

i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?

Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?

molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?

herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!

OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"

[Q] Nexuz 7 stuck at the google logo

Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.

Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.

aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on

Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.

I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.

He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?

sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.

[Q] [Help] HTCdev bootloader unlock not working

I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks

Dlome said:
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Click to expand...
Click to collapse
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.

xunholyx said:
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
Click to expand...
Click to collapse
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.

Dlome said:
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Click to expand...
Click to collapse
So, have you tried the code again? And/or have you gone back to the HTCDev site for a new unlock code?

I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.

Dlome said:
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Click to expand...
Click to collapse
Are you copying and pasting the very first part of the code?
The part that looks like:
"(bootloader) < please cut following message >
(bootloader)" ?
IMMEDIATELY after that is what you copy and paste.
The copy should start when it says "<<<< identifier token start >>>>"

I am only copying the <<<< identifier token start >>>> and <<<< identifier token end >>>> along with the string between and leaving out the bootloader tag that is on each line.

I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.

Dlome said:
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Click to expand...
Click to collapse
You seem to be doing everything right. I'm stumped. Hopefully someone else comes along with a solution. @redpoint73?

That's what I was afraid of haha. I don't know why but while I am no expert in this area I do not feel I'm ignorant either yet I always seem to have problems even when I follow the steps correctly >.<
I do appreciate the troubleshooting greatly thank you. I will keep trying things and see what I can find and if I figure it out you bet I will add it here because I can't be the only one getting stuck haha.

Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.

xunholyx said:
Hopefully someone else comes along with a solution. @redpoint73?
Click to expand...
Click to collapse
Ummm, yeah . . . in fact I think I do:
Maybe I'm missing something here. But the Dev Edition comes already bootloader unlocked, and therefore should be no reason to do so.
I think the prompt to unlock never comes up on the phone, since its already unlocked.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
bloodhawk said:
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
Click to expand...
Click to collapse
Yes, this will tell us a lot.
Or boot into bootloader and just see if it says LOCKED, RELOCKED or UNLOCKED.
I bet it says UNLOCKED.

Another Bricked Nexus 7 after Lollipop

Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.

this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!

I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".

Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.

Tried all NRT options including force flash.
Problem is none work with the locked bootloader.

Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.

IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?

Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.

Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."

I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!

As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..

Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.

tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..

tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?

dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.

tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does

I ve given up . Bought a Nexus 9. Wasted too much time on this.

Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.

My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.

Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk

Nexus 5X Problems

Hello. I am having some issues with Nexus 5X and was hoping someone could help possibly fix it, if it's even fixable.
I bought the phone from a used store for pretty cheap On march 5th this year.
Tuesday night i was surfing on google chrome app and all of a sudden the entire thing froze up on screen couldn't get it to do anything what so ever so i tried powering it down and rebooting it. Well i got it to power down but then it went into a constant boot loop where it just kept rebooting to the "Google" screen and then it wouldnt get any further. Eventually it ceased doing that after about 5-10 minutes and then i was unable to get the device to do anything, couldn't even get into the bootloader menu. Battery was at 55% when this all started and phone had been working very good prior. Last night i tried to get it to turn on again and this time i noticed a red flashing light on the bottom speaker. I have seen this one before on other nexus devices so i plugged it in and got the charging screen to come up, i let it charge full and then went to try and start it with no luck of getting it to do anything. Today i have managed to get it to simple Boot to the Google screen but it remains their for a few momments then shuts off and does nothing else, sometimes it goes into a constant repeat of that, i hear it's called a boot loop.
I am not sure what the issue is. What i wanna know is if it's an easy fix or not.
Thanks
**Update***
i was able to get it to finally go into to the bootloader screen, but have no clue what to do here, clicking restart just goes back to the same problems.

If you haven't already tried you could try doing a search for Nexus 5x BLOD or Nexus 5x bootloop of death, this may not be the issue but it will give you something to compare the symptoms your device has. There should also be plenty of info on any workarounds there are available to try and get your device back up and running.
Hope that helps

Ok will do thank you

Following thread https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
installed 4Coreoreo fix, but am having issues getting to to flash boot
Command window stays stuck on < waiting for device > and the phone is doing nothing, just sitting in the Bootloader menu
says fastboot mode
secure boot enabled
device state locked
am i missing something? Am thinking the bootloader is locked
unable to do an oem unlock because i can't get it to boot into the os.

Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.

junglism93 said:
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
Click to expand...
Click to collapse
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol

Gibson295 said:
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Click to expand...
Click to collapse
No problem, other than trying a different usb port, cables or updating your ADB and fastboot if you haven't already it sounds like it's the end of the road for your 5x.
Leave it in a cupboard for a few days and give it a go another time, you never know. I've still got my Nexus 4, new battery time for mine but it still runs like a charm lol.