Related
Its been doing this for a while. I'll go to check it and it's off, but the battery hasn't died. Last night it did this so my alarm didn't go off for work this am. Everything is stock on my phone. N
stock everything so please don't ask what rom/kernal/whatever ..
Any suggestions? I can't be late to work again because this phone is for ****
If you are absolutely sure that your phone is completely stock, then the problem is probably your battery. Does this only happen when the phone is not plugged in?
It does it when its on the charger too. Like I woke up this morning and found it off but it was on the charger when i found it like that. i havent flashed anything or changed any roms or kernals which is why I say its stock. otherwise people ask me what rom im using or whatever.
It could possibly be a lose battery. Generally people will notice it when there is movement to the phone i.e. shaking it or dropping it. If the phone is completely still when it randomly shuts off chance are that a lose battery is not your issue. Still its worth looking into. Most people fix a lose battery with a small piece of cardboard wedged between the battery and case.
Good luck!
Probably not a loose battery. I just had it charging for the past hour and went to check it to find it turned off. Any suggestions as to why it happens when its just sitting there charging?
My phone did the same thing, and with my wife having the same phone I was easily able to rule out battery. Since your complety stock it sounds like a problem with the phone. If your with Tmobile give them a call and see if they will replace it, they did for me.
Sent from my SGH-T959 using XDA App
My phone is already a year old tho. i think my warrenty is gone,
(At least in my case) the warranty didn't matter. I had a 100% bricked vibrant and I told them that "it just happened" and no one was the wiser. I got a replacement and all I had to pay for was shipping. So my advice, tell the T-Mobile rep: my phone is broken through no fault of my own and I want a replacement.
Edit: that stuff happened like a year ago so I don't know if that policy still applies. Hope this helps though.
I did download Load Monitor and made the settings a certain way. so far it hasnt shut off. We will see if I am late to work again tomorrow.
even some stock Samsung roms (like kb5 and ka5) lately have had the same turning off problem for me as well. i think it has to do with some of the older vibrant's when the hardware (battery) becomes charged or is depleting slowly, triggers a software issue like a discharge error forcing an emergency shut-down to prevent damage. the only thing i can recommend it to take the advice of previous posters and get a replacement or upgrade if you are nearing the end of your contract.
just a few things to consider.
Have you tried, I know this sounds odd, a drastic ROM change? Not just switching between Froyo ROMs, but moving to a Gingerbread ROM like MIUI? Could help isolate the problem if it keeps happening under a different OS.
my problem is gone now that i use custom roms. the same could help you thread starter.
Edit. i know you refer to developers as op's but do you do the same to a thread starter?
Pretty sure OP stands for "Original Poster", as in the person who started the thread. Developers start a lot of threads which is probably why you thought it referred only to developers.
Since installing Load Manager my phone hasnt shut off by itself. Seems to have fixed the problem!
**Please note, i have already searched this forum and found some similar threads as: charging paused, voltage too high, SGS2 charged all the time, Charging suspended. Voltage too high and Phone keeps charging after plugin off the charger but none of them had exactly my problems so i'll try to describe mine better here.**
Some background and possible cause first
I have been using Omega ROM @ 2.3.5 (yes it's old, but it doesn't matter) for more than 6 months now and i haven't had any problems with it, but a few weeks ago i decided to upgrade to ICS so i did a full backup with CWM and also backed up sdcard to pc. Did a full wipe, formatted sdcard and installed the AOKP ICS, hated the camera app, wiped everything again, installed normal ICS, it was looking ok but i needed my usual apps the second day so i decided to go back to my 2.3.5, restored backup, restored sdcard. I don't remember exactly if i had the phone plugged in before installing ICS or after going back to 2.3.5 but when i disconnected it, it showed that it was still connected and charging...
Please note that everything was ok before updating to ICS (which is one reason why i believe it's software related), i used the original mains charger / micro usb cables at home and i also used a cheap car charger but long before this started happening, and the last time i used the car charger was 2+ moths ago.
The thing is, i don't care if it things it's charging all the time, my problem is that when charging it keeps the cpu active, and even when setting it to 100 MHz the battery only lasts about 5-10 hours with low-moderate usage (see the screenshots of cpu spy, it is clear that the phone does not enter deep sleep while it "thinks" it's charging).
Symptoms
At first, it kept showing it was charging all the time, sometimes when reaching ~10% it went back to normal (YES, normal aka reporting as no plugged in and no charging (=discharging), so i don't think there's any short-circuit/something wrong with the usb connector (which i tried to clean up, as suggested, but the problem is still there) :
---
---
Then (and currently) after 1-2 mins of disconnecting charger/usb cable it stops the charging animation but *#*#4636#*#* and some battery app stats show that it's still plugged in but discharging (also it reports over-voltage, which is weird because when it is still charging it shows health:Good).
Also, if it goes back to normal (aka not charging and not plugged) and i connect the mains charger then disconnect and connect usb cable it will still see/think that the mains charger is still connected and i can't connect the mass storage to pc (the dialog never shows, because it still thinks it's connected to mains) and vice-versa, but the battery is charged no matter where it thinks it's connected.
Now the weird part, and the reason why i don't think it's hardware (aka usb pin short circuit or anything else stated in the other threads) if i remove the battery for long enough (something around 10-12 hours) over night, in the morning the phone would be completely normal (i was able to do this 2 times so far and both times the phone clock&date were resetted which makes me think the "connected" state is stored somewhere in a temporary memory powered by a small battery which keeps track of the time and alarms?; also if the time isn't resetted, the phone would still think it's connected (yes, even after removing the battery for some 8+ hours)), but the problem reappears if i connect charger/usb cable (something to note here, if i connect the cable and it's not plugged in, the problem doesn't start so this excludes micro usb connector problem).
---
And also, as in some other posts, while the phone is shut down it keeps showing the charging animation along with some warning high temperature? triangle:
Here is a screenshot of Battery monitor widget showing some weird voltage spikes, is it possible to reach 5V?
The wakelocks (from Better battery stats app):
Also, something that i've wondered if all S2s do, when i remove the battery and plug in the charger (of any kind) the phone shows a no battery image:
One other thing that might worth mentioning is that sometimes, just a few seconds after i lock the phone, the screen just lights up for a second then turns back off for a few times (2-5 times), but this might be just an app problem and it's not really currently bothering me.
Also i just noticed when posting the screenshots that the battery is always pretty hot, is 32 - 37*C too hot or is it ok?
Conclusion
Well, it's been 3 weeks since this problem has started because i updated to ICS and i still didn't fix it. My plan is to order an Usb jig from ebay, get everything back to stock and send it to warranty, but this will take some 2-3 weeks until i get the jig and another 2-3 until the guys fix/replace it so i'm posting here hoping for some suggestions from more experienced members or people that also had this problem, because i ran out of ideas to try here.
It's a very nicely thorough post, very detailed. I like it.
However, I believe your conclusion that it isn't a hardware issue with the port is a faulty one. I think 100% of the times I've seen issues like this it's an issue with the port that is resolved either by cleaning it, (which will likely only be a temporary solution) or replacing it. It's VERY likely they will do just that (replace the port) if you send it to service. If you can get it covered under warranty, do it. Otherwise the part will run you probably $15 or so, USD.
But the fact that the problem comes and goes away without physical actions and also the fact that everyone started getting this after upgrading to ICS makes me a bit suspicious...
dany123i said:
But the fact that the problem comes and goes away without physical actions and also the fact that everyone started getting this after upgrading to ICS makes me a bit suspicious...
Click to expand...
Click to collapse
And the fact that anyone who experiences issues like this, when they replace the part, it fixes all these issues?
if it comes and goes, I'd check the port for something when the issue is present. There's likely something lodged in there when it's happening, which gets dislodged when it's NOT happening.
People tend not to protect the port. It can get damaged over time. Also, ICS versions will seem more sensitive to it, because of additional programming and error messages specific to charging and voltage errors added in.
ctomgee said:
And the fact that anyone who experiences issues like this, when they replace the part, it fixes all these issues?
if it comes and goes, I'd check the port for something when the issue is present. There's likely something lodged in there when it's happening, which gets dislodged when it's NOT happening.
People tend not to protect the port. It can get damaged over time. Also, ICS versions will seem more sensitive to it, because of additional programming and error messages specific to charging and voltage errors added in.
Click to expand...
Click to collapse
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Btw, thanks for reading my entire post :highfive:
dany123i said:
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Btw, thanks for reading my entire post :highfive:
Click to expand...
Click to collapse
I just wish everyone who had an issue that needed help was as thorough as you. Most often, posts in Q&A unfortunately look like: "Halp! My fone broked! Whut happen?!?!"
So while some may scoff at the length of your post, they need to understand; when troubleshooting issues, more than enough information is ALWAYS better than not enough.
Don't worry you're not alone.I'm having this issue for about a week and I don't think that it is a hardware issue because my problem appeared when I was doing a restore from backup from custom rom to stock rom and the only thing that I did is that I pulled off the charger while my phone was doing the restore process. The second thing that I think it is not a hardware issue is that my phone is new I bought it two month ago and the USB jig is so clean, I compared to my brothers phone he has sgs2 too and he's USB jig is full of dust and cockroaches and mushrooms and stuff like that but its working perfect. I'm so sorry that I don't have the answer for you but I'm so mad about this problem that I needed to say something and by the way good luck and pm to me if u find the fix
Sent from my GT-I9100 using xda premium
bennycop said:
Don't worry you're not alone.I'm having this issue for about a week and I don't think that it is a hardware issue because my problem appeared when I was doing a restore from backup from custom rom to stock rom and the only thing that I did is that I pulled off the charger while my phone was doing the restore process. The second thing that I think it is not a hardware issue is that my phone is new I bought it two month ago and the USB jig is so clean, I compared to my brothers phone he has sgs2 too and he's USB jig is full of dust and cockroaches and mushrooms and stuff like that but its working perfect. I'm so sorry that I don't have the answer for you but I'm so mad about this problem that I needed to say something and by the way good luck and pm to me if u find the fix
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
toxicdust said:
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
Click to expand...
Click to collapse
I think it's a bit presumptuous to say it's DEFINITELY not a hardware issue. I've seen a TON of posts where people replace the part for the USB port and the problem disappears.
Maybe for someone its is a hardware problem but my problem appeared during restore from buckup.
Sent from my GT-I9100 using xda app-developers app
Same problem
dany123i said:
Or ICS screws something up permanently or maybe you're right, and it really is the port, anyway i'll still experiment a while until my jig arrives, if i discover anything i'll update the thread.
Click to expand...
Click to collapse
Did you discover the source of the problem? I am having the same issue with my sgs2 (only 6 months old). I have all the same symptoms - it tells me the USB is connected and the phone is charging, and I get the same alternating symbols when the phone is off (battery charging/temperature warning). I have done nothing out of the ordinary - no system alterations, all is as it was when I got it, other than apps etc I have downloaded. The port doesn't look that dirty, although having read your posts I am inclined to think that this may be the source of the issue? Any help would be appreciated!
solved
Same issue after upgrade, was searching for days ...
Factory restore, but didn't work.
Forced to stop all services, cleared all cache and cleared Ram and after restart everything back ok. Was not a hw issue.
toxicdust said:
Please take note.
This is not a hardware problem. This is a Firmware/Backup related problem
Had this exact problem on a friends SGS2 and it kept on happening after he did a restore from Titanium. Not that Titanium is broken BUT your backup stored on your SD has a CRC somewhere. What can I say ... It happens.
Just do a complete wipe and install the Rom you want. DO NOT RESTORE YOUR BACKUP !!!
Install everything again as per normal and set it up and you should be good. If this then still occurs then you can be sure its the hardware but this resolved it for him,
Click to expand...
Click to collapse
I agree with this guy over here, just wanted to congratulate you for this post.
And yes...back ups can be a BH.
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.
Good evening. As the title says, my SM-T820 turns off randomly. I've changed the battery and installed several official firmwares with no luck so I don't know what else I could try, if anybody has any idea please tell me.
Thank you so much
Kind regards.
I've had similar problem after trying different firmwares.
My solution was to go back to stock wiping everything there is.unfortunately I cannot really remember my steps, just be careful not to break anything, find a guide for this.
All I remember is doing some painful steps with Odin.
Thank you, I'll keep trying, if it's not broken by now I'm sure I'll not break it...
Regards
Mine also keep restarting by its own .. and freezing and turning off .. then I can turn it on without a hard reset ..
I found that power saver mode makes it longing till it restarts again.
Did you find a solution ?
I also had this problem. Mine was overheating heavily and restarting, then again overheating and so on. My way to fix it was to send it to Samsung Service, and unfortunately they said that they can no longer fix the device since parts are not available. So I asked them if they will exchange motherboard if I supply one, and they agreed but offered no warranty for such replacement. I got motherboard from aliexpress and my tablet started working as it should from the begining. The other issue I had with "old" motherboard was really high battery drain even when tablet was not used. It lasted like 2 days without use, now i'm charging it approx once a week.
Hi, I have a problem with a Honor 10.
Since August it started to restart randomly, I just replaced the battery and I just did two factory reset but the problem continues to manifest even in the configuration screen.
I would exclude the faulty power button, since before rebooting it usually froze on the activity I was performing.
Any ideas?
Thank you!
Test power button with ohm meter.
It was doing this after the reset with just it's factory load? No 3rd party apps loaded?
Try reflashing firmware.
Maybe be a mobo failure.
blackhawk said:
Test power button with ohm meter.
It was doing this after the reset with just it's factory load? No 3rd party apps loaded?
Try reflashing firmware.
Maybe be a mobo failure.
Click to expand...
Click to collapse
I really don't think is the power button because it reboot even in idle on the table, and i saw that if i put it on charge it reboot instantly.
I have this problem even in the configuration screens after the factory reset, indeed i've must configured two or three times because of that.
I'll try to reflash the firmware, then i'll wait for a new battery i ordered a month ago.
If it will be still broken i guess is a mobo failure.
I have a question: i didn't flashed a smartphone before, and i was asking myself if this reboot problem can mess up with flashing, bricking the phone. Can it be possible?
eddyxx said:
I really don't think is the power button because it reboot even in idle on the table, and i saw that if i put it on charge it reboot instantly.
I have this problem even in the configuration screens after the factory reset, indeed i've must configured two or three times because of that.
I'll try to reflash the firmware, then i'll wait for a new battery i ordered a month ago.
If it will be still broken i guess is a mobo failure.
I have a question: i didn't flashed a smartphone before, and i was asking myself if this reboot problem can mess up with flashing, bricking the phone. Can it be possible?
Click to expand...
Click to collapse
Yeah if it interrupts the flash that won't end well...
If you can return it, do so... otherwise...
Before you go flashing nuts try to determine if it's a hardware issue. Check ribbon cable connectors... and that switch.
Firmware shouldn't become corrupted unless there's a flash memory failure or it was a bad flash to begin with.
Does it not do this is safe mode? 3rd party app if so.
If it does it when in the boot menu it's likely hardware.
If so it may be just a failed battery. Try with charger connected to see if this alters the behavior.
If you don't feel comfortable repairing it, let a good tech do it for you. I always remember my first mechanical alarm clock disassembly... it didn't go well
blackhawk said:
If you can return it, do so... otherwise...
Before you go flashing nuts try to determine if it's a hardware issue. Check ribbon cable connectors... and that switch.
Firmware shouldn't become corrupted unless there's a flash memory failure or it was a bad flash to begin with.
Does it not do this is safe mode? 3rd party app if so.
If it does it when in the boot menu it's likely hardware.
If so it may be just a failed battery. Try with charger connected to see if this alters the behavior.
If you don't feel comfortable repairing it, let a good tech do it for you. I always remember my first mechanical alarm clock disassembly... it didn't go well
Click to expand...
Click to collapse
It reboots even in safe mode!
It would seem a hardware problem, possible that I bought a new battery already damaged?
It’s been a few hours since it works good after charging it to 100%, it seems that it starts to reboot towards 50%.
I wanted to flash it also because before doing the factory reset, it automatically installed some "stock" apps by itself, I refer to some games that Honor automatically installs at each factory reset, every time I uninstalled them, after some restart they reinstalled themselves.
It was a weird issue but looks like fixed with the factory reset, so now i only have the reboot issue.
I am so desperate that I would like to try the battery of my Honor 10 (the one with problems is that of my girlfriend), I would not buy another battery since I have to be delivered the one I ordered from a month.
It may be the battery, they can fail at any time.
It's rare for new ones to fail but it happens.
Use a firewall to block auto updates or installs.
Karma Firewall works well but its valuable logging feature doesn't work on Android 10 and higher, but it still will block apps.
Update: I just bought another battery and the problem persist.
Now im sure is not the battery so i will flash it very soon no matter what.
I have been having the same problem as you guys have since last Christmas (2020), when my phone was 18 months old.
I switched phone and gave the Honor 10 to my wife for Coin Master and the problem persisted.
However, two months ago the battery started to swell and surprisingly the problem went away completely for about a month. But as it swelled to the extent of pushing out the screen the problem returned a month ago.
Thinking it was possibly a battery/battery connection related issue, I changed to a new Pisen battery last night. Sadly, the rebooting continued but only for 2-3 times today.
So it is probably an issue with the board itself.
citibatter said:
I have been having the same problem as you guys have since last Christmas (2020), when my phone was 18 months old.
I switched phone and gave the Honor 10 to my wife for Coin Master and the problem persisted.
However, two months ago the battery started to swell and surprisingly the problem went away completely for about a month. But as it swelled to the extent of pushing out the screen the problem returned a month ago.
Thinking it was possibly a battery/battery connection related issue, I changed to a new Pisen battery last night. Sadly, the rebooting continued but only for 2-3 times today.
So it is probably an issue with the board itself.
Click to expand...
Click to collapse
The battery failure may have damaged the mobo or perhaps it was preexisting.
Check ribbon connector pins for damage. Look around for visible solder cracks. Try pressing gently on the mobo with a pencil eraser with device powered on to try to find the area. Check ribbon cables too by gently moving them.
One of the most likely places for a failed solder joint are the BGA chipsets. The many solder pads are under the chipset, inaccessible.
Press gently on them to try and verify this. A hot air station (and skillset to use it) is the only way to repair this type of failure.
Any battery swelling is a failure, replace it asap.
blackhawk said:
The battery failure may have damaged the mobo or perhaps it was preexisting.
Check ribbon connector pins for damage. Look around for visible solder cracks. Try pressing gently on the mobo with a pencil eraser with device powered on to try to find the area. Check ribbon cables too by gently moving them.
One of the most likely places for a failed solder joint are the BGA chipsets. The many solder pads are under the chipset, inaccessible.
Press gently on them to try and verify this. A hot air station (and skillset to use it) is the only way to repair this type of failure.
Any battery swelling is a failure, replace it asap.
Click to expand...
Click to collapse
As I said, battery has been replaced with a brand new one. Therefore the swelling issue is fixed.
Don't have the skill set to use a hot air gun or to solder so this is it for me.
Quite disappointed by the QC of Huawei as this was my first Huawei phone. I have been using Xiaomi since my first smartphone and never had an issue like this before.
citibatter said:
As I said, battery has been replaced with a brand new one. Therefore the swelling issue is fixed.
Don't have the skill set to use a hot air gun or to solder so this is it for me.
Quite disappointed by the QC of Huawei as this was my first Huawei phone. I have been using Xiaomi since my first smartphone and never had an issue like this before.
Click to expand...
Click to collapse
My point was a mobo failure is generally a game over event.
I run strictly Samsung's as I like their UI and have become familiar with them. Of course in 2-3 years that could change if Samsung keeps dropping the ball.
blackhawk said:
My point was a mobo failure is generally a game over event.
I run strictly Samsung's as I like their UI and have become familiar with them. Of course in 2-3 years that could change if Samsung keeps dropping the ball.
Click to expand...
Click to collapse
I understand.
That said, Huawei did replace the MBs for out of warranty customers in mainland China as a good will gesture.
Too bad that policy did not extend outside of China.
citibatter said:
I understand.
That said, Huawei did replace the MBs for out of warranty customers in mainland China as a good will gesture.
Too bad that policy did not extend outside of China.
Click to expand...
Click to collapse
Maybe see if they'll discount a mobo for you.
Not free but it might sweeten the deal.
Or write it off and move on.
All my Samsung's have been long lived with replacement batteries being the only repairs.
Another reason I like them.
In my case it was sort of dumb luck especially when choosing the first Note 10+. In this case they did live up to their hype.
The S4+ lasted over 5 years and still boots up.
I had the random reboots going on for weeks even at night, also bootloops sometimes .
I tried a lot of stuff but i got my phone going again for 2 weeks now without any reboots.
It might be just pure luck but this is what i did last time:
Did a complete reset of the Phone ( everything gone )
I changed simcard to other simslot (i think this made the difference, atleast for my phone)
No apps from Meta (You dont want any of their **** anyway )
ill keep you posted
exoronic said:
I had the random reboots going on for weeks even at night, also bootloops sometimes .
I tried a lot of stuff but i got my phone going again for 2 weeks now without any reboots.
It might be just pure luck but this is what i did last time:
Did a complete reset of the Phone ( everything gone )
I changed simcard to other simslot (i think this made the difference, atleast for my phone)
Put on performance mode (might not be it, but details mather here, today is first day without performance mode, no issues so far)
No apps from Meta (again because details mather, might not be it, i had random reboots all the time, but when i was using instagram or it was still running in the background , it was real bad, You dont want any of their **** anyway )
ill keep you posted
Click to expand...
Click to collapse
Yay!
Meta is malware.
Hey guys, it seems that I solved the problem by bringing the phone to a Huawei service center, they performed an "operation on the motherboard".
Actually they changed the battery with an "original" one for 60€ (the one I had replaced cost 10€ ), then when the problem obviously came back they did the repair on the mobo at no extra cost.
I guess it went well.
eddyxx said:
Hey guys, it seems that I solved the problem by bringing the phone to a Huawei service center, they performed an "operation on the motherboard".
Actually they changed the battery with an "original" one for 60€ (the one I had replaced cost 10€ ), then when the problem obviously came back they did the repair on the mobo at no extra cost.
I guess it went well.
Click to expand...
Click to collapse
Did you had any reboots after the motherboard change?
I got the same issue with my Honor 10. Tried every trick that I could think of, but nothing seems to help.
What I noticed, that sometimes when it restarts it does get very hot in the area near the camera. (not sure exactly what component it's there but it's something on the motherboard)
I'm thinking if it worth doing this motherboard change. (as it seems to be a design/component issue if there are so many that have this problem)
nomob said:
Did you had any reboots after the motherboard change?
I got the same issue with my Honor 10. Tried every trick that I could think of, but nothing seems to help.
What I noticed, that sometimes when it restarts it does get very hot in the area near the camera. (not sure exactly what component it's there but it's something on the motherboard)
I'm thinking if it worth doing this motherboard change. (as it seems to be a design/component issue if there are so many that have this problem)
Click to expand...
Click to collapse
No, no reboot at all, but I noticed later that they rolled back to Android 8.0, so I’m thinking that they didn’t fix the motherboard, but they actually found a workaround by downgrading the OS.
I’m afraid to try to upgrade to Android 10.0 for this reason, I don’t even know if I can do it considering the new Huawei policy of flashing and stuff, but my girlfriend is ok with that so I let it go.
I can confirm that even now, on each task (TikTok scrolling for example), it gets very very hot in that point near the camera, my perfectly still working Honor 10 instead does it only on intensive use of the camera.
I hope this information can help you with your Honor 10, I suggest you go back to an older version of Android if possible just for troubleshooting.
If it persists, the motherboard is probably faulty and you need to replace it, I guess...
eddyxx said:
No, no reboot at all, but I noticed later that they rolled back to Android 8.0, so I’m thinking that they didn’t fix the motherboard, but they actually found a workaround by downgrading the OS.
I’m afraid to try to upgrade to Android 10.0 for this reason, I don’t even know if I can do it considering the new Huawei policy of flashing and stuff, but my girlfriend is ok with that so I let it go.
I can confirm that even now, on each task (TikTok scrolling for example), it gets very very hot in that point near the camera, my perfectly still working Honor 10 instead does it only on intensive use of the camera.
I hope this information can help you with your Honor 10, I suggest you go back to an older version of Android if possible just for troubleshooting.
If it persists, the motherboard is probably faulty and you need to replace it, I guess...
Click to expand...
Click to collapse
Thanks for the reply and downgrade suggestion! (worth a try)