Phone froze - is it dying? - General Questions and Answers

Hi.
I'm trying to find out if my phone might be dying on me or if it just had a bad one-time crash.
I have a Galaxy S7 (not rooted) that has had no issues for about one and a half years.
Yesterday, after I closed a piano app and a bit later went back to my phone, the screen wouldn't turn on, and the phone was frozen. None of the buttons did anything to make the phone usable again, and no display or light features did anything. I held the power key without success. I plugged the phone into a charger, and no light came on although the charger seemed to recognize that something was plugged in.
Someone else was able to find the shortcut to force reboot the phone (hold Power and Volume Down for 10-20 seconds), and that finally did it.
However, it seemed to me that the reboot took considerably longer than usual - the desktop icons would not show up for about 10 seconds, and many apps would open but not display any of their data for again 10-20 seconds. After a while, everything seemed to work again, but I'm worried.
So far today, the phone seems to be working normally. I just used Helium to create a backup of my app data, and it made my phone really warm - although that could be normal for Helium.
I typically don't restart the phone often, maybe once or twice a month. I leave it on and charging overnight.
In your experience and estimation, is it possible that my phone may be close to dying, or is it likely an app just crashed catastrophically and froze the phone?
Any thoughts on what could have happened, and should I prepare for getting a new phone, or is there something else I can try to check if the phone is still alright?
Thanks!

rlund said:
Hi. I'm trying to find out if my phone might be dying on me or if it just had a bad one-time crash. I have a Galaxy S7 (not rooted) that has had no issues for about one and a half years...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3341138
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Just did, thanks!

Related

[Q] Frozen start screen on Samsung Omnia7

Apologies for starting this thread but I've searched the WP7 forums before posting this.
Last night my phone battery died (as per normal with heavy use), when I plugged it into the charger later in the evening, it turned on and has remained frozen on the start screen "Samsung Omnia7" and doesn't load up as normal from there.
I've left it charging for a few hrs, so I know battery is ok, but everytime I turn it on, it's frozen on that screen.
I've tried a hard reset which takes literally 2 seconds before saying that it's done but then goes back to the same start screen and remains frozen.
Any ideas what to do?
sameerabedi said:
Apologies for starting this thread but I've searched the WP7 forums before posting this.
Last night my phone battery died (as per normal with heavy use), when I plugged it into the charger later in the evening, it turned on and has remained frozen on the start screen "Samsung Omnia7" and doesn't load up as normal from there.
I've left it charging for a few hrs, so I know battery is ok, but everytime I turn it on, it's frozen on that screen.
I've tried a hard reset which takes literally 2 seconds before saying that it's done but then goes back to the same start screen and remains frozen.
Any ideas what to do?
Click to expand...
Click to collapse
Since you've already hard reset and lost your data, you could try flashing a new ROM from samfirmware.com.
There's a really good guide for doing this in the Omnia 7 forums:
http://forum.xda-developers.com/showthread.php?t=973420
Thanks for the suggestion, will give that a go.
Alternatively, I may just use my phone insurance and arrange a replacement through Orange.
Better get a replacement if can.
sameerabedi said:
Thanks for the suggestion, will give that a go.
Alternatively, I may just use my phone insurance and arrange a replacement through Orange.
Click to expand...
Click to collapse
You could do that. Flashing would most likely void your warranty so may be worth trying to get a replacement first.
Managed to get a replacement from Orange this evening.
The mods can delete this thread if you want.
Also, just a quick note, connected it to Zune and the NoDo update is still not available unless I push through the method mentioned here on the forums.

Phone randomly corrupted somehow, need help.

Hello people, first off lemme say I'm not necessarily new to this forum, I for sure have used it a hell of a lot in the past and I know roughly what goes on around here, I've recently created my account in order for me to actually be able to be able to plead for the amazing help the XDA is known for.
Anyway, long story short, I don't know what the hell happened, but allow me to start from the beginning. I went on a camping weekend with my OPO, phone worked flawlessly all weekend and lasted the whole time, everything was fab, went back to a mates house and asked if I could borrow his phone charger (He has a Lumia 625 incase anyone was wondering), we then went out shooting and I left the phone there for a few hours to charge. Came back to it and it was fully charged, but had turned itself off? Because it was on the power off charge screen when I came back to it, and was on lock when I left it, nobody touched it in that time. I took it off charge, powered the phone up and it must of boot looped about 3 times? Eventually it got into CM but there was no lockscreen, went straight to the homescreen. This is where it went nasty, the capacitive keys outright weren't responding, the device wasn't slow as such, nor was the CPU running hot or doing anything intensive (I have CPU load display enabled), but the date was set to Jan 1970, and the phone couldn't pull a signal at all. WiFi outright wouldn't switch on either. So I tried rebooting it a few times, to no prevail. For some reason, I accidentally tapped Bluetooth in the quick settings panel, the phone crashed and rebooted, and wouldn't stay on for more then 3 seconds? Before crashing and rebooting. I've since gone into recovery and tried a factory reset, cleared cache and media too, but to no luck. Phone still doesn't stay on for more than about 3 seconds once it actually gets into CM (The welcome to CM screen, it crashes 3 sec immediately after boot).
I have no idea what I'm supposed to do, can anyone try shed some light on this? Much help would be appreciated and I sincerely APOLOGISE for the wall of text. Many thanks.
^Dat wall of text doe (sorry about that)
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2922849
PS. You might want to consider using paragraphs in future posts, that's one hell of a long paragraph there [emoji13]
Transmitted via Bacon
Thank you man for the pointer, I'll give it a go. And yeah sorry for the wall.
No worries, I hope it works for you.
Transmitted via Bacon
I am having the same issue since last night. Put my phone to charge and when I picked it up it stayed on for about a minute unable to connect to Wifi or cellular signal. Then it went to a crazy boot loop. Wiped cache, media and at the end data. Now it boots and it stays on for a few seconds and reboots. I will try the solution when I get home tonight but I was just curious if it worked for you.

S6 100% unresponsive with irreplaceable photos contained within... need options

Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.
Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.
Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).
I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.

bricked S7?

Hi,
I think I have bricked my S7.
Yesterday I installed Superman Rom and everything was working fine until this afternoon.
I played a bit around and somehow my S7 got stuck and it seemed like i messed something up. I was in some kind of bootloop so i flashed everything new -Bootlaoder, Modem and Superman Rom.
Now I have a black screen and the LED is light up in blue.
I can't do anything. Tried to restart with Home Vol- and Power key but it doesn't work.
If I connect it to the Computer it won't be recognized.
Strange thing is, if I press the Power Key the computer recognizes Exynos8890 in the device manager, but only if I keep pressing the power key.
As soon as I release the power key the computer recognizes nothing...
Does anyone have an idea?
Try holding Volume Down & Home & Power until the phone reboots twice, keep the buttons pressed for 2 full reboots, and hopefully the 2nd one will get you back into download mode
Thank you for your help!
I tried that but it doesn't work.
It's strange because I can do what I want and nothing happens.
Black screen and blue light. It doens't even turn off or reboot...
Only thing what happens is that exynos8890 appears in the device manager as long as I keep pressing the power button.
Same problem as me?
http://forum.xda-developers.com/galaxy-s7/help/boot-loop-bricked-t3499109/post69596073#post69596073
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
alexx3333 said:
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
Click to expand...
Click to collapse
How long are you holding the button combination for?
Try 30 seconds+
I tried for several minutes, but the phone doesn't do anything.
I can only think you'll need to wait until the battery runs out, the phone shuts off, then when you charge it again, try the download mode button combo when you power it back on
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
alexx3333 said:
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
Click to expand...
Click to collapse
Connect the white Micro > Normal USB adapter that came with the phone to the MicroUSB port, and connect a power hungry USB device to it, I just tried with a USB desk fan and the phone powered it on spinning
That will drain the battery quickly
Great idea but it doesn't seem to work.
Looks like I have no power in the USB connection.
Seems like the phone is totaly frozen.
Ok so how it looks at the moment, my only choiches are wait several days until the battery dies (don't know how long this will take) or sending it to Samsung for a repair.
Thank you for your help!
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
*Detection* said:
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Click to expand...
Click to collapse
Yes I have tried that but no power at all...
stoanhart said:
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
Click to expand...
Click to collapse
That sounds exactly like my Problem.
A faulty storage chip would also explain my Problems before the phone died for good.
The day my phone died I had some Problems. The phone was frozen from time to time until it got into the bootloop, but I thought I messed something up in the Rom because I did a lot of testing and the Combo also did work.
After reflashing the Rom everything seemed to be fine first until it died for good.
Yes it's strange, I also didn't find anything similar on the Internet.
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
stoanhart said:
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
Click to expand...
Click to collapse
Contact Samsung on twitter, unlikely they'll force you to RMA to Nigeria, they'll have service centres in your region
I managed to get Samsung Canada to refer me to a local service center. I drove 1.5 hours to go there today, the dude plugs it into a charger, and the damn thing just lights up like nothing ever happened. Now it's working fine, but I swear this thing was fully bricked before. The battery still had 73% charge when it came back alive...
I'm happy it's working now, but I'm worried it's just going to crap out again at any time.
Update: after the phone revived itself, it worked pretty well for a week. It locked up a few times, but I was able to reboot each time.
But, after a week, it hard-froze again. This time, it happened to be on charge while it froze so the green LED was on. It's been completely unresponsive for 2.5 weeks now, off charger, with the green LED on. I keep waiting for the LED to drain the battery, but it's taking forever. I'm losing hope that it will recover this time. I guess I'll re-start the process of getting in touch with Samsung, or alternatively, look for a replacement motherboard on eBay.
Does anyone know if the G930F motherboard fits into the G930FD body? I don't actually care about dual sim, but I'm concerned the SIM tray/slot won't work with the G930F motherboard.
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
alexx3333 said:
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
Click to expand...
Click to collapse
Hi,
Do you need Proof of Purchase for the warranty?
Thanks.

Pixel (rooted) won't turn on or respond

I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
Maybe, but I got it brand new from Google a bit over a year ago (06/2017), making me generally hope it isn't something related to 'natural causes'. I think what bothers me the most about this is that I don't know what went wrong and can't think of anyway to check. Plugging it into a wall plug to charge doesn't do anything and when I plug it into the computer my computer doesn't see that anything is plugged in (as I have installed upgrades via my computer, it definitely has the right drivers and everything to see it...).
The slightly paranoid side of me recalls back a few days ago to an article I was reading about malicious apps using phones to mine cryptocurrency, sometimes leading to those phones wearing down enough that they could even brick. Logically I'm almost positive this isn't happening for two reasons. The first being that I haven't installed anything for about a week (and the phone was working fine until this morning) and secondly because I had an app that monitored my network traffic and there wasn't nearly the throughput I'd expect for that kind of processing. Still, I can't think of what else might have happened...
sdnative1 said:
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
post-mortem said:
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
Click to expand...
Click to collapse
Thanks for the freezer suggestion (I recall that trick for old hard drives, but never used it myself). How long you thinking for that to do anything? I tried about 10 minutes and didn't see any difference (not sure if I should be doing something closer to an hour or more?) I did Google support (online chat) and ubreakifix was one of two other options they suggested. It looks like they're a little bit of a drive for me, but I'll see if I can't stop by in the next couple of weeks. My old Galaxy S5 will have to do in the meantime (which is slow with poor reception at this point, but it functions as a phone, so I've got that going for me
I'll try to update if/when I get details from the repair guys.
If the freezer trick did anything, it would likely be temporary (possibly enough time to get data off of it). It would really just confirm a hardware failure, which at this point is my working hypothesis.
One day my pixel randomly shut down, unresponsive, holding power button did nothing, same when I tried to plug it to a pc or when plugged in.
It restarted when i pressed power + vol- (fastboot mode) for about 40secs - I know, it's a lot, never knew what happened.
Then it just worked normally

Categories

Resources