Quick Background,
My Nexus 5x was dropped in a swimming pool and put in rice for over 24 hours. After turning on the system it kept on going to this "Firmware Update" Screen, was able to get to bootloader assuming the system was wiped. Inside the bootloader i click on recovery and it just restarts with nothing happening. The OEM is locked and as a result i'm unable to load a factory image.
Unable to get to the "Firmware Update" screen when connected to a pc but it happens when plugged in.
I've attached the bootloader screen for reference.
Hopefully someone can help in getting my phone fixed,
Appreciate the help from everyone.
zman2010 said:
Quick Background,
My Nexus 5x was dropped in a swimming pool and put in rice for over 24 hours. After turning on the system it kept on going to this "Firmware Update" Screen, was able to get to bootloader assuming the system was wiped. Inside the bootloader i click on recovery and it just restarts with nothing happening. The OEM is locked and as a result i'm unable to load a factory image.
Unable to get to the "Firmware Update" screen when connected to a pc but it happens when plugged in.
I've attached the bootloader screen for reference.
Hopefully someone can help in getting my phone fixed,
Appreciate the help from everyone.
Click to expand...
Click to collapse
Go into bootloader, connect to PC, reflash stock.
Or connect as above, unlock bootloader, flash recovery, install your favorite rom as you normally would.
Related
First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...
I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Oh, and the best part is that all of this happened AFTER I already filed a warranty claim for the phones faulty mic. My new device comes tomorrow and if I send them this one back I'll be out 600 bucks.
Is there any way to fix this?
wolfsummers said:
I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
wolfsummers said:
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
Click to expand...
Click to collapse
When you enter your boot loader, what does the following command give you: fastboot devices
If you get your phone in response, you are not out of hope.
Sent from my Lunar Ecliptic One.
So I've had my Nexus 7 for a while now and I was using it for GPS maps the other day. The thing went to sleep and when about half an hour later I tried to unlock it, it didn't respond. The screen came on but it didn't seem to detect my finger. So I held the powerbutton for like 20 seconds and ever since it stuck on the google screen. When I go to bootloader and select recovery, it also stucks on the Google screen. I can also unlock the bootloader and flash TWRP but when I type fastboot oem device-info it will still tell me it is untampered and locked. Does anyone have any idea why this might happen? The thing wasn't rooted/bl unlocked. Thanks in advance.
PS: Don't respond with the 'try flashing a factory image/recovery', because trust me, I've tried those.
I had basically the same issue, however, I was unlocked and running stock 4.4.4. Mine reboot in the middle of Game of War, and was stuck at the Google Logo. I could get into Fastboot and my computer recognized, so I tried reflashing the stock images, but no dice. They appeared to flash fine without any error messages, but did not fix the issue. Also, selecting recovery, brought me back to the Google logo.
That said, I RMA'd the tablet. Apparently, there was a hardware failure as the packing slip from Asus noted that issue was a LED (Indicator) Error, and as a result they replaced what appears to be the main board (part number 90NK0080-R01000 Description ME571K MAIN_BD_2G/Q8064/16G).
So, this is likely not what you want to hear, but it sounds like a hardware failure. I bought a refurb tablet, and mine failed less than 24 hours out of the box. Thankfully, it came with a 90 day warranty.
if you cane unlock boot loader you can flash it , if you cant' there no way as i know
Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?
Moonboots said:
Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?
Click to expand...
Click to collapse
There is a post 4 down from yours on fixing bricked phones.
Tulsadiver said:
There is a post 4 down from yours on fixing bricked phones.
Click to expand...
Click to collapse
Hi Tulsa,
Unfortunately, that post doesn't apply to this situation, as my bootloader is unlocked, and I can't even get to the stage of having the drivers recognize the phone, because the phone will not turn on to bootloader mode, recovery or download mode.
UPDATE:
The phone reached the point last night where it would not even power on, access bootloader or download mode. Any button presses/holds left the screen black.
Today, for whatever reason, the device booted into fastboot mode. I was able to flash the complete stock factory image for the August security update Android 7.0 - the first stable build. However, when the device began to boot, it once again does not get past the Google page with the lock on the bottom. The screen goes black after that without entering the boot animation.
I've called Google to get a warranty replacement unit sent.
I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659
quadracer06 said:
I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659
Click to expand...
Click to collapse
Thanks for the reply, quadracer. I'll be taking the same path you are - Google already has the reorder on the way. Still trying to tinker in case there's a chance. Luckily, all the pictures from my engagement this past weekend were backed up to Photos or I'd be devastated.
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
i think if anything at this point, you need to assume none of your data can be saved. if you send it to google for them to fix, no data will be kept most likely, nor if you find any solution to do yourself. what happens if on the google screen you hold down power and voldown until it turns off and then keep holding them down?
It goes into fastboot with the android guy on it's back and it gives me the "restart bootloader", "recovery mode", "barcodes", etc, options. None of which the phone can enter apart from the barcodes and the powering off option. :crying:
HanaTruly said:
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
Click to expand...
Click to collapse
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Nilkong said:
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Click to expand...
Click to collapse
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
sudoxd said:
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
Click to expand...
Click to collapse
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Nilkong said:
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Click to expand...
Click to collapse
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
I flashed the new version of OTA from google's site. And it looks like it's booting up. Will report back if it crashes or continues to hold up.
Thanks!
EDIT: It's back to boot looping. It was at the "G" screen with white loading bar underneath. It froze there and went back to bootloop. Looks like there might be no avail.
Similar issue here. I gave up on it a month ago, but I figured it can't hurt to ask around. FWIW, there seem to be a lot of similar reports on Google's Pixel support forum.
Anyway, during the 2nd year of owning my Pixel XL (got it in Septempter 2017), I started experiencing slowdowns and random reboots more frequently, but never any bootloops until after receiving Android 10. After receiving Android 10, the random reboots seemed to be happening more frequently. I also experienced a weird issue where the phone would spontaneously exit out of the Google app (reached by left edge swipe from home screen) consistently within a few seconds of entering it.
Eventually, after another increasingly common random freeze, the phone rebooted and got stuck in a bootloop. Initially, chances were high that I would be able to complete the boot process after a few attempts, but inevitably, it would freeze and start bootlooping again. During the handful of successful boot attempts, I was able to backup some photos, and more importantly, enable OEM bootloader unlock in the developer options. After several more failed attempts to boot successfully, I did a total reflash of the latest factory image as of September 2019, after which I was able to get partially through the new phone setup process before crashing. For each subsequent attempt, the crash would happen earlier and earlier in the setup process until it wouldn't get further than the 'G' logo before rebooting. When the October 2019 factory image became available, I tried flashing that as well, but no luck.
On one hand, considering that the failures got progressively worse over time, it seems that this is fundamental hardware failure in the SOC, motherboard, RAM, etc. On the other hand, there seems to have been so many recent reports of this, especially after the Android 10 update, that I wonder whether or not it is software issue. Or could it be some combination of both, where the Android 10 update is pushing the hardware in new ways that is more likely to exacerbate an underlying hardware flaw?
Should I try re-flashing with Android 9 instead? At this point, it is a total brick...
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
ckidmcd said:
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
Click to expand...
Click to collapse
Needs to boot to any recovery, custom or not, to sideload an ota
sudoxd said:
Needs to boot to any recovery, custom or not, to sideload an ota
Click to expand...
Click to collapse
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
ckidmcd said:
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
Click to expand...
Click to collapse
does fastboot see your phone at all if you type `fastboot devices`