Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.
Related
So i see there are a few other threads but none that i found were quite like this. My phone randomly restarts and goes to the white screen that says stick together and won't load back up, also when i reset or take the battery out unless i have held the phone infront of my AC in my car or put it in the fridge/freezer it will not boot back up, it has heat issues but it's not actually that hot, i used to play playstation games and it would get much hotter and not freeze like this, it randomly started happening a couple of months after I got it.
it will freeze often in any temperature that is not considered cold, even in room temperature it will do it, any time i try to load my playstation emulator or use the internet it has a very high chance or resetting and not booting,
if the phone gets warm at all though it's a garuntee that it is going to happen, it just depends on when, i could just be finishing a call, sending a text etc, it will happen, and the only cure is putting it in the fridge.
i'm going to guess I have a virus of some sort or something really messed up in the ROM, but i've switched ROM's and it still does it,
should i do the SD card hspl back to SPL and try to find a legit original rom copy or is there a better solution for this? i.e deleting all my addons and going with a different ROM?
my rom history is TOUCH XTREME, Miri and Dinik(this is where it started) and now Energy(it is still happening here)
might be a good idea to go back to stock, though you dont need to remove hspl at this stage, just flash your phones original rom over usb, and have a real close look at the battery pins, they can often get bent leading to all kinds of reboot issues.
If its still the same under stock rom, then maybe remove hspl (no need for sd card flashing, can remove it using hspl2/hspl3(for tmous))
one of my pins was actually bent a while back! i bent it back to the shape it's supposed to be and used a safety pin to widen it back up so it looks like the rest, do you think that caused permanent damage? and if so is there something i can do to the pins to make it work right again? and not reset so easily
Well, i reflashed the stock SPL and ROM and yeah it won't even turn back on, just stays on the white stick together screen. it's done, being replaced by tmobile next week.
hmm, could be, perhaps if the pin is cracked a little, affecting power flow. not sure what to suggest.
I got the exact same problem as lllpulselll. I have already done a lot of things but none of them worked for me.
I did an hard reset
Tryed a lot of different rom's
Used the telephone al while without SD-card but still the same problem.
But I read somewhere that ik could also been your Sim-card, is that logic or not?
And by me also one of the pins by the battery is not right so I will that try to.
(Sorry for that bad English)
looks similar to overheating, you could install BattClock (it can monitor batery temperature) to check whether the self-reset happens at the same conditions,
had the same issue, finished with new mainboard (replaced under warranty),
during worst moments before repair I had to put my Leo in the fridge for few minutes before it could restart
p107r0 said:
looks similar to overheating, you could install BattClock (it can monitor batery temperature) to check whether the self-reset happens at the same conditions,
had the same issue, finished with new mainboard (replaced under warranty),
during worst moments before repair I had to put my Leo in the fridge for few minutes before it could restart
Click to expand...
Click to collapse
That's probably it then, probably bent the metal things connecting to the battery and messed up the flow causing the battery to overheat or think it's overheating somehow. sucks that that is all that's wrong with it and it has to be replaced, wish the prongs could be repaired.
lllpulselll said:
probably bent the metal things connecting to the battery
Click to expand...
Click to collapse
not necesserilly so don't blame yourself - mine had faulty mainboard (not battery) probably from the very beginning, but as it was purchased in winter, the symptoms did not show up until late spring, when outside temps grew
Hi there; Could do with some help please I seem to have a series issue with my Samsung Galaxy S2 today. It started this morning; I noticed the screen was randomly turning on; for no reason what so ever. It only does it when the phone isn't charging, if the data cable or the charger is plugged in; it doesn't do it.
Its on version KE7. I have tried a factory reset, and that hasn't sorted the issue. Therefore I seemed to think it was a hardware fault, however with it not being an issue when plugged in I wondered why it might be doing it.
Tap to speak also kept coming up for no apparent reason, I say kept coming up, doesn't happen all the time, but did come up about 6 times today, when I hadn't pressed anything, which would suggest the bottom centre button could be stuck or sticky, however that seems fine; and its not been near any moisture and has been a hot day.
The phone has not ever been rooted; so no issues there.
The phone battery dies very quickly within about 4 hours with the screen turning on all the time; and the phone will randomly freeze up completely, and I have to remove the battery to reset the phone.
Anybody got any ideas? Really could do with some help
Thanks
Rich
Update: It is plugged in charging now; and the MTP Application has come up; like the data cable is plugged in. That seems very odd to me...
Don't be afraid to send it back. These things aren't cheap even if you're paying through your contact, you're entitled to get what you paid for.
Your specific issues may be down to more than one thing. My screen lights up when I've read my gmail on a different device and it needs to clear the notification. Nothing too worrying about that. The other stuff does sound like some sort of shorting though and people have been given replacements for less serious issues.
I'm tempted to get mine swapped because the wifi often won't pick up an IP address and the gps won't get a fix if the phone gets too hot. Relatively minor compared to your issues.
Sent from my GT-I9100 using XDA App
Yeah I think its going to have to, I've tried playing about with settings, giving it time to cool down; pretty much everything I can think of, I really can't think what it could be, it seems to be many issues rather than just one, with it only being a month old, I expected slightly more.
Love the phone, did brilliantly yesterday; used it for lots of things; then today it just suddenly went, took it of charge, and it played up the whole way through.
Given up with it now, will take it back and see if I can get it fixed, I have 24 month warrenty with my contract.
Thanks
Put your original firmware back on if you can before attempting a warranty claim .
jje
Hello everyone. Before I sell my Atrix on eBay as a broken phone for parts, I thought I would make see if anyone can think of anything I might have missed. I have an unlocked Atrix, using CM7, flashed to CM9, then back down to CM7 until the bugs get worked out. My wife dropped my phone, which caused some problems that have now bricked it.
Specifically...
When she first dropped the phone, I picked it up, turned it on, and immediately noticed that the headphone icon was on, even though no headphones were inserted into the jack. This effectively killed any sound on the device. I rebooted a few times, and occasionally the icon would go off and bring back sound. Then, it would go back.
I noticed that if I sort of twisted the Atrix (held it in my left hand, gripped the top of the phone with my thumb at the top right and my forefinger on the top left and squeezed), I could make the icon go off. It might come back on, but I could squeeze it and make it go away.
A few days of this went by, when I noticed that the headphone icon was staying off. However, when I went to actually insert headphones, they wouldn't register. However, it was at this time that I realized that the volume rocker was dead and unresponsive.
In retrospect, this is probably where I should have realized that I should leave well enough alone and limp along with my crippled, but 80% functioning Atrix until my next upgrade. However, I soon found out about the CM9 betas coming out, and quickly downloaded ROMs to flash. Flashing turned out to be tricky, as the only way I could get into recovery was by shutting down the phone with the command to go into recovery. Holding VOLUME + and power do nothing because the rocker is broken. Similarly, I cannot get into fastboot (presumably because of the broken rocker).
The first thing I noticed with the ICS build that I flashed was that the camera wasn't working. I first assumed that this was a software glitch, except that the camera seemed to be working since the first of February. I then flashed down to CM7. However, the camera still didn't work. It then dawned on me that I had not tried to use the camera since the drop. I then guessed that I just now noticed that my crippled phone is down to about 50% functionality.
So, last night I decide to flash up to a new CM9 beta. Not sure why. Guess it was boredom. The flash, however, didn't take, as my phone now is stuck on the boot screen. Ordinarily, I'd boot into recovery, wipe, and re-flash. Except with the broken rocker, I can't get into recovery without first booting into Android and then re-booting into recovery. So...it is effectively a brick now.
I decided to take it apart using iFixit's guide, but I didn't see any obvious damage. However, I'm guessing that there is some crack on the motherboard from the drop that is not discernible to my untrained eye. The fact that the camera and sound use the same ribbon cable is what is leading me to this conclusion.
So, now that you have the full story, what's the verdict? I'm guessing I need to sell it on eBay as a broken phone for parts. Someone can make good use of the housing, digitizer, and glass. I was thinking of starting at $75, but taking the first offer in the $50 range. Is it time to sell it for parts, or am I missing something?
I don't know how to fix it (I'm sure there's a way!), but if somebody doesn't find the answer soon, PM me about it. I would totally buy the battery if you're willing to part with that.
I ordered a camera/volume rocker module and am waiting for it to arrive. Not sure if this will fix it or now, as I don't know if the motherboard is intact. I figured that it was worth $15 for the part.
I'm actually using an extended battery I bought from Amazon. I'm always looking to make money, but I think for karma's sake, I should advise you to look there for some stock and generic batteries. I found a really good deal on an extended battery that came with a battery door. So, my stock battery and door have been sitting in a desk drawer for weeks.
FIXED
OK, not that anyone seems to care, but in case anyone is Googling with similar problems, I'll go ahead and post a reply. For $15, I was able to buy a camera module. The camera is attached to the volume rocker, so I took the Atrix apart, put the new unit it, and VOILA!!!
The phone seemed to hang on the red Moto logo...but with a working volume rocker, I was able to get into FASTBOOT, wipe the recovery, flash a new recovery, then boot into new recovery, wipe, and flash!!! Back in business!
I'm going to start a new thread as I think this is a new problem, but now the phone has a SOD when I talk on the phone. Battery pull and reboot works, but so doe simply plugging it in to a power source...I have to believe this is a software issue...
hey guys my vibrant turns on goes up to the galaxy s logo (sometimes lock screen) and then shuts off no warning, i tried another battery as well, though i do notice when a lighty tap it against something it shuts off no matter what. what should i do?
P.S. i tried contacting samsung but they said it would be $70-$150, im geting a s3 soon so i dont feel like sending to them.
You can donate to me when you get your s3!!!
sent from the depths of helly bean
Perhaps the battery contacts is getting worn? There are also soldering points for the battery contacts on the device's motherboard, you can check to see if they're loose, but you'll have to open up the device, though this isn't likely since it should be in a sturdy position. Have you done a factory reset?
I don't know if your on stock or not, but if your running a custom ROM, and you are overclocking, perhaps try turning that off.
Or as mentioned try wedging something to make the battery tighter against the leads.
i have taken it apart and seen nothing wrong with the leads i might try reflowing the mobo and seeing if that works.
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.