Database Develop

Weak signal after radio and ROM flash

After the most recent stock update that added Sense 3 I started having intermittent radio problems. I had always been on stock and never fiddled with the firmware, radio, anything like that. The radio would randomly disconnect from the network and stay disconnected for a while, or I could get it back faster if I rebooted the phone or cycled flight mode. Using data often acted as a catalyst for the problem and I could reduce occurrences by using wifi when I'm at home. Total annoyance. I decided to try fixing it myself and I've found a lot of useful information here.
I first installed a couple different ROMs and found that after booting, there was no signal, so it was probably the radio. I had HBOOT 2.0 so I had to downgrade, use Revolutionary to get S-OFF, then start working with different radio versions. I haven't had any luck since.
Current setup:
Bought unbranded and unlocked from the UK. 900/1700/2100 model
Revolutionary HBOOT-6.13.1002
Baseband: 20.4802.30.0882U_3882.10.08.28_M
ROM: Virtuous Quattro RC2 (Android 4.0.2)
Network: 3 Sweden (UMTS 900/1200 network)
I've also had the same problem running Cyanogen 7.1 and Android Revolution HD 2.1.3. I had high hopes for ARHD since it said it specifically was designed for the radio I've flashed. I actually even went through and tried every single radio release from Gingerbread for the IncS. Same problem on all.
Strictly speaking it's not actually a no-signal problem, it's a very weak/malfunctioning signal problem. When I do a network scan I usually only see two of the three GSM networks here and most if not all 3G networks are missing. The few times my home network has actually shown up in the network scan list, I can't register on it. I get the "Temporarily unable to register on this network. Try again later." message.
I hope I've done enough searching and effort on my own here before posting. Needless to say I'll be grateful for any help I can get here. After many hours of reading, flashing, rebooting, reflashing, rinse and repeat, I'm looking for an end to this!

mroach said:
After the most recent stock update that added Sense 3 I started having intermittent radio problems. I had always been on stock and never fiddled with the firmware, radio, anything like that. The radio would randomly disconnect from the network and stay disconnected for a while, or I could get it back faster if I rebooted the phone or cycled flight mode. Using data often acted as a catalyst for the problem and I could reduce occurrences by using wifi when I'm at home. Total annoyance. I decided to try fixing it myself and I've found a lot of useful information here.
I first installed a couple different ROMs and found that after booting, there was no signal, so it was probably the radio. I had HBOOT 2.0 so I had to downgrade, use Revolutionary to get S-OFF, then start working with different radio versions. I haven't had any luck since.
Current setup:
Bought unbranded and unlocked from the UK. 900/1700/2100 model
Revolutionary HBOOT-6.13.1002
Baseband: 20.4802.30.0882U_3882.10.08.28_M
ROM: Virtuous Quattro RC2 (Android 4.0.2)
Network: 3 Sweden (UMTS 900/1200 network)
I've also had the same problem running Cyanogen 7.1 and Android Revolution HD 2.1.3. I had high hopes for ARHD since it said it specifically was designed for the radio I've flashed. I actually even went through and tried every single radio release from Gingerbread for the IncS. Same problem on all.
Strictly speaking it's not actually a no-signal problem, it's a very weak/malfunctioning signal problem. When I do a network scan I usually only see two of the three GSM networks here and most if not all 3G networks are missing. The few times my home network has actually shown up in the network scan list, I can't register on it. I get the "Temporarily unable to register on this network. Try again later." message.
I hope I've done enough searching and effort on my own here before posting. Needless to say I'll be grateful for any help I can get here. After many hours of reading, flashing, rebooting, reflashing, rinse and repeat, I'm looking for an end to this!
Click to expand...
Click to collapse
Remember to close your back cover after each radio flash so you will get much accurate result.
Sent from my HTC Incredible S using Tapatalk

nsg86 said:
Remember to close your back cover after each radio flash so you will get much accurate result.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
wow..i was having the same problem. totally forgot about the antenna in the back cover. i was going nuts flashing different radios wondering why i was getting only edge. i feel stupid. thanks

I had no idea the back cover made any difference at all. Thank you for pointing that out to me! I was seriously about to go buy an iPhone or something, but I remembered I loathe the keyboard in iOS
I'm all good now! Running radio .28_M with ICS and things are as they should be. At least throughout all this hassle I got my radio upgraded to a hopefully less-crashy version and I got some ICS up and running
Cheers guys!

[Q] My IncS completely disconnects, often!

First of all, let me start of what I've tried doing, in order.
New SIM-card, factory reset, unlock + root, custom ICS (VirtousQuattro).
None of the above solved my problem, it still persists! The problem is, the phone disconnects completely from the network (no bars) and I can't manually search for a new provider due "active package transmission" or something like that, it stays disconnected for 1-3 minutes and then reconnects. It happens fairly often, like once for every 5 times I try using the phone. I haven't noticed the problem when being connected to a WiFi, so I'd assume the problem is related to an issue between the phone and the network.
Has anybody else had this problem? Any idea how to solve it?

Have you tried flashing a new Radio? I can't see how that would differ from flashing a custom ROM, but might be worth a shot?

CyanideJack said:
Have you tried flashing a new Radio? I can't see how that would differ from flashing a custom ROM, but might be worth a shot?
Click to expand...
Click to collapse
I haven't tried that, I might in a couple of days if nobody has any other solution though.. I've had the problem for a couple of weeks so I'm kind of used to it!

Naforcee said:
I haven't tried that, I might in a couple of days if nobody has any other solution though.. I've had the problem for a couple of weeks so I'm kind of used to it!
Click to expand...
Click to collapse
You need s-off to flash a new radio m8.
Sent from my Incredible S using XDA App

Adde79 said:
You need s-off to flash a new radio m8.
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
So much for being "unlocked". Also, hey mate

Yes Naforcee, I have exactly the same problem. And it never happens while using wifi as you said.
It started immediately after I updated to Sense 3 / Android 2.3.5 from HTC.

What was the version of Android in your previous Rom? I had issues when I was on Froyo and went to Gingerbread without flashing a new radio.
Sent from my HTC Incredible S using XDA App

keiichi_san said:
What was the version of Android in your previous Rom? I had issues when I was on Froyo and went to Gingerbread without flashing a new radio.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
I had 2.3.5 earlier, so that'd be GB. Same problems with ICS now though =/

Antenna in the back cover got busted?
Maybe the contacts aren't touching enough?

fallenwout said:
Antenna in the back cover got busted?
Maybe the contacts aren't touching enough?
Click to expand...
Click to collapse
Don't think it's a physical problem, I have perfect connection and it just dies out for about 2 min until it reconnects, and I can't search for network when it's down due to active packet transfer..

Could try a new SIM card. Might not fix it, but worth a shot - I've seen this posted as a fix for other people.
I used to have this problem on certain radios on the Desire Z, after flashing around a bunch of radios to try all of them. Stuck with one and it went away, so it was software for me.

kaijura said:
Could try a new SIM card. Might not fix it, but worth a shot - I've seen this posted as a fix for other people.
I used to have this problem on certain radios on the Desire Z, after flashing around a bunch of radios to try all of them. Stuck with one and it went away, so it was software for me.
Click to expand...
Click to collapse
New SIM was my first try to fix it, it didn't work.. I guess radio is the only solution left!

Naforcee said:
New SIM was my first try to fix it, it didn't work.. I guess radio is the only solution left!
Click to expand...
Click to collapse
What version radio do you have installed?

Naforcee said:
First of all, let me start of what I've tried doing, in order.
New SIM-card, factory reset, unlock + root, custom ICS (VirtousQuattro).
None of the above solved my problem, it still persists! The problem is, the phone disconnects completely from the network (no bars) and I can't manually search for a new provider due "active package transmission" or something like that, it stays disconnected for 1-3 minutes and then reconnects. It happens fairly often, like once for every 5 times I try using the phone. I haven't noticed the problem when being connected to a WiFi, so I'd assume the problem is related to an issue between the phone and the network.
Has anybody else had this problem? Any idea how to solve it?
Click to expand...
Click to collapse
I was sick and tired of these problems, and then i made s-off, rooted and isntalled custom ROM and changed Radio 20.4802.30.0822U_3822.10.08.28_M and now everything is good

He has: 3822.10.08.28_M
Sent from my Incredible S using XDA App

Nonverbose said:
What version radio do you have installed?
Click to expand...
Click to collapse
He has: 3822.10.08.28_M
Sent from my Incredible S using XDA App

Naforcee said:
First of all, let me start of what I've tried doing, in order.
New SIM-card, factory reset, unlock + root, custom ICS (VirtousQuattro).
None of the above solved my problem, it still persists! The problem is, the phone disconnects completely from the network (no bars) and I can't manually search for a new provider due "active package transmission" or something like that, it stays disconnected for 1-3 minutes and then reconnects. It happens fairly often, like once for every 5 times I try using the phone. I haven't noticed the problem when being connected to a WiFi, so I'd assume the problem is related to an issue between the phone and the network.
Has anybody else had this problem? Any idea how to solve it?
Click to expand...
Click to collapse
Try flashing this radio http://forum.xda-developers.com/showthread.php?t=1471861 using the ADB method. If that doesn't help I recommend doing a full wipe and reinstalling the ROM. There are a lot of different custom ROMs for IncS which can be found at http://forum.xda-developers.com/showthread.php?t=1136463
I personally like Niks ROM and Android Revolution HD.

Looks like rom installation issue.

My son's Inc-S having a similar problem to the OP, but more severe. A couple of weeks ago he entered airplane mode with all behaving normally, but since exiting airplane mode at the end of the flight he hasn't been able to register on the network (voice or data). We've tried:
fiddling with all the network settings
change sims (all sims work on my Inc2, none work on his IncS)
cleaning the antenna connections
reboot
factory reset
flashing new ROM (Android Revolution HD 2.3.0)
flashing new radio (3805.10.03.29_M)
So far, no satisfaction. We're still seeing no bars of reception (with an X) in the notification area, and don't have the option to manually or automatically register with any network operator (although several occasionally show up as options under "Search Networks"). We usually get the error message, "Unable to search for network while packet connection is active" when trying to select a network. Funny thing is, mobile network data has been shut off on his phone for the past month so the packet connection is definitely not active (wifi is on). Based on a network signal analyzer app, the phone is receiving the same mobile network signal as mine (-65 to -70 db) when they are side-by-side, so the problem does not appear to be in the antenna. The phone works just fine using wifi but is useless as a phone.
Any ideas about what to try next?

scrinch said:
My son's Inc-S having a similar problem to the OP, but more severe. A couple of weeks ago he entered airplane mode with all behaving normally, but since exiting airplane mode at the end of the flight he hasn't been able to register on the network (voice or data). We've tried:
fiddling with all the network settings
change sims (all sims work on my Inc2, none work on his IncS)
cleaning the antenna connections
reboot
factory reset
flashing new ROM (Android Revolution HD 2.3.0)
flashing new radio (3805.10.03.29_M)
So far, no satisfaction. We're still seeing no bars of reception (with an X) in the notification area, and don't have the option to manually or automatically register with any network operator (although several occasionally show up as options under "Search Networks"). We usually get the error message, "Unable to search for network while packet connection is active" when trying to select a network. Funny thing is, mobile network data has been shut off on his phone for the past month so the packet connection is definitely not active (wifi is on). Based on a network signal analyzer app, the phone is receiving the same mobile network signal as mine (-65 to -70 db) when they are side-by-side, so the problem does not appear to be in the antenna. The phone works just fine using wifi but is useless as a phone.
Any ideas about what to try next?
Click to expand...
Click to collapse
Probably a RIL-Radio communication issue. Recommended radio is the newer 3822.01.08.14_M radio, so maybe you should try that.

[Q] Lost stable WiFi after updates, can't get it back

Hello everyone! This is my 3rd day of tinkering with the phone and since I can't handle it I'm asking for help. I'm a noob who read a lot, tried and apparently messed up.
I bought a new HTC One from T-Mobile in Poland, branded with CID T-MOB101 and Hboot 1.44. Everything worked fine but the phone still had Android 4.1.2 and no update available. I decided to get rid of the brand and get international stock version to be able to receive OTAs. I unlocked bootloader with htcdev.com, installed TWRP 2.6.3.3, achieved s-off using revone, changed CID to HTC___001 and used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed . My phone did not see OTA so I applied updates manually in following order:
OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7vl8dqsvls0h1t0.zip
OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
OTA M7 UL JB 50 S HTC Europe 2.24.401.8-2.24.401.1 Release 331108tottoh71qygw07hf
OTA M7 UL JB43 SENSE55 MR HTC Europe 3.62.401.1-2.24.401.8 Release 338160gxmo5sd9337kadux
After each OTA i tried to look for updates in phone's settings and found only two little updates (few MBs) that did not lead to bigger ones; I believe it was after first and third OTA.
After all this I started having WiFi issues. The phone stayed connected to my WiFi the whole time but after few minutes pages would not load, games would not connect. Resetting the connection would help for another few minutes (or less). Factory reset seemed to help a bit, the WiFi was able to keep the connection yet it 'paused' from time to time. By 'pause' I mean lose the connection for a second and regain right after, e.g. I could connect to games such as Hay Day, but after a ~minute I would lose the connection and have to reconnect (in game, without touching phone's settings) and redo last X seconds of game.
Because of that I went and applied ARHD 31.6 custom rom and hoped for the best. The situation remained the same so I flashed ARHD 41.0, yet the problem still remains.
In the end I downgraded my Hboot so it goes back to 1.44 and used the RUU I used the first time, after that I changed CID back to T-MOB101 and applied my full backup I saved by booting (prior to flashing) TWRP before I changed anything in the phone.
I did full wipe every time I changed the system and I did factory reset multiple times.
As of now I am on my backup with
Android 4.1.2
Version 1.29.111.16 CL175271 release-keys
Radio 4A.13.3231.27_10.31.1131.05L
and my WiFi is unstable. I can browse internet, watch YouTube or do things like that, yet I cant play games requiring constant internet connection, such as Hay Day.
So my question is: What do I do to get it to work as it used to at the beginning? I would prefer having the newest Android version, but at this point I simply need a working phone so if anyone has a solution that would work on my current system or by flashing a new one I will be extremely grateful.

I've been having the same issue. Thought it was just me because I've looked for a solution ever since the Jelly Bean update. Mine is a Sprint One and worked perfect with the original firmware. Once updated wifi connected and would randomly drop for a few seconds and reconnect. I've noticed it's router specific. I had a Linksys wrt160 that had a problem at home, but at the office the Cisco E2500 works fine. I swapped my home out with an Asus RT-N12 that has the problem too, but not as bad. Was hoping KitKat would fix the issue, but it didn't. I've worked with HTC support for a while and they said the new rom's have updated wifi drivers so there must be some compatibility issue with it.
Think the best bet is a custom rom that has all the new kitkat features but the old wifi (and BT since the new one doesn't load the contacts in my car) drivers. Someday, I'll take the time to figure out making my own rom.

same boat
1sae said:
I've been having the same issue. Thought it was just me because I've looked for a solution ever since the Jelly Bean update. Mine is a Sprint One and worked perfect with the original firmware. Once updated wifi connected and would randomly drop for a few seconds and reconnect. I've noticed it's router specific. I had a Linksys wrt160 that had a problem at home, but at the office the Cisco E2500 works fine. I swapped my home out with an Asus RT-N12 that has the problem too, but not as bad. Was hoping KitKat would fix the issue, but it didn't. I've worked with HTC support for a while and they said the new rom's have updated wifi drivers so there must be some compatibility issue with it.
Think the best bet is a custom rom that has all the new kitkat features but the old wifi (and BT since the new one doesn't load the contacts in my car) drivers. Someday, I'll take the time to figure out making my own rom.
Click to expand...
Click to collapse
I have tried about every Rom, Firmware, RUU out there and cant get mine to work

robbie09 said:
I have tried about every Rom, Firmware, RUU out there and cant get mine to work
Click to expand...
Click to collapse
For now I'd recommend contacting HTC support and create a ticket so they know this problem is more widespread. That way all the new roms out there would have a working WIFI driver.

thanks
1sae said:
For now I'd recommend contacting HTC support and create a ticket so they know this problem is more widespread. That way all the new roms out there would have a working WIFI driver.
Click to expand...
Click to collapse
that's exactly what ive done on 2 different occasions, the last time this evening and they advised i exchange with my carrier

robbie09 said:
that's exactly what ive done on 2 different occasions, the last time this evening and they advised i exchange with my carrier
Click to expand...
Click to collapse
That's odd, when the first tier support couldn't figure it out they opened a ticket for me with higher level techs and they had me save a bunch of capture logs when the drops happen to email them. The carrier would be useless on this.

1sae said:
That's odd, when the first tier support couldn't figure it out they opened a ticket for me with higher level techs and they had me save a bunch of capture logs when the drops happen to email them. The carrier would be useless on this.
Click to expand...
Click to collapse
I sent them a bunch of logcats as well and they told me to exchange my phone with my carrier
Sent from my HTC One using XDA Premium 4 mobile app

Frustrations with MMS on T-Mobile (ATT model, black)

An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.

Miguel_Lancaster said:
An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.
Click to expand...
Click to collapse
When I was running the T-Mobile 4.4.2 with Sense 5.5 I had issues receiving MMS when connected to WiFi. They would always fail, I would have to disconnect from WiFi and then the MMS would automatically receive. But, since the update to the T-Mobile 4.4.2 Sense 6.0 OTA rom, all the MMS now work as normal whether I'm connected to WiFi or not.
I do know that the SMS app called ChompSMS has a specific T-Mobile setting that will temporarily switch from WiFi to cellular to send/receive MMS and back again. Maybe you can try that if you don't want to run the stock ROM.

@Miguel_Lancaster
Try upgrading to the latest tmous firmware. 5.14.531.1 ,might help. I will include the latest tmous radio and radio config. I have an att phone/sim, but i'm running gpe firmware and rom. I hope this helps.

It had seemed when I first got the device up and running that everything was fine with MMS (that was using 4.4.2, Sense 6.0), but either after a certain number of messages, or while in certain areas I would have to turn off WiFi to be able to send MMS.
That's why I tried downgrading to 4.3 with the alternate version of Android Revolution HD (essentially a tweaked version of the stock HTC ROM). What I find odd about the two version of that ROM (30.6 vs. 71.1) is that the installer for one includes an model selection screen and the other treats them all alike. 30.6 allows me to choose between International, ATT/Developer, Sprint, T-Mobile, etc.
Initially I chose ATT/Dev as that's the hardware model of my HTC One and wasn't keen to deal with a soft-brick. As stated in my first post, this seemed promising initially but shortly after ran into the same bug. I flashed one more time and tried using the 'T-Mobile' model selection during install. This has proven the most reliable method for me thus far. I suppose it would have to do with the radio being flashed between versions? It's curious to me that a similar option is not included in the other ROM version -- something I wanted to address in that ROM's development thread, but am prohibited from doing currently due to my post count.
Anyhow, 4.3 with Sense 5.5 seems to finally be working for now. Android 4.4.2 and Sense 6.0 did have some some aesthetic differences that I preferred, in addition to seeming marginally faster. I'll deal with an older version of the OS though if it means my phone functions properly.
Thank you both for your replies.
One thing that may be worth mentioning is that I've yet to enable Group MMS in my messenger settings this go-around. I suspect that its coincidental, but I'm reluctant to see what happens if I do enable it.
Maybe I'll try again with 4.4.2 in the future, but all this flashing, re-flashing, and settings tweaking becomes pretty tedious. In relation to that point: Does anyone have any experience with the built in HTC/Google app backup/sync. For some reason I've never really trusted any all-in-one solutions to be reliable, especially between ROMs or Android versions. Perhaps I should trust them more?

P.S.
CID Getter app lists my CID as CWS_001 --
don't know why I never bothered checking that until now. Could changing it to TMO_001 be helpful at all or does it not matter?

I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.

Miguel_Lancaster said:
I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.
Click to expand...
Click to collapse
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551

alray said:
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551
Click to expand...
Click to collapse
Yup, it's a shame that such a well documented bug has gone unfixed.
Good to finally have figured out my problem, only took a few days of tinkering to finally narrow it down to ABP and be able to make a relevant search to back up my hunch.

"Unfortunately WiFi has stopped working" (Plentiful details included)

So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls

Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.

esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.

I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760

Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help