Sleep/Wake problems [SOLVED] - T-Mobile Samsung Galaxy S6 Edge+

So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.

msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel

powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.

So enjoy the fix if you ever run into the above issue.

Im fine with stock, but I miss the fun of trying new roms.

Related

Device strange issue will not stop giving problems!

This is a list of events that I have gone through today. I received a new charger because the old one I had became defective & was charging my phone up & then it would go back down to 0% & then shut off & it would end up in a problem where the phone would not turn on unless I pulled out the battery while the AC was in & then it was able to charge but still it would turn on, on its own to drain the battery when off & this was very frustrating. The charger I have now works but the device acts strange over the last few months doing a task29 & flashing the first ROM after would make that ROM not work & then I had to flash a totally different ROM to make it work. I was using Android & it had died a few times & also I experienced the same thing I did when it would charge up & go back down to 0%. please read below:
I got my new charger today & at 62% of charge I decided to flash to a custom ROM via mem card again well the ROM was a success but when pulling battery out to restart it didnt want to work. So I went to flash again in bootloader by memory card it shut off on me in the middle & restarted into bootloader again & shut off again right away. I did a task29 it worked got it out of bootloader & now the orange led flashes off & on when its off & now ive gotten that to stop. What exactly is wrong with this device?
it was @ 73% and finally setup a ROM NRGY however it ended up shutting off on its self & going into a power boot loop constantly restarting until that ROM can no longer start & now its stuck on the boot screen w/ its info.
I flashed the stock SPL on USB now im going to try to flash the carriers ROM back.
Stock SPL = Successful!
2nd Touch Pro 2 ROM Version Flash = Successful!
Its working for now. Battery is @ 80%
AHH! After charging to 100% idk what it did but when I went into the other room to check out its all possessed.
I have a black screen w/ white text that says:
The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
This operation will delete all your personal data and restore the device to its factory default settings.
IDK how this happened.
When I hit any key it didnt do anything it was stuck until I did a battery pull. Then I restarted the device it was stuck at the boot screen w/ its red info. It erased the entire ROM. Then I tried to do recover mode & it did nothing. I tried to flash the stock ROM again & no results & then again & still no results. I think its now not accepting the ROM at all since from: in the ROM update utility is blank.
Now it decides to get past the boot screen but then it malfunctions again & restarts itself & it tries to setup a 2nd time then after it does & its on sense home for a couple of mins it reboots twice & now its stuck on the boot screen again.
Things that I can think of.
- Isn't your batterie just broken? You will break your batteries when you deplete them completely. Maybe try a new batterie, because you said that you let it die for a few times. It could be that this is causing your problems.
- Did you flash true usb when you were in the bootloader? Give that a try, because I believe that the customruu performs some sort of checks. Maybe this is nonsens, but you can try it.
The battery was fully charged & it was working better than before.
I reflashed the Stock SPL to flash the carriers ROM back & that worked but at anytime it just rebooted for whatever reason to make it so the ROM was unusable at any time I would reboot it would decide to actually go past it seldom. I experienced that at one point oddly it went into setup n it did it again after a while its just acting strange.
If you're back to stock SPL and stock ROM, can't you just send it back for a warranty replacement ?
IDK how old it is. I bought it brand new from ebay.
Viper Matrix Wireless said:
IDK how old it is. I bought it brand new from ebay.
Click to expand...
Click to collapse
No warranty bro...
You can try but no warranty 9/10 times.
What ROM are you using? I used to have that issue with my betas.
It wld destroy itself after softreset and I would have to reflash.
Try to flash, turn off right after it boots, turn on and see how that works for ya.
Rep had told me I could get it replaced & they know I bought from ebay. But I havent called them on this yet.
It doesnt work. It usually doesnt go past the boot screen. Flashing does nothing to help it. Whenever it feels like it it may have to stay on for a few mins to go into setup but most of the time it will stay there & reboot, reboot, reboot, reboot each time its a different # of times & it will reset itself at anytime. Ive even had bootloader shut off on me & restart itself during flashing its a pain. I had another issue I didnt mention my device on any custom ROM when I had 0.85 olinex SPL the device would just freeze & not respond every time. Now this is a different situation. I am back of SPL 0.87 which is the default. I flashed the entire carrier ROM which 0.79 was rewritten w/ 0.87 & that was successful but its still rebooting & causing fatal problems including the black screen w/ white text.
UPDATE: I just walked into the kitchen. Somehow the device turned on by itself & now its sitting on the sense home screen. I know its not fixed but idk why it would turn itself on.
Moved as not ROM Development.
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
I got so frustrated I just got done calling T-Mobile Tech Support & they are going to ship me a replacement.
ultramag69 said:
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
Click to expand...
Click to collapse
I thought I would reply to you.
This is what started my problems is when I did a task 29 my device was acting funny afterwards. I did it again about a month later cuz I flashed way too much & it kept getting worse. But Task29 didnt help this time its what caused me to have to flash 2 different ROMs cuz the first one I flash after doesnt work.
I received the battery & it didnt do anything.
I'm still waiting on the replacement to come.

Desire not bricked but......

Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks
Are you using a custom rom of any kind, rooted etc. giving details like this helps people answer questions.
My advice is if you are useing a custom rom then backup your apps etc. then redownload the rom and flash it as new then recover your apps.

[Q]Rogers Galaxy S3 constantly restarting even in recovery/download mode

So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.

[Q] Phone turns off automatically

I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.

Overheating, freezes, and screen artifacts

Hello,
Ive had this device for now 3 months and never once had a problem. I did however stay on stock for quite awhile just rooted. Recently Ive been testing out different roms and ran through quite a few until I heard about the all mighty CM gem by Sultan. So I figured I would give it a shot. Went ahead and downloaded that along with gapps like any other rom. Booted into TWRP and wiped both the system and cache/dalvik. Then went ahead and attempted to install the rom. Unfortunately midway through it froze and my screen artifacted. I figured I would give it a few seconds and the screen turned black with the notification light turned on. I then tried to reset it with a volume+power combo and nothing happened. After about 5 mins of letting it rest it turned back on.
I went ahead and tried this process again thinking it was just a fluke but nope happened again. So I figured it was a corrupt zip file and I would just go back to the stock image I flashed before which was working perfectly fine. Again froze and gave me artifacts. Hoping to find an answer I downloaded the latest TWRP image and flashed the roms again. Same outcome. I even went out of my way to flash the stock recovery, fully reset all my data through there and then reflash TWRP and sideload Sultan's CM. Which I for once actually got into the ROM however now whenever I get into the ROM my phone overheats instantly and I get the nasty artifacts back along with a reset of the phone. Well kind of the screen goes black and I have to wait until it cools off to turn it back on or else it wont turn on.
Anyone have this issue? Anyone know how to solve this? This is my only phone and I go off to college next monday. Thanks in advanced.
UPDATE: I now cannot get the phone to turn on. No haptic feedback, no LED notification light, no recognition in windows. Literally a paperweight at this point.
The same here, flashed CM and Gapps...
Phone hangs on boot, rebooted the phone and now it won't go on..

Categories

Resources