I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?
tried this ?
WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks
bump
Surely, there's someone out there that can help?
kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.
Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?
Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.
Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.
Is OpenSense considered a "Sense ROM?"
http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.
I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)
so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!
wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings
Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp
Hello,
I can not find similar topic in the HELP forum so let me start it (at least for new users of XDA forum).
At the very beginning I would like to thank bilal_liberty for all his work given for Liberty ROM. Same time I want to thank all participants of his success - all developers, testers and helpers for their time and patience..
Now, my problems:
1) I can not run WIFI hotspot. The icon is working, working and... doing nothing.
2) From time to time I can not run WIFI connection in my home. Of course everything is "ON", I tried to restart the phone, turn of the data transfers and some other tricks - the connection was working just after installing the ROM, but it is a lottery.
3) I have an issue with memory: I can't see the "SDCARD" memory - only when in TWRP mode, after mounting the SDCARD drive. When connecting in normal mode through USB - I can see only about 2 GB.
Is there any solution for those problems?
HTC One S(4), s-off, TWRP 2.7.0.1, hboot 2.15 (I don't believe 2.16 will change it but "if" - I'll upgrade, of course...
Thanks for any help.
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
ChrisAr said:
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
Click to expand...
Click to collapse
Hi ChrisAr.
Thanks for your reply.
I'm not scared with the hboot change I just couldn't see any reason to change it if the ROM (at all) was working. Now I see that my issues can be caused by this tinny missing so I'll update hboot after working hours
I'll update this thread after the upgrade.
Thanks for help.
No problem, glad to help
Be aware though. After upgrading hboot(following carefully MaximusHD's instructions), you must reflash recovery with 2.16 hboot support which can be found here -> mdmower.cmphys.com/twrp-ville/ (Cannot post full link due to post restrictions)
Just be sure to flash the one under /data/media storage (HBOOT 2.16.0000 only) header.
:good:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
xklonik said:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
Click to expand...
Click to collapse
Sorry I didn't see your post earlier. I was away on vacation.
In that time, sixth sense got 2.15 support.. Irony
Not sure why you had that problem. Maybe you had to perform a full wipe (from the recovery options) to force re-partitioning. Old hboot had created different partitions on phone's memory and you had to create them from scratch, for the new hboot.
Also I assume you know that when you change hboot, you have to re-install also everything from scratch since everything installs according to hboot. If you just upgraded hboot, it would not work as expected if you just left the old installation there.
Anyway, glad to hear this worked for you and that you also found a workaround with "adb push" by your self. Good job :good:
Enjoy this awesome ROM. (Just flashed it too this morning) :highfive:
yeas... actually I did the instalation agait too..
and unfortunately wifi still wont work
btw. I'm always performing full wipe, so have no idea what happened then..nevertheless, I've full space and rest of toys, just without wifi and hot spot, what in fact, eliminates this ROM.. :/
unfortunately 2) no one answered my mail regarding any ROM supporting all One S features (camera, wifi, hotspot, BT) and Sense 6 on newest kitkat... so I'm still in the oblivion.. waiting for some light..
just to confirm - build 106 - after changing 1.35a.32.45.27, WCNSS, ADSP, wifi & hotspot still not working,
what is interesting, previously the wifi icon only blinked - currently "scanning" & "disconnecting" subtitles are visible under this icon...
also previously just right after installing I could connect to my network and wifi was turned off just after authorisation and few next screens..
now with new 1.35a.32.45.27, WCNSS, ADSP I can not join at all..
I've been following your posts on the development thread.
This issue is really weird...I wanted to write about different WCNSS versions (some people flashed it from the Viper ROM) but I couldn't post due to post count restriction. Anyway, bilal noticed that too in his recent post. I have flashed everything you flashed and only reverted to radio 1.20 but with hsdpa fix (it is included in one of the flashable radios, don't know if it's included in the version you downloaded)
WiFi is working perfectly for me. Only this "keep always on" issue.
Hi everyone,
First off thanks to bilal for his amazing work, second I hope I am not off topic since this is a help thread for Liberty SixthSense.
After reading the entire development thread on this ROM, I still can't figure out how to install it on hboot2.15. I get a feeling that there is a different way to install this rom on 2.15, or I'm missing something.
So yes, I download the zips of r106 version and the radio 1.20 version. But afterwards I just do as I would do with any other ROM? I mean full wipe, dalvik cache wipe, recovery cache wipe, and then install from zips? and if so, which should be instlled first, the radio or the whole rom?
Mindue, I am noob at this, so I don't understand everything I've read so far and this would be the only way I know to install a rom.:silly:
quick checklist:
- S4
- recovery TWRP 2.7.1.0 the one from Cyanogenmod 11 since I'm on this rom now.
- S-OFF
- hboot 2.15
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
ChrisAr said:
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
Click to expand...
Click to collapse
Thank you! I will try and see where it leads me, if it fails I believe I can put back the cm11 right ? even with the new flashed radio.
As far as I know, there are no problems with cm11 and radios...but even if there is, you can always flash an older radio...but 1.20 is the recommended for our device in general.
Glad I could help :good:
Ok, so I try to flash the radio (before full wipe and rom flash) but it fails, I get the followings:
checking for MD5 file > no MD5 file found
verifying zip signature > failed
any ideas to where I went wrong?
LATER EDIT: scratch that, the problem was the 'ZIP signature files verification' box should have been unticked and thus no more md5 file required. --> radio flashed! now on 1.20. later I will try to flash the liberty rom. update afterwards
PS. found this in another thread:
"an md5 is not "added to a file", nor is it "a part of a file". An md5 is merely a hexadecimal readout of the contents of that file.
Here's how it works: A file is created, in our case it is a zip file. The creator or publisher of that file uses an md5 generator to generate the md5sum, which as I said before, is just a numerical readout (like a fingerprint) of the contents of that file. Now the end user has a tool to make sure that the file hasn't been compromised during a download or transfer. Using an md5 checker is a simple way to verify that the file is uncompromised. Input the md5 given by the publisher into an md5 checking app, then the app calculates the md5 of the file you've downloaded, if they match you know the file integrity is good."
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
ArcsONE said:
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
Click to expand...
Click to collapse
Glad to hear that.
I had also these random restarts, but they are gone now.
Enjoy
Still new here so can't post in the dev thread, but...
Installed the latest version (clean install), everything works solid. Hotspot works as before - have to turn it on, then reboot and Wi-Fi mostly works but occasionally needs restart to work. Other than that, everything is stable and quick, very happy with the ROM. As I primarily use 3G and don't rely on Wi-Fi as well as can use USB tethering instead of Wi-Fi hotspot, I'm not that annoyed by these issues.
However - on r107, I tried out the ElementalX 7.0 kernel as well but as I experienced issues with touch screen, I searched the thread and found a fix which turned out to be a special kernel. Therefore although the kernel in the ROM was updated and now there are no touch issues with the default kernel, the ElementalX kernel also needs updating. Really miss DT2W but a responsive touchscreen is more important to me.
Tried the kernel now after r111 install but the touch problem is still there so had to revert to default kernel.
I hope the kernel's developer sees this and can release an update :fingers-crossed:
no recent apps
I cant find the recent apps in this system
Problems
Hey guys, first post in this forum. I'm a total noob when it comes to rooting and roms and all this stuff, but if I didn't try it I would always be, so I tried this rom on my htc one s.
Several problems, I may have screwed up of course, I followed some tutorials, so I have this rom, but I am S-On, and my hboot is 2.15, I think that is what is causing me problems (SD card not recognized, meaning, no storage space, wifi problems, can't log in to google play).
But I can't get S-off, I've tried every single way, and something always goes wrong, I don't know what to do now, I think the solution would be to change to hboot 2.16, but I just can't do it, probably need to be S-off? No idea, would love to hear some feedback, I'll leave you with whatever it says on my bootloader.
TAMPERED
UNLOCKED
VLE PUT SHIP S-ON RL
HBOOT- 2.15.0000
RADIO - 1.15.50.05.29 (tried changing it, can't as well.)
OpenDSP - v31.1.0.45.0015
Plese help me guys, really don't know what to do, I think I might have accidentally deleted the stock Android.
Much thanks
Anyone else having problems with audio quality in calls? Any fix? I found liberty rom v2 on an italian forum, it says audio quality it's fixed in that, has anyone tried it?
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT - 2.16.0000
RADIO - 1.20.50.05.16
OpenDSP-v33.1.0.545.1128
eMMC-boot
After a tragedy with my S3, I'm having to limp along with my old One SV. Unfortunately I am having trouble getting this thing to keep a newer ROM. And before anyone says "turn s-off" I have S-Off already.
Booting to the boot menu it says:
moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-1.01.4444
RADIO-1.1250.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
Jan 16 2013, 01:26:39:-1
I've tried jellybean flashing
I tried the viper ROM (which gets stuck flashing unless I don't install all the google apps)
Post every flash, I turn the phone off and then power it back up. For a little while it'll say something "correctly" like that it's android 4.4.... buuuuut it is still the default wallpaper and goes back to saying android 4.0 and of course the bugging to update to a new stock android is still present as is the "out of storage space" error message....
I've tried updating the recovery (currently a somewhat buggy cwm where the screen is 1/8th offset half the time... v6.0.2.8) and that hasn't worked... Typing this out I decided to try flashing the recovery once more since when I first was doing it I apparently had S-ON... So I flashed the latest TWRP (3.0.1-0-k2_cl) and..... now it's bricked.... it won't boot normally nor will it boot into recovery mode, but I can get to the hboot menu.... HALP! lol
The final kicker to my scenario is that I'm on linux and don't have access to any Windows machines, but I do have heimdall and adb installed.
Okay... So because I was still able to get into the HBoot menu and then put it into the Fastboot menu with the USB cable connected I was able to flash a new recovery.
I got the TWRP 2.8.5.0 recovery from http://techerrata.com/browse/twrp2/k2_cl
I was able to install fastboot and adb thanks to http://forum.xda-developers.com/showthread.php?t=2638673
I re-tried flashing the Jelly Bean rom I had with the same result as before the bad recovery problem occurred... It boots up, but it's still Android 4.1, even though it is S-OFF-ed.... And that shouldn't be happening... I'm pulling the battery and rebooting after flashing so nothing should be overwritten... What gives?
Your best way to go:
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
As far as i remeber, there was no custom rom that was made for k2cl.
correct.. there is no custom rom for the boost variant.. there is a partition swapper changing the 4gb media with the 1gb internal storages.. romcleaner works to get rid of all the boost garbage.. twrp will fit your screen.. havent used cwm since my hero
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
I tried to get the RUU to work, but couldn't. I borrowed a friend's Windows laptop, installed adb and fastboot and it just would not connect or see my phone in the RUU. I even tried forcing the driver to be installed correctly, which never worked for some reason.
I ended up installing Link2SD and setting up a 16gb partition for apps. So at least it's not complaining about being out of space anymore. It is still wanting me to download the OTA update. Not the end of the world.
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Hathalud said:
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
Click to expand...
Click to collapse
Hm,
From the Viper Rom thread:
Modding.MyMind said:
THE VIPERSV ROM IS NOT FOR BOOST MOBILE (K2_CL) USERS!!!!!!!!
This is what could happen to you if you fail to follow instructions!
Click to expand...
Click to collapse
xpirt said:
This Rom is not compatible with Boost/Cricket variants, which model have you flashed it on?
xpirt
Click to expand...
Click to collapse
Hathalud said:
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Click to expand...
Click to collapse
This was a permission bug from updater script, when i remember.
Wiper is some wifi or network location service. If you don't need it, rename it or delete it.