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
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 ...
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.
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 .
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app
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...