Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
benny6812 said:
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
Click to expand...
Click to collapse
If it helps, i accidentally formatted the PDS partition a while back and the reason for reboot is AP KERNEL PANIC
Any help would be greatly appreciated.
I am having similar problems. Just last night my phone started rebooting frequently after having turl's v8 build of cm9 for probably a week and it was working great. However, now I have tried wiping everything, putting on different cm7 or cm9 builds and what I have come to the conclusion is anytime I turn the WiFi on, it reboots.
It is not even connecting to anything, just turning it on makes it reboot. I was on the .36 radio with this issue, I tried using the .37P radio and it did not fix it.
Does anyone have any other ideas to try and fix?
Benny,
Do you get the option to turn it on? I'm on cm9 and it'll show up like the attached after it reboots.
No. I dont have that screen. It just says wifi error and Bluetooth crashes as well....
Sent from my MB860 using XDA App
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
bassmarkie said:
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
Click to expand...
Click to collapse
But, how come whenever I flash a new rom, the WiFi will work temporarily, i.e. it would connect, obtain IP etc for a few minutes then just not work until I reflash?
Surely that is not hardware?
Bump
Sent from my MB860 using XDA App
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Drakonas said:
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Click to expand...
Click to collapse
Tried all of the above and still nothing unfortunately. Just want to update on symptoms of the phone if that helps:
Everything eventually gets more and more buggy, even recovery is really laggy and slow
Data will stop after a few days use, and only fix that i know of is to reflash
WiFi does not work, it connects for about 30 seconds after a reflash, but then nothing.
Logcat says - Failed to Load WiFi Driver (after reporting WiFi HUNG)
The phone can crash when I plug in the MicroUSB to charge, when it restarts it says AP KERNEL PANIC.
I have tried everything except for flashing via RSD lite, do you think that could work?
Thanks
BUMP,
Any help at all with this unique situation would be very helpful.
Thanks
I am one GPE verizon rom (4.2.2) and my phone was working fine and suddenly its not not getting any service. I tried rebooting, battery pulling, and eve re-flashing the rom but nothing. Can someone help? thanks
I had the exact same problem that persisted for about 9 hours on the stock rom. I'm not saying this is going to work but call up vzw support and tell them about the problem and for my own situation they actually had to fix something for me on their end and before the phone call was over with. Not saying it'll work but it's worth a shot.
Also make sure your modem is the same version as your bootloader (ex: mI1 bootloader, MI1 modem). I've found this is the best and most stable situation.
Good luck.
Ok guys. I browsed through the forums for this but can only find my issue on custom Roms. My issue is with my wife's phone on the Stock Rom. I rooted her phone the other night and since then her phone has no wifi signal til a reboot then her wifi comes back in nice and strong.
Is this a known root issue? Her phone is on 4.0.1, which I believe is the latest firmware for this phone to date. The only thing I did after rooting was, of course, install apps necessary for root and flashed a security program. Nothing else.
Device: Galaxy S3
ROM: Slimkat
ROM version: Slim-4.4.4.build.6-OFFICIAL-5242
Build: slim_d2lte-userdebug 4.4.4 KTU84P 5242 test-keys
Kernel: 3.4.95-cyanogenmod-gd56ed95
I purchased my S3 in April of last year (4.1 Jellybean), and at the time the wifi worked perfectly. After the first (or second?) OTA that was pushed to my device, my wifi started acting up. It would cut out and I would have to cycle the wifi off and back on in hopes it would work again. I have been patient hoping they would push an OTA that would finally fix it. A year or so and a few OTA (I don't recall how many, or which versions) later and it still doesn't work properly, so I decided to finally try a custom rom to see if it would solve the issue. The last stock version of android I was using was the 4.4.2 OTA.
I rooted my device using towelroot, flashed CWM Recovery (CWM_6.0.4.7_Non-Touch_GT-I9300) using ODIN 3.04, then proceeded to flash the Slimkat rom listed above using CWM recovery. The wifi seems to be better, but it still cuts out and is unresponsive even though it says I have full wifi signal. A wifi cycle seems to fix it temporarily, but I'd like to solve this issue.
So as far as I can tell the last working modem I had was stock 4.1 or so. So I guess my question is, can I flash previous modems to try to get a working one with this rom? I have tried using WIFI Fixer from play store, and even with full signal on WIFI I get signal poor, signal hop scan messages spammed. Any and all help would be greatly appreciated!
Would like this thread to be a single thread for all the modem/wifi issues. I see many people(including myself) cluttering up Rom threads with these issues. There are so many different variations of our issues and what bootloader we have vs. how we are rooted.
I'm on original MDK bootloader using TWRP as my recover and have the Verizon S4. I've never had any issues with wifi or bluetooth until I got into HyperDrive Rom around RLS 16. My issues started with no wifi or bluetooth but my hotspot would work. Then I got to the NC2/NC5 modems and lost bluetooth and wifi. The only way I can get everything to work is go back to the retail MDK modem file. Seems all the NC5 and NC2 fixes are for Safestrap. When I install those it messes with my HLOS and I lose sound and have other issues.
So, does anyone have any suggestions on where to start from?
Update: Another issue that I see, is under settings, under my hotspot option, it has "error". Never seen that before.
krazykevin76 said:
Would like this thread to be a single thread for all the modem/wifi issues. I see many people(including myself) cluttering up Rom threads with these issues. There are so many different variations of our issues and what bootloader we have vs. how we are rooted.
I'm on original MDK bootloader using TWRP as my recover and have the Verizon S4. I've never had any issues with wifi or bluetooth until I got into HyperDrive Rom around RLS 16. My issues started with no wifi or bluetooth but my hotspot would work. Then I got to the NC2/NC5 modems and lost bluetooth and wifi. The only way I can get everything to work is go back to the retail MDK modem file. Seems all the NC5 and NC2 fixes are for Safestrap. When I install those it messes with my HLOS and I lose sound and have other issues.
So, does anyone have any suggestions on where to start from?
Update: Another issue that I see, is under settings, under my hotspot option, it has "error". Never seen that before.
Click to expand...
Click to collapse
Very similar problem, if not the exact same problem. I had been fighting it since Hyperdrive 16 like you as well. I just fixed it about an hour ago with the help of some other people on the forums. Here is what I did to fix the problem. I started with the files here:
http://forum.xda-developers.com/showthread.php?t=2487298
I flashed the "MDK Modem+NONHLOS" file in TWRP and booted into the ROM to confirm that everything was working with the radios. Then flashed the standard retail NC5 modem (modem only file) from TWRP and booted into the ROM. All of my radios are working better than ever. I finally have fully functional WIFI and Bluetooth on Hyperdrive 18.1. I can't explain why this works yet; as I just discovered it and haven't had time to research yet. Hope this helps you out. I know half a dozen other people in the forums that I need to share this info with as well.
vonhulio said:
Very similar problem, if not the exact same problem. I had been fighting it since Hyperdrive 16 like you as well. I just fixed it about an hour ago with the help of some other people on the forums. Here is what I did to fix the problem. I started with the files here:
http://forum.xda-developers.com/showthread.php?t=2487298
I flashed the "MDK Modem+NONHLOS" file in TWRP and booted into the ROM to confirm that everything was working with the radios. Then flashed the standard retail NC5 modem (modem only file) from TWRP and booted into the ROM. All of my radios are working better than ever. I finally have fully functional WIFI and Bluetooth on Hyperdrive 18.1. I can't explain why this works yet; as I just discovered it and haven't had time to research yet. Hope this helps you out. I know half a dozen other people in the forums that I need to share this info with as well.
Click to expand...
Click to collapse
Have you turned on and used your hotspot app. Then turned that off and tried wifi?
krazykevin76 said:
Have you turned on and used your hotspot app. Then turned that off and tried wifi?
Click to expand...
Click to collapse
I have; both work very well. Why do you ask?
The last few times that I have gotten my wifi to work, once I tried my hotspot app then went back to try wifi, it was broken. When I hit my wifi quick launch button my hotspot will turn on.
So I finally Rooted my S4; Stock root with the towelroot method. And now the bluetooth won't turn on.