Database Info

Wifi Problems

Hi everyone, I was wondering if anyone else was experiencing wifi problems after updating from 2.2 to 2.3. I lost my wifi after switching to the CM7 nightlies awhile ago and i thought it was just the rom, but I've used RoyalGinger, RoyalMint, and RoyalGlacier. I followed the instructions exactly, but when i turn wifi on, it just says error. This is also the case for the wifi hotspot. Any help would be much appreciated

Try flashing, booting and letting it load without trying to turn on wifi. Then after a few minutes reboot and let it load again then try turning on your wifi. Let us know if that helps you.
Sent from my HTC Glacier using XDA App

Try flashing faux123's custom kernel.
Here's a user that used it and it fixed his WiFi issues: http://forum.xda-developers.com/showpost.php?p=12661728&postcount=580

I tried both methods posted above, and still no go. I've been using faux's kernel since RoyalGinger came out but it hasn't fixed my wifi. I'm currently using the latest RoyalGlacier with the latest faux sense kernel.

Well **** buddy, I dunno what else to suggest. You have tried various kernels, and multiple ROMs all to no avail.
I know our devices are notorious for weak wifi, but never heard of it being completely broken. I would nandroid restore to the stock ROM and kernel and see if it's still broken. If so, then have HTC or T-Mo switch it out for you.

are you using anything like titanium backup to restore settings? read some where that restoring like can break wifi. other then that and making sure you fully wiped everything thats all i can think of.

I've also tried a few different kernels like gorilla's and smartass stock. Also, I'm not backing up with titanian backup. Could it be my ext partition?

ROM issue

I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.

STEyeAndroid said:
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
Click to expand...
Click to collapse
You need a gingerbread radio for a gingerbread rom.. so MR2 or MR2.5
Sent from my ThunderBolt using XDA Premium App

i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff

poloboogie said:
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
Click to expand...
Click to collapse
when you say everything is the same, do you mean it still has the previous radio version number?

I'd suggest that you both:
1) Wipe data/dalvik/cache and flash back to a froyo ROM where you do have a signal
2) Upgrade from froyo to the MR2/2.5 radio
3) Re-wipe data/dalvik/cache (or even do it twice for good luck ) and re-flash BAMF 3.0
If its worth doing, its worth overdoing, especially when you're messing with radios and the like. Best of luck!

That's the same problem I first had with gingeritis before flashing the correct radio.. if you are still experiencing the problems after the radio flash i would suggest confirming the radio did install by checking the version number..
if it is all correct do as MattBeyers said and wipe and reflash

Thanks, that seemed to work. I still got a couple of force closes but much less than before. Also I can see my radio now! If I wanted to restore my old my Backup (Stock Froyo - MR1), do I restore my backup then flash MR1? If so, does anyone have a link the MR1 image? TIA!

I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App

MattBeyers said:
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.

I tried mr2 and mr2.5 but could only get 3g. Went back to CM7.
Sent from my ThunderBolt using XDA Premium App

Mr_Joshua said:
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
Click to expand...
Click to collapse
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )

Make sure u have a gb radio mr2 or mr2.5

MattBeyers said:
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Click to expand...
Click to collapse
This makes sense from a logical reason. Perhaps a ROM developer on this site can confirm this.

WiFI - turning on and on and on... RESOLVED!!!

Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
EDIT: wifi was not working about half a hour...but than...voila!!! It is for no reason back working the phone was just liyng on the table, than i took it and just set wifi on, "what if"... that´s really strange, but. But great! Now go back root, s-off and some awesome custom rom

lord5619 said:
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
Click to expand...
Click to collapse
Have you tried to restore the stock ROM?
http://forum.xda-developers.com/showthread.php?t=1529941

I agree I would recommend flashing the full ruu to take you back to stock Rom I did the same thing to get rid of my problem and flashing the full ruu did the trick I'm now s off Revolutionary style and flash 4ext custom recovery and su file and custom Rom the correct way
Sent from my HTC Sensation 4G using xda premium

Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....

lord5619 said:
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
Click to expand...
Click to collapse
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?

malybru said:
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
Click to expand...
Click to collapse
will try your patch, thx
EDIT: it says -Revolutinary- and HBOOT is 1.27.1100 Thanks!
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?

lord5619 said:
will try your patch, thx
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
Click to expand...
Click to collapse
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.

malybru said:
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
Click to expand...
Click to collapse
I am afraid, even this is not working. Pins definetly have some resistance and resting to its place. :-/ when i return from vacation, i´ll take my precious Sensation XE to a doctor, he will know perhaps.

I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.

i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance

alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I honestly don´t know, i thought, wifi is (almost)only kernel related, but now i see, that it is not :/ It is almost exactly my problem, i was using ViperS and changed kernel...but it didn´t suit me, so i restored the previous one...than i woke up and wifi is gone i cant solve it for now, i don´t have any freetime at this moment for making full stock condition.
i have tested stock rom with stock kernel, with some other HBOOT but still the same.

bhma said:
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
Click to expand...
Click to collapse
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.

lord5619 said:
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
Click to expand...
Click to collapse
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma

bhma said:
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
Click to expand...
Click to collapse
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...

lord5619 said:
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
Click to expand...
Click to collapse
Originally Posted by Zeustopher
Wanted to update on my progress. I solved the issue on my phone:
I was messing around with it today while waiting for a meeting to start and I found where the wifi settings, etc are stored. It ended up being a corrupt/invalid wpa_supplicant.conf file. All I had to do was pull that file out from the directory and turn on wifi and *poof* it worked again. When I turned wifi on it created a new file and everything has been great so far this afternoon.
In case anyone wants to give it a shot who is having wifi issues you can find the wpa_supplicant.conf file in /data/misc/wifi/ directory on your phone. Simply cut/rename the file and put it somewhere else. If you have wifi passwords you want to save, you can open the original file using a text editor and copy the settings over to the new file.
I believe the cause of my issue was actually Titanium Backup. Looking at the last time it backed up my wifi settings was back when I wasn't running ICS yet. Yesterday I did restore an app using it and must have accidentally restored that old backup. Their formats are different from Gingerbread to ICS apparently and it was causing errors.
i found this on another post dont know if it will help but it could be the problem with the ota update from gb to ics
now the silly noob question how do you access the directory ????http://forum.xda-developers.com/images/icons/advanced/sign.png
i got into the directory but it doesnt seem to work in another thread someone got it to work with a virtuous rom
ill try that on thr weekend
enjoy your vacation

hmmm thats iteresting, but if you do full-wipe and flash some rom and kernel, these files are rewriten...but because i am curious i tried it and!!! it is not working for me :-/
And how to get into this directory?Simply... download dome file manager from Play Market(i lika Total Commander), but you can use whatever you like, set in options "root function everywhere" and allow superuser. than you can go in any directory and read/write/change
EDIT: ou, now a see whole post, ignore my instruction i am mega-sleepy

alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.

alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
Yank v2.52? hmmm that´s kernel by Faux?

lord5619 said:
Yank v2.52? hmmm that´s kernel by Faux?
Click to expand...
Click to collapse
yep

alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
No help for me still the same "turning on"

S3 rom wifi issue help please

hey im new to the forum and i rooted my s3 and have the r420 senergy rom installed but the wifi dooesnt work! uhhhhh i cant post in the development section till i have 10 posts. so any one who can help that would be great. ive been doing a lot of reading and what is the differnce between nightly and and regular roms? and i read that the wifi wont work on the nightly rom with out a kernel flash?>?>? Is this right? im going to try the v1.6 senergy any way .....my model is the i535 but yall probably already know that because you hacked my ip address and seen my phone plugged in J/K ha thanks in advance

First off, Synergy r433 is the latest version. And a new release is scheduled to drop any minute now.
A nightly is an experimental build that gets updated nightly. Whereas a stable build is less frequent but as the name suggests is stable. Nightly you must really know what you're doing and are be okay with occasional bugs, otherwise use the stable releases. (fyi SynergyROM stopped releasing nightlies)
As for your Wifi problem, reflash but the make sure you do a full factory reset, and then a super wipe within the AROMA installer. *This will wipe internal storage, make sure to have the ROM zip on external storage* Wifi is not bugged, I'm suggesting the was a flashing error.
Sent via SGS3 using Tapatalk

Thank you so much for replying. i was thinking the same about the nightly "name" but thanks for clarifying. i have tried several times. in clockworkmod recovery(or whatever the name is) i factory reset and in the installer i wipe everything. (on the internal sd) and then install cleanly. but my kernel doesnt flashed it says its not unlocked.?!?! how do i unock it? i unlocked the bootloader and once more so i knew for sure. and my phone says custom with a padlock unlocked symbol below. but same thing everytime...wifi is buggy. i like this rom and just want it to work...thanks!!!!!!!!!!!!! is there a special "better" kernel unlock method? my paitients are getting low...lol well my girl wants her phone stock ...F**CK THATT!!!!!!!!!! thanks man

Bump please someone plesase help.. I need this phone working asap

Check out this link
seems to work for some.
http://forum.xda-developers.com/showthread.php?p=40531554
Mine has always been good.
I also use an app called Opensignal
https://play.google.com/store/apps/details?id=com.staircase3.opensignal
When on the OpenSignal app select > wifi then select the > refresh then the > refresh network.
I do this every week or so. I have no issues with wifi, ever.
Some say tightening the screws
help check out rhe link below
http://gs3.wonderhowto.com/how-to/s...-gps-problems-your-samsung-galaxy-s3-0145332/
I hear it's just some phones. Anyways
good luck
Sent from my Smoking smooth
Synergy r484
Mods by gunthermic,
Theme by jbeitel

I am experiencing the same issue.
I rooted, flashed CWO, and then installed synergy. Nothing worked... then I read that you need to unlock the bootrom so I did that, rebooted and got the same... no wifi. After unlocking the bootloader I reinstalled synergy (R484) and still WiFi will not turn on.
I followed they synergy thread for flashing and This thread for bootloader unlocks.
Provider: Verizon
Phone: GS3
ROM: SynergyROM (r484)
Recovery: ClockworkOrange

Got it fixed!
So... I only used odin... no romloader apps or any of that crap...
1: Reinstalled stock ROM
2: Reinstalled CWO
3: Reinstalled Root+Bootloader
4: Reinstalled SynergyROM
5: Enjoy! Wifi works, all applications work!
Chris

Issues with Mobile Data Rapidly turning on/off after using hotspot

Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?

Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?

Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047

I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.

kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?

Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?

After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave

deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img

Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.

deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!

I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?

deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.

jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.

deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?