I9505 (euro/international, not connected to any carrier)
I used to run samsung's 4.2, it ran fine. later I ran some hacked google 4.3, it ran fine too.
after that I tried 4.4.1, and after many trials and tribulations managed to get it to work, with functional wifi and phone. Not sure if I get LTE, never saw the appropriate letter on the signal bar, but then again I can't vouch for LTE network where I live anyway.
but... started getting random lockups/reboots. typically once or twice a day, when phone is idle. I only notice those as I get a notification from startup manager than boot took NN seconds. twice witnessed this first-hand. once while fiddling with the phone, another time during a call.
screen, button backlight, notification etc all go blank, phone stops responding to any buttons. stays like that for half a minute or a minute. after that responds to voldown-power-home hold force reset and possibly a little later to power button hole power on. if left unattentded boots up after a while too.
a possible hint to what's going on, camera freezes sometimes, when it does other apps, like flashlight, refuse to start claiming that dive is already used.
upgraded to janjan 4.4.2 v2.2, problem still there.
verified that I'm running recommended XXUEMKE modem.
not sure what other flashable parts are recommended. e.g. non-hlos.
can someone who runs 4.4.x on i9505 possible tell me exact versions of all the partitions?
or download said partitions and tell me e.g. md5 hashes thereof?
thanks
Related
Hello,
ok, I gave up on moving APPs to external SD on ICS 4.0.3...
Here is my new issue in a nutshell....
I updated to ICS 4.0.3 with no problems and everything worked fine for months. Within the last month, the tablet has developed a random problem, usually 30-90 seconds after it boots, where it may or may not freeze up (i.e. the screen is unresponsive) and I have to turn it oss and reboot and hope it doesn't happen again.
Sometimes this happens one or two times in a row and then its fine, sometimes it will happen five times or more, and then the next boot it is fine, sometimes it works fine on the first boot.
I have removed all kinds of apps and media to make sure I have lots of room and curently have about 5G free. but that didn't fix the issue.
I looked into the GPS txt files being left behind and made sure they are removed regularly, but that doesn't help the issue.
I used a Device Info APP to display what is going on when this happens, and while it doesn't show any APP or process I can see as the culprit, the CPU is being maxed at 100%?
It also seems to have "something" to do with the WiFi, as when it "locks up" the WiFi icon in the tray goes away and when I go to settings it seems stuck trying to turn off the WiFi. But at other times then the WiFi is working fine?!
Also, sometimes if I let it go to sleep for too long, when I wake it up this will happen..
SO... anyone got a clue what this could be?!
So I've attempted to debug this best I could but I've come up with absolutely nothing thus far.
About a month ago, I'd say, I started having very infrequent complete lock-ups. I'd pick up the phone and try to turn on the screen and nada. It would still be running as the notification LED would sometimes pulse according to my Lightflow settings. Plugging it into my computer, it appeared as an unrecognized device and adb wouldn't be able to get anything from it. I've never had this happen while I was actively using the phone, mind.
Holding down the power button until it force shuts down and rebooting it works just fine, but it's a bit annoying and worrying to have it go blank every few days. Once, it was even completely working but the touchscreen would not respond regardless of what I tried.
I since did a factory reset, thinking it might've been a kernel issue (I was running on faux's kernel) and it went fine for a week but it just did it again... And this is on stock 4.4.2, rooted, without any new app in a long time (ie. I can't think of an app that I'd have installed when the crashing started).
Any ideas, short of writing it off as the occasional problem and planning on a much earlier replacement than initially expected?
Hi,
I am new to this forum and do not know much of the technical terms. So here is my problem as best as I could say...
I have a unlocked Samsung S4 purchased last Sept (Philippines/SE Asia version, I think). The phone worked fine until the latest upgrade to Kitkat 3 weeks ago.
A week after the upgrade, the phone started rebooting itself. After checking this forum, it looked like a battery problem. On checking, it did have a swollen battery. At the same time, the S4 stopped working as a phone - meaning I could browse, use apps, but could not make calls.
First changed the battery with an original from Samsung, hoping everything would sort out. Unfortunately, it did not. The phone still kept restarting and the network signal showed as not available. So I went to my provider and got a new SIM card and changed it.
Unfortunately, that has also not solved my problem.
Now, my phone keeps rebooting itself. If I connect it to the charger, then the phone starts successfully. At times, it behaves well, but suddenly/randomly, if I touch an app (any app, no pattern) it will reboot again. Once it starts rebooting, it keeps doing that in the screen which has the samsung music comes - it would turn off again and keep restarting until that screen reaches again. Only if I connect to the charger would it start. Again, there is signal at times and there is no signal most of the times. My area has good network signal, so that should not be the problem.
I tried clearing the cache and clear all data/apps, but still no luck. Also, my battery still has / holds charge - so that is not the problem.
Could somebody please help me!!! Please let me know if you need any other details regarding this.
TIA.
Baseband version: I9505XXUFNBE
1. Sig & log in Sammobile.com
2. Download ur firmware: HERE
3. Unzip it
4. Phone in DOWNLOAD MODE
5. Flash the firmware through ODIN like the pic attached
It has nothing to do with your battery...but yes a swollen battery can be dangerous. Follow the steps told by @Joku1981 and don't upgrade to kitkat. Wait for a stable release from samsung.
Hi,
I have already upgraded to kitkat, so cannot downgrade now.. . I had the request to upgrade to kitkat by the phone (Samsung).
As mentioned by Joku1981, I downloaded the Philippines firmware and did as mentioned. However, the phone was still randomly shutting down on opening some apps (esp Gallery, Playstore, Chrome) and failed to reboot.
I also tried to download the pit file and flash it again as mentioned in http://forum.xda-developers.com/showthread.php?t=2265477. Still no lock.
I tried with UK's version of firmware, still same problem.
The phone can be restarted only if connected to the usb cable.
The "No Signal" issue seems to have been solved, but the rebooting randomly seems to be a real pain now.
After my latest flash, while i was in the third screen setting up the phone for language/accessibility --> "wi-fi setup" --> "Accept Samsung t&c's", the phone shut down again...
Is there any counter to identify the number of times the phone is flashed? Would it cause any problem?
Thanks
Also No Service now!
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
akpreets said:
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
Click to expand...
Click to collapse
Though you flashed, do a factory reset one more time to be on the safe side - make sure the phone is 100% charged, and given your case do NOT touch the phone until the reset has completed.
One more thing to try - from experience some batteries are bigger than others and you said your previous one became swollen. This may cause the power pins to become too compressed causing the new battery to lose contact. This manifests on the phone as rebooting at the slightest of movement/flexing, try this:
1. Remove the battery
2. GENTLY pull out slightly the power pins on the phone - don't pull too hard.
3. Put the battery back, put a piece of cardboard or something at the bottom of the battery to make sure there's good contact
Let us know of the results
Nothing seemed to work but only got worse. The phone could not stay on even for a few hours. Finally gave it to the Samsung Service centre yesterday. They sad it might take upto 3 weeks if there was a motherboard change needed.
Fingers crossed...:crying:
Hello All,
I just got a new XPERIA E4 (Model E2104) from CLARO RD, its running on 4.4.4 KitKat , 24.0.A.2.12 Firmware and 3.4.67 Kernel. The thing is i have encountered a lot of problems and would like to know if its possible to update to a newer Firmware version (24.0.A.4.14 at least) in hopes of fixing them. I downloaded FlashTool and XperiFirm, and got the latest firmware from the XperiFirm database for this model (24.0.A.5.14) but im unsure of the flashing process, since ive never done it before. I went through some tutorials and saw that there was a bundling process involved but apparently the E4 is not supported since it doesn't show on the devices list for bundling that the program has, also saw another method that was done directly without the bundling but im unsure of what to check and what not to on the wipe options.
Problems include:
-Phone shutdowns and restarts automatically if left untouched for random intervals, sometimes it does it in short intervals ending in a "no screen lock position" (power button doesn't lock the screen and screen doesn't "sleep"), having to restart the phone by long pressing the power button and selecting Restart option to fix it.
-WIFI stops receiving data and stops working after extended streaming on YouTube (somewhere from 15 to 30 minutes), shutting down and turning back ON the WIFI doesn't work, Restarting the phone fixes this also.
-Doesn't allow 420p quality on streams either nor HD (but i think it doesn't support 720p on the E4 anyways).
-Battery doesn't last as much as its supposed to, screen sometimes uses 70% power on low brightness and nothing open.
I replaced the first phone i got for a new one and still having the same problems, so i figure it must be software related or a faulty line of phones.
Any help would be appreciated!
Thanks
I have an S7 edge (SM-G935F) that currently runs the Superman rom. It has a strange issue where suddenly, out of nowhere, wifi stops responding. It has done this before, but then it was on stock rom. It was actually one of the reasons I reflashed it. After flashing, everything was fine for 2-3 months and then it started acting up again.
It's so bad that I now mostly run it on 4G (luckily I have a 35GB plan) because it can take upto a full minute to get it to respond on wifi after it's been sleeping.
As far as I can tell, the problem manifests itself like this:
* Phone has been unused for a while, wifi is on, wifi is connected to a network (problem is not network specific)
* I try to open any app that uses data, no response. If I just keep hammering retry/refresh/update etc it starts responding after anywhere between 20-60 seconds.
* During the non-responsive period the wifi-icon sometimes gets the little exclamation mark, but not always.
* After a period with wifi off it sometimes uses 20+ seconds to refresh and connect to a known hotspot.
I can probably fix it again by reflashing another rom, but I'm afraid the problems will be back in another few months.
Any suggestions on what I can try (besides returning it, I'll do it if I have to, but I'd rather not). Are there any wifi logs I can check after the problem appears next time. (I know how to use a terminal)
Anything
--
Rom: Superman Rom 2.4.1
Baseband: G935FXXU1DQGC
Kernel: 3.18.48-SuperStock_SM-G935F_V2.4.1
--
Install the stock rom. It was your faulty custom ROM if all get back to normal.
Sure, I can do that. But you did see that the problem existed before I installed the custom rom right?
The original manifestation of the problem was the reason I flashed another rom in the first place.