Database Info

Dead photon?

Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance

Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger

Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.

Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened

kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.

This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.

kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?

arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.

kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.

arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom

Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.

kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.

Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot

kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.

http://i.imgur.com/3XYLngJ.png

kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?

Yes

Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.

I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now

S6 keeps Rebooting

Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?

mtshure said:
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
Click to expand...
Click to collapse
The OE2 tar file shouldn't wipe your phone as it is not a full wipe tar. I don't know if your phone would do it with it's reboot problem but a dirty flash of clean rom shouldn't wipe your phone either. However, a reboot during the middle of either of those would not be good. Flashfire does seem to be able to keep a phone from rebooting once it gets going or at least it has for me when I have been caught in a bad way before.

Problem Solved!!!
Thank you Tulsadiver for your suggestions. But is it okay to do odin without wiping anything?
I almost gave up after struggling several hours and thought about doing a factory reset, but the problem is solved now.
I found it weird that the soft key lights never turn on, so I thought that there might have been something wrong with the power management. So I turned the ultra power saving mode on (fortunately the phone didn't reboot before I did that), and it didn't reboot itself. I turned it back off then now the problem is gone!
I am happy with it now, and this might be one of the things to try if you experience a random reboot.

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

S7 crashes on boot. No response to input. Drain to 0% to power on again.

It started a few days ago, I was testing a cardboard/gear vr unity game and the screen would turn black but the buttons were responsive and I could get it to hard reboot or make it come back again after plugging it back into the gear. I looked around but couldn't find anything that resembles my issue.
Now as soon as it boots it goes into a black screen after samsung and carrier logos show, i sometimes get a glimpse of the lock screen and respond to some input.
The phone is still on, I can feel the battery warm.
-No response to any input. Not even pwr+vol down.
-PC won't detect it when plugged.
-No lights on charging.
-I need to let it fully drain for it to shut down and try anything again.
-Did a factory reset from recovery mode, wipe cache. Still the same.
-No root.
-There was an update that may have installed overnight but can't confirm because can't access system info.
EDIT: New find! when booting to recovery, goes into "Installing Update" and then "No command".
Any thoughts??
Is there some pc software that i can use to try to reinstall firmware? Something like SEUS for sony phones back in the day?
Is odin safe or should i look into a samsung official tool? I've never used odin so i'm not sure of it's capabilities (this is my first sammy phone, I had it to get to test gear vr apps)
Sorry for the long post but wanted to get all the info out there.
Thanks!

Can you enter "Download Mode"? (By rebooting and pressing HOME + VOLUME DOWN)
If yes, I suggest that you try, as you suggested, reinstalling your firmware.
You will have to know your carrier, or specific phone model (G930X, where X represents carrier letter (Example: T for T-Mobile) )
Modified Odin (by PrinceComsy): https://androidfilehost.com/?fid=24591023225177749
Then I suggest downloading firmware from https://SamsungBay.com as all other sources restrict download speed (So it takes a minimum of 13 hours).
https://samsungbay.com/download-firmware/?device=&model=sm-G930&firmware=
Once you have Odin and Firmware, load the correct files.
(AP_G930X), (BL_G930X), (CP_G930X), and (CSC_G930X) into Odin.
Power off phone, and boot into download mode (Pressing HOME + VOLUME DOWN)
N.B/ You will lose all your phone data, sadly, but it seems you've already wiped it.

Samsung S7 - Random Crash / Restart constantly

Hi,
My S7 crashed randomly and was stuck in a loop of the recovery menu. The short version is, I was fairly convinced it was a battery issue, and after changing the battery I was able to boot up successfully and (eventually) backup / copy off all my files. It wasn't esasy as it was constantly crashing and very unstable.
So, I did a full factory reset. This was via the settings menu after booting up and logging in because I couldn't access the recovery menu method. Factory reset has not solved my issue is still crashes usually after a few minutes at best.
Things that work
- Screen not broken, works perfectly, no dead pixels.
- No water damage / not dropped
- Volume Up and Down keys work (for volume and force power off when its crashed)
- Speakers / Microphone
- Both Cameras
- Wireless charging
- Cable Charging
- Full factory reset to latest stock android 8. Never rooted. Totally stock.
Things that don't work
- Vol Up + Home +Power to get to recovery menu / safe mode. Never managed to successfully do this
- I think it could be running a bit hotter than before, this may be subjective.
- Sometimes it crashes, screen powers off, but red charging light remains even when unplugged and it runs hot. Basically until the battery dies.
- Often crashes on first boot, e.g. during "samsung" boot screen. - Will restart and often gets to login on second attempt.
I've been testing via the diagnostics menu *#0*# (What a cool feature!) - Generally this is working ok, and nothing jumps out as failing, but its not easy as it crashes so randomly anyway. Can anyone recommend anything specific I should test?
So - Have I got a new Brick? Is there anything else I should do to try to save my phone? If it was smashed I could begrudingly write it off, but its in otherwise perfect condition! (3 months out of warranty!)
First time poster, any help appreciated.
Thanks

Sandstone Stickman said:
Hi,
My S7 crashed randomly and was stuck in a loop of the recovery menu. The short version is, I was fairly convinced it was a battery issue, and after changing the battery I was able to boot up successfully and (eventually) backup / copy off all my files. It wasn't esasy as it was constantly crashing and very unstable.
So, I did a full factory reset. This was via the settings menu after booting up and logging in because I couldn't access the recovery menu method. Factory reset has not solved my issue is still crashes usually after a few minutes at best.
Things that work
- Screen not broken, works perfectly, no dead pixels.
- No water damage / not dropped
- Volume Up and Down keys work (for volume and force power off when its crashed)
- Speakers / Microphone
- Both Cameras
- Wireless charging
- Cable Charging
- Full factory reset to latest stock android 8. Never rooted. Totally stock.
Things that don't work
- Vol Up + Home +Power to get to recovery menu / safe mode. Never managed to successfully do this
- I think it could be running a bit hotter than before, this may be subjective.
- Sometimes it crashes, screen powers off, but red charging light remains even when unplugged and it runs hot. Basically until the battery dies.
- Often crashes on first boot, e.g. during "samsung" boot screen. - Will restart and often gets to login on second attempt.
I've been testing via the diagnostics menu *#0*# (What a cool feature!) - Generally this is working ok, and nothing jumps out as failing, but its not easy as it crashes so randomly anyway. Can anyone recommend anything specific I should test?
So - Have I got a new Brick? Is there anything else I should do to try to save my phone? If it was smashed I could begrudingly write it off, but its in otherwise perfect condition! (3 months out of warranty!)
First time poster, any help appreciated.
Thanks
Click to expand...
Click to collapse
Can you flash latest unbranded stock? If still happens then it's battery failing. S7 is old phone now

cooltt said:
Can you flash latest unbranded stock? If still happens then it's battery failing. S7 is old phone now
Click to expand...
Click to collapse
Thanks, I've replaced the battery with a new one. Tried full factory reset a second time but it crashed and hasn't restarted since.
I think it must be a hardware issue. It thinks its charging when unplugged, gets hot when "off" won't switch off when crashes so need to wait for battery to die before recharging and trying again.
Yes, its old ish, but really only just over 2 years. My S3 lasted 4.5 years so getting half the lifespan from the S7 is really dissappointing. It was in perfect condition until this happened .