Develop Bugs

my desire died out of nowhere... :( please help!, rooted with R5, MCR 3.1 for 2weeks

dear all,
My Telstra branded HTC Desire 8183 died out of nowhere.
Here's what I did:
Rooted with R5
MCR 3.1 ROM (custom kitchen with A2SD+) and r17 froyo rom (mostly MCR3.1)
everything went well, and i was happy with it for 2 weeks (blasting fast HSDPA speed and runs perfectly fine)
i noticed the signal strength was really low two days ago, i thought it was my area having service outage. (called and confirmed) I had my girlfriend's Nexus One AT&T version side by side she's getting full bars.
now the phone will show Emergency Call Only all the time, sometimes even with signal, i wont be able to use the data connection (it's show H, but cant even load google.com with the browser)
Diagnostics that i had done:
unroot with generic WWE rom with goldcard (since the telstra rom that people posted on here have 0.75 bootloader and mine is 0.8 so i can only use 1.21 generic WWE rom)
root again with R5 method
update radio
install MCR 3.1 again
replaced my sim card at AT&T store just to make sure
called AT&T to inquire about service outage
none of them works, now i'm stuck with a phone that doesnt make phone calls and data connection.
did i do anything wrong that mess up the radio of the phone? are these rooting guide and custom rom don't support 8183?
please help me! i really like this phone and it's such a waste to let it sit there
best regards,
ted

The emergency calls only thing is usually associated with a sim problem - like invalid sim, unactivated sim etc.
Have you paid your account?

thanks for the advise
yes i did...same thing happened, sometimes when i get signal, i cant seem to use data connection...cant even make phone calls...if im lucky i can make 1 out of 10 times..
i suspected the sim card problem, that's why i went to AT&T store for a replacement.

Solved
I had the same problem, I also have the A8183
To solve it, I went fastboot mode with USB plugged.
then on Android SDK, I did :
./fastboot-mac enableqxdm 0
./fastboot-mac oem boot
just fastboot for pc
and the phone reboot, turn it off and insert your SIM.
I knew it was fix first boot because sdcard was now mountable.
Then SIM was recognized.
But then I have USB problem in recovery, I think I'll need to flash the misc partition.

blauze said:
I had the same problem, I also have the A8183
To solve it, I went fastboot mode with USB plugged.
then on Android SDK, I did :
./fastboot-mac enableqxdm 0
./fastboot-mac oem boot
just fastboot for pc
and the phone reboot, turn it off and insert your SIM.
I knew it was fix first boot because sdcard was now mountable.
Then SIM was recognized.
But then I have USB problem in recovery, I think I'll need to flash the misc partition.
Click to expand...
Click to collapse
What you are describing is the fix for the usb brick issue. This is not the problem here.
To me this sounds like a faulty handset, as all the software fix options seem to have been done. I'm no expert though!

what is fastboot-mac
im using windows xp with androidsdk tools
i have fastboot command...how do i type that?

socktug said:
What you are describing is the fix for the usb brick issue. This is not the problem here.
To me this sounds like a faulty handset, as all the software fix options seem to have been done. I'm no expert though!
Click to expand...
Click to collapse
is it really? i got my hopes up for a second...i really wanna get this thing fixed...

teddyonair said:
is it really? i got my hopes up for a second...i really wanna get this thing fixed...
Click to expand...
Click to collapse
You can give the commands a go, but I doubt they will help with this. Have a look at the threads on usb brick.

socktug said:
You can give the commands a go, but I doubt they will help with this. Have a look at the threads on usb brick.
Click to expand...
Click to collapse
tried the first command, it says "waiting for device"...no response from phone and command prompt at all
hey guys, keep the opinions coming...thanks in advance!

Try flashing to a different compatible radio version as the version you currently have may be causing the poor reception/signal strength issues.
-------------------------------------
Sent via the XDA Tapatalk App

MasDroid said:
Try flashing to a different compatible radio version as the version you currently have may be causing the poor reception/signal strength issues.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
i did tried 3 different radio...its not just signal being weak...kept on showing X and whenever i tried to use the data connection when H shows up, it will just stuck there when loading google.com in browser.

teddyonair said:
thanks for the advise
yes i did...same thing happened, sometimes when i get signal, i cant seem to use data connection...cant even make phone calls...if im lucky i can make 1 out of 10 times..
i suspected the sim card problem, that's why i went to AT&T store for a replacement.
Click to expand...
Click to collapse
Hmmmm - the rooting process does not affect the A8183 - cos that's what I've got and it works fine. Maybe try and flash the Telstra ROM? That's the one that would have come with the phone in the first place. Who knows, that might reset something? Probably a long shot but you sound desperate!
You can get that ROM in the ROM sticky in this topic.

Now i have 0.80 bootloader it wont let me install the telstra rom since bootloader version being different (0.75)
any idea how i can override that?
After the rooting process when i first got the phone everything was working fine til two days ago

teddyonair said:
Now i have 0.80 bootloader it wont let me install the telstra rom since bootloader version being different (0.75)
any idea how i can override that?
After the rooting process when i first got the phone everything was working fine til two days ago
Click to expand...
Click to collapse
you could try this: http://android.modaco.com/content/h...-com/310186/mcr-telstra-8183-mod-version-3-5/
I think that will work with 0.80 bootloader.
I guess it's not easy to take the device for repair as I'm tippin you got it through eBay or similar, and HTC in the US probably won't support the warranty.

I believe that i had sort of the same issue as you are describing, sometimes my 3G connection died, and there was nothing i could do too get it back, and it sometimes failed to make a connection when i tried to make calls with full coverage.
I don't know how i got the problem, because the phone has been fine since i rooted it 1 week ago.
I decided to go back to the latest radio update I had before I rooted, and now it works fine again.
I used 32.34.00.28U_4.05.00.30_2 from the stock HTC radios thread. (new users not able to post links)
Hope this solves your issue as well, I have an unbraded Desire A8181.

JoakimCarli said:
I believe that i had sort of the same issue as you are describing, sometimes my 3G connection died, and there was nothing i could do too get it back, and it sometimes failed to make a connection when i tried to make calls with full coverage.
I don't know how i got the problem, because the phone has been fine since i rooted it 1 week ago.
I decided to go back to the latest radio update I had before I rooted, and now it works fine again.
I used 32.34.00.28U_4.05.00.30_2 from the stock HTC radios thread. (new users not able to post links)
Hope this solves your issue as well, I have an unbraded Desire A8181.
Click to expand...
Click to collapse
im going to give the radio you mentioned a try...would u mind telling me where are you located and what network provider are you with?

Tried that radio already now it shows signal but the behaviors are the same, feels like its trying to establish connection but got stuck on upload (not sure if thats the case since only the up arrow stay lit but not the other one)

@teddyonair: did u drop down ur mobile by any chance ??? might be some hardware disconnection inside is giving u this trouble i guess.... otherwise with so many software reflashing & modding,ur mobile should have been working by now....
u better get a professional help either from the htc or from someone who deals with htc repairs.... this is my sincere advice if u wish to listen to me.... hope u have not screwed up ur mobile.... might be a hardware problem... just try this once... ok ????

i've managed to unroot the phone with telstra shipped rom. phone has been acting the same way.
so im not sure if it's the hardware issue. anybody has experience how to send the phone back to Telstra Australia for repair?
thanks!

It sounds to me like you may have a faulty antenna in your phone

WIFI wont work on Desire....says turning on then....error.

rooted mine my bros and bros girlfriends desires...
all went fine, no problems.
then my bros girlfriends started doing this thing and would'nt connect to wifi...it says turning on then error.
i thought ok, its an old rom version updated to the latest along with the latest radio 5.20 (or whatever it is ) and still the same....
ok...must be the rom...tried opendesire, which is working perfect on my phone and its still not working....
so to shortlist the problem is when i try connect to wifi it says turning on...then error...and wont even turn on...
definately not the rom.
definitely not the radio.
anyone got any ideas?
i tried to flash back to stock RUU but it would not let me "update" it with an HTC ruu a europe RUU and even a TMO UK ruu....
just kept saying cant update....
so anyone got any suggestions?
thanks!!

The same problem with me. I flash several ROMs, but no change. I think it's hardware fault.

Full wipe before flashing new roms? Have you tried a FroYo sense rom?
Sent from my HTC Desire

Now i use office 2.2 ROM, the same problem.

ye wiped and everything.
i cant even flash a RUU package which is gay!!
ill try a few other things and see if i can get it to work....and then maybe just send it back for repair or something.

I seem to have the same issue did anyone have any luck?

Just to give more background to me issue:
I've come up against a weird bug\issue\failure.
I've been running Leedriod ROM for a while with very very few issues. I upgraded to 2.0c over the weekend & everything was working fine.
This morning however neither my wifi or bluetooth is work.
Wifi tries to start but I simply get "Error" in Setting-->Wirless & Network-->Wi-Fi
My bluetooth has also stop working.
I'm not sure if this is related to the Leedroid ROM or potentially a hardware failure...
I have gone back to 1.9 (last know good backup) & I've done a complete fresh wipe & install of 2.0c. None of which I have had any luck with. I've also trawled the web and forums but nothing similar is popping up....
Any help or advice much appreciated...

IEArmand said:
Just to give more background to me issue:
I've come up against a weird bug\issue\failure.
I've been running Leedriod ROM for a while with very very few issues. I upgraded to 2.0c over the weekend & everything was working fine.
This morning however neither my wifi or bluetooth is work.
Wifi tries to start but I simply get "Error" in Setting-->Wirless & Network-->Wi-Fi
My bluetooth has also stop working.
I'm not sure if this is related to the Leedroid ROM or potentially a hardware failure...
I have gone back to 1.9 (last know good backup) & I've done a complete fresh wipe & install of 2.0c. None of which I have had any luck with. I've also trawled the web and forums but nothing similar is popping up....
Any help or advice much appreciated...
Click to expand...
Click to collapse
Didn't my advice in another thread work?
It sounds like you guys have what's called a usb-bricked phone.
Sent from my HTC Desire.

JustinTrouble said:
Didn't my advice in another thread work?
It sounds like you guys have what's called a usb-bricked phone.
Sent from my HTC Desire.
Click to expand...
Click to collapse
Sorry, mate...somewhere in my brain I thought I have replied to you. I tried the USB Brick Fix you suggested but no luck....
I'm beginning to think it's a hardware fail....

Normally means you didn't update with the gold card in the phone - you need this for ALL updates on previously branded phones...

What exactly is a USB brick? Does it brick the phone or just stop the USB from being able to update the phone?
Sent from my HTC Desire using Tapatalk

Hey, I have much the same issue, I've tried a whole lot of ROMs and none of them seem to make the wifi work.
As soon as I revert back to the original installation it's working as expected, but whenever the phone is flashed (with the updated radio too), wifi stops.
As far as I can tell, Bluetooth, GPS and 3G are fine, but wifi tries to connect states that it's "Acquiring IP Address" and then disconnects and starts the cycle again.
Any help would be greatly appreciated.
Thanks.

Do you use the gold card when updating?
Sent from my HTC Desire using Tapatalk

IEArmand said:
Sorry, mate...somewhere in my brain I thought I have replied to you. I tried the USB Brick Fix you suggested but no luck....
I'm beginning to think it's a hardware fail....
Click to expand...
Click to collapse
Hey, no worries!
Your symptoms definitely suggest your phone is "usb-bricked". What method did you try?
This is the best (and easiest): http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
I followed it myself with success some time ago.
If your phone is no longer rooted, you will need to root it. Else start with step 2.

EddyOS said:
Normally means you didn't update with the gold card in the phone - you need this for ALL updates on previously branded phones...
Click to expand...
Click to collapse
I've never used my gold card when updating my branded Vodafone Desire.
I only used the gold card for initially rooting my Desire!

aindow said:
What exactly is a USB brick? Does it brick the phone or just stop the USB from being able to update the phone?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Sometimes when a update/flash goes wrong the Desire going in to a low level debugging mode, which we refer to as a "usb-bricked Desire".
You will observe the following symptoms:
* FM Radio Malfunction.
* Bluetooth Malfunction.
* Charging doesn't start immediately.
* Radio Malfunction.
* SD Card Malfunction.
* Unable to connect your phone using USB when booted into Android.
* Unable to connect your phone using USB in Custom/Pushed Recovery.
...other than this, the phone will work as expected.
So the WiFi problem is something different. I was directing my reply directly at IEArmand because we were chatting on a different thread.

JustinTrouble said:
Sometimes when a update/flash goes wrong the Desire going in to a low level debugging mode, which we refer to as a "usb-bricked Desire".
You will observe the following symptoms:
* FM Radio Malfunction.
* Bluetooth Malfunction.
* Charging doesn't start immediately.
* Radio Malfunction.
* SD Card Malfunction.
* Unable to connect your phone using USB when booted into Android.
* Unable to connect your phone using USB in Custom/Pushed Recovery.
...other than this, the phone will work as expected.
So the WiFi problem is something different. I was directing my reply directly at IEArmand because we were chatting on a different thread.
Click to expand...
Click to collapse
Thanks for the info, was just curious as my Desire, although now fully updated, didn't seem to like the latest RRU update file and couldn't be connected via USB. It's weird as disk mode and sync still work completely fine and it updated fine via OTA.
Sent from my HTC Desire using Tapatalk

Ok this is weird.....
Woke up this morning and found my Wifi and Bluetooth functions have returned!! I did not try anything last night so I'm at a loss to know what has fixed it.Functions did not return right after USB Brick fix but who knows...
Not much help to folk with this issue I'm afraid..

EddyOS said:
Normally means you didn't update with the gold card in the phone - you need this for ALL updates on previously branded phones...
Click to expand...
Click to collapse
Hey, I rooted my phone using the Unrevoked method, I didn't think I needed a Gold Card to complete this.
Maybe I read this incorrectly. Can I just repeat the process with the GC?
And...does the GC help with Rooting or Flashing?
Thanks.

That's rooting, you don't need a gold card for that. If you want to flash a generic ROM onto your branded Desire you'll need a gold card. If you want to flash a custom ROM, you just need to use a custom recovery (which you'll have thanks to unrEVOked)
As for JustinTrouble not needing one, I'm guessing it's just Orange users having issues then as most people need the gold card to stop the WiFi issue rearing its head

Device Reboot when using WiFi or Mobile Interent

Please help. I just got used HTC Incredible.
It is S-OFF, Hboot-0.92, Radion 2.15.00.07.28 and Android 2.2
It is only work when no WiFI and not Mobile Internet.
If I turn on Mobile Interent I have up to minutes to use Interent and then device going in rebootin and white screen. Removing battery sometimes help and device starts loading but then will rebooting again.
Will changing ROM helps?
As I saw a lot of people has similar problems in USA.... may be I got bad device(

You received your DInc with S-OFF? Sounds like someone sent it in and the refurb department didn't do its job in checking the phone and reloading it... then sent it to you.
You could always flash the stock ROM back onto and see what it does.
http :// dougpiston . com/?page_id=108
is where you can get the Stock ROM from. You will need to place it on you SD card and name it PB31IMG.zip
Boot up into your HBOOT and proceed with the update

Thanks! It was on original Rom when I got it but with S-OFF! and was rebooting when try to use WiFi or Mob. Internet.
Now I'm on cyanogenmod 7 and then same problem.
Do I need play with radio version? Will it may help?

If you go back stock it will unroot you..... if you give me some more info I might be able to help..... like when you flashed cm7 did you do a full wipe and what recovery do you have
Plus did you get it from Verizon or Craigslist or something
Sent from my Incredible using XDA App

Yes, I did full wipe.
Now I'm under CM7 and seems it working now more stable. So I can use interent via WiFI near 10-15 minutes. Under Mobile connection near 5-10minutes. If I do just quick connection on 30-60 second it not rebooting at all.
I got the phone from a person who, I think, take it from ebay. It has verizon sign on it.
When I got it was with original lates ROM.
I'm starting think that it is overheating. May be I can low processor speed?
Updated. Also I've installed prog called 'neocore' which does 3d benchmark testing. I need to run just 2-3 times this test and my device starts rebooting.

I had a similar problem when using custom kernels with HAVS or smartass governors on them. Do you have Set CPU or any other program that controls your processing speed/voltage? If so, try disabling them and see if you still have the problem. Some phones do not react well to under/overclocking.

im not sure what kernel comes with cm7 but some dincs dont like multitouch kernels.... and they will kick you off apps and sometimes reboot so i would try switching kernels first.. try one that is close to stock

Just back to stock ROM. And what I see, that if I disable Mobile Internet it works stable. Just turn on Mobile Internet and it starts rebooting. Stock rom has a lot of apps which connect to the internet. Even with disabled auto-update I still see how on booting 3g icons areas and arrows up-down are blinking.
As I see after connection to the mobile internet my device starts rebooting. And only one think helps - remove battery and wait several minutes, which allows boot in successfully. And then if turn off mobile access it will work well (((

Thats odd that ur phone does that. Did u try and change the radio?

Seems that is last what I can try. Or will need to sell it on parts for cheap (.
As I know radio 2.15.00.07.28 is very stable. Which one you recomend to use?
And how to be sure that it will work well with my Current ROM?
Can I install older radio? like 2.07.00.07.16? or even older?
Thanks for help!

RedMonkey100 said:
Seems that is last what I can try. Or will need to sell it on parts for cheap (.
As I know radio 2.15.00.07.28 is very stable. Which one you recomend to use?
And how to be sure that it will work well with my Current ROM?
Thanks for help!
Click to expand...
Click to collapse
i have an idea man maybe you should run an RUU to unroot you and format everything back to the way it was from the factory.... if that dont help it has to be a hardware issue.... let me know and ill help you through it

Thank for helping. Just not sure that unroot may have difference. But will try at last.
What I had found last days. I had changed radio to some version.
On 2.15.00.09.01 was very fast rebooting after try use internet.
On 2.07.00.07.16 was working a bit longer, but not so much.
And 2.05.00.06.11 - the best one! Plus I switched to Stock rom with Android 2.2 and whole day without rebooting.
Only one reboot was when do charging of the device.
The only problem I've under 2.05.00.06.11 that Interent working only via 1x speed. It always tries to connect via 3G, but no luck and switch to 1x.
What do u think now?
Again, thanks for help!

WiFi not turning on?

Ok so a couple of days ago I installed a 4.0 ready radio on my galaxy s2 and then went on to install Jedi Knight 6 ROM (4.0.4 and radio is UVMC6) and after installation everything was working fine.. I was messing around for a while.. it worked today, I shut my phone off to charge it up real quick, and when I turned it back on my WiFi would not connect. Well not necessarly connect.. it just wont even turn on. When I go into settings and click WiFi, it just sits there saying, Turning WiFi on, and never changes.. I can't seem to imagine what could have happened to it, and I really dont wanna have to reinstall the ROM again because i just spent hours getting this one all set up to my liking...
Anyone got any ideas?
EDIT: BTW, I have tried many things.. Tried airplane mode to disable everything then turn it back on, obviously tried rebooting the phone, i have tried wiping cache in CWM recovery and also tried fix permissions in recovery (another topic said to try those..)
Nothing has worked so far, i'm about to try reflashing my radio, see if that works.. but I really really dont want to have to reflash my whole ROM.. So if anyone has any other ideas please help, i'll edit if the radio works..
EDIT 2: Reflashing the radio did nothing.. it's really wierd, the data, bt, gps.. all of it works fine, it's just the WiFi that's frozen turning on... cant get it to stop turning on and can't get it to actually turn on..
EDIT Final: Ok well, i guess nobody knows what might have been going on.. so I just wound up reflashing my ROM, which obviously fixed it.. i just had to lose all that time spent setting everything up... But oh well.. Kinda sucks nobody even tried to help..

Gopher love said:
Ok so a couple of days ago I installed a 4.0 ready radio on my galaxy s2 and then went on to install Jedi Knight 6 ROM (4.0.4 and radio is UVMC6) and after installation everything was working fine.. I was messing around for a while.. it worked today, I shut my phone off to charge it up real quick, and when I turned it back on my WiFi would not connect. Well not necessarly connect.. it just wont even turn on. When I go into settings and click WiFi, it just sits there saying, Turning WiFi on, and never changes.. I can't seem to imagine what could have happened to it, and I really dont wanna have to reinstall the ROM again because i just spent hours getting this one all set up to my liking...
Anyone got any ideas?
EDIT: BTW, I have tried many things.. Tried airplane mode to disable everything then turn it back on, obviously tried rebooting the phone, i have tried wiping cache in CWM recovery and also tried fix permissions in recovery (another topic said to try those..)
Nothing has worked so far, i'm about to try reflashing my radio, see if that works.. but I really really dont want to have to reflash my whole ROM.. So if anyone has any other ideas please help, i'll edit if the radio works..
EDIT 2: Reflashing the radio did nothing.. it's really wierd, the data, bt, gps.. all of it works fine, it's just the WiFi that's frozen turning on... cant get it to stop turning on and can't get it to actually turn on..
EDIT Final: Ok well, i guess nobody knows what might have been going on.. so I just wound up reflashing my ROM, which obviously fixed it.. i just had to lose all that time spent setting everything up... But oh well.. Kinda sucks nobody even tried to help..
Click to expand...
Click to collapse
+1 I'm going through the same thing now

I have been having this same issue as well. It started out as stock happening sporadically. One thread suggested rooting and removing my account. Problem still occurring. Tried flashing multiple ROMs and now WiFi hasn't connected at all always stuck at turning on. I have tried clear cache, fix permissions, as well as reinstalling ROM dirty and with factory reset. I'm hoping this isn't hardware failure because I just bought this phone used but it seems to be a reoccurring problem with others as well. Any NEW suggestions not given from quick Google/xda search?

stoneduser8907 said:
I have been having this same issue as well. It started out as stock happening sporadically. One thread suggested rooting and removing my account. Problem still occurring. Tried flashing multiple ROMs and now WiFi hasn't connected at all always stuck at turning on. I have tried clear cache, fix permissions, as well as reinstalling ROM dirty and with factory reset. I'm hoping this isn't hardware failure because I just bought this phone used but it seems to be a reoccurring problem with others as well. Any NEW suggestions not given from quick Google/xda search?
Click to expand...
Click to collapse
I'd suggest to check your Wireless Access Point (modem or router) wireless settings for security, check and see if it's set to use WPA/WPA2, which is common on some modems/routers, change it to either WPA or WPA2 (preferred) not both, it's a known issue with WiFi networks and having it set to using both, I had the same problem before with my phone connecting to my WiFi.
Also if you use MAC Address Filtering on the modem/router, you should disable/clear that and let phone re-connect before enabling mac filtering again.

Almite said:
I'd suggest to check your Wireless Access Point (modem or router) wireless settings for security, check and see if it's set to use WPA/WPA2, which is common on some modems/routers, change it to either WPA or WPA2 (preferred) not both, it's a known issue with WiFi networks and having it set to using both, I had the same problem before with my phone connecting to my WiFi.
Also if you use MAC Address Filtering on the modem/router, you should disable/clear that and let phone re-connect before enabling mac filtering again.
Click to expand...
Click to collapse
The problem I am having is not that it won't connect to a particular network. Wifi will not initialize on the device at all and is stuck in "Turning On..." state. I found more and more posts where people ended up having to send in to Samsung so I spoke with them and even though I purchased the phone used its thankfully still under warranty and they will be replacing it. The did not confirm whether or not it was a true known device issue but were quick to file the exchange for me.

sigh, me too!
Just started having this problem on 4.3.1
great.

In my case, I had to wipe system and data before reinstalling my ROM.
Though the only reason it was happening to me was because Beanstalk 4.4.2 didn't want to get past the splash screen when I tried to install it so I downgraded back to ICS 4.0.4 without wiping. Good luck getting this issue fixed. Also another kernel might fix thingz for you if your current one does not like your device.

I have a similar problem. After a while, WiFi gets disconnected. If I go in settings - wifi, i get the message "unfortunately, settings has stopped" and I can't get WiFi to work again until I reboot the phone. The Wifi works again for a couple of minutes then stops.
I have flashed various different ROM (CM11, PA) but keeps getting the exact same behavior.
I've rebooted in safe mode and I don't get the problem now.

[Q] Wifi Problems: Wifi won't turn on

Hello everybody,
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip on my desire.
But I have a problem using Wifi connection. I have read several threads about similar topics, but could not find a solution. I experienced the same problems with the previous release. At first, after installation, wifi worked well, but after having it turned off it won't turn on anymore. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
Does anybody have an idea?
It would be great if anybody could help me.

I've had this issue with some Roms previously, the Wifi turns On, but won't turn on again after you turn it off
(is that the problem you're having?)
the solution/work around was to put the phone on Airplane mode, and back
this sometimes fixed it
..if not then I'd just restart the phone
there might/should be some other solution..look around or wait for someone to reply :good:
I can confirm that 'MildWild (Android 2.3)' does Not have this issue

Prodc said:
Hello everybody,
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip on my desire.
But I have a problem using Wifi connection. I have read several threads about similar topics, but could not find a solution. I experienced the same problems with the previous release. At first, after installation, wifi worked well, but after having it turned off it won't turn on anymore. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
Does anybody have an idea?
It would be great if anybody could help me.
Click to expand...
Click to collapse
Did you find a resolution to this problem? Mine has just stopped working after many years of being OK.
Cheers

I resolved this by running a factore reset eventually, but this of course means you have to reset up your phone from scratch.
See - http://forum.xda-developers.com/showthread.php?t=2646168