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 .
Related
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
anthraxcp said:
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
Click to expand...
Click to collapse
Sounds like you might have flashed the wrong kernel for your phone.
did you first check what was the original kernel on your phone? acutally, run me through your root process so i can figure where you went wrong, because the Resurrection remix rom is just about perfect
I know it was KG2 kernel originally. Don't remember the other numbers.
I'm now on a different kernel because when I used KG2, the phone wouldn't work at all (the buttons were screwy).
The process went something like this:
1. Rooted KG2 kernel installed
>Phone still works like before, but rooted
2. Put Res remix rom on my phone's storage
3. Go into clockwork recovery
4. Flash/Recovery
Format /system
Wipe Cache
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
>Buttons sort of work now but lots of problems
>All of my old files/music are still on the phone despite all that format/recovery stuff. Is that normal?
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Mv101 said:
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Click to expand...
Click to collapse
*lowers head in shame*
Nope. But if I understand correctly gapps is just the google stuff (maps, gmail, etc) but that all works fine for me.
anthraxcp said:
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
......
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
Click to expand...
Click to collapse
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
I have a bell s2 and i did this
Google: how to root galaxy s2 kg2. Use the one that comes up. Will show the right cf root.tar to flash through odin
Follow these steps to the T
http://androidforums.com/galaxy-s2-...ock-root-bell-galaxy-s2-step-step-guide.html
Sent from my GT-I9100 using XDA
ooh you messed up real good! think you need to flash the insecure kg2 kernel through odin again
ZACQ8 said:
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
Click to expand...
Click to collapse
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
anthraxcp said:
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
Click to expand...
Click to collapse
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
ZACQ8 said:
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
Click to expand...
Click to collapse
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
anthraxcp said:
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
Click to expand...
Click to collapse
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
ZACQ8 said:
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
Click to expand...
Click to collapse
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
anthraxcp said:
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
Click to expand...
Click to collapse
Why not start with a working phone + a nandroid backup before you start playing with roms .
Stock rom + CWM and root kernel = Nandroid backup .
If CM does not work then read the CM thread faqs and instructions .
jje
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
ZACQ8 said:
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
Click to expand...
Click to collapse
It does work with 9100M.. I have the same phone and am running v1.4 flawlessly
Sent from my GT-I9100 using XDA
I have a Galaxy S2 I9100 which I had flashed to CF-Root XX_NEE_LPD-v5.5-CWM5. After this I flashed CM9 and have tried CM10 - all have been working fine without problems,
Recently, wanted to try MIUI and tried flashing it. Everything works *except* the lock screen. Simply put, it doesn't lock. Tried setting to other locking methods and nothing works. Bascially, when the screen is off and when you wake it, it just starts (kind of like the No Security setting). I need to mention that before before I flash to CM9, the lock screen also did not work on the stock rom which had been updated by Samsung service center when I sent the phone in for servicing(which is why I rooted and flashed CM9 as the phone was out of warranty anyways).
I came across info that someone had a similar problem and resolved it by using Siyah. Flashed Siyah 4.15 using ODIN and still not working. And the strange thing is Siyah does not seem to be in. I can get into Siyah the first round but if I boot into recovery again I seem to end up in CF-Root (no fancy Siyah eye logo). Did I screw up something here?
I reviewed the MIUI tutorial and it recommended doing things like replacing bootloaders, etc using ODIN (en.miui.com/a-123.html). Having not done this before(except using ODIN to get CF-Root), I'm apprehensive to try it.
I'm running out of ideas to try. Any tips and suggestions here would be useful. Thanks.
tanchankai said:
I have a Galaxy S2 I9100 which I had flashed to CF-Root XX_NEE_LPD-v5.5-CWM5. After this I flashed CM9 and have tried CM10 - all have been working fine without problems,
Recently, wanted to try MIUI and tried flashing it. Everything works *except* the lock screen. Simply put, it doesn't lock. Tried setting to other locking methods and nothing works. Bascially, when the screen is off and when you wake it, it just starts (kind of like the No Security setting). I need to mention that before before I flash to CM9, the lock screen also did not work on the stock rom which had been updated by Samsung service center when I sent the phone in for servicing(which is why I rooted and flashed CM9 as the phone was out of warranty anyways).
I came across info that someone had a similar problem and resolved it by using Siyah. Flashed Siyah 4.15 using ODIN and still not working. And the strange thing is Siyah does not seem to be in. I can get into Siyah the first round but if I boot into recovery again I seem to end up in CF-Root (no fancy Siyah eye logo). Did I screw up something here?
I reviewed the MIUI tutorial and it recommended doing things like replacing bootloaders, etc using ODIN (en.miui.com/a-123.html). Having not done this before(except using ODIN to get CF-Root), I'm apprehensive to try it.
I'm running out of ideas to try. Any tips and suggestions here would be useful. Thanks.
Click to expand...
Click to collapse
Check the link below, hope it will be of some help to u
http://forum.xda-developers.com/showpost.php?p=23641669&postcount=8
Sun90 said:
Check the link below, hope it will be of some help to u
http://forum.xda-developers.com/showpost.php?p=23641669&postcount=8
Click to expand...
Click to collapse
Thanks for the link. Tried the solution but no joy - screen not locking like it should.
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
I have a Galaxy S2 i9100. I was wondering if it's a known bug that sometimes the screen never turns off unless I press the power button? No matter what I set Display -> Sleep to, the screen often never turns itself off. I can't see any pattern to it for when it works and when it doesn't. Is there any known apps that can mess with it, like NoLED?
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
marjune23 said:
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
Click to expand...
Click to collapse
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
djondjoe said:
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
Click to expand...
Click to collapse
Oh forgive me, I was thinking of v5.6 hahaha...
Please disregard the Smart Stay, that is not present on NeatRom AOSP v2,4.1...
Just do my first advice, wipe cache and dalvik from recovery mode...Then Reboot...
1. Reboot to recovery...
2. Wipe cache partition...
3. Advance>Wipe Dalvik...
4. Reboot your phone...
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
djondjoe said:
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
Click to expand...
Click to collapse
Oh thats bad...would you consider reinstalling the Rom without full wipe or full wipe again?...
I guess it will solve now the issue....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
For now I'll try to live with it. I can confirm that a reboot fixes the problem for some time.
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
djondjoe said:
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
Click to expand...
Click to collapse
Sorry to here that mate...
It looks like you need to do a full wipe now...
Optional, do a nandroid back up...
1. Flash compatible KK cwm...
2. Wipe data...
3. Wipe cache...
4. Wipe advanced>dalvik...
5. Format cache, system, data and preload from mount and storage...
6. Flash Rom and Gapps.
7. Reboot and enjoy...
8. Report back please...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
djondjoe said:
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
Click to expand...
Click to collapse
Before we start the lesson, let me ask you first if your issue has been resolve already?...
Don't worry I won't give up on you until I satisfied you baby hahaha...
Q. I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
A. How did you manage do flash Rom without flashing compatible KK CWM Recovery?...Unless you came from another KK Rom, it is possible...
It is necessary coz simply it is the basic requirement of KK Roms (with maliV3 drivers)
Q. Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version?
A. Yes, as you can see in Post #3 in NeatRom AOSP thread (last paragraph)...although it is already integrated with Philz kernel...
Q. I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
A. CWM are just type of recovery. Other than CWM there is what you called TWRP (touch wiz recovery program, which is used by NeatRom AOSP)). TWRP is more on just tapping on your screen to navigate your recovery.
So you need to find compatible CWM or TWRP to be able to flashback to 4.1.2. And same with Kitkat, you need to find compatible CWM or TWRP.
But there are some kernels who is now working to be able to handle to flash a KK or Jellybean. (e.g. is Dorimanx Kernel)
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
djondjoe said:
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
Click to expand...
Click to collapse
Wwaahhh read carefully mate my comment above...if you want to go back to neat 5.6, Post #3 last paragraph....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
djondjoe said:
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
Click to expand...
Click to collapse
Nice nice...safety first ...
Hhmmnnn AFAIK there were different versions of recovery...As of now it's so hard to follow....So for me I just follow instructions (ofcorz reading comments) before proceeding....but sometimes I like being risky always hahaha...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
djondjoe said:
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
Click to expand...
Click to collapse
If you want to retain your apps do dirty flash...but if something went wrong or you want fresh installation do the full wipe...see post below...
http://forum.xda-developers.com/showthread.php?p=49887400
Ooopppsss just a tips also, please hit thanks button if somebody help you on their comments to your post
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
djondjoe said:
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
Click to expand...
Click to collapse
As you can see on my post 1% fail and 99% success...
The only main problems sometimes why bootloops occurs is users don't follow the steps provided to them...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...