Related
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
rcfcyl said:
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
Click to expand...
Click to collapse
What about the cm-7-20120722-NIGHTLY?
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
gsstudios said:
What about the cm-7-20120722-NIGHTLY?
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
Click to expand...
Click to collapse
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Hi @gsstudios,
Ah I see, I did wonder why there was 2x seperate branches for the same device... I could understand if one was for the HD or the LTE version, but I guess they already have their own variant name in CM already... Just thought it was odd to have 2x i9100 builds going on together.... lol
Anyway, regarding CM7.... I've finally managed to get it to work!!!! YIPPIE!!!!!!! Finally... Although I swear it wasn't as hard as this when the phone DIDN'T belong to me, and I did it as a test for my mate... But anyway, got it installed and loving it... It's nice to go back once in a while to where it all began (well, for me anyway.... My first device came with Android eClair, I think Android 2.1 or summit??) But CM7.x was my first custom OS ever installed on ZTE Blade.
It would seem all the CM7 builds that I can find, both on CM site, and other hosts are all BORKED (broken) and that they lack Boot info, hence the BootLoops... and that all their recoveries are broken, as not a single one would go back into recovery after flash, had to Odin it back to life with a PC. Not cool if ya gone out for the day... lol So basically I found some random GB kernel, and flashed that after CM7 + GApps + Recovery.... and thank the lord, it all boots again...
I'd just like to THANK YOU, for always consistently and continually coming to my support needs..... Your help/advice has been extremely helpful.... thanks
Lister
gsstudios said:
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Click to expand...
Click to collapse
Hi Guys,
I've run into a bit of a problem and cannot find my way around it, my phone can be used for everything except making a damn phone call i.e. I can make calls, folks can see me calling and receive it but I hear a blank on my end and so does the receiver, no dialogue. I tried everything listed on other topics but cant seem to get phone calls working again....so please help....
I know exactly when this started happening so here's the details
I was running the Foxhound 3.0 ROM listed in the following thread and it was running perfect
http://forum.xda-developers.com/showthread.php?t=1486199
then I found a new ICS theme posted on the following thread
http://forum.xda-developers.com/showthread.php?t=1334922
and tried flashing that according to every step mentioned and although the ROM was running ok, I couldnt access system settings because my only option available was NOVA settings, my back button, phone calls & wifi wasnt working.
I looked into some of threads posted on the forum listed below and tried out every step to fix the problem but to no avail.
http://forum.xda-developers.com/showthread.php?t=1286432
http://forum.xda-developers.com/showthread.php?t=1313659
http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46
List of methods attempted
1. Restore mirror from my stock rooted ROM - fixed wifi but no phone calls
2. Restore mirror from ICSrewd ROM - same result
3. Used ODIN to go back to Unrooted Stock - still no phone calls
Kernel + non-rooted UCKH7 system package
4. Used ODIN to flash a different Kernel with root - same result
Kernel + cache + rooted UCKK6 system package
5. Full wipe and reflashed ICSrewd - same result.
Now i have so much info cluttered in head that I'm experiencing what people call 'writer's block' or what I would call 'Brain Dissolution' :-(
Can anyone please suggest a solution for this? My current phone deets are as follows
- At&t Samsung Galaxy SGH i777
- Android 2.3.6 Baseband i9100XXLPH
- Siyah v2.6.7
- Build ICSrewd v2.0.1 KL1
unkindestdude said:
Hi Guys,
I've run into a bit of a problem and cannot find my way around it, my phone can be used for everything except making a damn phone call i.e. I can make calls, folks can see me calling and receive it but I hear a blank on my end and so does the receiver, no dialogue. I tried everything listed on other topics but cant seem to get phone calls working again....so please help....
I know exactly when this started happening so here's the details
I was running the Foxhound 3.0 ROM listed in the following thread and it was running perfect
http://forum.xda-developers.com/showthread.php?t=1486199
then I found a new ICS theme posted on the following thread
http://forum.xda-developers.com/showthread.php?t=1334922
and tried flashing that according to every step mentioned and although the ROM was running ok, I couldnt access system settings because my only option available was NOVA settings, my back button, phone calls & wifi wasnt working.
I looked into some of threads posted on the forum listed below and tried out every step to fix the problem but to no avail.
http://forum.xda-developers.com/showthread.php?t=1286432
http://forum.xda-developers.com/showthread.php?t=1313659
http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46
List of methods attempted
1. Restore mirror from my stock rooted ROM - fixed wifi but no phone calls
2. Restore mirror from ICSrewd ROM - same result
3. Used ODIN to go back to Unrooted Stock - still no phone calls
Kernel + non-rooted UCKH7 system package
4. Used ODIN to flash a different Kernel with root - same result
Kernel + cache + rooted UCKK6 system package
5. Full wipe and reflashed ICSrewd - same result.
Now i have so much info cluttered in head that I'm experiencing what people call 'writer's block' or what I would call 'Brain Dissolution' :-(
Can anyone please suggest a solution for this? My current phone deets are as follows
- At&t Samsung Galaxy SGH i777
- Android 2.3.6 Baseband i9100XXLPH
- Siyah v2.6.7
- Build ICSrewd v2.0.1 KL1
Click to expand...
Click to collapse
You got an i9100 modem on your device from something you flashed (probably the theme package from the i9100 forums - but I didn't d/l it to look) as evidenced by your baseband reporting i9100XXLPH.
Though I think some of the packages you have tried flashing to fix it have modems, I would go to the appropriate modems thread (I think they are linked from the sticky in general) and grab whichever i777 modem you were running before and flash that...
dandrumheller said:
You got an i9100 modem on your device from something you flashed (probably the theme package from the i9100 forums - but I didn't d/l it to look) as evidenced by your baseband reporting i9100XXLPH.
Though I think some of the packages you have tried flashing to fix it have modems, I would go to the appropriate modems thread (I think they are linked from the sticky in general) and grab whichever i777 modem you were running before and flash that...
Click to expand...
Click to collapse
Ok, so here's my question, when I flash the Stock ROM, doesnt it already come with the stock modem too? or do I still have to dl and flash the stock modem separately?
unkindestdude said:
Ok, so here's my question, when I flash the Stock ROM, doesnt it already come with the stock modem too? or do I still have to dl and flash the stock modem separately?
Click to expand...
Click to collapse
ICScrewD should have given you the UCKH7 modem. Not sure why it didn't overwrite your i9100 modem. As I haven't been in this situation to have to get out of it, there may be more to it. My first step would be trying to flash just the correct modem package over what you currently have...other than that, others have been in this situation - search is your friend.
dandrumheller said:
ICScrewD should have given you the UCKH7 modem. Not sure why it didn't overwrite your i9100 modem. As I haven't been in this situation to have to get out of it, there may be more to it. My first step would be trying to flash just the correct modem package over what you currently have...other than that, others have been in this situation - search is your friend.
Click to expand...
Click to collapse
Ok I was still on ICSrewd when I tried flashing UCKH7 but it didnt overwrite the i9100 modem even after multiple flashes. I tried doing it thru ODIN and it still failed. So I went back to the Stock ROM and re-tried it and guess what....success!! ......which is weird, I'm not sure if it is an issue with ICSrewd new version 2.0.1...anyhow...now I'm experiencing ridiculous battery drain, so should I try various modem combinations to see which one works?
unkindestdude said:
Ok I was still on ICSrewd when I tried flashing UCKH7 but it didnt overwrite the i9100 modem even after multiple flashes. I tried doing it thru ODIN and it still failed. So I went back to the Stock ROM and re-tried it and guess what....success!! ......which is weird, I'm not sure if it is an issue with ICSrewd new version 2.0.1...anyhow...now I'm experiencing ridiculous battery drain, so should I try various modem combinations to see which one works?
Click to expand...
Click to collapse
After all that flashing, you'll probably see heavy battery drain for a few days. I usually have to go 3 battery cycles full to empty (which is 3 days for me) before I see stable battery behavior after flashing new roms.
Sent from my SGH-I777 using XDA App
dandrumheller said:
After all that flashing, you'll probably see heavy battery drain for a few days. I usually have to go 3 battery cycles full to empty (which is 3 days for me) before I see stable battery behavior after flashing new roms.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
I should've read this earlier
What I did instead was flash the turkbey ROM and went thru 2 cycles with it already so now I'm seeing some level of stability i.e. 19 hrs of battery time approx with about 5 hrs of Screen On time, which is pretty decent I guess.
Thanks for advice mate.
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
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, my samsung galaxy s2 started making problems, if i reboot, most of the times I get a black screen which, curiosly, if I press the menu and back buttons, they light up! still, I have to reboot it several times (removing the battery does not help) untill i get a "successful" boot. I'm rooted and I am using omega v13 AOKP, based on JB 4.2.2 but this problem started some time ago, when i was using Omega v24 based on 4.1.2.
My phone is in warranty, but I woud like first to determin if it is a software or hardware thing, because if it is a hardware problem, I have to figure out a way or restoring to stock without leaving traces, so I can use it...
any ideas what the problem might be? the kernels on both versions I used were different, so it has to be something different...
thanks
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
thanks
MistahBungle said:
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
Click to expand...
Click to collapse
thanks, that is was i was thinking, although i hate to waste such an amount of time.. anyway, thanks for the advice, I'll guess I'll have to do it.