Wifi - Unable to start

[Guest woollypigs]

Took over my partners Nexus One, a few months back and all was ok and even after I set it up for me.

Then the wifi just died, as in it will not even start up. So I waited to for the update to 2.2 FRF83 but that didn't help.

So I tried out CyanoganMod newest build and r19 from Paul. The nexus runs just fine but the wifi still reports "unable to start wifi".

[Guest justajason]

Took over my partners Nexus One, a few months back and all was ok and even after I set it up for me.

Then the wifi just died, as in it will not even start up. So I waited to for the update to 2.2 FRF83 but that didn't help.

So I tried out CyanoganMod newest build and r19 from Paul. The nexus runs just fine but the wifi still reports "unable to start wifi".

Try flashing the new radio. That might do the trick.

[Guest McBaul]

Took over my partners Nexus One, a few months back and all was ok and even after I set it up for me.

Then the wifi just died, as in it will not even start up. So I waited to for the update to 2.2 FRF83 but that didn't help.

So I tried out CyanoganMod newest build and r19 from Paul. The nexus runs just fine but the wifi still reports "unable to start wifi".

My wifi suddenly died just like you.

Some other guy suffer the same issue has been confirmed wifi module fried by HTC.

[Guest Phily]

I had the same issue when flashing just the system partition of a image, needed to flash the 'boot.img' before the wifi would start - looked like a kernel issue when i ran; adb logcat when the phone was booted and I tried to enable wifi.

Kernel lives in boot maybe?

[Guest bobtentpeg]

I had the same issue when flashing just the system partition of a image, needed to flash the 'boot.img' before the wifi would start - looked like a kernel issue when i ran; adb logcat when the phone was booted and I tried to enable wifi.

Kernel lives in boot maybe?

The boot.img is for all intents and purposes the kernel :lol:

[Guest Phily]

The boot.img is for all intents and purposes the kernel :D

I learn :lol:

[Guest woollypigs]

Thanks all. still have this issue.

I have tried out the CM5 and 6 and r22.1 and r21 etc and yet to fix this.

Is it possible to get a newer or older boot.img ?

I'm running the 2.6.33 kernel and 4.06.00.12_7

[Guest MDAC3N1]

Thanks all. still have this issue.

I have tried out the CM5 and 6 and r22.1 and r21 etc and yet to fix this.

Is it possible to get a newer or older boot.img ?

I'm running the 2.6.33 kernel and 4.06.00.12_7

I would return the device to a Stock state see if this corrects it. Then flash whatever ROM afterwards.

Download the Signed EPF30 http://shipped-roms.com

rename downloaded file to PASSIMG(.zip) copy it to the SD Card root > Turn device OFF > Turn device ON holding Volume Down > It will check the PASSIMG and should ask you to press Vol Up to install.

Let me know if it works.

Thanks

Edited July 13, 2010 by MDAC3N1

[Guest woollypigs]

I would return the device to a Stock state see if this corrects it. Then flash whatever ROM afterwards.

Download the Signed EPF30 http://shipped-roms.com

rename downloaded file to PASSIMG(.zip) copy it to the SD Card root > Turn device OFF > Turn device ON holding Volume Down > It will check the PASSIMG and should ask you to press Vol Up to install.

Let me know if it works.

Thanks

Thanks for your help, but that was a no go, still get the "unable to start wi-fi"

I forgot to say that, while playing around with other builds I did manage to turn on the wifi. Though only one time and couldn't find a network nearby adn as soon as the screen timed out was back the unable to start bit again. The problem I is that I can't remember what versions I was running before this problem started and which one that let me start it again.

EDIT : I tried again with full wipe before the install and this time it restarted the phone when I turned on the wifi. This is what happened when I first got this problem before it just gave me the error.

Edited July 13, 2010 by woollypigs

[Guest Hap Hazard]

I have a similar issue after every time I reboot my phone. Looking at the log, I noticed it said it did not have permissions to access particular file. So, after rebooting I will either adb or open a terminal and run the following command (in su):

chmod 666 /data/misc/wifi/wpa_supplicant.conf

I think I broke it myself when I tried to allow for ad-hoc wireless connections and there's probably an easier/long-term way of fixing it but for now that works for me.

Hope this helps.

[Guest woollypigs]

I have a similar issue after every time I reboot my phone. Looking at the log, I noticed it said it did not have permissions to access particular file. So, after rebooting I will either adb or open a terminal and run the following command (in su):

chmod 666 /data/misc/wifi/wpa_supplicant.conf

I think I broke it myself when I tried to allow for ad-hoc wireless connections and there's probably an easier/long-term way of fixing it but for now that works for me.

Hope this helps.

Hi

I take it that file is not on the SD card (since I can't find it there) and therefore do not know how to get to that file.

I have managed to install the adb server on ubuntu and can see the phone, well it tells me that it is there. But I do not know how to use it.

Edited July 13, 2010 by woollypigs

[Guest woollypigs]

Hi

I take it that file is not on the SD card (since I can't find it there) and therefore do not know how to get to that file.

I have managed to install the adb server on ubuntu and can see the phone, well it tells me that it is there. But I do not know how to use it.

I had a little play around and now got this when playing with adb ...

~/sdk/tools$ sudo ./adb shell chmod 666 /data/misc/wifi/wpa_supplicant.conf

Unable to chmod /data/misc/wifi/wpa_supplicant.conf: Permission denied

~/sdk/tools$ sudo ./adb root

adbd cannot run as root in production builds

back to the drawing board for me

[Guest MDAC3N1]

I had a little play around and now got this when playing with adb ...

~/sdk/tools$ sudo ./adb shell chmod 666 /data/misc/wifi/wpa_supplicant.conf

Unable to chmod /data/misc/wifi/wpa_supplicant.conf: Permission denied

~/sdk/tools$ sudo ./adb root

adbd cannot run as root in production builds

back to the drawing board for me

Is the Device currently rooted? do you still get the error when using a ROM with root?

Thanks

[Guest woollypigs]

Is the Device currently rooted? do you still get the error when using a ROM with root?

Thanks

Yes I'm now running CM6 RC1 and everything else works fine except wifi. Though it does just say error now.

EDIT : I tried all the above and gave up. Since I need the phone tomorrow I installed CM6 as it is easy and fast todo so.

Edited July 13, 2010 by woollypigs

[Guest Hap Hazard]

I had a little play around and now got this when playing with adb ...

~/sdk/tools$ sudo ./adb shell chmod 666 /data/misc/wifi/wpa_supplicant.conf

Unable to chmod /data/misc/wifi/wpa_supplicant.conf: Permission denied

~/sdk/tools$ sudo ./adb root

adbd cannot run as root in production builds

back to the drawing board for me

Try:

adb shell

su

chmod 666 /data/misc/wifi/wpa_supplicant.conf

Or in a terminal on the phone:

su

chmod 666 /data/misc/wifi/wpa_supplicant.conf

[Guest woollypigs]

Hi, thanks for your help

Try:

adb shell

su

chmod 666 /data/misc/wifi/wpa_supplicant.conf

I tried that last night and ever could get past the su

Or in a terminal on the phone:

su

chmod 666 /data/misc/wifi/wpa_supplicant.conf

Tried this just now and got "no such file or directory"

[Guest woollypigs]

Ok so created the wpa_supplicant.conf first empty and then with this in

network={

ssid="xxxxx"

scan_ssid=1

password="xxxxx"

}

ok I do not know what I'm doing here so it was a stab in the dark.

But nothing helped.

[Guest woollypigs]

I have tried a few more ROM's and older radios (4.02 etc) but still get either "error" or "unable to start" when tying to start the wifi. And every install or version I can't find wpa_supplicant.conf file.

Anyone got an idea ?