Hi
I hope that this is the correct place to ask for some help.
I have a problem with my Galaxy S4 i9506 running cm-12 - It keeps rebooting. It normally happens when I can scrolling.
I have looked through the last_kmsg.log as (I think) the Kernel is normally the problem but cannot see any panic. I have attached all my logs in this zip (dmesg.log, event.log, last_kmsg.log, logcat.log, modem.log)
download it here - onedrive.live.com/redir?resid=6E2A6FF7DD2216AD!176&authkey=!ACfMmx7p_Y8zQ2U&ithint=file%2czip
If someone can take a quick look and let me know if they can see what may be causing my problem that will be much appreciated.
Many Thanks in advance
i think that there are 2 possibilities:
Kernel Problem: try to flash through recovery/odin a custom kernel for your device
Data Problem: if you have upgraded to another version of CM, try to make a full wipe from recovery
if the problem persist, contact the rom developer
Related
Hi Guys, I need your help.
I have a S3 I9300, I was modifying its ROMS with different versions from SamMobile and Cyanogen, they worked fine, at the end I let the Jelly Bean version from samsung that I download from SamMobile, It worked fine for a couple of weeks. One day I was working with my S3 using the Wifi connection during morning, then I turn it off as normal, but in the afternoon I had to use the wifi again, a followed the normal process from the task tab and It showed Activating, but suddenly it stops, If I tried to turn it on, same thing happens. It looks the it is trying to identify or recognize the Antenna, but it hangs searching and searching and nothing comes up, same thing happens if I tried to use the host spot.
I though, it could be a physical problem, so I replace the antenna but problem still. the guys from the store said that I have to change the Main board, but I don´t think so, I guess is more Software relate it.
All the rest features works fine, just WIFI does not.
I appreciate your help.
Firstly I'd suggest doing a backup from CWM Recovery (only if you want to) and try to reproduce this issue after full wipe ( /system /preload /data /cache) on trusted stock rom, ARHD for example. If after full wipe it still occurs then it's definitely hardware problem and can't be fixed by "software" ways.
R: Help the WI-FI for my S3 (I9300) stop working
JustArchi said:
Firstly I'd suggest doing a backup from CWM Recovery (only if you want to) and try to reproduce this issue after full wipe ( /system /preload /data /cache) on trusted stock rom, ARHD for example. If after full wipe it still occurs then it's definitely hardware problem and can't be fixed by "software" ways.
Click to expand...
Click to collapse
What he said, cuz some custom roms also come with preinstalled working modem. Also some kernels or worng teaks can cause this (happened to me couple of days ago), you did any of this?
Sent from my GT-I9300 using xda app-developers app
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
monolithcog said:
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
Click to expand...
Click to collapse
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
huytrandinh said:
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
Click to expand...
Click to collapse
Thanks mate for your reply,
I installed cm 11, this did not resolve it.
need the file for the radio/modem, i'm hoping this will fix it but not sure exactly what I am looking for.
**Update***
Just finished installing I9100TDVLSM_I9100TVAULSF_VAU (latest release from Sam Mobile) 4.1.2
Still wi-fi not working.
will try and install cm 10.2 on your recommendation huytrandinh
Okay latest nightly of CM is installed cm-10.2-20131216-NIGHTLY-i9100.
Still has not resolved the wi-fi issue.
anyone have a potential solution?
there is this post for S4, but obviously only viable for S4
http://forum.xda-developers.com/showthread.php?t=2192025
There is also this video tutorial which is for S4
http://www.youtube.com/watch?v=YL8H70Es4wg
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
jedzkiiii said:
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Have been trying that, still no success.
have spent all day trying to find a solution
I tried the modems from here:
##hxxtp://###.veyka.co.uk/sgs2/radios/## (unable to post links ffs)
and few other random links from the forums
MistahBungle said:
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
Click to expand...
Click to collapse
Thanks Mistahbungle,
I checked out that thread http://forum.xda-developers.com/showthread.php?t=2345831
Nothing i could really use.
But I did try a few other kernels:
Siyah-s2-v5.0.1
Unfortunately as soon as flashing with other kernels the screen would go black after the initial boot logo.
Only way to resolve it not booting into the OS was to roll back to:
1. GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9 (flashed with odin)
2. flash CWM-SuperSU-v0.97 with CWMRecovery
3. install cm-10.2-20131216-NIGHTLY-i9100
4. then your general cleaup through cwmrecovery
I'm not sure if I'm doing something wrong when trying to apply another kernel.
anyone able to offer assistance please with right kernel?
cheers
**Update**
Just found a post in that thread - http://forum.xda-developers.com/showthread.php?t=2345831&page=6
Will try the 3 part rom XXLSJ for GT-I9100.
Fingers crossed
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
MistahBungle said:
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
Click to expand...
Click to collapse
Okay just finished testing the rom by installing it via odin (3 part)
still has not yielded any favorable results .
Little disapointed as this was a great backup phone and served for the past 12 months as a mp3 player
Guess as they say; It is all planned obsolescent which is fracked ...
Thanks for the suggestion/help anyway.
I know this is an old thread but my gs2 had this problem and I was able to fix it. Using es file explorer made my way to /data/misc/wifi pulled up the properties to wpa_supplicant.conf and changed group to wifi...then wifi finished initializing...hope this helps somebody
Sent from my SM-T310 using XDA Premium 4 mobile app
for consideration.
I have this phone. the GT-i9100. Had this issue also. I took it apart. The little onboard battery had blown and corrosion got all over all it.
and guess where WiFi hard is. Right Next door. I cleaned it up real good. Put it back together and WiFi came back to life.
So give it some thought guys.
Hi,
I own a Defy+ and I wanted to give it a try with kitkat. With stock ROM I had no stability problems, but when I load kitkat after a few minutes I get a message on screen , saying the modem has a problem and the phone wants to reboot, giving the choice immediatly, remind later or not reboot.
This happens with quarx ROM from 20.1.2014, but also with older versions. I even went back to CM10.1, but it has the same modem problem.
Someone suggested to change CPU and Voltage to fix a reboot problem, but it did not make a difference.
I found some instructions how to create logs when the problem happens, I followed this instructions
http://forum.xda-developers.com/showpost.php?p=49576546&postcount=2104
and cat /proc/kmsg into a file on sd card while the modem message appeared on screen.
The file is attached, I hope it is usefull. If something else is needed to track down the problem, pls let me know.
defybooter
Good evening, good morning and good afternoon! (Depends what time zone you're in but I like to be polite).
I have a slight problem with a my brothers S2 that I need some advice on please:
Preface - I am not new to flashing phones but nor would I say I'm on the level as some of the people here. This is my third root, custom flash and recovery and I've kinda hit a funny bug. (First being a Samsung Galaxy Ace, second being my old Google nexus 5 due to 5.11 crashing it out & this is my third yay )
To my problem and what appears to be a bug or something I'm doing wrong-
There is no problem with the flashing or rooting of the phone when I've put on a nightly build of 12.1, latest version.
It's stable and runs like a dream. But when I reboot the phone, BOOTLOOP! So, like anyone would, I've reflashed the phone and it works fine - till you restart it.
Would I be correct in thinking I might have just got an unstable version OR do I need to install the latest Gapps? (? = not sure on spelling) to break from this boot loop? Effectively, the phone is dead after a reboot, power down or whatever the case is. But it does make me wonder why it works in the first place only to crash out after a reboot.
Now, thinking that it might be an issue with the nightly version, I've reflashed with a stable CM11 and there is no bootloop on restart/reboot. But I really want my brother to have the CM12.1. It's cleaner, faster and looks better IMO.
So, can anyone point me in the right direction?
May I thank in advance anyone who stumbles across this thread and reads and is/is not able to help me.
EDIT REASON: Naughty commers.
Cm 12.1 is known to be buggy. You compound the issue with that old of a device. Best bet would be search around for the threads on how to pull a bootlog from it.