Hey guys,
Within the last two days I experienced the follwoing problem with my S4 mini GT-I9195;
For some reason it crashes so I can't turn on my screen and it becomes hot.
If that happens I have to remove the battery to be able to re-boot again.
The phone is rooted but with stock-rom - I didn't find any thread describing a similar problem.
Unfortunately that always happened while the phone was in my pocket and not in use...
The phone is 1 week old was rooted at the first day and this failure occured starting on Thursday.
Thanks,
Sebastian
Do you have a lot of apps installed? If so, you may have conflicts between some that run in the background (it happens).
If you haven't tried, do a data wipe / factory reset and see if that will resolve it.
You might have a badly manufactured S4 Mini and the last resort would be to flash it a stock rom and kernel to lose traces of rooting and just take it back wherever you got it from. Hopefully it can be replaced with a new one.
Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian
You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?
9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.
fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.
I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?
No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.
For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.
I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.
I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.
The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?
i have already done it, even the SD card, still same problem.
Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!
Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!
I get restarts because the modem crashes... its a known issue apparently
gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back
So the tablet sometimes loses touchscreen function. The physical buttons work fine when it freezes, it's just the screen that gets completely unresponsive.
The physical buttons work fine when it freezes, its just the screen.
I don't remember facing this issue in Lollipop, only in Marshmallow. Reseting didn't help.
This issue is similar to this one: https://forum.xda-developers.com/galaxy-tab-s/help/tab-s-vzw-loses-touchscreen-t3037140
Same problem with my 807R4. Will be in the middle of something and the capacitive buttons and screen stop responding. Tried restoring all available firmwares thru Odin and problem persists. I'm wondering if it's a memory issue? This tablet is a pig with RAM! I would like to flash an AOSP rom to see if it's a memory issue unfortunately my model is snap dragon based and there is only 1 working recovery and 0 custom roms.
Visionikz03 said:
Same problem with my 807R4. Will be in the middle of something and the capacitive buttons and screen stop responding. Tried restoring all available firmwares thru Odin and problem persists. I'm wondering if it's a memory issue? This tablet is a pig with RAM! I would like to flash an AOSP rom to see if it's a memory issue unfortunately my model is snap dragon based and there is only 1 working recovery and 0 custom roms.
Click to expand...
Click to collapse
Haha across this and my starting doing this as well. I was even thinking of looking for a broken SM-T800 model and swapping the motherboard so I can use ASOP.. but idk.. might not be worth it...
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
ashyx said:
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
Click to expand...
Click to collapse
What is the process for this?
Apparently very common. Have the same issue with my wife's SM-T807R4, the US Cellular version. Also seemed to get worse after MM update. Rooted it a couple days ago and started disabling or deleting the Samsung bloatware but so far it hasn't done anything. One thing that did work, though only temporarily, was clearing the cache with Titanium Backup. After doing this (and it took several minutes), I was able to surf the web (with Chrome) for over 30 minutes without it freezing. However, it started freezing again after a while and now is back to freezing every 2 or 3 minutes. It will however play an entire 2 hour movie without locking up so it definitely appears to be related to the touchscreen.
Update:. I think this may be a hardware issue. I booted into TWRP recovery and had the screen freeze. When booting to recovery, there's not much if any of Android loaded. If it was software related, I don't think the screen would freeze in TWRP.
Udate? Samsung nor Verizon offer update!
ashyx said:
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
Click to expand...
Click to collapse
Seems like a lot of people have the same problem no one has solution is what I hear?
same problem
among other problems im having with my Tab, this is annoying me so much. i need to flash the stock 4.4.2 firmware and they delete all versions of firmware for this specific tablet from sammobile, the Verizon model. wtf is there any way i can get a stock kitkat rom for my SM-t807V? where? o if anybody can send me a backup o something.
As we all know there is touch issue when our phone is at charging state, but I was able to get it resolved with help of Lenovo service center
Last month I had installed ViperOs on my phone but due to network issue I rolled back to stock ROM from TWRP backup.
After this my phones screen started blacking out and LED light On only when I was on data.
So I flashed stock Indian ROM which found on zukfans.eu using QFIL, but still the issue didn't resolved. So I took my phone to the service center as it was under warranty and also I was back on stock ROM with boot-loader locked.
After inspecting my phone, they said there is an issue with touch panel and needs to get replaced. After 1 week they replaced my phone screen and since then the touch issue is resolved on my phone.
Whoever is having the same issue, I think you should try this out if your phone is under warranty.
kevinp1992 said:
After inspecting my phone, they said there is an issue with touch panel and needs to get replaced. After 1 week they replaced my phone screen and since then the touch issue is resolved on my phone.
Click to expand...
Click to collapse
Yes, I remember the touch issue with stock Indian 2.5 ZUI. But even since switching to custom rom, I have totally forgot about that. Tried a few ROMs, none of the custom rom is having this issue for me. Presently running AiCP 13.1 Latest along with nameless R17.