Hello everyone,
I have a Galaxy S7 G930U and it was out of warranty.
I searched the internet and I could see that so many people have had the same issue, not only the S7 but also other galaxy phones. I tried all the solutions available on the internet but still couldn't solve the problem
I was exposed to a light rain (I didn't have to use an umbrella) while it was in my pocket
1/ Opening the camera app, the phone, the camera app fails -> the phone freezes and reboots immediately -> after the reboot, the OS loads the camera in the background (I don't touch anything and let it boot up normally itself) -> the phone freezes again and reboot -> it booploops for several times until it's usable again
2/ what I have tried:
- Clearing the caches of gallery, camera app, clearing the Cache partition and factory reset in recovery mode, forced reboot by Vol -down + Power, booting in safe mode -> all of them couldn't fix the problem or just the phone was partially usable for a while until it happened again
- Navigated to Developer options -> Inactive apps -> inactivate the camera -> sometimes it worked but sometimes it didn't. I mean it prevented the bootloop unless I opened the camera again
- factory reset in recovery mode: it even bootlooped during the initial setup wizard -> it took me 6-7 times to finish the wizard due to the reboot during selecting the options
- Hard reboot by Vol-down + power -> sometimes, it was fixed but now this doesn't work anymore
- I took out the sim and SDcard tray and left it open for exactly 2 days. No improvement
- I tried to use my phone without the SDcard, nothing changed
- I left the default mode of the camera app in the rear camera and sometimes the camera worked. As soon as I switched to the front camera, it failed
- I tried to press the areas around the camera, tap continuously, shake the phone. Nothing happened
- checked for updates but no update was available
- I also noticed while I was entering the recovery mode, it said: "No command" (never happened before). It let it run for 30 seconds without touching, it successfully booted up to the recovery. This has happened all the time since then
bootloops
My current workaround to stop the bootloop is to clear the camera app data and never turn it on + inactivate the camera in developer options
Please help!!! This issue is very severe and makes me angry. I wonder why I bought this phone in the first place with this kind of issue. It's no longer a normal phone anymore
Thank you
If the rain caused the problem you could try using Isopropyl alcohol to clean the water residue off the board which could be causing the problem
deleted
hello, thank you for your answer, unfortunately, I'm not able to open up the phone myself, none of my friends can also do that. when I bring it to a phone repair shop or samsung, they may refuse to do what you suggest and recommend a full mainboard replacement. This may cost more than the phone itself. I'm don't really know what to do now
Related
Hi all,
Some months ago my screen cracked and last week I finally received a replacement screen which I was able to install.
I have been looking for many hours to find a similar case but could only find cases where the touchscreen didn't work at all or intermittently stopped working.
The problem:
I can start my phone, the touchscreen works perfectly.
When I lock the phone and seconds / minutes / hours after I wake it again, the touchscreen stopped working (the power button and volume button still work)
Repro:
1. I replaced the screen.
2. started the phone -> touchscreen is working 100% (i can do everything)
3. I lock/sleep the phone (power button)
4. I unlock/wake the phone (power button) -> touchscreen is not working anymore
5. I restart the phone by taking out the battery and we are back to step 2, it works but stops as soon as I lock it again
What I've tried:
- multiple different roms, all resulting in the same problem
- hard resets / factory resets/ cache resets / dalvik resets
- removing the slide lock
Is there anything I can still try?
Isn't it strange that the touchscreen does work after booting, but the moment it sleeps/locks it stops working
The only way it works is by never putting my phone to sleep, which is not the best solution, right!?
Unfortunately at the support center of the manufacturer they don't know the answer either:
==
Hi,would you please take it to your local repair store?
Please give me feedback from them.
FaeaMobile Support
==
I tried adding a link to a youtube video I made, but I'm unable to add it because of the no. of posts i have.
Does this video help explain the issue, and does anyone have any idea how I can fix this?
youtu.be/5L6CHNrIp8M
Hi XDA, looking to you for answers...
The Device: I bought my Verizon Galaxy S6 straight out due to that phone trade in for $100 gift cards that happened way back in April. So I have no insurance on the device. No worries, as its in a otter box commuter case with tempered glass and I baby my devices.
The problem part 1:
-Last week just before I walked out the door for my anniversary dinner. I restarted my device and it didn't come back on.
- I plugged it in and got no light. Pressed volume +/-/home/power - and got the boot screen
- Accidentally factory reset the device when I let go off the combinations of buttons (why factory reset is the second option I have on idea)
- After the initial factory reset, I noticed it didn't go through. Rebooted and saw DM-Veritiy verification error
- Tried multiple times to get a clean factory reset until finally I got into the phone setup wizard
- Phone setup wizard froze on me about 3 times before I was able to get it to work
- Finally with finesse and some luck, I was able to get the phone partially restored but I knew something was fishy
- Brought the phone to Verizon which said I have no insurance, the only thing I may have is a manufacturer warranty with Samsung.
- The rep tried to factory reset the phone, however the DM-Veritify verification error came up again and could no longer continue.
- After some time there, I felt like I was wasting my time, Figured I would this myself.
- Went home and flashed the STOCK OS on my galaxy s6 with ODIN.
- After ODIN, and many OTA updates, I was on 5.11 and restoring my phone
After all this, the phone worked PERFECTLY FOR A WEEK
The problem part 2:
- Was in a parking lot to get some groceries, sent a text and put the phone in my pocket. When I looked at it again, the phone was off
- Tried to turn it on... nothing... I held the +/-/home/power buttons again and rebooted normally
- Phone started up just fine but froze after a minute.
- If I get the phone on, it will either freeze/hard-lock or when the screen turns off, then its just turns off, or restarts itself to failure
- I've tried to reboot into recovery volume +/home/power to wipe the cache, however I get an android in distress
- After a few attempts to get into recovery to wipe the cache, I managed to get past the distress icon and press get the menu selection down once before the device froze
- After more attempting to to wipe the cache. I don't even get the android in distress icon anymore, just the blue android screen hangs
- If I use all the buttons to reboot normally - the phone will freeze or once the screen turns off, its off.
thats it
I feel like I just ate $700
XDA please help
Phone freezes in "recovery mode" 3 seconds in. Managed to get one wipe cache in.
Getting a "system rev. check fail device: 3 binary 1 error" error when trying to flash ODIN.
Guess you can't flash stock OS from 5.1.1
got a factory reset to go through just fine. Restored phone for 30 minutes and proceeded to use it.
Seemed fine and then froze while texting.
Seems to be randomly freezing and then a sudden restart.
Contacted verizon for the number to call for warranty send off.
*looks around* I see MULTIPLE issues regarding the S6 randomly restarting.
I should have got the Note 4
Hi,
Sorry, but if it keeps happening persistently even after factory resets and successful stock installs, I'd call it a hardware problem. The best thing you can do is contact Verizon or Samsung and try getting a replacement.
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.
mazzuli said:
Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.
Click to expand...
Click to collapse
Did you wipe your data partition when you updated frowm 4.4 to 6.0? Its most likely that all the apps are crashing due to incompatible data files.
I've once had the same problem and i managed to fix it with deleting data for every crashing app, so this might be an option.
Otherwise you might fix your phone by factory reseting from recovery.
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 .
I've been using HTC U11 Plus as my main phone since the day it came out. I absolutely love this phone. In my opinion it's the best phone I've ever had. I never felt the need to get a new phone. I've been gaming, working, etc. and I never had any issue with it.
Two days ago all of a sudden while using my phone it got stuck. None of the button were working and the screen also had response so I pressed and hold the Power button and Volume Down button to boot into recovery mode. So i could clear cache and reboot again but my phone doesn't seem to reboot. It just turns off when I select reboot now. I even tried "Wipe data/factory reset from the Recovery menu options" and then delete all user data option and then Reboot system now to restart your phone. Still no luck. As soon as I press on reboot system my phone just turns off and doesn't reboot or turn on at all.
Even when I put my phone on charging there is not light to indicate that my phone is charging at all.
PLEASE HELP!!!!
Same problem here... Screen flashed white, phone rebooted to encryption screen to enter pin, then powered off... Hasn't been back on since (thins happened in October 2021).
I'm interested in a possible way to get the data off the phone, even if some parts swapping is involved.
PS. I changed the battery thinking it was that, but the phone still isn't coming on or showing the red battery charging light.
I guess it is time for you both to use ADB. When installed properly you should be able to see your phone in device manager on Windows systems. That in itself would be a good starting point. Or just fire up ADB and check if ADB detects your phone. If you are unfamiliar with ADB, Google it.
In ADB use: *.\adb devices* (without the *) If it works properly you should get a return with a device number. You could then flash a boot image or system image or both and see if your phone start's up again.
Hello,
same Issue here.
Solution is to heat up the Phone above 50°C and hold the temperature while it run and copy Data.
I have spend 40h+ to Backup Data and heat up the Phone.
Seems for me to the same problem like the RROD at Xbox360.
Lead-Free solder at the BGA-Chips.