Related
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
I suggest that you flash the factory image following the instructions in the sticky threads.
You flash it from you computer and I think there is a good chance that it will fix your tablet.
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
misteragony said:
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
Click to expand...
Click to collapse
Unlock your bootloader through ADB and than flash the factory image, make sure you flash the right one..
This LINK is a great guide that'll show you how to unlock the bootloader and flash a factory image through ADB (post 2).
Everything should get restored with a factory image flash, but if not you probably have a permanently bricked device because ASUS will most likely turn the device down if they notice any signs of the device being taken apart.
AarSyl said:
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
All I had to do was download the Google Driver from SDK and install it. ADB was able to recognize my device without a problem.
Well, I first installed SDK when rooting my HTC Evo, and boy did I have a grand time getting the right drivers! [/sarcarsm] By the time I was using my next HTC phone, I was using Ubuntu, and it doesn't require any device specific drivers.
USB debugging
Well the thing is: USB debugging was not enabled before I couldn't boot my Nexus anymore. Since I can't boot it, I can't enable USB debugging if I'm not mistaken.
So I boot into the bootloader (volume down + powerbutton), then select recovery mode and press the powerbutton.
Next I press the powerbutton and volume up and I'm in the recovery mode.
There I can see the error messages about my cache partition being corrupted, wiping/formatting it there does not help.
I can put the tablet in 'adb sideload' mode, but I guess since the tablet is not in debugging mode that won't do much good?
Using the Nexus 7 toolkit I always see the message: waiting for ADB mode but it detects the device though (it lists a serial number as well).
I tried to boot the tablet by holding up and down volume and then the powerbutton (this is supposed to be 'fastmode' no?).
The screen of the tablet remains black/ not active, my PC (under Win7) detects a new device at this point but it fails to load a driver.
When I try this under Linux I see a 'qualcom device when I do 'lsusb', and under /dev I see: /dev/ttyUSB0 appear.
I tried "fastboot oem unlock" but that doesn't work.
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
misteragony said:
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
Click to expand...
Click to collapse
You flash a stock image in fastboot. You hold volume down + power to enter it.
I tried to unlock: I chose yes using the vol buttons and pressed the powerbutton.
At that point the screen freezes on my tablet, and in the command line it gets stuck at this:
Device detected in FASTBOOT MODE
Device Serial Number is: 0xxxxx
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Hey all, I need some assistance here. So my device is Nexus 5x H790 unlocked bootloader, stock ROM, Usb debugging enabled. I had the latest October updates (90S I believe) and everything was running just fine on it until about 5 days ago. I was using my phone like normal and suddenly it turned off. I could not turn it back on and when it did it would get stuck at the Google screen and then begin to bootloop several times before turning off. I have gotten to the recovery screen 1 time and wiped cache but still same result. There was one instance where the phone completely booted up and was receiving the numerous texts over the few days and even sent a few. Then it crashed again after 5 mins :crying:
Here is what I've tried:
-Attempted to reflash October images from googles website. I have experience doing this before from using Heisenburg's method 9 (no change)
-Then began to research and thought it was the power button getting stuck issue. Brought it to a repair shop and they opened it and checked out the power button and said it was firmware not the button and to factory reset (brought it here because the device is 13 months old and figured it was cheaper/faster than sending to LG and waiting a whole month to get it back)
-Brought home from repair shop, reflashed latest October images and still could not boot up fully.
-Now I want to factory reset but cannot get to recovery screen, when I enter bootloader and scroll to Recovery it just goes to Google image again....I believe there are commands to wipe device userdata and tried "fastboot erase userdata" and "fastboot format data" but gave errors
I will try next to use a different USB port, now that just found a thread on here saying the 3.0 ports dont seem to work with that command even though I've used the same port for every image flash I've done in past
Any help/ideas would be appreciated. Thanks in advance
Same problem...
I have the same problem. Mine started bootlooping to the Google screen the same day my warranty expired...
I'm gooing to send it off to LG, but I really wish I could get my pics and texts off before they wipe it
mjp5099 said:
Hey all, I need some assistance here. So my device is Nexus 5x H790 unlocked bootloader, stock ROM, Usb debugging enabled. I had the latest October updates (90S I believe) and everything was running just fine on it until about 5 days ago. I was using my phone like normal and suddenly it turned off. I could not turn it back on and when it did it would get stuck at the Google screen and then begin to bootloop several times before turning off. I have gotten to the recovery screen 1 time and wiped cache but still same result. There was one instance where the phone completely booted up and was receiving the numerous texts over the few days and even sent a few. Then it crashed again after 5 mins :crying:
Here is what I've tried:
-Attempted to reflash October images from googles website. I have experience doing this before from using Heisenburg's method 9 (no change)
-Then began to research and thought it was the power button getting stuck issue. Brought it to a repair shop and they opened it and checked out the power button and said it was firmware not the button and to factory reset (brought it here because the device is 13 months old and figured it was cheaper/faster than sending to LG and waiting a whole month to get it back)
-Brought home from repair shop, reflashed latest October images and still could not boot up fully.
-Now I want to factory reset but cannot get to recovery screen, when I enter bootloader and scroll to Recovery it just goes to Google image again....I believe there are commands to wipe device userdata and tried "fastboot erase userdata" and "fastboot format data" but gave errors
I will try next to use a different USB port, now that just found a thread on here saying the 3.0 ports dont seem to work with that command even though I've used the same port for every image flash I've done in past
Any help/ideas would be appreciated. Thanks in advance
Click to expand...
Click to collapse
How could ur warranty be expired when it is 24 months by buy date.
Domin_PL said:
How could ur warranty be expired when it is 24 months by buy date.
Click to expand...
Click to collapse
I'm fairly certain its 12 months for manufacturer. I did not get the extra Nexus protect
In Europe there is 24 month warranty for all sold products. Kind of bad thing or kind of good thing.
ugh wife's Nexus 5x did this same thing. Been up all night trying EVERYTHING. Fastboot works but bootloader is locked so I can't do anything. Going to recovery just reboots the phone to logo.bin and then turns off again. Download mode is unreliable and when I get it to finally trigger, it doesn't go to the second phase where it waits for a firmware update (so I can't do the LGUP thing).
So I guess this is an OTA problem? Some BS.
fanta110 said:
In Europe there is 24 month warranty for all sold products. Kind of bad thing or kind of good thing.
Click to expand...
Click to collapse
In France LG does not guarantee the 24 months since March 2016. my nexus 5x is broken down one year and 1 day after the date of purchase with this same issue. At first LG told me that the warranty was OK then they retracted. I have a beautiful invoice with the change of motherboard ....
****
androcib said:
In France LG does not guarantee the 24 months since March 2016. my nexus 5x is broken down one year and 1 day after the date of purchase with this same issue. At first LG told me that the warranty was OK then they retracted. I have a beautiful invoice with the change of motherboard ....
Click to expand...
Click to collapse
Just curious how much the new motherboard was quoted for repair? At this point I finally reached the recovery screen and performed a true factory reset but havent tried flashing latest images from google. I will update and let you know if that worked. If that doesnt work, I will be getting the pixel on Verizon on black friday for the $10/ mo
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!?!
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app
Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors:
https://imgur.com/a/bBdbnvH
It was previously unlocked until I tried flashing the recent December update.
Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Ofuroski said:
Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors: https://imgur.com/a/bBdbnvH It was previously unlocked until I tried flashing the recent December update. Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Click to expand...
Click to collapse
Don't start a duplicate thread dude! Starting to sound like a Google FRP workaround to me. What does Google support say??
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
starcleff said:
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
Click to expand...
Click to collapse
I might be a bit late, but I had exactly the same issue, lost hope and all. I have tried multiple chargers and cables but nothing helped.
How I fixed it is:
1) Left the phone on in fastboot mode, until the battery died (unplugged obviously).
2) Left the phone unplugged for about 8h.
3) In the morning, keep pressed power button and plugged in the charger.
4) After few seconds it started up.
Hope this is helping you guys.
This just happened to me. Has the problem returned on you? Assuming I can get it to boot again, I'm wondering if I should do a factory reset to give myself a fresh start and clear out whatever software issue may be causing it, if it is a software issue.
Thanks fixed it
Thanks NathanTan...
It fixed my issue. I left it overnight with fastmode displayed. After it ran out of battery powered on and boom phone was back to normal. I never thought it will sort without replacing handset. Thank you
Hey guys. Please help. I am facing this issue in Pixel 5a now.
Only the end user can set the user-settable root of trust. It cannot be set at the factory or any other point before the device is delivered to the end user.
geometry dash is a game that is loved by many people.