Guys I have some issues with my s advance. They all started when I flashed cm10.2, but I also encountered them in cm11, and now in stock jb (now my phone is not even rooted).
The main issue is the internal storage space (ROM memory) which after a period of time gets full although I don't a lot of apps. The first time when I had the problem it appeared after about a month of using cm10.2, then even sooner in cm11, then after a couple of days in stock jb, and today after a couple of hours (about 4). The only solution I managed to find till now is flashing a new rom or doing a factory reset, but I don't want to do this every couple of days. Today it happened even though I had only one app instaled besides the ones that come with the stock jb. First time I thought that it had to do with cyanogenmod os, then with the fact that my phone was rooted and I had a lot of apps instaled, some of them not from google play, but since I reflashed jb I didn't even root the phone. So if you have any suggestions about this problem please let me know because I don't know what to do.
The second issue has the same story behind it, meaning that it appeared in cm10.2 and I don't know what it causes it and how to solve it. So the phone restarts itself usually when is not used for a period of time. For example in the morning after I wake up, but during may night shifts at work (where I dont't sleep) it nevere restarted. Also during the day if I don't use the phone for a period of time I found the phone restarted. The frequencyof this problem is variable, sometimes a couple of time in a day, sometime one time in a couple of days.
I mention that at home my phone is always connected to the internet via my wireless connection. I don't know if this has something to do with it, but when I searched the web for my problems some users where suggesting that the phone stores some data over the wifi connection. Also some where suggesting to install es file explore and find the folder or folders that occupies the space but es file explorer does not show how the internal storage is occupied by files and folders. There weren't a lot of result when I searched for my issue but there were complains of similar problems with different models of phones, most of all galaxy s2 and some htc.
slider2 said:
Guys I have some issues with my s advance. They all started when I flashed cm10.2, but I also encountered them in cm11, and now in stock jb (now my phone is not even rooted).
The main issue is the internal storage space (ROM memory) which after a period of time gets full although I don't a lot of apps. The first time when I had the problem it appeared after about a month of using cm10.2, then even sooner in cm11, then after a couple of days in stock jb, and today after a couple of hours (about 4). The only solution I managed to find till now is flashing a new rom or doing a factory reset, but I don't want to do this every couple of days. Today it happened even though I had only one app instaled besides the ones that come with the stock jb. First time I thought that it had to do with cyanogenmod os, then with the fact that my phone was rooted and I had a lot of apps instaled, some of them not from google play, but since I reflashed jb I didn't even root the phone. So if you have any suggestions about this problem please let me know because I don't know what to do.
The second issue has the same story behind it, meaning that it appeared in cm10.2 and I don't know what it causes it and how to solve it. So the phone restarts itself usually when is not used for a period of time. For example in the morning after I wake up, but during may night shifts at work (where I dont't sleep) it nevere restarted. Also during the day if I don't use the phone for a period of time I found the phone restarted. The frequencyof this problem is variable, sometimes a couple of time in a day, sometime one time in a couple of days.
I mention that at home my phone is always connected to the internet via my wireless connection. I don't know if this has something to do with it, but when I searched the web for my problems some users where suggesting that the phone stores some data over the wifi connection. Also some where suggesting to install es file explore and find the folder or folders that occupies the space but es file explorer does not show how the internal storage is occupied by files and folders. There weren't a lot of result when I searched for my issue but there were complains of similar problems with different models of phones, most of all galaxy s2 and some htc.
Click to expand...
Click to collapse
You should do factory reset when you change ROM. On CM10.2 there might be still some problems - yes reboots happen some times. So I suggest you to use CM10.1 or CM11.
You can use this to see what uses most of the space on internal memory. With space you get how much space is occupied in folder.
http://forum.xda-developers.com/showthread.php?t=2105707
hmmm
So you are saying that I should flash a new rom for example cm11 than I should do a factory reset from recovery? It may be possible that I had already done this but I will try i again because I got nothing to lose.
slider2 said:
So you are saying that I should flash a new rom for example cm11 than I should do a factory reset from recovery? It may be possible that I had already done this but I will try i again because I got nothing to lose.
Click to expand...
Click to collapse
And to see what do you have on internal memory manualy.
Related
Hello,
for a few days now i have something strange going on with my galaxy s. When i reboot the device, somewhere around the moment you can enter the pincode for the sim, the phone shakes one time first and and then two times as if there is something crashing.
After that all seems to be working fine... That is, until i notice up to two times now, an app went missing, from which i can't remember i removed it. After i reinstall the app, all settings i configured before for that app where there in place...
I am not sure if these two issues have something to do with each other...
I am running the stock Froyo rom 2.2.1 with the speedmod kernel (k12t)...
Is there someone out there who has an idea?
Thanks in advance.
Regards,
Mart
Did you recently change to the froyo 2.2.1 rom, and did problems only occur after changing?
Did you do a full wipe when changing?
Thanks you for the reply...
well no, i am running the 2.2.1 for a few weeks... As far as i am able to point to the moment it started it was just after i removed the battery when the phone was locked (i mistakenly thought it was off). After i placed back the battery and started the phone, i started noticing the possible crashing...
A day or 2 later i noticed an app was lost, the icon was still on the desktop, but it was a green android (like that from the market) and won't start. Because i didn't remember removing the app i looks strange to me. After reinstalling the app all settings i configured before where in place, as if wasn't gone for a while... That's why i notice it, because when i remove an app, i normally make sure everything is removed including settings...
Up until now i have found two of these in a strange way lost apps...
Because there was some time between the removing of the battery with the start of the first issue and noticing these lost apps, i am not really sure they are connected...
It seems that you have any kind of data corruption. If the phone shakes 1 and then 3 times, it is saying that some process has stopped. Also if you lost some app without your intervention... looks like I said. Consider backup your data, wipe and reinstall.
Good luck
Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.
Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny
Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks
Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny
Maybe a factory reset (do it in recovery) would help?
I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.
@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?
2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G
UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.
sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)
tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))
I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App
Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App
Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.
related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.
gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine
More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G
I suspect my issue is a problem of the phone not remembering some settings. I am using the latest CM7 nightly as of this morning (155), but this has been an issue for quite a while.
If I am having only one problem, it manifests itself in a several ways...
1) My facebook contacts won't STAY in sync. Every time i turn my phone on, I have to re-sync my facebook contacts if I want to see them.
2) The first time I send a text from outside the SMS program (sending a text via Vlingo for example) after a reboot, the system asks me which SMS program I want to use. It remembers that choice until the next reboot - when I have to chose again.
3) The first time I tap an internet shortcut, the system asks me which browser I want to use. It remembers that choice until the next reboot - when I have to chose again.
4) I have to re-sign into Twitter the first time I open it after every reboot.
There are other similar issues - none major, but annoying nonetheless.
What am I missing? I've gone through all my settings and can't find one for "Remember all my $hit" . I've run the phone with sync on, and I've run it with sync off - still the same results.
Any help would be appreciated.
I had something similar happen at one point about 6 months ago. I ended up (after much trial & error) just reflashing the whole danged thing....my sd card, recovery, and rom. No issues since.
Not sure what happened, although that was the time I was really flashing lots of different ROMs.
cmason1015 said:
I had something similar happen at one point about 6 months ago. I ended up (after much trial & error) just reflashing the whole danged thing....my sd card, recovery, and rom. No issues since.
Not sure what happened, although that was the time I was really flashing lots of different ROMs.
Click to expand...
Click to collapse
I tried this yesteday morning. As you suggested, I formatted everything including the memory card. Twenty-four plus hours later, everything is working fine.
Thanks for the tip.
I'm hoping someone can help me. I installed CM KANG 7.1.5 on my Milestone a couple of months ago and for the most part, everything was working great (at least better than the stock 2.2 on it). But over the last week or so, I've been having a problem with wifi on my phone. Basically, wifi is not working any more or at least it's inconsistent now.
Previous to this week, I had no issues. I had a number of wifi networks set up, and everytime I went to the wifi hotspot, the phone would automatically switch from using data to wifi.
However now, it appears the phone doesn't detect wifi networks any more. I've tried multiple hotspots and still nothing. I've tried using Wifi Analyzer and doesn't see anything either. I've rebooted the phone multiple times, taken the battery out, reseated the SIM card and still nothing. I use 3G Watchdog and Juice Defender and have removed both and still nothing. The strange thing is it's sporadic. ie. wifi will work one day and then the next day in exactly the same spot, the phone get no wifi at all.
Has anyone else experienced this issue? How did you fix it? I've thought about wiping the phone and starting over again but I'm hoping to avoid that, if possible.
Thanks for your help in advance.
Doing a complete nandroid backup, wiping everything, and installing a new ROM takes me a total of about 15 minutes. If the problem I was having isn't fixed by that, I just restore the backup.
I should also point out that 7.1.5 is outdated and the current version is 7.2.0; quite a bit of work was done on WiFi issues in the past few months, and you're probably missing out on fixes for these exact issues.
It can be a pain to set up a new ROM, but worst case scenario is that it doesn't fix anything and you can just restore the backup and be right back to where you were an hour ago.
Please keep us updated here.
Sorry, I'm somewhat new to this (this Milestone is the first phone I've ever rooted, installed CyanogenMod, etc) so I'm probably going to ask some very noob questions here. My apologies if these are very simple or dumb questions.
I've been hesistant to rebuild/upgrade my phone to fix this problem for a couple of reasons including -
My wifi still comes and goes randomly. I worry that maybe it's a flaky hardware issue more than software so I don't want to spend all this time rebuilding it again to find out it's a loose connection or something like that instead.
I assume all my apps, data, settings, etc will be wiped out if I rebuild or update my CyanogenMod unless I use something like Titanium Backup to back them up? Or is there some better/faster way for doing it or maybe CyanogenMod and Nandroid have some better/faster solution that I don't know about? It took me, it seemed like days, to fully restore all that stuff last time so I want to make sure it's worth doing.
Is there an ETA on a "production" aka non-RC version of 7.20? If it's coming soon, I'd rather wait. I'd hate to upgrade to the RC version and then 2 weeks later have to do it all over again.
Thanks for your help.
About ugrading to 7.2:
- do full nandroid backup first
- clean both caches
- apply 7.2 zip
- clean both caches again
- rebot
I use that method when moving from one version of the ROM to another and no serious issues (one or twice I have to clean caches one more time after first restart). In worst case you have nandroid backup so you can quickly move back.
I have done full wipe (including partial sd and complete ext partitions cleanup) just few times e.g. moving from CM6 to CM7.
Generally I apply full wipe only when moving from one ROM to another, in beetwen versions of the same ROM I just clean caches twice.
Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!
Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!
Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.
Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!