Help No WiFi in WebOS Android Fine

[Rabid1]

So I picked up a couple of used 32GB Touchpads Both were stuck at the setup screen waiting for WiFi to find a network. They would just continually scan.

So I bypassed the setup, neither WiFi or Bluetooth will turn on. I tried a few fixes I found on the internet with no luck. Enable then Disable Airplane mode, Leave it running trying to turn on BT and WiFi overnight on a charger. I rolled it back to 3.0.0 then back up to 3.0.5 one by one with the same results.

I decided to go ahead and try CWM and see what happens. WiFi and Bluetooth work perfectly in CM9 and CM10??!!?? Not a single issue. So I went back to WebOS and since I don't have WiFi I used WOSQI to install Uberkernel and Govnah, thinking maybe a new kernel would fix it. The same results as before.

For the life of me I am stuck. Sure Android works perfect but I would still like to figure out where the problem is. With hours of trolling posts the closest I can find was one douchy post where the l33t dude said he could fix it but us mere mortals just couldn't handle the info. OK so the post wasn't douchy, the poster was.

Anybody have any ideas?

 

[colchiro]

Hi Rabid. Strange problem, but your best bet for a webOS problem would be a webOS forum... a place where people actually use it. About the best we could do here would be what you already did, get the exact wording from you and Google it.

Did you try a factory reset under webOSt? You've already tried a couple of tweaks, it's hard to know what the previous owner did to them so the best thing would be to acmeuninstall to remove CM10 and webOS doctor them back to a known version. But that's a lot of work and there is some risk any time you run DR. Also, never run DR without removing Android first or you could end up with bigger problems.

Most TP users don't use webOS at all after installing Android OR they're like me and only use it to fix Android. (I used it to run Tailor to resize partitions and regularly use it to flash my A6 chip.) Tailor would require wifi to work to install it, but doubt you'd need it for the other. There's also that certificate in the webOS store that requires turning back the date to install, that would require a working wifi.

 

[Rabid1]

Yeah I posted on Nation and a couple other forums as well. It's a fairly common problem once you research it a little. it looks like the Atheros chipset is given a MAC address by webOS after the driver initializes, instead of using the MAC on the hardware. I get the idea as sometimes a series of devices will come out of the factory all with the same MAC on the hardware. But in this case there is no MAC generated and you get all 0s.

What I don't understand is why with a complete wipe doesn't force it to generate new tokens. OS2 had a similar issue but a wipe would fix it.

So far a complete manual wipe and rebuild of the partitions after a secure erase, the debrick, and rolling from 3.0.0 through 3.0.5 didn't work. The issue is definitely not related to Android in anyway,

I'm looking at seeing if there is a way to reflash the Atheros chip through Novacom.

It's interesting that both these came from different sources. One was originally new in the box from the fire sale and the other was a store demo picked up after the fire sale. Both did a reset and ACMEUninstall then when they tried to setup webOS wifi would not work.

 

[colchiro]

You would think the demo would have been fixed under warranty as soon as they knew wifi wouldn't work. At least you can get CM to work, which is the important one.

 

[Rabid1]

You would think the demo would have been fixed under warranty as soon as they knew wifi wouldn't work. At least you can get CM to work, which is the important one.

Yeah it's more of a "dammit I can fix this." plus I actually like using webOS as an everyday. A few of my favorite games that don't play well on Android run perfect on webOS.

I am getting closer. A post about hex editing the token may not work, because even if I back up and mount a good token from another Touchpad, the result is the same so something is messing with the token in the system, If I boot a new install the hardware shows up as eth0 and has a valid mac in ifconfig, but the WIFIoADDR token shows 00:00:00:00:00:00 as does the BToADDR, which are both off the same Atheros chip, but no devices show up under iwconfig. I am pulling apart a Doctor file and looking to see if the Atheros flash is embedded like the A6. If it is I might try a reflash. I was reading about editing Doctor files to do that, but that is a little beyond me, yet....

 

[colchiro]

Sounds like you're already past most people's skills.

I'm very comfortable with Windows and with direction, Android, but I'm lost with it comes to Mac., yet I own all 3. Something tells me you'll going to get real comfy with webOS before you're done with this.

 

[Deleted User]

Geez, seems like one could use a terminal program in WebOS to push the mac address info to the WiFi like we do to flash the A6 firmware. Otherwise, totally over my head.

 

[Rabid1]

Geez, seems like one could use a terminal program in WebOS to push the mac address info to the WiFi like we do to flash the A6 firmware. Otherwise, totally over my head.

There is fior the eth0 but it doesn't change the token. That was why I was thinking reflash the Atheros chip. The drivers are in the same folder as the bin file for the A6 . I am still playing around with it. I may send a pm to scullins and see what he thinks.

The good thing it is not faulty hardware. I just saw another 32GB with this issue go for $45 on ebay.