Related
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
I used the Kingo Root method to root my Note 3 that was running 4.3. When I decided that I was ready to go ahead with the AT&T 4.4.2 FOTA; I used it to un-root so my phone would accept the update. Both processes indicated that they were successful. However; my Note 3 will not accept the update under any circumstances. It downloads the FOTA - which takes close to an hour - and gets to the 25% install point after rebooting and fails with "Invalid Signature" appearing for a few seconds after the "Installation Failed!". It then unceremoniously does a factory restore and I'm left with, yet, another setup procedure and reinstallation of all of my apps, passwords, etc.
This has happened twice with two different phones - the other being my Samsung S4. Exactly the same sequence. I took the S4 to Best Buy, after AT&T forced an update to it, and it, too, failed. Samsung did a direct flash to the S4 and it indicated that it took the 4.4.2 successfully. However, when the phone rebooted, it was still 4.3. Samsung scratched their head and couldn't figure it out. I see no sense in try to do the same with the Note 3 since it will likely be the same experience.
Neither phone show the KNOX trigger having been tripped, and both show "Official" as though nothing had ever been done. I never did any modifications to either phone, other than the root / un-root to stall the FOTA, until I was sure that I was comfortable with the update.
I sent an email to the same effect as this post to Kingo, with no response.
Has anyone had the same experience?
I know that for a while, there was a great deal of concern over the Kingo Root method, but thought that it had been resolved and that any myths had been debunked.
Did I shoot myself in the foot?
Hey friend, this has been asked A LOT in this forum. All you had to do what look through the first page and you'd see this topic.
However you're scared and our phone are probably our more personal and needed device so I understand your impatience and panic.
How to fix: http://forum.xda-developers.com/showthread.php?t=2701062
Be well, relax, everything is going to be ok. You're not alone . We're with you my new friend.
Sent from my SM-P600 using Tapatalk
Sorry for posting in the wrong thread. I searched over the weekend, but didn't see what looked like an answer.
Thank you so much for posting the direct link! And, thanks for not mountain climbing me about the gaffe.
I'm still fairly new to this, so I genuinely beg everyone's pardon for the mis-post. I'm still trying to learn how to navigate through the different sub-forums. I'll try to be more courteous in the future.
Now, I'm in a REAL pickle! AT&T is trying to cram KK down my throat on my Note 3 and I have about 4 hours (according to their website) to respond before they force it. On the AT&T variant; there is no way that I know of to block the update; except temporarily. Then; it's back to the wash, rinse, repeat cycle of having to restore my phone and apps - EVERY time the update fails!
I still haven't done the downgrade; because after rooting and installing a custom 4.4.2 ROM on my kid's phone least night; I decided that I want to re-root my Note 3 and install KNOXRAID as a custom on my Note 3.
My dilemma is; if AT&T crams the update down my throat - as they did with my S4; it's going to fail again, and I'm going to have to start from scratch again, and again until I find a solution.
I tried re-rooting my Note 3 with Kingo, but it fails every time, now.
So; what should I do? My hunch is that I'm going to have to do the 4.3 fix and restore it back to factory, but then it would allow AT&T to actually force THEIR KK into the N3, and I'd be screwed, until a root method is obtained for KK.
PLEASE! Any suggestions? I suppose, for the short term; I could cut off my N3; install my SIM into my S4 and use it until I'm able to resolve the issue with the N3. I need Total Recall to work on my N3, and KK will definitely kill it.
*UPDATE* I turned the N3 off, removed the battery and SIM and installed the SIM in the S4, and am using it for the short term. Unfortunately; my S4 already has the AT&T KK update installed, and I need to resolve the issue with the N3 as quickly as I can. My hunch is; to avoid them doing it again; I'm going to have to turn off Wi-Fi and place the N3 in "Airplane" mode and leave the SIM card out of it until I'm comfortable - and have a clear method of installing KNOXRAID.
Still hoping for a solution. At this pint; I'm not that concerned about tripping the KNOX sensor on the N3, but would prefer to be able to flash back if I needed to enforce my warranty.
Thanks!
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
contrinsan said:
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
Click to expand...
Click to collapse
This seems to be a common error with the S5 mini. There is a whole thread in the German Android forum about this issue. Also the German Amazon product page for the S5 mini has about 40 users complaining about this problem.
Some users report that the reboots start after some weeks of usage. First it just reboots once per week, then it gets more frequent until it reboots once per day.
Factory resets or firmware updates do not help. Some users sent their phone in for repair but not with huge success.
But not every device is affected by this. So far I did not notice that behavior with my phone (G800F).
I guess it is a hardware issue as not every device is affected and the error gets worse after some time.
The only way to diagnose what's wrong with the device is to check the adb and kernel log (at least the last kernel log before reboot might be available at /proc/last_kmsg). But this would require rooting the device which in turn would void the warranty. It would also be interesting if those reboots also occur with CM 12 (installing this will also void your warranty).
So it seems that sending the device in (without a great chance of repair) is the only option that Samsung gives you without loosing warranty.
Alternatively you also might want to wait for the official Lollipop release and hope that this will fix the problem.
If someone with this problem already rooted his device it would be interesting to get the log files (adb + kernel) of the times of the crashes.
Thanks for your reply, so it might be a hardware problem after all
Hello,
I have a Samsung Galaxy Note 3, N900A, Android Version 5.0 on AT&T, Baseband N900AUEOC1, Kernal 3.4.0-4335446, rooted.
If I turn the phone off and then back on again or reboot I get a long white scree with the AT&T logo, Android is upgrading... Optimizing app # of 316, then a long time I can use the phone.
I did some online searching, and found some really old posts. I don't mess with the configuration much. I rooted it many months (years?) ago, and can't recall why. I think i wanted a hotspot, but that never worked out for me.
I suspect that AT&T is sending an over the air update and does not like the rooted phone. I searched thee settings in an effort to turn off auto update with no luck. I am hoping for something other than: wipe, reload...
Service Disabler from the Play Store ended up working.
Easy to use and dumped some bloatware while I was in there.
meyen90 said:
Hello,
I have a Samsung Galaxy Note 3, N900A, Android Version 5.0 on AT&T, Baseband N900AUEOC1, Kernal 3.4.0-4335446, rooted.
If I turn the phone off and then back on again or reboot I get a long white scree with the AT&T logo, Android is upgrading... Optimizing app # of 316, then a long time I can use the phone.
I did some online searching, and found some really old posts. I don't mess with the configuration much. I rooted it many months (years?) ago, and can't recall why. I think i wanted a hotspot, but that never worked out for me.
I suspect that AT&T is sending an over the air update and does not like the rooted phone. I searched thee settings in an effort to turn off auto update with no luck. I am hoping for something other than: wipe, reload...
Click to expand...
Click to collapse
Un-Fxed
Well this is a little frustrating. Went on and off with no update process yesterday. Today I rebooted and the 316 updates were optimized. I looked at the service disable app and the AT&T update service was still disabled.
Anyone have any thoughts?
Clearing the cache seemed to help. Let's see if the updates come back over the next few days...
No updates yesterday. Today there are 322 apps to optimizing... Anyone seen and fixed this before?
I started having the same problem 2 weeks ago after updating SU . Looks like they sent out 2 bad updates. Here is a link to the issue. I have been unable to solve it and their recommendations is to reroot the phone.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Thank you pinkpanther28. A true smoking gun. I disabled SuperSU and the update issues was gone. Enabled SuperSU and sure enough it came right back. The real irony is that I upgraded to SuperSU Pro to make sure 'Disable Service" had access. For now I will leave SuperSU disabled....
Well so much for the smoking gun. I turned my phone on this morning and the updates issue is back, even with both SuperSU and SuperSU Pro disabled. Does anyone have any ideas?
Soo...
When I got the phone, I was able to remove the bloatware; cant quite remember what I used or downloaded to the phone. It was a while back and lost all my files on the laptop.
However,
I updated my Samsung Galaxy S8 and it seems like it was fine for a day or so, all of the sudden it started boot-looping..
Just restarting and showing the Samsung Galaxy S8 screen, over; and over..
I am looking to reset it, and hopefully remove all of the T-Mobile bloatware again. I have tried a couple of these methods however each one seems to fail at some point. So I have no clue what state my phone is in, or what needs to be done.
Below is the information to my phone, any chance I could get some assistance to something that will get me back to at least using the phone. Or even better, using my phone without the bloatware; just simple Google apps.
Any help would be GREATLY appreciated. Thanks again ahead of time!
SAMSUNG GALAXY S8
SM-G950UZKATMB
(Last time it worked, I had updated it to OREO)