[Q] Is my Wi-Fi chip broken? - Kindle Fire General

At this moment I can't turn on my wifi. My router is fine (I have other android devices with wifi working just fine).
I was using CM7 Barebones with wifi working, then installed NRGZ28 CM9 Energy (03-19). I couldn't connect to wifi, so i restarted it. It couldn't connect so I restored to my CM7 Barebones backup. Wifi wasn't working but after trying switching off and on it worked... for 2 minutes (I was able to read a few emails and suddenly wifi stopped working). I tried to switch off and on a few times with no good results.
After that I tried the following:
- Restarted.
- Wipe Cache + Dalvik Cache + Factory Reset.
- Restored an older backup (CM7).
- Resintalled CM7 (THIS ROM).
- Resintalled CM9.
- Reinstalled CM7 with different kernels.
- Restored my Stock ROM (logcat attached).
- Reinstalled "Amazon Pure Stock" using THIS METHOD. Then I did a Factory Reset. (Logcat attached).
- Reinstalled CM7 again (logcat attached).
- Reinstalled CM9 again (logcat attached).
After all that, wifi doesnt turn on (sometimes I get an error, other times it gets stuck "turning on").
I have read that it may be a hardware issue. Is there any diagnostic tool to confirm that?
I attached various logcats in case you figure out how to solve (or diagnost) this problem.
THANK YOU IN ADVANCE.

psiwar said:
At this moment I can't turn on my wifi. My router is fine (I have other android devices with wifi working just fine).
I was using CM7 Barebones with wifi working, then installed NRGZ28 CM9 Energy (03-19). I couldn't connect to wifi, so i restarted it. It couldn't connect so I restored to my CM7 Barebones backup. Wifi wasn't working but after trying switching off and on it worked... for 2 minutes (I was able to read a few emails and suddenly wifi stopped working). I tried to switch off and on a few times with no good results.
After that I tried the following:
- Restarted.
- Wipe Cache + Dalvik Cache + Factory Reset.
- Restored an older backup (CM7).
- Resintalled CM7 (THIS ROM).
- Resintalled CM9.
- Reinstalled CM7 with different kernels.
- Restored my Stock ROM (logcat attached).
- Reinstalled "Amazon Pure Stock" using THIS METHOD. Then I did a Factory Reset. (Logcat attached).
- Reinstalled CM7 again (logcat attached).
- Reinstalled CM9 again (logcat attached).
After all that, wifi doesnt turn on (sometimes I get an error, other times it gets stuck "turning on").
I have read that it may be a hardware issue. Is there any diagnostic tool to confirm that?
I attached various logcats in case you figure out how to solve (or diagnost) this problem.
THANK YOU IN ADVANCE.
Click to expand...
Click to collapse
for what its worth i have 2 fires after flashing one i had problems basically did what you did with no results i then unplugged my router then plugged back in and it worked may help you

Thank you for your response. Unfourtunately i had already tried that. After all, it doesn't even turn the antenna on.
Anyway, I really appreciate your response. I have been waiting for someone to at least give it a shot.

Could you send it back to Amazon? I think you just have to restore stock.
Sent from my Kindle Fire using xda premium

I already contacted Customer Support and they told me it is a known hardware issue and they can replace my device if I send it back to them. The problem is that I don't live in the US and they wont pay the transport fees from and to other countries. So it will be hard and expensive to send back my Kindle Fire for replacement (I would need to pay more than $100 in transport and importing fees).
I'm now looking for a method to enable USB Reverse Tethering. Right now I cannot install/update using the Android Market (any app that uses ACCESS_NETWORK_STATE permission cant download anything from the internet).

Related

Wireless "Disabled" - help

I just recently got this tablet from someone else. (This person had no problems and is trustworthy in reporting all that was done and care taken with it, even offering on advice on things you can do with it.)
My first step was to connect to Wifi. This happened without problems.
When returning home from work where I also connected, my wireless connection(s) said "Disabled" after trying to obtain the IP where they worked fine before. The first time this happened I had to do a factory reset to solve it (hardware reset didn't do it).
Today, it is happening again. I woke it from "standby" to start using again at home and received this message. In fact, any attempted WiFi connections comes up saying "disabled" after attempting to connect and obtain an IP. Again, these are saved connections that previously worked. I know for a fact that it's not the routers.
Please help if you can. I've tried:
1) power off/up 2x in a row to no avail
2) removing and adding back the connection with the appropriate passwords
3) a factory reset but I really don't want to do that again because I'm afraid flashing it back will bring back the same problem.
3) I haven't put any new apps on it since it last worked earlier today so I can't figure that as an issue. The first time it happened a week ago was when I'd just gotten it. It has worked for almost a week without problem. I did nothing special but travel home.
SPECS:
A500 Wifi
Rooted (was unrooted when it first happened); rooted now using IconiaRoot v1.3
(previously rooted and unrooted with Gingerbreak which would no longer root)
ROM: Honeycomb 3.1 with Virtuous Picasso v.1.1.0
Kernel: 2.6.36.4-UNITY-V5-ge7dee2a-dirty
Thanks in advance.
it's a known problem with this tablet when moving from one access poin to another, introduced with the update to 3.1. you have to reset using the pin hole near the micro USB port. i use a staple.
it may take a few tries. if it never works, there's a specific file you can delete if you're rooted. if you cant do that, you will have to do a device wipe.
There is a known issue of connecting to PEAP/EAP networks, which most work networks are. After connecting successfully, often many times, it will suddenly fail to connect. It also shows the signal from the access point to be very low or non-existent. After this happens, it can also cause problems with other PEAP/EAP access points as well.
If this is what happened to you, here's the fix. Try to connect to the access point giving you problems. While it is stuck on trying to connected, click the access point name and tell the tablet to Forget it. Then enter the same access point information manually and try to reconnect. This fixed my problem, and the fix sticks for a few weeks or so until it comes back.
Interesting, I had this same problem a few weeks ago when I visited my parents house. After a couple reboots it just started magically working again and didn't think anything of it. Their router is whatever the Verizon FiOS people install when you get their service.
Thanks, GeekGuy and Falkner, but.....
I've tried both before, but I went ahead and tried both of your recommendations again (pin reset and connection attempt/forget/add). Neither fixed it.
I would like to try to delete the file that Falkner mentioned, but you didn't specify a name and/or location of it. Can you share that?
I could never find what file to delete, so I've just installed a new ROM (thanks to XDA for info on all the how to stuff).
We'll see if it repeats.
Gone from V.Picasso v.1.1.10 with HC 3.1 to Taboonay 2.1 with HC 3.2.
Thanks for the attempted help!
Just guessing but I would say your problem is solved since no reply from yesterday?
Per my last post, I've switched ROMS. As it happened randomly before, I can only wait to see if it happens again. I will post back if it does.
And....as of tonight it happened again.
Note: Different ROM working since the last post 9-26-11.
ROM Taboonay 2.1
The only thing I can wonder about is if it happens when it tries to connect to a network that is actually down such that it cannot obtain an IP that actually gets internet access. However, it was "disabled" when I brought it up before ever trying to specifically reconnect to a network to realize the ISP wasn't doing their part.
Still....no reboots, or hardware resets have worked. I'm working on an image restore of only the system from the 9.25 install of the ROM rather than a factory data reset. Not sure if that would have been better. Trying to save some of what I've done recently. Gonna have to get used to a weekly backup if this is to continue.
Grrrrr..........restoring a backup turned out to be the last ROM. After reinstalling Taboonay 2.1, I still had all my apps and found the same problem. I'm doing a factory data reset as it's the only thing that fixed it before :-(
The only "oddity" I've experienced has been since last Thursday. The Android Market doesn't even recognize now that I have another device. Have communicated with them; they are investigating and saying they have received reports of this on free downloads giving an "unable to process purchase" message. It updates installed apps, but I cannot download any new ones through market, appbrain -even the appbrain app only and not to the market app. I can download through Amazon, so it's the Market issue. Still, that shouldn't affect this issue.
If you have any constructive feedback, I'd appreciate it!
This was happening to me. I had problems with every rom I tried until the following combo: Taboonay 2.2 with Richard's Villain ROM 3.7 kernel. Every other combo would lead to erratic wifi...now it hasn't happened in 2 days. I don't know why this is happening as many of the roms I tried claim to have the wifi fix integrated. I hope this helps. Just flash the latest Taboonay and then the kernel zip file on too of it. By the way, latest rabbinate is 2.2....NOT THE ONE YOU HAVE NOW.
Sent from my A500 using xda premium

One solution to Android Wifi "Error" or "Turning on..."

Hello everyone,
I found the solution on another forum (GalaxyTDM's post) and I wanted to share it over here because it's a PITA.
Symptoms:
1. None of the wifi toggle buttons work to turn on wifi.
2. When examining the wifi settings, the status will show either "Error" or "Turning on..."
3. If it sits on "Turning on..." for any longer that 2 minutes, it will probably stay in that state.
4. If it changes to status of "Error," it may work after several times attempting to turn it back on from the settings screen.
Apparent cause:
1. Memory is low on the device. Examining the RAM Manager, one can see less than about 45MB free of memory. This apparently is preventing the wifi from starting. Either that, or there is some other program or setting that has crept in and needs to be killed.
I found this to be the case on my device, memory was hovering at about 40MB free and wifi was sitting on status "Turning on..."
Solution:
1. Go into the RAM Manager and do a level 1 clear of the memory. If that doesn't do it, do a level 2 clear.
After I did a level 2 clear, about 80MB of memory was freed and wifi immediately connected and I saw the icon on the status bar.
Hope this helps.
Android 2.2.1
Galaxy S
Best,
Christopher
Thanks Dude...
had same problem in my xperia x10 mini pro... running custom cm7 v16... nw okie..
Same issue, but i have 370mb of internal mem avail.
(Sprint Htc Evo) I have tried the revolutionary meth. followed steps, manually flashed, due to boot loader stating that S-On, i have superuser app, retried with same problems, but anyways that's another problem I am working on solving.
I have had the WiFi Error problem since I first tried to root a few days ago, I am going to attempt to download and install ram manager via usb. But like i stated i have 370 mb of internal memory available. Any other ideas or solutions?
Not Working
Non of it working . Everytime i need to restart my phone if i want to turn on the wifi back.
had a similar issue....always wondered what the problem was
Yes!
I have a Galaxy S (T-Mobile Vibrant) running 2.2 and it worked for me. Memory was at 45 MB. I cleaned up about 20 MB and tried again. It worked. Thanks!
I solved my wi-fi error problem by flashing EZGINGERBREAD ROM.
Old G1 dream
EASY !
Same problem GS2
dirtyrob said:
(Sprint Htc Evo) I have tried the revolutionary meth. followed steps, manually flashed, due to boot loader stating that S-On, i have superuser app, retried with same problems, but anyways that's another problem I am working on solving.
I have had the WiFi Error problem since I first tried to root a few days ago, I am going to attempt to download and install ram manager via usb. But like i stated i have 370 mb of internal memory available. Any other ideas or solutions?
Click to expand...
Click to collapse
Same issue, 700mb free on Galaxy S2. Have tried multiple ROM's incl. CM7 [2.3?],Slim [4.0.4],MIUI [4.0.3], all with the same problem. WIFI continuously says "Turning on....".
The only other 'USEFUL' piece of info I've found on this is a changing a mac address on a blade phone thread saying "data/misc/wifi folder you have a file called athSavedEeprom.bin" I have no such folder or file which may be a problem.
tks
thanks. useful info.
Hi guys.
Ik don't own a SII, so IDK if this works for you also.
Open your dialer and type *#*#526#*#*
Your phone will go into Engineering Mode and reload the driver.
Apologies if this is old news, but it does the trick for me !
coby kyros mid 7010 wiFi network connection problem
Dear All,
I'm new here. please advice me. i needed your help. i got coby kyros mid 7010, which was gifted to me by my brother. it is working fine. but the only problem is wifi connection. when i try connecting to a working wireless network connection, it keep on tying and then disconnecting. but the same connection is working with my laptop. please help me what to do....
Thanks in advance
I usually click wifi off, wait for a couple of seconds and try again and that solves the problem.
Is there any other way to fix WiFi error issues? I have a Vodafone Smart Tab 7 / ZTE 71A.
It was working fine with CM10 port, but then I tried to flash Paranoid Android Jellybean which failed to boot; so I rolled back to CM10 however it appears WiFi has stopped working.
It gets stuck on "turning on...", and would crash/reboot the tablet sometimes, or just give the "Error" message...
I have tried recovering back to standard and also flashing back to stock ROM however still no luck!
It normally gives that when it can't see the wireless card, first check if blue tooth works, the wireless and bluetooth are normally bundled together.
If it does work thenstart from fresh, wipe everything apart from the sd card and installed a recommended rom, fingers crossed that'll sort out any software issues.
I had this exact problem on my old DHD, the problem was I dropped it and the wifi antennas popped off.
Sent from my HTC One X using xda premium
thnkx
Sent from my GT-I9100G
Thanks Cristobalmiguelo, I had this problem on my old phone. Sometimes after long use of the phone I couldn't connect to wifi and as you wrote, it stayed forever on "Connecting". Restart always helped and in fact, that phone had only 256MB RAM and I always had hust around 30MB free.
also have wifi error
i have the same problem on an att samsung rugby smart since i installed updated kernel and when i go into wlan test it says noset driver loaded and everything fails on the status i wish i could redo my phone to out of box state
thanks For Share :good:
i have the same problem with my samsung s2, it's showing error when access portable wifi hotspot, i have just wipe dalvik cache and wipe cache partition but it doesn't work, any idea please ? :crying:
Kernel Issue?
I believe this can be a kernel issue as well. I just came across this issue after flashing a new kernel. Flashed old kernel. All seems fine.

[Q] Wifi won´t activate on stock 4.2.2/cm 10.1

Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.

[Q] Why does my Wifi & Bluetooth not working even with stock rom?

Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!

Phone's wifi&bluetooth dead

Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
try this rom
follow the guide completely
http://forum.xda-developers.com/oneplus-2/general/rom-hydrogenos-v1-2-0-sensors-t3264711
araaraara123 said:
Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
Click to expand...
Click to collapse
Earlier today, my fingerprint sensor/home button completely stopped working.
I tried restarting, wiping cache and dalvik cache, re-installing the ROM, and I even went back to OOS and H2OS (both stock ROMs) to see if it would work. Alas, nothing worked.
A friend of mine then called me. I told him my home button is dead. He told me it happened to him once, and all he had to do was force restart the phone and it worked again.
I'll suggest that you try the same.
Hold the power button for ten seconds while your phone is on and it'll force restart.
Hope this fixes your problems, mate!

Categories

Resources