Greetings guys. I'll skip the bs and tell you what my problem is. I just rooted 2.20 like everyone else and everything has been mostly fine but when I flash any JB ROM my WiFi doesn't work. I've tried flashing different stock ROMs in which the WiFi does work then wiping from recovery and reflashing jb but no dice. I've also tried fixing permissions and every other solution I've found via search.
Making a thread is a last resort as I know you guys are being flooded but any help would be much appreciated.
Try the 10/25 experimental nightlies CM10. Have heard this fixed wifi issues with most people
Any jb Rom? Are you having the same issue on aokp or miui
Sent from my HTC One XL using xda app-developers app
Does it say error? When I'm on jb I have to try to connect it like fifteen times than it finally does
Sorry about the delayed response. Was posting from work.
area51avenger said:
Try the 10/25 experimental nightlies CM10. Have heard this fixed wifi issues with most people
Click to expand...
Click to collapse
Ill try that out. Thanks
absolutelygrim said:
Any jb Rom? Are you having the same issue on aokp or miui
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Honestly I haven't tried those yet. That was probably gonna be my next step. I was just set on jb because you know, butter.
omario8484 said:
Does it say error? When I'm on jb I have to try to connect it like fifteen times than it finally does
Click to expand...
Click to collapse
I don't get any errors. It just doesn't pick up my router. Although when I disable all security on the router it picks it up just fine. A totally unlocked router is out of the question though.
StarGuitar said:
Sorry about the delayed response. Was posting from work.
Ill try that out. Thanks
Honestly I haven't tried those yet. That was probably gonna be my next step. I was just set on jb because you know, butter.
I don't get any errors. It just doesn't pick up my router. Although when I disable all security on the router it picks it up just fine. A totally unlocked router is out of the question though.
Click to expand...
Click to collapse
Are you sure you don't have SSID disabled?
try it using WPA/WPA2 security
absolutelygrim said:
Are you sure you don't have SSID disabled?
try it using WPA/WPA2 security
Click to expand...
Click to collapse
Yeah. I spent a good long while tinkering with my router and even factory reset it as well as tried every security type, changing ssid, hiding it, the works. My old iPhone picks up the router just fine, as does my laptop. This leads me to believe the problem lies with my phones ROM. I'm gonna try to flash a couple of the ROMs suggested to me once my phone charges.
So Ive flashed the experimental CM nightly released on the 25, MIUI v4, AOSP Nocturnal Dirty Rom 4.1 as well as AOKP JellyBean. Still nothing. Im sure I'm forgetting a couple too.
Don't really know what else I can do at this point. Ive tried different gapps packages too just in case that could be it. I might have to abandon all hope of running project butter right now. :crying:
Damn shame too, I really really like AOKP JB
StarGuitar said:
So Ive flashed the experimental CM nightly released on the 25, MIUI v4, AOSP Nocturnal Dirty Rom 4.1 as well as AOKP JellyBean. Still nothing. Im sure I'm forgetting a couple too.
Don't really know what else I can do at this point. Ive tried different gapps packages too just in case that could be it. I might have to abandon all hope of running project butter right now. :crying:
Damn shame too, I really really like AOKP JB
Click to expand...
Click to collapse
Are you on 2.20 firmware?
Did you wipe System and Factory Reset, then flash the Boot.img, then the ROM?
absolutelygrim said:
Are you on 2.20 firmware?
Did you wipe System and Factory Reset, then flash the Boot.img, then the ROM?
Click to expand...
Click to collapse
Yeah, that's the standard protocol Ive been taking with every ROM I flash, even ones of the same kernal type. Reboot to recovery>Factory reset>flash boot.img for that ROM>reboot to recovery and install.
I did a complete wipe system and everything just now and still nothing.
StarGuitar said:
Yeah, that's the standard protocol Ive been taking with every ROM I flash, even ones of the same kernal type. Reboot to recovery>Factory reset>flash boot.img for that ROM>reboot to recovery and install.
I did a complete wipe system and everything just now and still nothing.
Click to expand...
Click to collapse
And while on JB your phone doesn't see the router, or just unable to connect?
absolutelygrim said:
And while on JB your phone doesn't see the router, or just unable to connect?
Click to expand...
Click to collapse
It doesn't recognize it at all. Unless I completely disable any kind WPA/WPA 2 security. Back on stock unrooted Sense it would pick it up just fine though.
StarGuitar said:
It doesn't recognize it at all. Unless I completely disable any kind WPA/WPA 2 security. Back on stock unrooted Sense it would pick it up just fine though.
Click to expand...
Click to collapse
that sounds like a legit issue, you should probably report that to h8rift in the cm10 thread and see if anyone else has the issue.
out of curiosity what type/brand of router do you have ?
Update: Now running Cleanrom and everything seems to be working properly. I'm gonna stick with it for a little while until I can figure out how to run JB with wifi.
Crappyvate said:
that sounds like a legit issue, you should probably report that to h8rift in the cm10 thread and see if anyone else has the issue.
out of curiosity what type/brand of router do you have ?
Click to expand...
Click to collapse
That's a good idea for sure, I'll do that.
My router is a D-Link.
StarGuitar said:
Update: Now running Cleanrom and everything seems to be working properly. I'm gonna stick with it for a little while until I can figure out how to run JB with wifi.
That's a good idea for sure, I'll do that.
My router is a D-Link.
Click to expand...
Click to collapse
It probably won't help.. But have you tried updating the firmware?
I had an old D-Link and wifi worked fine on JB based ROMs for me.
a WBR-2310A to be exact
I've had the same issue in every aosp ROMs however on my phone i do get the WiFi to work. It takes me a while but I eventually get it. What I do I turn WiFi on and off, leave it off for a minute or so, re start my phone, after phone starts I turn WiFi on and most of the times it does it, you have to have patience
Sent from my One X using xda premium
Depending on ROM an kernel, WiFi scan intervals are up to 5 minutes apart.
Just saying.
WR
Sent from my One X
Related
hello,
i've been trying to get my mt4gs to turn wifi on in ics. when i turn it on it says, "turning on" but just goes back to "off". i tried turning it on via settings and via the panel. i do a full wipe every install -reset data, clear cache, wipe dalvik cache. also not sure if it's related adb cannot detect device when booted but works fine in recovery when in ics.
i've read and tried the various .zip files for various radio/kernel posted by football but still no go. i may be overlooking a step when flashing but here is my device info:
CWM Recovery version 5.5.0.4 also used 5.0.2.7
Baseband: 11.59.3504.00U_11.16.3504.20_2
HBOOT: Unlocked
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
RADIO-11.16.3504.20_4
Nov 21 2011
it works using gingerbread - tried OTA Stock, as well as bulletproof and it connects ok, but i need to turn wifi off first if i need to reboot otherwise i get the same issue, wifi won't turn on.
sorry for the long post, and forgive me if i missed an already existing thread. thanks for reading. any help is greatly appreciated.
well what rom are you using
I had the same problem with certain ROMs. Sometimes it would even say instead of switching back to off it would just say error. I used Dark Raider for Vivid and had that problem. I did everything and gave up. I downgraded my vivid to GB and rooted it. WiFi is an essential to me so I have to stay where I can switch it on. I hope there's a fix for this soon.
Sent from my HTC PH39100 using XDA
xmc wildchild22 said:
well what rom are you using
Click to expand...
Click to collapse
i tried your rom, |-ROM-|-4.0.4-|-AOKP-B38-|-CM9-|-6/9/12-|-BETA-|-WildchildIcE-v0.8-|-Nightlies-|
this,
[ROM]MyTouch4G Slide CyanogenMod 9 Alpha 4 (06/08) - 4.0.4
haven't tried anything else, unless you have any recommendations.
Chavisca1 said:
I had the same problem with certain ROMs. Sometimes it would even say instead of switching back to off it would just say error. I used Dark Raider for Vivid and had that problem. I did everything and gave up. I downgraded my vivid to GB and rooted it. WiFi is an essential to me so I have to stay where I can switch it on. I hope there's a fix for this soon.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
that's what i've encountered with ics, on gb, if i forget to turn wifi off before rebooting, my wifi will just say error. so i end up having to master reset too.
thanks for the reply.
when you flash a rom, are you restoring a backup in titanium or something?
i have never had this problem and i have tried every rom on xda and rootzwiki
I've had this happen too. I've fixed it by using fastboot and flashing the boot.img from the ROM or Kernel update that I had last installed. My phone is s-on so I have to do that everytime I apply a ROM or am update that has a boot.img in it.
xmc wildchild22 said:
when you flash a rom, are you restoring a backup in titanium or something?
Click to expand...
Click to collapse
no backup, i'm doing the install fresh
mattlowry said:
i have never had this problem and i have tried every rom on xda and rootzwiki
Click to expand...
Click to collapse
and i wish i was in your situation, since it looks like a mixed bag for mt4gs owner, some get it some don't.
txmtb said:
I've had this happen too. I've fixed it by using fastboot and flashing the boot.img from the ROM or Kernel update that I had last installed. My phone is s-on so I have to do that everytime I apply a ROM or am update that has a boot.img in it.
Click to expand...
Click to collapse
i tried doing that as well, my phone is S-OFF.
It was really frustrating for a while. It was the exact symptom you have described. I kept trying by flashing the kernel with fastboot, then flashing the ROM, and then flashing the kernel again with fastboot. It seemed that whenever I changed something, I had to use that sequence to get it to work again.
txmtb said:
It was really frustrating for a while. It was the exact symptom you have described. I kept trying by flashing the kernel with fastboot, then flashing the ROM, and then flashing the kernel again with fastboot. It seemed that whenever I changed something, I had to use that sequence to get it to work again.
Click to expand...
Click to collapse
i think i will try this method. i'll try with the previous roms i've posted first. i'll post my results later today.
Update
Wifi still no go using ICS. Is there a recommended radio version when using ICS ROMS?
Any stock GB Rom version wifi is ok. Using Bulletproof 1.1 works fine as well. Tried v0.9b WildchildICe and update4 of unofficial cm9 and still no wifi. Gonna stick with WildChildIce rom for now and try different Radio combinations.
d0nat0 said:
Wifi still no go using ICS. Is there a recommended radio version when using ICS ROMS?
Any stock GB Rom version wifi is ok. Using Bulletproof 1.1 works fine as well. Tried v0.9b WildchildICe and update4 of unofficial cm9 and still no wifi. Gonna stick with WildChildIce rom for now and try different Radio combinations.
Click to expand...
Click to collapse
U got the problem solved? I have exactly the same issue each damned time
When you flash, try mounting system and data in recovery prior to the flash. There used to be an error where wifi would hang as described if those were not mounted upon flashing. Couldn't hurt to try.
Hastily spouted for your befuddlement
tugushi said:
U got the problem solved? I have exactly the same issue each damned time
Click to expand...
Click to collapse
Try this. Go HERE. Go down to the 3rd post. Look for GanOptimizer & follow the instructions. No promises but sometimes that will lock it on in ICS.
Hey guys,
I've noticed in the last few days that my Wi-Fi just doesn't work any more. It won't even allow me to turn it on. When I go to the settings, it shows the option to turn Wi-Fi on, but it is greyed out now. I don't know what happened.
I'm using CM10 nightlies. I usually flash the new one every night and that's when I noticed this start happening. Since it started, I have tried flashing back to some older ones, even doing the full factory resets and cache wipes. No luck. Even after doing a fresh wipe, when the phone starts the initial google set up, the LTE isnt even working. It takes a few minutes for LTE to finally turn on, but the Wi-Fi has yet to.
Any suggestions as to what I should do?
Thanks
Znichols513 said:
Hey guys,
I've noticed in the last few days that my Wi-Fi just doesn't work any more. It won't even allow me to turn it on. When I go to the settings, it shows the option to turn Wi-Fi on, but it is greyed out now. I don't know what happened.
I'm using CM10 nightlies. I usually flash the new one every night and that's when I noticed this start happening. Since it started, I have tried flashing back to some older ones, even doing the full factory resets and cache wipes. No luck. Even after doing a fresh wipe, when the phone starts the initial google set up, the LTE isnt even working. It takes a few minutes for LTE to finally turn on, but the Wi-Fi has yet to.
Any suggestions as to what I should do?
Thanks
Click to expand...
Click to collapse
Go back to stock sense and try or. Sense rom ...have u dropped your phone at all
Reflash your stock rom
Sent from my LAVA S12 using xda app-developers app
omario8484 said:
Go back to stock sense and try or. Sense rom ...have u dropped your phone at all
Click to expand...
Click to collapse
I just tried this right before I read your message. I wiped and flashed CleanROM 5.0. Sure enough Wi-Fi was working, but then went back to the CM10 ROM and it appears to not be working again. I've been looking at the CM10 thread and nobody else seems to be having this problem.
..
omario8484 said:
Try giving your device the death grip ...like push on the back a little and try to connect
Click to expand...
Click to collapse
It's been fixed... I'm an idiot. lol
Thank you
omario8484 said:
Try giving your device the death grip ...like push on the back a little and try to connect
Click to expand...
Click to collapse
Another horrible idea.
Sent from my HTC One XL
ECEXCURSION said:
Another horrible idea.
Sent from my HTC One XL
Click to expand...
Click to collapse
Stfu ...
lava s12 rom
Rajdeep18 said:
Reflash your stock rom
Sent from my LAVA S12 using xda app-developers app
Click to expand...
Click to collapse
dear friend can you please upload the rom of your lava s12 device.i am badly in need of it as i have messed up my lava s12 and it has become useless
Same Problem
I faced the same problem when i tried to tweak my wifi so it can read an AdHoc. I had to download and flash a stock rom using odin.
Download from www.sammobile.com !!
Thank me
vitiweet said:
dear friend can you please upload the rom of your lava s12 device.i am badly in need of it as i have messed up my lava s12 and it has become useless
Click to expand...
Click to collapse
jgkhalil said:
I faced the same problem when i tried to tweak my wifi so it can read an AdHoc. I had to download and flash a stock rom using odin.
Download from www.sammobile.com !!
Thank me
Click to expand...
Click to collapse
This is one x section...
on my phone running cm10 10/12 wifi just stops working. can't turn it off and it won't scan properly for networks. i have to reboot. happens everytime. that's the only bug actually i found with 10/12.
I'm posting here, because I could not post on the blackbean development thread because I'm new to the forums, which I don't understand because I have been using this forum for a while. Anyways, I installed blackbean #6 and it was running awesome, better than cleanrom, but I was unable to connect to my wifi, for some reason it says connecting...and then it doesn't connect. Any help please, I really like this rom.
What channel are you using? I've seen posts recently about channels on the upper end not available on some ROMs.
For me, BB has had some of the best WIFI reliability, so I'm surprised to hear you'd have an issue that wasn't present in CM10.
naykam0810 said:
I'm posting here, because I could not post on the blackbean development thread because I'm new to the forums, which I don't understand because I have been using this forum for a while. Anyways, I installed blackbean #6 and it was running awesome, better than cleanrom, but I was unable to connect to my wifi, for some reason it says connecting...and then it doesn't connect. Any help please, I really like this rom.
Click to expand...
Click to collapse
are you on the newest build that was posted today
do any wifi networks come up?
Drgravy said:
are you on the newest build that was posted today
do any wifi networks come up?
Click to expand...
Click to collapse
I updated to the latest build, wiped cache and dalvic, system and did a factory reset. Wifi networks come up, but I'm unable to connect to my newtwork.
wifi
naykam0810 said:
I updated to the latest build, wiped cache and dalvic, system and did a factory reset. Wifi networks come up, but I'm unable to connect to my newtwork.
Click to expand...
Click to collapse
I flashed #6 as well --- My WIFI works all locations
If you backed up previous ROM -- restore back and see if WIFI works there
jerrybaxter said:
I flashed #6 as well --- My WIFI works all locations
If you backed up previous ROM -- restore back and see if WIFI works there
Click to expand...
Click to collapse
Yep, already did that, I'm running cleanrom and it's working. So don't know what the problem is. I'll probably try again today.
naykam0810 said:
Yep, already did that, I'm running cleanrom and it's working. So don't know what the problem is. I'll probably try again today.
Click to expand...
Click to collapse
My guess build.prop or default.prop changes made by blackbean and router sees your tab differently. If you have WPS use it while on blackbean then connect.
I have been having issues, with my control panel ( NewSENSE CP ), I get to my Modifications tab and i try to change my mods Lockscreens or Overscroll rosie mods or system UI Settings And it right away Forcecloses on me with a quickness..... Any Suggestions help and or Solutions ? ive tried to superwipe Everything over 5 times and reinstall Rom . and it still FC's on me ....
Did you download the Rom over WiFi, Hardline, or the Network ? Did you Restore any Data ? Did you verify the MD5 sum before Flashing ?
prboy1969 said:
Did you download the Rom over WiFi, Hardline, or the Network ? Did you Restore any Data ? Did you verify the MD5 sum before Flashing ?
Click to expand...
Click to collapse
Ive Downloaded Via Wifi. On laptop. Ive also Redownloaded Via Hardline Ive Checked the MD5, Restoring Data No all Was Fresh Wiped.
Try reflashing the Rom. Only this time manually wipe everything. There's a how to link in my Sig if your on a PC.
TEAM MiK
MikROMs Since 3/13/11
Ive tired your tut and its still a no go Ive Wiped Everything x3 Fully and Manually.... Ive waited the 10 minutes to settle everything into the rom. and Still its a no go. still getting the FC In the Modifications Selections. :crying:
Have you tried fixing permissions in Recovery ?
Have you tried flashing rc1 and doing the upgrade to rc2?
prboy1969 said:
Have you tried fixing permissions in Recovery ?
Click to expand...
Click to collapse
Yes i have tried fixing permissions in Rom and Outside of rom within Recovery still it was still a no go. But i may take the shot of Downgrading to RC1 The Re upping to RC 2 I may have some chance with that. Other then that, I will keep you all posted if its a go or no go.
Ianonymous said:
Yes i have tried fixing permissions in Rom and Outside of rom within Recovery still it was still a no go. But i may take the shot of Downgrading to RC1 The Re upping to RC 2 I may have some chance with that. Other then that, I will keep you all posted if its a go or no go.
Click to expand...
Click to collapse
If RC1 to RC2 doesn't work I think you're out of luck, unless drob releases an update
bilgerryan said:
If RC1 to RC2 doesn't work I think you're out of luck, unless drob releases an update
Click to expand...
Click to collapse
Well, Ive tried the RC1 going to RC2, IT was a no go. It told me it could not even Download. So im thinking an update maybe. it was a good run while it lasted hopefully i can get some news about it to see where i stand with newsence.
Ianonymous said:
Well, Ive tried the RC1 going to RC2, IT was a no go. It told me it could not even Download. So im thinking an update maybe. it was a good run while it lasted hopefully i can get some news about it to see where i stand with newsence.
Click to expand...
Click to collapse
Sorry to hear that, it is a GREAT ROM. Although there is not a lot of difference between RC1 & RC2, if you can live without some of the mods, RC1 is still AMAZING!
Yes RC1 is Amazing, so is RC2 . Hmmm....What Recovery are you using ? Still trying to figure out why your having this issue.
EDIT: just saw your post on the thread, and read about it maybe being a server issue
I'm having this same issue; I've also done everything suggested in this thread but it keeps force closing on any of the Modifications options. I guess it's not a huge deal because I don't even know what I'm really missing but it would be nice to have some more stuff to tinker with. Other than that, love the rom!!!
klund29078 said:
I'm having this same issue; I've also done everything suggested in this thread but it keeps force closing on any of the Modifications options. I guess it's not a huge deal because I don't even know what I'm really missing but it would be nice to have some more stuff to tinker with. Other than that, love the rom!!!
Click to expand...
Click to collapse
It's a server issue... tommytomatoe was hosting them and I'm guessing they got moved or something.
bilgerryan said:
It's a server issue... tommytomatoe was hosting them and I'm guessing they got moved or something.
Click to expand...
Click to collapse
Well somebody needs to get it fixed. Like right damn now.
Jussssst foolin'. It's all good. Thanks for the clarification.
klund29078 said:
Well somebody needs to get it fixed. Like right damn now.
Jussssst foolin'. It's all good. Thanks for the clarification.
Click to expand...
Click to collapse
Get ahold of Dread7us if you really want it fixed.. He was gonna check on it and probably forgot.
bilgerryan said:
Get ahold of Dread7us if you really want it fixed.. He was gonna check on it and probably forgot.
Click to expand...
Click to collapse
Nah it's not a huge deal. Like I said, I don't even know what I'm missing
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
BreatheHT said:
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
Click to expand...
Click to collapse
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Mister J said:
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Click to expand...
Click to collapse
i've tried everything like mentioned in the original post.... EVEN RUU
BUT AOKP roms works fine.
I'm started having the same problem this morning on every single sense ROM that I tried. I finally had to flash CM because I needed to call someone. RUU, wiping everything, different radios and different recoveries, nothing worked.
Sent from my One X using xda app-developers app
tried everything possible -_-
NobodY??????
I'm going to try a few other things when I get a chance, hopefully tomorrow. I would like to get this solved.
Sent from my One X using xda app-developers app
BreatheHT said:
NobodY??????
Click to expand...
Click to collapse
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
area51avenger said:
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
sweeterman said:
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yep it can't be hardware.
Have you checked HTC for a bug update? I know they have had these problems in the past. Might not hurt to check.
Sent from my HTC One X using xda premium
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing... And I don't really have a good backup...
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
BreatheHT said:
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
Click to expand...
Click to collapse
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
BreatheHT said:
Should I flash CWM again?
Click to expand...
Click to collapse
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
BreatheHT said:
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing...
Click to expand...
Click to collapse
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Good to know...I was thinkin bout flashing CWM, but I guess if I haven't had issues with TWRP, "don't fix what ain't broken."
Sent from my now S-Off HTC OneXL
redpoint73 said:
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
Click to expand...
Click to collapse
Thanks bro
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Will try, thanks bro!
elfysrfr said:
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
I'm using 2.3.x.x haha 2.4.x.x is so bad... Or not compatible...