Related
I recently flashed KGB 12/2 with SC3 0.5 not realizing that 12/2 had issues. Anyway when KGB 12/12 got released I flashed that. It resolved all the slowdown problems.
This is the first kernel I have ever flashed. I just flashed the 12/12 kernel over the 12/2 kernel. Then I started to have internal memory issues. i.e. market apps wouldn't update due to low space on device.
I thought I found a solution after searching a while and thought it was because I flashed 12/12 over 12/2 without disabling lagfix. I then disabled lagfix, cleared both caches and then flashed 12/12.
Since I was unable to find a Q&A directly related to kernel flashing I am hoping someone can point me in the right direction.
What is the best way to flash the new kernel over an existing kernerl? Specifically regarding KGB kernels. I just used CWM but I feel like I should have used ODIN. Before I do anything further to mess this phone up I wanted to throw this out here.
Thanks in advance.
Kernel flashing is the same as flashing anyother zip. Wipe cache and dalvik then install zip from sd. If you are still having issues odin back to stock and start over. There also is a kernel cleaning script you can try before odining, but your best bet is to start over imo.
Ok...I installed the new kernel just like I would install any patch. I saw the kernel clearing script on a forum for another version of this device, but I'm assuming it will work. I'll give that a shot first. After all if it screws me up I'll be going back to stock anyway.
Thanks.
i switch kernels all the time but i do use a cleaning script every now and then just to be on the safe side. starting over would hurt a thing either.
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
As long as you follow the instructions, it doesn't matter what you're coming from. See full instructions here http://forum.xda-developers.com/showthread.php?t=1419102
Notice that for the CWM method, the third instruction is to flash a particular CWM recovery to avoid potential problems. There are instructions on how to flash on the link to it.
n125 said:
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
Click to expand...
Click to collapse
Easy enough upgrade path
If you are worried about doing this, flash the ODIN "resurrector" CM9 package - it should sort out wiping and everything else for you.
If you want to do it via zip, put the zip file on the SD, do a nandroid backup, wipe data and cache, then flash the zip and latest ICS gapps.
I don't think you'll have any issues with installing CM9 using that CWM. If you do, ODIN flash latest Siyah Kernel. Go to recovery and flash CM from there and you'll be fine
Thanks for the help guys. I went with the CM9 Odin Resurrection method and then updated to the latest nightly (20120511) with CWM.
I'm very impressed with what I see so far. I'll have to keep an eye on it, but I am a little worried about the battery life. (Though considering that I am on a nightly build, less than optimal battery life might be expected..)
Also, my signal strength seems to be fluctuating a bit, usually between 3 and 4 bars, although sometimes it will go down to 2 bars. The modem that came with this build is XXLPQ. Is there a better modem that I can try, or is it just a matter of going through all of them? I was on MUGKG2 previously and it was quite stable for me.
I think LPQ must be your earlier Modem which is retained after instlling CM9, if I am not wrong CM9 doesnt contain a modem.
try KE7 modem, I have got a very nice experience with KE7 on ICS roms
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
monolithcog said:
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
Click to expand...
Click to collapse
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
huytrandinh said:
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
Click to expand...
Click to collapse
Thanks mate for your reply,
I installed cm 11, this did not resolve it.
need the file for the radio/modem, i'm hoping this will fix it but not sure exactly what I am looking for.
**Update***
Just finished installing I9100TDVLSM_I9100TVAULSF_VAU (latest release from Sam Mobile) 4.1.2
Still wi-fi not working.
will try and install cm 10.2 on your recommendation huytrandinh
Okay latest nightly of CM is installed cm-10.2-20131216-NIGHTLY-i9100.
Still has not resolved the wi-fi issue.
anyone have a potential solution?
there is this post for S4, but obviously only viable for S4
http://forum.xda-developers.com/showthread.php?t=2192025
There is also this video tutorial which is for S4
http://www.youtube.com/watch?v=YL8H70Es4wg
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
jedzkiiii said:
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Have been trying that, still no success.
have spent all day trying to find a solution
I tried the modems from here:
##hxxtp://###.veyka.co.uk/sgs2/radios/## (unable to post links ffs)
and few other random links from the forums
MistahBungle said:
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
Click to expand...
Click to collapse
Thanks Mistahbungle,
I checked out that thread http://forum.xda-developers.com/showthread.php?t=2345831
Nothing i could really use.
But I did try a few other kernels:
Siyah-s2-v5.0.1
Unfortunately as soon as flashing with other kernels the screen would go black after the initial boot logo.
Only way to resolve it not booting into the OS was to roll back to:
1. GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9 (flashed with odin)
2. flash CWM-SuperSU-v0.97 with CWMRecovery
3. install cm-10.2-20131216-NIGHTLY-i9100
4. then your general cleaup through cwmrecovery
I'm not sure if I'm doing something wrong when trying to apply another kernel.
anyone able to offer assistance please with right kernel?
cheers
**Update**
Just found a post in that thread - http://forum.xda-developers.com/showthread.php?t=2345831&page=6
Will try the 3 part rom XXLSJ for GT-I9100.
Fingers crossed
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
MistahBungle said:
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
Click to expand...
Click to collapse
Okay just finished testing the rom by installing it via odin (3 part)
still has not yielded any favorable results .
Little disapointed as this was a great backup phone and served for the past 12 months as a mp3 player
Guess as they say; It is all planned obsolescent which is fracked ...
Thanks for the suggestion/help anyway.
I know this is an old thread but my gs2 had this problem and I was able to fix it. Using es file explorer made my way to /data/misc/wifi pulled up the properties to wpa_supplicant.conf and changed group to wifi...then wifi finished initializing...hope this helps somebody
Sent from my SM-T310 using XDA Premium 4 mobile app
for consideration.
I have this phone. the GT-i9100. Had this issue also. I took it apart. The little onboard battery had blown and corrosion got all over all it.
and guess where WiFi hard is. Right Next door. I cleaned it up real good. Put it back together and WiFi came back to life.
So give it some thought guys.