Related
Hey, My wi-fi/hotspot shows up as error when i go to settongs and wireless networks. i had the problem with alien#4 so i decided to switch to cynanogen 7.1 and still nothing :/ is it a hardware problem or i need to flash a different baseband/kernel or what? thanks for the help in advance if anyone reples. it would mean alot haha
I had that issue when I installed one of faux123 kernels.I re-flashed the kernel wipped cache and dalvik and rebooted.I didn'tn have the issue afterwards,hope this helps out.
thanks. I tried flashing a 1.30 ghz kernel by faux123 and i have a bootloop :/
try flashing a different kernel.I notice the 1.3 works better than 1.45 for me no bootloops.try going into cwm and clear cache dalvik and fix permissions.
ok,im using tenfars recovery. should i be using clockwork mod?
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Atrixn00b said:
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Click to expand...
Click to collapse
Tenfa'rs recovery is outdated. Use romracer's instead (he just updated today).
*Edit* I ran into this same problem early on when I started flashing customs mods. Ended up having to go back to my "stock" backup before wi-fi started working again. After that, I haven't had it re-occur. That might be your best bet to get it functioning again. If not, it may be a hardware issue.
haha I just got this thing 3 months ago...hopefully it's not a hardware issue. but i'll try that
MY phone is completely effed right now..like the "soft keys" on the bottom don't work and the screen sensitivity is really low..it's like my phone is destroying itself or something.
Sounds like a hardware issue. I had the same exact issue.
Wifi error, some random reboots especially after trying to turn it on.
after much testing, reading, and playing around i started getting constant reboots. You could get too the lock screen, then it would reboot.
Before jumping to conclusions about hardware go back to your stock backup.Also use RomRacers newest recovery.then start flashing kernels again and see if the problem persists.Its easy to blame everything on hardware issues but often that's not the problem.
I’ve flash about 20 different ROMS since I got my SGS2
I’m running checkromHD 4.0 every two days or so my phone seem to turn off or go into a sleep mode and cant be woken up, my friend running the same ROM (which I installed for him) and has got no problems
Ive tried wipe / format data cache and factory reset, tried flashing a stock ROM, then Checkrom 4.0 still the same problem
Can too much rom flashing affect the phone?
Any help would be appreciated
No
Problems are usually user error or rom error .
jje
I agree, I flashed mi phone like 32 times and still rocking
long ago i rested counter and at the moment i have like 50 flashes and i think im gonna flash again tonight...when sth is wrong its either the rom or the users fault...nothing against u but mostly its the users fault
raidenuk said:
I’ve flash about 20 different ROMS since I got my SGS2
I’m running checkromHD 4.0 every two days or so my phone seem to turn off or go into a sleep mode and cant be woken up, my friend running the same ROM (which I installed for him) and has got no problems
Ive tried wipe / format data cache and factory reset, tried flashing a stock ROM, then Checkrom 4.0 still the same problem
Can too much rom flashing affect the phone?
Any help would be appreciated
Click to expand...
Click to collapse
this sounds like too much undervolting, or playing with set cpu settings, very common issue, had it like millions times, either flash a different kernel, or increase voltages of the sleep/wake frequency ([email protected])
with some kernels my voltage for 200mhz was at 825 and was running fine at some kernels i was having no wake issues, so had to put it up to 850-875 or change governor hope this helps
Flash durability
Flash memory durability depends of type. You can expect to be able to flash your phone at least 10,000 times. You will find that the connector which is also rated for 10,000 connections, would wear out first.
Regards,
John.
Hi, i've been experimenting this problem for 2 months. I've got CyanogenMod 9, but before I flashed Cyanogen Resurrection 4.0.3 and I formated everything as possible (Wipe Data, Cache, Dalvik and format /system). The battery doesn't lose charge when I restart it.
Thanks!
So, what is your question..?
Sent from the Matrix
If any of you have the same problem and know the solution. I've read other messages like mine, but I'm not in the same circumstances. I haven't got any apps except social (whatsapp, twitter...) none of my apps it's draining the battery I simply don't know why my phone shuts down by itself
You're running stock kernel right? Have you changed anything at the Performance-menu at Settings? And when do this reboots occur?
Have you tried flashing for example CM10.1 to see if the same problems come up? You could make a Nandroid backup to try this.
Sent from the Matrix
Thanks for the answers. I have the stock cm9 kernel. I don't touch anything at the performance settings. Actually, this problem comes from a couple of roms more. AOKP, ParanoidAndroid, and another one 4.2.1 which I don't remember the name. I've tried a stock ROM before but the performance was not good at all, freezes and slow work at general. Thanks.
Make a full wipe (4) and go as stock as you can. Try it for a day or two and then go back to custom.
You wanna see if it keeps going off on its own, don't worry about performance just yet.
If it does it on all roms you've tried its obviously a hardware issue.
Try a different battery, if that doesnt help then send it for repair.
SGS2 power off issue
Hiya,
I have been running and updating Resurrection Remix and Siyah/Dorimanx kernels for awhile now and this worked fine up until last week. After an update to Dorimanx 7.50 my phone started dropping its network connectivity and powering off randomly, i then updated the Kernel to a new verison hoping the issue had been address (8.3 to be specific) after which my phone wouldnt even go through the boot sequence properly.
After a bit of fiddling i have managed to install an Official JB ROM, (details in the image attached) and network connectivity now seems to be ok, but the phone still powers off...ALOT. Anyone else experience similar issues and find a solution?
Note: I have ordered a new battery in case that is the issue as suggested above, but just checking incase theres something im missing while I wait. Also, the phone is about 16 months old.
Sv: [Q] SGS2 turns itself off
Check your fuel gauge chip. Reset it with siyah or dorimanx kernel.
Skickat från min GT-I9100 via Tapatalk 2
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 .
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button