HTC One S doesn't connect to WiFi in Cyanogenmod 10.2 20131115-NIGHTLY - HTC One S

Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-

Related

Team EOS issue

Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....

[Q] Here's a head scratcher! CM10 CWM problem?

I was happily running along with my GT2 10.1 5113 using CM10, updating nightlies, all is well. Then I put the CM 10.1 unofficial, that went well, was using it and put the 12/09 version on, that went well also. However I decided I didn't like it and wanted to go back to CM10. I had a back up that I made in CWM with the 12/08 nightly and had begun restoring it when an error came up stopping the restore, only said file error restore can't continue. OK, that kinda blows chunks cause I know my rom just got hammered. Tried to restart, boot loop. Got back into recovery re flashed the CM 10.1, trying to save my data, bootloop. Got back in recovery and wiped data re flashed, bootloop. On an act of desparation I flashed the 12/08 nightly and, viola she lit up and booted to the setup screen.
Set it all back up and updated to the next nightly, 12/10 and I'll be danged, bootloop. Went back to recovery re-flashed the 12/08 nightly and all went well. No data loss just worked fine.
Bottom line I can't get anything but the 12/08 nightly to boot up. I even flashed stock with Odin, that bootlooped too! So I'm stumped.
It boots into the 12/08 nightly just fine and that's it.
I know this is wordy, but I wanted to make a thorough explanation. I feel this is related to the CWM error, but I have no idea where to go from here.
Anybody got a suggestion? All help is greatly appreciated.
I think cm10 installs jelly bean on your system. and switching back to an older version will cause the bootloop. that's what i believed happened to me when I installed cm10 by mistake instead of cm9 which is what i wanted. it took me several tries with odin and the stock rom to be able to go back.
I think the key is when you have cm10 installed then you need to enable the "usb debugging" in the developers section. that is probably what is stopping you from switching back to an earlier version or a new version or the stock rom using odin.
anyway that's how I was able to switch back to stock.
I think the reason you can´t restore CM10 is the fact that Android 4.2 introduces muti-users management. Thus, the system do not store in /sdcard/ any longer, but in /sdcard/0/ (for the first user). Since you still have a 4.1 recovery version, it doesn´t find the backups files any more. A solution is to move your sdcard data from /sdcard/0/ to /sdcard/ before restoring your backup.
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Einril said:
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Click to expand...
Click to collapse
Bingo! That worked, 12/11 worked. I had no idea that was happening. I made all the file changes actually because I wound up with sdcard/0/0/0 from all the flashing back and forth, that was funny. All is normal now thanks!
Sent from my GT-P5110 using xda premium

[Q] Broken wifi in cm10 based roms

So here is the deal, I am new to the phone and getting used to the flashing process but I am not a newb to all of this. When i flash over to a cm10 based rom my wifi just does not turn on at all. I have searched and searched and found nothing. Any ideas? Do i need to flash a radio(which i tried, i mean a specific one) and yes i tried the ones that said for JB.
Also it works just fine in stock based roms so its just a cm 10 thing.
I have wiped it all and redownloaded it all, multiple roms and everything so I am at a dead end. Thanks for the help
Can't connect or WiFi never turns on? Cm10 and 2wire routers don't like to connect to each other I know that much

XT925 - Wifi not working after Custom Rom install (but bluetooth works?)

So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
di3zelherbert said:
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
Click to expand...
Click to collapse
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
koftheworld said:
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
The first time, no. I thought I may have installed 4.4 incorrectly so after installing 10.2 i tried flashing 4.4 again, but I did wipe the caches, system, data and dalvik caches the second time going back after reading in this forum how to flash over a custom rom. But then seeing that the bugs were still there, i wiped again and went back to 10.2 and I've been there for a day now.
Missed Wifi
I'm facing the same trouble , same conditions.
Solved
zirig said:
I'm facing the same trouble , same conditions.
Click to expand...
Click to collapse
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
zirig said:
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
Click to expand...
Click to collapse
That worked! Thank you!

[Q] Losing Network Constantly - Latest CM Nightly Build

Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima
Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.

Categories

Resources