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.
Related
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"
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
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
I'm something of a noob here, so I appreciate your patience and help.
My wife's Nexus 5x applied the latest update for 7.1.1 and her phone then fell victim to the dreaded bootloop. I was able to get through this guide to apply a rescue OTA: https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view (sorry, I can't post the hyperlink to an external site since I'm so new here, lol).
All of the steps completed down to step 21, when I tried reboot after the update - it rebooted then went right back into the boot loop.
The OTA I used was for Bullhead N4F26O (which is the one I should use based on the guide). I also tried N4F26I, but the OTA failed and it went straight to the bootloop.
I ran out the battery, charged it a bit, and tried again, but ran into the same problem (update completes, reboot, bootloop starts again).
Does anyone else have any more ideas on what I can try? At this point all I really care to do is recover any photos I can from the device (my wife forgot to setup image backup on her phone and USB debugging was never turned on). Google Fi already offered to send out a replacement, so I'm not worried about getting the device fully functional again.
Thanks for your help.
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
LeChuck5000 said:
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
Click to expand...
Click to collapse
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Tulsadiver said:
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Click to expand...
Click to collapse
I can get it into fastboot, and can sometimes get it into recovery (but not consistently...it often just goes into the bootloop when I try to launch recovery).
To apply the update I just followed the guide I linked to in my OP. First, installed the adb, fastboot, & usb drivers on my computer. I then put the phone into recovery, and wiped the partition cache. I then connected the phone to my PC, picked Apply update from ADB on the phone, and ran adb sideload c:\MyNexus\bullhead-ota-n4f26i-06953aec.zip from the command line on my PC.
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Arrivale said:
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Click to expand...
Click to collapse
You stick it in the oven? Use a heat gun? How hot/long?
tallgrasshawk said:
You stick it in the oven? Use a heat gun? How hot/long?
Click to expand...
Click to collapse
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
How else?
Arrivale said:
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
Click to expand...
Click to collapse
I don't have a heat gun, how else can I heat it? Also, excuse my ignorance, I'm new to phone thing since my Nexus 5x went into bootloop last week I've learned a lot, fast. Where exactly is the EMMC? How else can I heat it? I'm desperate to get this phone working as I just went overseas and Nexus won't send a replacement here
My attempt at the Rescue OTA fails in step 19, I can't get the device state to be "unlocked" does anyone know how to unlock it when the phone is in bootloop? (So all I really have access to is command prompt, which says I can't unlock the oem) HELP!?!
I had been running stock on my factory refurb device I got in Sept and thought it's time to look at running a 8.x ROM - downloaded stock, Pixel Dust, TWRP 3.2.0. Flashed stock, did enough setup to enable USB, fastboot the twrp.img, installed the twrp zip - and I can't recall now clearly, as it was last night, but I think at that point I restarted to recovery and then adb pushed the PD zip to the Download folder, then rebooted. The screen never came back on. I tried a few things last night and no change, called Google, got told i was just past warranty long enough for them not to be able to help me. This morning for ****s and giggles I hit the power button and I see the battery icon flash on, for maybe 2-3 seconds and then shuts off. The only other thing I've seen is a red light one time while plugging it into the computer to see if I could see it with fastboot or adb during that 2-3 second battery image.. No go.
Not sure where to go next, last night I thought it might be a dead system board, now I'm confused.
Thanks
Boot into the invisible bootloader. Terminal or command console type "fastboot continue" that's the only thing I can think of to help. GL
Also if you successfully get into the invisible bootloader you'll feel a vibration with pwr+voldown
DR3W5K1 said:
Boot into the invisible bootloader. Terminal or command console type "fastboot continue" that's the only thing I can think of to help. GL
Click to expand...
Click to collapse
Thanks - it turns on, shows the battery icon, then turns off. Not much I can do.. I'm not sure if I screwed up and killed the bootloader or not - took it to a repair shop to see what they say. I've never not been able to resurrect a phone since I've started messing with ROMs in.. must have been 2006? (Cingular 8125)
Oh well, I have a backup Vernee Mix 2 that I guess I'll use for a bit and maybe wait until the next Google phone is out in the fall
Thanks
Np!
(One thing to note) the 128gb models die like that.
DR3W5K1 said:
Np!
(One thing to note) the 128gb models die like that.
Click to expand...
Click to collapse
Thank you, this post has saved me much headache.
Battery is ****ed for sure