Deep sleep issue - Samsung Galaxy S7 Edge Questions and Answers

Hi everyone,
I have installed the app S Tools + on my Galaxy S7 Edge and noticed that my phone does not go into deepsleep, not even once.
The phone is SM-G935F with stock firmware G935FXXU1APD1.
Could somebody please guide me on how to check why it does not go into that state, and how to fix it? Thank you in advance.
EDIT: After reading on other threads i found out that after charging the phone it does not go into deep sleep, but after a normal restart it will again

Related

Samsung S6 edge + battery problem

Hi,
I'm new to Android so please help me. About 2 days ago i bought a Samsung S6 edge +, everything it's working fine on it except the battery... even when i take him out off the charger in Battery section says that i have only 10 H aprox to go with it...is this normal? And the big problem is that if i leave him with 80% battery, in the morning i have only 32% with background apps closed before sleep. I mention that i have 6.0.1 on it and i have warranty so i don't realy want to root the phone or something that will make me lose the warranty.
Thank you!
snapydj said:
Hi,
I'm new to Android so please help me. About 2 days ago i bought a Samsung S6 edge +, everything it's working fine on it except the battery... even when i take him out off the charger in Battery section says that i have only 10 H aprox to go with it...is this normal? And the big problem is that if i leave him with 80% battery, in the morning i have only 32% with background apps closed before sleep. I mention that i have 6.0.1 on it and i have warranty so i don't realy want to root the phone or something that will make me lose the warranty.
Thank you!
Click to expand...
Click to collapse
Hello Snapydj, I think the problem can be caused by any app you installed. For be sure, first thing is restart de phone in safe mode (you can search how to do it here in this fórum) and see the behaviour of the phone in terms of battery. If the problem persists, try a full wipe and don't install immediately any app from play store. See the behaviour and then install apps one by one and observe battery drain. After all these steps if the problem continue you must send it to warranty.
I wonder I could help you.
Regards
flechinha said:
Hello Snapydj, I think the problem can be caused by any app you installed. For be sure, first thing is restart de phone in safe mode (you can search how to do it here in this fórum) and see the behaviour of the phone in terms of battery. If the problem persists, try a full wipe and don't install immediately any app from play store. See the behaviour and then install apps one by one and observe battery drain. After all these steps if the problem continue you must send it to warranty.
I wonder I could help you.
Regards
Click to expand...
Click to collapse
Hi,
I searched yesterday a couple of hours on forums and i think i find the answer. There are many threads that says that it is a known problem for S6 and S6 edge, they called it Deep Sleep problem. But any fix for it that i can find is with root, and i don't want to root the phone... I can't post external link because i am a new user on this forum...
snapydj said:
Hi,
I'm new to Android so please help me. About 2 days ago i bought a Samsung S6 edge +, everything it's working fine on it except the battery... even when i take him out off the charger in Battery section says that i have only 10 H aprox to go with it...is this normal? And the big problem is that if i leave him with 80% battery, in the morning i have only 32% with background apps closed before sleep. I mention that i have 6.0.1 on it and i have warranty so i don't realy want to root the phone or something that will make me lose the warranty.
Thank you!
Click to expand...
Click to collapse
snapydj said:
Hi,
I searched yesterday a couple of hours on forums and i think i find the answer. There are many threads that says that it is a known problem for S6 and S6 edge, they called it Deep Sleep problem. But any fix for it that i can find is with root, and i don't want to root the phone... I can't post external link because i am a new user on this forum...
Click to expand...
Click to collapse
Not at all. Yes, there is a deep sleep problem but is not the case of you certainly, because even with deep sleep issue in S6 edge+, it doesn't make battery drain like you have. I can say to you that my battery drain over the night isn't more than 1 to 2% per hour. So your phone has a abnormal battery drain for a regular S6 edge+ with stock rom. I remember you that my phone is standard, not rooted
Check your knox in bootloader. Maybe your phone has root before you buy it. Turn off . Press volume down, home and power button. Relase it when green screen appears. Then continue. Check info about knox warranty. There should be all 0. If you see somewhere 1 it will means that your phone has root before.
Damian83 said:
Check your knox in bootloader. Maybe your phone has root before you buy it. Turn off . Press volume down, home and power button. Relase it when green screen appears. Then continue. Check info about knox warranty. There should be all 0. If you see somewhere 1 it will means that your phone has root before.
Click to expand...
Click to collapse
Hi,
I checked there and you're right. Appears void 1 but I checked with a program and says that the phone doesn't have root. I took the phone before I used it on a service shop to unlock to work on all carriers because was locked on single one. Maybe that's why appears void 1 there right ? I flashed myself yesterday afternoon the last build for 6.0.1 and now I'm waiting to see if something changed.. And then I restore to factory settings and then cleaned wipe partition.
Sent from my iPhone using Tapatalk
Hi ,
I want to share with you the fix i found. So... as you know , i have flashed another build of 6.0.1 , the general version for Romania. This still hasen't fix my problem, but last night after reading more post, i saw someone who said that if you have knox tripped to 1 is a known bug to have battery drain and the only fix is to root the phone, so i said that i should try this too. I root the phone with CF root method through Odin and then install CPU Spy and 3Cpu and ... surprise!! ... Cpu's are going to sleep now, and the problem is fixed. I don't need to install anything else (on some forums says that you have to install twrp recovery and the install a zipp).
Now the only question is, i don't know why knox was tripped to 1 ... the phone wasn't rooted before... i read somewhere that even if you flash another stock rom with odin you trigger know , is this true ? Is any method that i can reset the counter after i unroot the phone ? I mean i don't want to lose warranty.
Rooting always trips Knox, and tripping Knox is irreversible.
B3311 said:
Rooting always trips Knox, and tripping Knox is irreversible.
Click to expand...
Click to collapse
I don't think you understand. Knox was already tripped before I root the phone. And only thing has happened before was flashing another stock rom on the phone.
Sent from my iPhone using Tapatalk
I understand, you don't.
Your phone had been previously rooted. Whenever and whoever unrooted it at a later date is irrelevant - knox is tripped.
You asked if there is any other method to reset the counter. The answer is no.
snapydj said:
Hi ,
I want to share with you the fix i found. So... as you know , i have flashed another build of 6.0.1 , the general version for Romania. This still hasen't fix my problem, but last night after reading more post, i saw someone who said that if you have knox tripped to 1 is a known bug to have battery drain and the only fix is to root the phone, so i said that i should try this too. I root the phone with CF root method through Odin and then install CPU Spy and 3Cpu and ... surprise!! ... Cpu's are going to sleep now, and the problem is fixed. I don't need to install anything else (on some forums says that you have to install twrp recovery and the install a zipp).
Now the only question is, i don't know why knox was tripped to 1 ... the phone wasn't rooted before... i read somewhere that even if you flash another stock rom with odin you trigger know , is this true ? Is any method that i can reset the counter after i unroot the phone ? I mean i don't want to lose warranty.
Click to expand...
Click to collapse
if you knox is 1 ,you will be lost of warranty.[/B
normal ,flash another stock rom will not tripped knox .
only flash custom rom or twrp will trippe knox.
after you trippe knox ,knox cannot go back 0.
FOR YOU BATERRY ,
YOU CAN use debloater to debloatware of preinstallar system app.
here is link [ if you like ]
Universal Debloater-Mod for S6EdgePlus - v2.2 | AUTO-ROOT & BUSYBOX |
http://forum.xda-developers.com/s6-edge-plus/development/universal-debloater-mod-s6edge
this will save alot of baterry.
or flash custom rom
for example like
Pure-Stock ExtraLite Rom
http://forum.xda-developers.com/s6-edge-plus/development/sm-g928c-pure-stock-extralite-rom-t3383399
FOR you flash rom , one thing importante
you need backup EFS .
ENJOYED FLASH

Yotaphone 2 reboots by itself after after the screen switches off.

Hello
I have a Yotaphone 2 running android 5.0. I have a huge problem with the device which is, that the phone reboots automatically all by itself after the screen turns off. The screen timeout is set at 1 minute and once the screen goes off, the phone reboots! I don't know what the problem is but its making me crazy!
Note: The phone does not reboot if the screen doesn't turn off. So I changed the screen timeout to 30minutes. Also note that Wi-Fi doesn't start immediately. It doesn't even start most of the time and is stuck at "turning on"! And also, the phone isn't detecting my SIM Card!
Hope someone can solve my problem.
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
I got the phone as a gift
TheArt. said:
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
Click to expand...
Click to collapse
-The phone was a gift from "Aramex Company".
-Yes, I have factory reset it! Note: It wasn't possible to reset it from settings because it would always get stuck in "Shutting Down" phase and nothing would happen. So I hard reset it.
-I found something strange going on though. Whenever I reset it, It would restart (after the reset is over) and say that "ANDROID IS UPGRADED TO 5.0".
I think it is upgrading by itself to 5.0.
-No, I haven't tried any flashing.
-Yes, the phone was working fine for a while and then started behaving like this!
Cheers!
(Thank You for your support and attention by the way)
Video
Hello!
I have made a video showing what the problems are! Please give me your e-mail so that I can send you the "Dropbox" link to the video.
Thank You!
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Flashed it!
TheArt. said:
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Click to expand...
Click to collapse
Hey!
As you had prescribed, I flashed it! First I flashed it with Android 5.0.0-ME1.1.60 and after opening the phone I used it for a while and the phone was same as before flashing! There was no difference at all! The phone was restarting on turning screen off as usual, the WiFi wasn't turning on, and the SIM wasn't being recognized!
But then I flashed it with Android 4.4.3-S01-003-ME1.0.3.61a and the phone is still rebooting by itself upon switching the screen off and the WiFi problem still persists! The WiFi just simply won't turn on. It's stuck at "turning on"! The SIM isn't recognized either! Also, the phone is restarting from the inside now (It wasn't restarting before. I had to keep the power button pressed every time I wanted to restart)! But NOTE that the phone still cannot be just shut down, it can only be restarted!
I don't know what to do!
Cheers
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Why are you unable to make yotaflasher work
lgk350tr said:
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Click to expand...
Click to collapse
Hi lgk350tr,
Why are you unable to make yotaflasher work, it is a pretty simple application. Have you tried to see instruction videos on YouTube on how to use it? Instructions are also available on XDA Developers' website. ( https://forum.xda-developers.com/yotaphone-one/general/yota-flasher-download-t3480922 )
Don't hesitate to contact, for any problem!
Cheerio
Please help..................I spent 800 USD on this phone and I can't use it
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
akahomeacc said:
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
Click to expand...
Click to collapse
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Is this what you mean?
tomgaga said:
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Click to expand...
Click to collapse
I have attached a screenshot of the Yotaphone 2 General guide page, I want to know if you are referring to the text that I highlighted in the screenshot!
Thank You
I do experience similar issue, but only recently. I haven't done anything like flashing or upgrading my phone, it started by itself .
I am experiencing reboots whenever battery drops below about two thirds of its capacity. Also, charging and handling some load prevents this.
Note that my Yotaphone has both displays damaged. Still working though.

SM-G935F issues after update to 7.0

Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
That's very unusual to trip knox via Odin, was second hand phone?
Maybe try flashing 6.0.1 firmware and hold off updating until 7.0 is sorted.
It was an upgrade on my contract in October so it was brand new.
I'll try to flash 6.0.1 again and see if I have any more luck with it.
I'm tempted to go back to the store and ask for a replacement but I know they'll question the warranty void counter. I'm just so confused as to why it's tripped it.
Sent from my SM-J320FN using Tapatalk
Perhaps is a bad flash reverting back to MM should fix issue but certainly not knox counter.
I'm also awaiting long overdue nougat update and was going to flash via Odin until I read your post. Slightly nerves now wonder if anyone else has had the same issue of tripping knox.
I've just updated via odin and no knox trip, void counter remains the same.
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
dollar7 said:
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I'll give this a go tonight and see how I get on.
I find it very odd that both 7.0 and 6.0.1 gave the same restarting issues which is why I'm worried it's a hardware issue and not software.
I do have the TWRP file so could flash that, do a dalvik and normal cache wipe too after installing nougat again.
Sent from my SM-J320FN using Tapatalk
So I installed 7.0 again and it is still crashing and becoming a completely unresponsive phone with a black screen. Again, left it over night and plugged in this morning to charge and it's on again. I have absolutely no idea what to do to fix this issue.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
SHREYSTARK said:
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
Click to expand...
Click to collapse
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to ? they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Galactus said:
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Click to expand...
Click to collapse
Since installing Superstock Rom, the phone has, so far, been completely crash free and no random reboots when trying to do something simple like uninstall an app. Fingers crossed it stays this way!
Sent from my SM-G935F using Tapatalk
Search 1st b4 post!
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
There's already a thread about this!
Nougat known bugs thread *Updated*

I'm unable to root my S5 Lolipop 5.1.1. keep getting error msg w/my apps???

Quick, recap, I own a galaxy S5 Lolipop 5.1.1 SM-G900W8 build #LMY47X.G900W8VLU1COI4, previously rooted.
It all begin, when my phone been experiencing some battery draining issue. So I decide to do factory rest. But get this at that time my phone was fully rooted, w/Lolipop 5.1.1...
So I've read all the informations I could get online made sure to unroot the phone ( using CF-Auto Root ktlevl-sm G900W8.), with Odin, and reflash the phone with custom recory (G900W8VLU1COI4.tar.md5 file). I've made sure to get the exact one matching my phone carrier.
And after rooted the phone...All went well...Then 24-48 hours after the **** hit the fan.!!!!
They weere dialogue box keep poping up, from Touchwiz has closed, to Unified Daemond has closed just to name a few...
I decided to factory rest the phone again, reflash and rooted same problem occuring occuring.
So I decide not to root and the issue stop but now I'm unable to fully use my phone because it anin't root so certain function of my phone can't benefit such like using Airplane mode or Mobile data toggle using tasker. When my phone was fully rooted I was able to take full advantage of my Tasker profile. I've google the web and came acrros people who expericing the same issue as I did, but can't find a solution.
If there anyone who had that problem and manage to solve it, kindly share your story and solution with me....
Thank you in advance on getting back to me,

S7 Edge, Won't boot OS.

Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
JTec11 said:
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
Click to expand...
Click to collapse
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
xTweeBy said:
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
Click to expand...
Click to collapse
Love a good Samsung lmao, thanks for your reply

Resources