Hello, how are you?
I have a problem with all ROM CM9 based, Wi-Fi stops working in mysterious ways, after flashing the ROM, is connected to wireless networks, but then still waits IP address and the process becomes cyclical becomes not connected to any other network.
I tried to change the baseband but nothing changed, I tried a variety of ROM CM9 based and all this problem occurs. I need help! :crying:
Sorry for my poor English.
EDIT​
If you have this problem use a root file manager.
Go to /data/misc/dhcp and delete all the files in it.
It will happen once in a while. When it happens, just repeat the procedure.
Thank you all for your help.
Binary_File said:
Hello, how are you?
I have a problem with all ROM CM9 based, Wi-Fi stops working in mysterious ways, after flashing the ROM, is connected to wireless networks, but then still waits IP address and the process becomes cyclical becomes not connected to any other network.
I tried to change the baseband but nothing changed, I tried a variety of ROM CM9 based and all this problem occurs. I need help! :crying:
Sorry for my poor English.
Click to expand...
Click to collapse
Do you have a GSM or CDMA Xperia Play? Also, what baseband are you on?
Justinchi said:
Do you have a GSM or CDMA Xperia Play? Also, what baseband are you on?
Click to expand...
Click to collapse
I have a GSM with .64 baseband.
Binary_File said:
I have a GSM with .64 baseband.
Click to expand...
Click to collapse
Ok, I hate to send you through all the trouble again, but make sure you're using Zeus ROMs and not Zeusc.
Copy CM9 to your SD Card
Copy the modules for the kernel listed below to SD card too
Flash this kernel: http://forum.xda-developers.com/showthread.php?t=1781677
Press back when it vibrates on bootup to go into recovery
Do a factory reset, wipe dalvik cache in recovery
Install the ROM
Install the wifi modules
Reboot phone
Justinchi said:
Ok, I hate to send you through all the trouble again, but make sure you're using Zeus ROMs and not Zeusc.
Copy CM9 to your SD Card
Copy the modules for the kernel listed below to SD card too
Flash this kernel: http://forum.xda-developers.com/showthread.php?t=1781677
Press back when it vibrates on bootup to go into recovery
Do a factory reset, wipe dalvik cache in recovery
Install the ROM
Install the wifi modules
Reboot phone
Click to expand...
Click to collapse
I tried also with that kernel, using the Zeus ROMs and following the steps you indicate.
Above all ROMs based on CM9 worked perfectly on my terminal, but has less than a month that does not work correctly.
It's funny because with the ICS-based Beta ROM I have no problem.
Binary_File said:
I tried also with that kernel, using the Zeus ROMs and following the steps you indicate.
Above all ROMs based on CM9 worked perfectly on my terminal, but has less than a month that does not work correctly.
It's funny because with the ICS-based Beta ROM I have no problem.
Click to expand...
Click to collapse
Oh wow...hmm. I'm sorry, I don't know what to say =/
I have days trying to fix my problem and it persists. Is there anyone else who can help me? :crying:
Binary_File said:
I have days trying to fix my problem and it persists. Is there anyone else who can help me? :crying:
Click to expand...
Click to collapse
Maybe try flashing a different kernel and it's wi-fi modules? Mjolnir Kernel and Turbo Kernel both work for CM9 based ROMs.
game_guy said:
Maybe try flashing a different kernel and it's wi-fi modules? Mjolnir Kernel and Turbo Kernel both work for CM9 based ROMs.
Click to expand...
Click to collapse
Yes, try with these kernel. Because I've only tried with Lupus and FXP. :good:
Just delete /data/misc/wifi/wpa_supplicant.conf if you have it... or whichever file saves your wifi passwords.
zeppelinrox said:
Just delete /data/misc/wifi/wpa_supplicant.conf if you have it... or whichever file saves your wifi passwords.
Click to expand...
Click to collapse
Previously I had tried to do that, but it did not work, the problem persisted.
I'm currently using the latest build of CM10 and I have no problem. But when I can, I will return to CM9 to verify solutions to my problem
Thank's :good:
zeppelinrox said:
Just delete /data/misc/wifi/wpa_supplicant.conf if you have it... or whichever file saves your wifi passwords.
Click to expand...
Click to collapse
After deleting the file, the wifi not lit.
I was also using the latest build of CyanogenMod 10, and after 5 days of proper operation, the problem appeared, as in CM9 based ROM.
I'm desperate, I don't know if either motherboard problem. :crying:
Thank you all for your help, I solved the problem by removing the contents of /data/misc/dhcp
Oops clicked thanks but whatever... lol
Yeah I guessed that it must be something in data, because flashing another rom without wiping data would of course leave all data alone, the bad along with the good.
Related
I know its a noob question but i am new to developing and the rom world.Here is my problem, every time i flash a custom ics rom and the modules may i say it works fine on gingerbread, but on ics wifi turns on but dosent recognize any network any tips on how to make it work?
xperiaplayicsuser2013 said:
I know its a noob question but i am new to developing and the rom world.Here is my problem, every time i flash a custom ics rom and the modules may i say it works fine on gingerbread, but on ics wifi turns on but dosent recognize any network any tips on how to make it work?
Click to expand...
Click to collapse
First view if WiFi is active on your phone.
Else reflash modules from recovery (install zip from sd)
reply janito24;28771518
janito24 said:
First view if WiFi is active on your phone.
Else reflash modules from recovery (install zip from sd)
Click to expand...
Click to collapse
Thanks for the reply but i tried it and wifi turns on but wont detect a network it worked fine on GB
Any other suggestions?
any one else having the same problem?
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
fuhrl said:
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
Click to expand...
Click to collapse
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Xperia Player said:
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Click to expand...
Click to collapse
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
fuhrl said:
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
Click to expand...
Click to collapse
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
DubleJayJ said:
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
Click to expand...
Click to collapse
ok. thanks. Just as a clarification to the first part of the original response, I am installing the original stock kernel after i flash back to the stock ROM?
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
fuhrl said:
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
Click to expand...
Click to collapse
What version of FXP are you using, and what are the wifi zips called that you're using?
lightningdude said:
What version of FXP are you using, and what are the wifi zips called that you're using?
Click to expand...
Click to collapse
i used FXP 132. I know it's not the latest but I'm sure that it was when I downloaded it a month ago. The zips were cleverly named wififix2, WiFi_FiX_LuPuSv3 and the other was CDMA_mega_fix_v2_by_Leraeniesh. The last one had a WiFi fix in it by Atarii or someone like that.
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
nyvang101 said:
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
Click to expand...
Click to collapse
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Xperia Player said:
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Click to expand...
Click to collapse
i think you have to flash doomlords wifi modules in recovery. it's what worked for me when i was using that rom.
http://forum.xda-developers.com/showthread.php?t=1579388
fuhrl said:
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Click to expand...
Click to collapse
The ftf has the stock kernel in it.
Sent from my SCH-I500
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
nyvang101 said:
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
Click to expand...
Click to collapse
did this work? i have the latest PACman JB rom for the r800x and im using the lupus v5 kernel that came with it. for some reason all the other roms have working wifi except cyanogenmod based roms....... why is this?
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
no matter what baseband i flash via odin, wi-fi could not be enabled after rebooting.
baseband version changes successfully. anyone have a solution for this issue? thanks
in advance.
flash it twice!
lOtz1009 said:
flash it twice!
Click to expand...
Click to collapse
doesn`t work.
is it neccessary that kernel and baseband have to be the same version?
crxvti said:
doesn`t work.
is it neccessary that kernel and baseband have to be the same version?
Click to expand...
Click to collapse
nope, I actually found a fix for the same issue, root your phone then delete /data/misc/wifi/wpa_supplicant.conf then flash your rom again (not sure if you need to clean data and cache) with odin and it should work.
Levent2101 said:
nope, I actually found a fix for the same issue, root your phone then delete /data/misc/wifi/wpa_supplicant.conf then flash your rom again (not sure if you need to clean data and cache) with odin and it should work.
Click to expand...
Click to collapse
unfortunately, this does not work, wi-fi can only be enabled if i use the one from my rom
I was have same issue.
How did I fix it? (I have 9190)
I flashed 9195's stock rom via odin. Of course odin gave me error. I removed the battery and placed it again. Flashed latest 9190's stock rom and wifi issue solved.
i flashed a rom that fits for i9195, that is not my problem. i have no wi-fi after i update my modem. version number is correct but wi-fi can not be enabled, even if i flash it twice. my rom is the sc-stock rom
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-stock-nk5-deodexed-debloated-4-4-2-t3104160
crxvti said:
no matter what baseband i flash via odin, wi-fi could not be enabled after rebooting.
baseband version changes successfully. anyone have a solution for this issue? thanks
in advance.
Click to expand...
Click to collapse
The ROM controls the wifi, not the modem. Strange that multiple ROMs can't even be enabled, I suspect data is left somewhere, do full wipe to install a new ROM so all old data etc is wiped and make sure you are not installing app data etc from a backup for this.
Else it might be the kernel.........
IronRoo said:
The ROM controls the wifi, not the modem. Strange that multiple ROMs can't even be enabled, I suspect data is left somewhere, do full wipe to install a new ROM so all old data etc is wiped and make sure you are not installing app data etc from a backup for this.
Else it might be the kernel.........
Click to expand...
Click to collapse
wi-fi is working with the baseband which is included in the rom (until i flash another baseband, then it stops)