Database Info

Is there a solution for the WiFi issue?

It's been some time since I posted the problem. I searched around and didn't find any new information, so I am just hoping I missed something, like a possible thread that has a fix.
I have no WiFi, have gone through the book trying to fix it, to no avail. HOWEVER, I left the phone un used for about a month, battery had died long ago. A few days ago, I grabbed and and just decided to give it another shot and install revolution hd on it. For whatever reason, it installed successfully and the WiFi was working perfectly. So I updated the 4ext and had notice that a new version of HD had come out, so I decided to update it, and well, back to square 0, WiFi no longer works. So I tried to back pedal and repeated the steps leading up to the WiFi working, Super Wipe with smart flash enable, reboot, installed HD with no smart flash. But this time it did not work. Strange that it worked before though, I wonder if it being out of battery for so long had something to do with it.

did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash

rzr86 said:
did you try to flash the boot.img of your rom?
also if you are S-ON when flashing a rom always enable smartflash
Click to expand...
Click to collapse
What he said.. if you're s-on always flash with smartflash
Sent from my HTC Sensation 4G

I too had the wifi issues for quite some time. After updating my kernel it got fixed.
Probably you could do the following:
1. If your HBOOT is S-ON, make sure you follow the above two posts while flashing ROM
2. Ensure that the latest firmware is being used.
2. Try changing the kernel (mine is faux 009b4 now).

I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.

F9zSlavik said:
I am S-OFF, like I said, I've tried everything.
Just seem odd that out of nowhere it flashed correctly, I should of just left it at that, maybe if I leave the battery inside the phone drained for a while I can repeat the successful flash.
Click to expand...
Click to collapse
well don't know if you have tried this but the last thing I can think of is to go back to stock ruu, if it still doesn't work it might be hardware related
Sent from my HTC Sensation 4G

I faced with same issue. I use ARHD 6.7.1 and i have no problems with wi-fi , but when I try to install sense 4.0 roms for sensation, I always have wi- fi problem.I live in Almaty and I use Beeline for mobile carrier, My device is Revolutionary S-OFF. I live in Almaty and I use Beeline for mobile carrier, and also I have one sim card for Turkey, AVEA, when I use Beeline wi-fi doesn't work but when I use Avea wi-fi works completely. I tried wifix manager. But I can't find solution :/

Same thing happened to me when I updated, go to tools in 4ext before flashing and enable smart flash, I'm pretty sure this will help
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app

Clearing up the Wifi Issues

Alright guys so im on HBOOT 1.14 tried several roms all cant connect to wifi, I tried flashing the partions with no luck. I want to know what you other guys have done to fix this issues.

adolfo778 said:
Alright guys so im on HBOOT 1.14 tried several roms all cant connect to wifi, I tried flashing the partions with no luck. I want to know what you other guys have done to fix this issues.
Click to expand...
Click to collapse
The only fix is update with OTA or downgrade the Hboot.

I ran into the same issue with 3 other ROMs today. Finally used TWRP recovery (instead of the CWM I had been using) and installed JellyBam 4.0.0 (and flashed the boot.img with fastboot.)
I can't say that's what fixed it because I can't honestly say the other ROMs were the cause of the problem. All I can tell you is that within minutes of rebooting after the install, my phone connected to wifi.
Good luck with it - I'm sure others who actually know what they're talking about will offer more than I can.

Thanks guys just wanted to see what my solutions were.
Sent from my HTC One S using xda app-developers app

david251 said:
I ran into the same issue with 3 other ROMs today. Finally used TWRP recovery (instead of the CWM I had been using) and installed JellyBam 4.0.0 (and flashed the boot.img with fastboot.)
I can't say that's what fixed it because I can't honestly say the other ROMs were the cause of the problem. All I can tell you is that within minutes of rebooting after the install, my phone connected to wifi.
Good luck with it - I'm sure others who actually know what they're talking about will offer more than I can.
Click to expand...
Click to collapse
Don't help with Sense based roms.

Any guides or links on how to update? I'm on my phone atm.
Seems every HTC device is different when it comes to this stuff lol
Sent from my HTC One S using xda app-developers app

Never had wifi issues on my 1.14. Although the only sense-based roms Ive used have been ICS ones. Maybe the wifi wouldnt work on JB sense roms.
Wifi works fine on JB AOSP roms though.

Similar problems with wifi. I've tried several ROM's, lastly Jellybam 4.0.0, came from CM10, before that some other custom rom, now stock 3.16.401.8. I think my wifi hardware is broken. Going tomorrow to warranty service. I'm not expecting the warranty to cover this since I tried several ROM's, but I will try and see what happens.

lukevader said:
Similar problems with wifi. I've tried several ROM's, lastly Jellybam 4.0.0, came from CM10, before that some other custom rom, now stock 3.16.401.8. I think my wifi hardware is broken. Going tomorrow to warranty service. I'm not expecting the warranty to cover this since I tried several ROM's, but I will try and see what happens.
Click to expand...
Click to collapse
Downgrade your hboot man worked like a charm. If you need any help with the process just lmk
Sent from my HTC One S using xda app-developers app

CM10-20130114-Nightly Kernel

Quick question:
I've been having wifi issues which I've searched for the solution, but haven't found it. I don't want to downgrade hboot because I see my limitations laying in there somewhere and don't want to mess everything up. Wifi is the the only issue I'm having.
I flashed the Fusion Ultimate v.4 kernel hoping it would help, but it hasn't, although my phone seems to run faster and smoother.
So I'm wondering... will a kernel even really help a wifi issue and, if so, is there one better suited than the Fusion Ultimate?
My phone:
HTC One S (S4) S-On
hboot: 1.14
kernel flashed via Flash Image GIU

It seems many have wifi issues with custom roms and hboot 1.14. Kernels doesnt help.
The only solution Ive seen around the forum is, downgrading the hboot.
In terms of kernel, you are one of the lucky ones who managed to get v4 to boot, welcome to the club Theres a giant bug somewhere in it which causes it to not boot for the majority of the users.
You could try Fusion v3.1 instead - but I doubt that will help your issue.

Surprisingly, it seems to have worked. At least, I assume it did since I made no other changes tonight and Wi-Fi is working. Even when I leave the house, it connects when I get back. Whatever happened, I hope it keeps up.
Thanks for the reply.
Sent from my HTC One S using Tapatalk 2

[Q] Hboot 2.15 and wifi probs

Hi all!
After ditching my Desire HD, I bought myself a HTC One S for its faster soc and better screen.
As I was used to having everything working on my former phone I'd expect this for the One S as well..
So far I've reached Unlocked bootloader, SuperCID and S-Off. Still on HBoot 2.15 though.
On PAC-man Rom at the moment and experience some Wifi problems as its not connecting to all wifi networks, yet some of m work.
Tried all sorts of radios from the Development forum, Sense version, Temporally version and CM version. None seem to take effect.
Tried some different Kernels as well, same outcome..
Tried ViperRom (with and without update) this morning and Wifi isnt able to switch on, even after different kernel and radios..
In short... is there a way to get all types of Wifi working on AOSP or Sense rom?
Is it neccessary to downgrade HBoot (as there is bricks reported)?

I'm on 2.15. S-off. Super cid. But I never had wifi problems. Have you tried the wi-fi fix on the radio thread?
Sent from my HTC One S

veeny101 said:
I'm on 2.15. S-off. Super cid. But I never had wifi problems. Have you tried the wi-fi fix on the radio thread?
Sent from my HTC One S
Click to expand...
Click to collapse
I have not found a seperate file tot flash or push for wifi fix, so i presume it is incorporated in the aroma installable radios.
Wat ROM are you on?

OK. Here's what I've found out..
Since I'm really anonoyed by my phone not connecting to all types of Wifi I flashed an RUU.
I did this during SuperCID and S-OFF and just ran a .exe RUU.
First one I tried: RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
It had no effect, booted up, yet Wifi was not fixed.
Next one I tried: RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
And voila my Wifi worked.
On Hboot 1.06 now, flashed recovery and next PAC-Man ROM v20.0.0.
Now my Wifi again is selective like it was before.
I hope someone has an idea where to look as I simply don't understand what the problem is..
Tried the Temporary Radio V2 as well, no effect.
Anyone?

In the developer forum there is a radio thread with the WiFi fix.
Sent from my One S using xda app-developers app

In the developer forum there is a radio thread with the WiFi fix.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Yes, as mentioned, I have tried the wifi fix, doesnt make a difference :s

Have you tried switching your hboot around?
http://forum.xda-developers.com/showpost.php?p=38387544&postcount=148

Thanks for the hint.
However something I found out was that the new version of VenomROM V2.1 does give me full Wifi.
Unfortunately I don't realy like Sense Roms and rather have a different one.
I redownloaded PACman v20.0 and have tried all Hboot versions, none seem to make an improvement on Wifi capability.
Some work, some won't..
Going to try one or two Hboots with different Radio's from Temp Radio installer V2.
Anyone got an idea? Or perhaps a nice Hint again

Updated: JB nav issue also on 100% stock ROMs

EDIT 3/16: After more detailed testing during the day today I withdraw all of the claims below. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text below intact for context.
------------------
It would appear that the JB nav issue some of us are plagued with is exclusively due to something devs are doing with their custom ROMs. Here is why...
I am one of the unlucky ppl who could not get Nav to work with JB. I have tried multiple custom ROMs, including stock rooted, and nav always crashes within two minutes. Today I RUU-ed back to 2.20, changed CID to AT&T, took the official OTA and played with Nav without a hickup for 30 mins. I then unlocked again, Super_CID-ed and flashed CleanROM 6 R2. Nav immediately went haywire with the same symptoms as before. I then went through the RUU and OTA process once again, and Nav purrs like a kitten.
Not sure what custom ROMs are doing to mess up things...but the above suggests that something common that devs use to root is interacting incorrectly with JB on some phones. We seem to be a minority of users, as busy as our devs are we may get no love.
At this point I will stick with AT&T true stock for a while, will just flash a custom recovery and debloat it to an extent with the TWRP file manager or just slim down update.zip.

Re: JB nav issue seems to be caused by custom ROMs
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2

Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.

pablo11 said:
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It is well documented that only some HTC phones suffer from this problem. It has been seen on the HOX, the EVO, even on some SG3s. This is what has made it so maddeningly frustrating. It affects a small fraction of the users, so the devs don't spend any time trying to address it. Not blaming the devs, they can't go after every small issue. However, for those of us unfortunate enough to have it it has been a PITA.
slippers67 said:
Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.
Click to expand...
Click to collapse
Yes, I tried AT&T stock rooted, no dice. The ONLY thing that has worked so far is 100% stock unrooted OTA.

Re: JB nav issue seems to be caused by custom ROMs
don't know much about it, but I have the issue and I am most puzzled why the app hasn't had an update with bug fix. It's been too long an issue for the official channels not to have been noticed. If it IS ONLY custom roms, I wouldn't be surprised of the official channels just ignored the bug.
I initially thought maybe HTC made a deal with Google too break nav so people would start paying for a subscription to the HTC nav app. But I just use waze now. It seems to find better routes anyway.
This post was created and transmitted completely in analog.

I thought we had already covered it .. isn't it some people have a little diff hardware then others I think one member suggested gyroscopes differentiations being the problem...but I've never had a problem with nav on any jb sense rom nor jb in general ... It shouldnt be caused by custom roms as that doesnt make sense

Re: JB nav issue seems to be caused by custom ROMs
It really would be nice to see a firmware upgrade pack for the hox. It seems we actually need it.
Sent from my HTC One X using xda premium

Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.

slippers67 said:
Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
Click to expand...
Click to collapse
I already did this and try to convey it in the OP but perhaps was not clear.
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was done
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
Click to expand...
Click to collapse
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.
Click to expand...
Click to collapse
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.

GroovyGeek said:
I already did this and try to convey it in the OP but perhaps was not clear.
This was done
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.
Click to expand...
Click to collapse
Don't use CR6.2. Use the stock 3.18 rom he released. Then restore the boot.img from the backup. At that point, the only difference will be the different recovery on your phone, as everything else will be the same as taking the OTA.

I've had the issue but only after updating to the latest ViperXL OTA.

After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.

GroovyGeek said:
After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.
Click to expand...
Click to collapse
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL

ECEXCURSION said:
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL
Click to expand...
Click to collapse
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?

GroovyGeek said:
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?
Click to expand...
Click to collapse
I'm confused. This phone was released 11 months ago. Announced 13 months ago.
10 months in the US, even.

Not sure why groovygeek thinks the phone was released so long ago... May 9th 2012 in the US.
Sent from my HTC One XL
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
For those with the nav crashing, are you charging the phone when this happens? Does it cash both ways?
Sent from my HTC One XL

I have two phones bought at the same time. One is stock unrooted and runs the OTA 3.18 with no google maps crashes. My phone as described in my sig has map crashes always. I haven't jumped around to many other JB roms besides Viper to this point because they all seemed to be having issues with the JB and Google Maps. Didn't have any crashes with ICS.

Just wanted to say that many one s owners are experiencing the same problem.
Sent from my HTC One XL