• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [rooting involved] Wifi causes reboots

M

Mofus

Newbie
I posted this in another thread, but thought it might deserve it's own thread...

My phone reboots when I am at home with the wifi on. I cannot reproduce it anywhere else. Sometimes it will go for hours without a reboot, and sometimes it'll reboot repeatedly until I can turn off the wifi on the phone. I do not get an error code, but it generates a huge error log that gets sent to HTC. Of course, the Sprint store won't do anything about it. They said contact HTC.

So, after pouring through the error log I found some error references. I took screen caps, but heres a bit of what it says:

wcnss_8960: crash shutdown : 0
modem_queue_start_reset_notify
Rebooting in 5 seconds..
Going down for restart now
arch reset: mode 104
set_modem_efs_sync: wait for modem efs_sync
Unable to handle kernel paging request at virtual adress 80c448b0
pgd = c0004000
[80c44b0\ *pgd=0000000
internal error: Oops: 5[#2] PREEMPT SMP
Modules linked in: prima_wlan(P)
CPU: 0 Tainted: P D W
(3.0.8_01360-g3fd0422 #1)
PC is at_kmalloc_track_caller+0x10c/0x22c
LR is at should_fail+0xbc/0x158

I did a factory reset, and it still reboots. I rooted/unlocked and installed a new ROM and it still happens. I changed the channel on my router. No help. I have a newer Airport Extreme base station, and an old mushroom base station as a network extender. I have unplugged the second base station, but I still get reboots.

Any ideas/help would be appreciated.
 
Generally, when you flash a new ROM and problems persist it means it is hardware related and not software related. Did you wipe system before flashing?


I don't know why sprint would refuse to replace it.
 
No. I wiped the previous day, but not during the ROM install. I'll try that when I get home. One of the reasons I chose FreshROM was because I didn't have to wipe...I guess I was being lazy. But now that I have TB and nandroid available wiping isn't a big deal.
 
If your ever having issues a full wipe is always recommended. I'd even throw in a superwipe to make sure its all clean
 
Glad you started a new thread as I was about to do the same.

EarlyMon I hope we can keep this separate from other threads because I think this is a somewhat different scenario and I dont think a lot people are experiencing this specific problem.
I have checked other forums and there is not a lot of reference to wifi causing reboots.

Below are links to my posts in the other thread.

http://androidforums.com/htc-evo-4g-lte/571106-random-shutdowns-help.html#post4574852

http://androidforums.com/htc-evo-4g-lte/571106-random-shutdowns-help.html#post4575284

http://androidforums.com/htc-evo-4g-lte/571106-random-shutdowns-help.html#post4578017

http://androidforums.com/htc-evo-4g-lte/571106-random-shutdowns-help-2.html#post4622307

http://androidforums.com/htc-evo-4g-lte/571106-random-shutdowns-help-2.html#post4624351
 
I just spoke to a sprint technician and was told they have no references on this topic.
He did however suggest that I return the phone to Bestbuy for a replacement and he also created a service ticket for me in case of any issues with Bestbuy.
So if anybody else has this problem please contact Sprint CS and let them know about it, because if they are not aware then the problem cant be fixed.

Thanks
 
Well, if no one else is going to chime in, I can't cross-reference, so I'll just toss this out from the basement days of wifi -

Once upon a time, there was a unix DHCP software stack that collided miserably with one from one particular router, unfortunately, the most popular model used by Cox Cable at the time. Both sides pointed fingers (having to do with _very_ arcane interpretations of one phrase buried in the spec) - and while they did that, all sorts of heck was suffered.

From that log slice above, the kernel panicked on a bad memory reference, and I'm just going to guess that it may be caused by the same sort of DHCP nonsense (a stretch because I'd not seen it in probably over a decade).

We used to have the ability to specify a fixed IP address to get around this sort of thing - seems gone in Sense 4.

All I can suggest is trying settings, wifi, advanced, best wifi performance.
 
Interesting about the Cox thing, as I do use Cox as my ISP.

Just to be clear this happened before I rooted, and persists after rooting. I did Superwipe and installed Viper's rom. I thought it solved the problem, but about 24-hours later it started doing it again.

I'll have to figure out a way to get HTC to fix this, or exchange my phone for a new one. Sprint won't help unless I pay them $35 and leave it with them for a month (their words).
 
If it's being caused by a DHCP problem it would be great if it were more robust, but if the root cause is on an odd router, HTC won't fix it because they can't - all that they could do is put up a different failure mode.

Rooting and romming is extremely unlikely to fix this, as all kernels are the same now.

Any chance that there's a firmware update available for your router?

Fwiw, the unix side was made more robust back in the day, but the determination came down against the Cox router, per the maker supplying it.
 
I doubt there is a router firmware update available, but I will check. I just upgraded my router about 6-months ago to a docsis 3.0. I doubt calling Cox would be of any use because I can't really point to any specific problem caused by them.

Since I killed my Google Wallet, maybe I can parlay that into a new phone one day.

Thanks for your help.
 
EarlyMon, thank you for your attention to this thread.

I went back to completely stock and dropped my phone off at the Sprint store because of the GW secure element issue. According to the Google rep they should give me a new phone. So, if I don't have the issue anymore when I get home I'll know it was a hardware issue (assuming I get a new phone.) If it still happens it's my network. I'll let you know.
 
Well after updating my phone today, while online using wifi just reading stuff the phone froze tried to use the back button and the phone rebooted creating the usual abnormal reset message.
This is my third phone, don't know what to try next.
 
My wife's One S just started getting this same error / reboot behaviour, immediately after the 60mb Telus system update. No such problem before. She is not rooted and is connecting to a Apple Airport Extreme v7.6.1. "Best WiFi Performance" was already checked. She has switched her default launcher to Apex (pro v1.2.5), so I'm going to stick to just Sense for awhile to see if it's an incompatibility there. If that changes nothing, I'll try connecting to a different router.

(I realize this is a different phone... since it's the same behaviour I thought this data may offer a clue).
 
I got a brand new phone and it still froze/rebooted before and after the ota update, and again after rooting. It must be my Airport Extreme base station doesn't like my phone. Any recommendations on a new wireless router?
 
I am currently using a suggestion from someone on another forum and so far I am getting better download and up load speeds.
I will let you all know how I am doing with reboots.

Their suggestion is get into your router settings and set to " G " mode only.
 
I've the same problem in my xperia u.
It isnt related to the router..because wifi, bluetooth and wifi hotspot all of them lead to the rebooting cycle
Tried alot of roms..No effect
Sometimes it works fine..sometimes its back and then i've to wipe data to use normal phone without wifi.
 
You must log in or register to reply here.
Back
Top Bottom