I just got my Rezound and got it perm rooted and tried unsucessfully to make wifi tethering work.
I then tried to install CWM and all seemed fine but Wifi stopped working.
When I enabled Wifi I would get scanning then error.
I hard reset it and now I simply got an error.
I am not using a custom Kernal unless CWM installed one (I kind of doubt it)
Please help.
Bump
Please help
My WiFi is also broken. I'm perm root with Ziggy's kernel (Vigor GB Kernel) and Ching'ys rom (Ineffabilis v1.0). In Ziggy's thread it states that the WiFi error is due to the rom, not the kernel. Chingy's thread states that the WiFi error is due to the kernel not the rom. there are people using stock kernel and Chingy's rom with working WiFi.There are people using Ziggy's kernel on stock rom with WiFi working.Ii have tried wiping and re flashing. Still nothing. Anyone help would be great!!
Envy Nixon said:
My WiFi is also broken. I'm perm root with Ziggy's kernel (Vigor GB Kernel) and Ching'ys rom (Ineffabilis v1.0). In Ziggy's thread it states that the WiFi error is due to the rom, not the kernel. Chingy's thread states that the WiFi error is due to the kernel not the rom. there are people using stock kernel and Chingy's rom with working WiFi.There are people using Ziggy's kernel on stock rom with WiFi working.Ii have tried wiping and re flashing. Still nothing. Anyone help would be great!!
Click to expand...
Click to collapse
If you have an Error under your wifi in settings, that means that you need to reflash the kernel. You will generally need to reflash the kernel AFTER the rom to get the wifi to work.
I have heard that its related to the Kernal not the Rom in all my readings. Unfortunately that does nothing for me since I havent changed the kernal or the rom all I have done install CWM and tried to get Wifi Tethering working. It broke sometime when I did those two things.
Have you gone back to stock on the Kernal? I have heard all over the place that people are having boot loops and wifi errors with Ziggy's Kernal. If you continue to have problems I would try the Kernal. I have never heard that a ROM has broken Wifi.
Envy Nixon said:
My WiFi is also broken. I'm perm root with Ziggy's kernel (Vigor GB Kernel) and Ching'ys rom (Ineffabilis v1.0). In Ziggy's thread it states that the WiFi error is due to the rom, not the kernel. Chingy's thread states that the WiFi error is due to the kernel not the rom. there are people using stock kernel and Chingy's rom with working WiFi.There are people using Ziggy's kernel on stock rom with WiFi working.Ii have tried wiping and re flashing. Still nothing. Anyone help would be great!!
Click to expand...
Click to collapse
BTW I am going to try RUU now to see if I can get it working by going back to stock.
Related
I've searched the forum for a sollution to no avail and since I can't post this in the actual ZMOD 003 thead (low post count) I was wondering if anyone else is having the same problem?
When I start up the Wifi on my X10 I am just met with "Error".
I've reflashed and fully re-installed the .71 baseband, ROM and 003 update and this had happened each time (after first phone reboot I think).
I'm otherwise really pleased with the ROM (full camera, 6+ days battery, etc), is there a sollution?
SOLVED: Downgrade busybox to 1.17.1 (re-install by the andriod installer back to the older version) and reboot.
Assuming you have a custom kernel ... After flashing the cm7 zmod rom, try flashing the wifi modules to match your kernel, then reboot phone and wifi should work.
Had this problem on a few of the roms I've tried, got into the habit of installing the wifi modules immediately after installing any rom I try, before rebooting into the new rom for the first time.
Sparhawk
u can also try it with static ip.
Z3US911 said:
u can also try it with static ip.
Click to expand...
Click to collapse
It's not that it won't connect but the Wifi won't turn on no matter what I try. I've tried this anyway but with no sucess.
Sparhawk76 said:
Assuming you have a custom kernel ... After flashing the cm7 zmod rom, try flashing the wifi modules to match your kernel, then reboot phone and wifi should work.
Had this problem on a few of the roms I've tried, got into the habit of installing the wifi modules immediately after installing any rom I try, before rebooting into the new rom for the first time.
Sparhawk
Click to expand...
Click to collapse
Ok thats sounds like some good advice. Noob question but where could I get the wifi modules for zdzihu's custom kernel? Or do you mean flash the default wifi modules? Also do I just install them through xrecovery, I'm a little lost?
Seems like I'm not the only one having this problem:
http://forum.xda-developers.com/showthread.php?t=1135475&highlight=zKernel+wifi+module&page=81
help anyone, im lost without my wifi.
edit:
Busybox seems to be the issue, I downgraded from 1.19.2 (i think) back to 1.17.1 and the wifi went straight back to working on reboot.
Problem seems to be solved, for now. I now have the perfect ROM.
Need to know is anybody else experiencing this kind of problem.
I unlocked bootloader, installed proper kernel and wifi modules.
First had Lion's rom and got network error every time while searching for networks, so I thought that was rom problem. After I installed Alexander's miui, I had the same problem. It's not modules and kernel problem, cause I tried OC and non-OC versions and it's the same.
And booting time is forever, I mean like 2-3 minutes.
Any help is appreciated..
*bump
Anyone?
Which baseband?
Baseband .71
Have you tried flashing the kernel then NOT flashing the Wifi modules? I used it for a few days without flashing the Wifi mods and used Wifi regularly... then I flashed the Wifi mods and had the same errors you're getting.
Deviantelf said:
Have you tried flashing the kernel then NOT flashing the Wifi modules? I used it for a few days without flashing the Wifi mods and used Wifi regularly... then I flashed the Wifi mods and had the same errors you're getting.
Click to expand...
Click to collapse
WiFi is fine, network error is problem.
But I'll try, maybe it will work.
So here's an interesting situation.....let me preface this by saying I know exactly what I'm doing when it comes to flashing things.
I started out running RezRom 1.0, with Ziggy's kernel. I got no problems, no errors. Then I decided to try out Chingy and Newt's ROM Ineffabilis, which comes with the stock kernel. I flashed the new ROM, then the stock kernel, then Ziggy's kernel using Con247's auto installer. When I booted up, I got no Wifi connection. When I went into Wifi settings, it just says error, nothing more. So I went back to the stock kernel, and the Wifi came back.
Then I restored my Nandroid of RezRom, just to see what would happen with Ziggy's kernel there. Reinstalled Ziggy's kernel on RezRom, no problems. Flashed the stock kernel on RezRom, same Wifi error. Bizarre. Back to Zig's kernel, Wifi is back.
Thoughts anyone? Why would the stock kernel not work on one ROM, and Ziggy's not work on the other?
Evo4gLI said:
So here's an interesting situation.....let me preface this by saying I know exactly what I'm doing when it comes to flashing things.
1:I started out running RezRom 1.0, with Ziggy's kernel. I got no problems, no errors. Then I decided to try out Chingy and Newt's ROM Ineffabilis, which comes with the stock kernel. I flashed the new ROM, then the stock kernel, then Ziggy's kernel using Con247's auto installer. When I booted up, I got no Wifi connection. When I went into Wifi settings, it just says error, nothing more. So I went back to the stock kernel, and the Wifi came back.
2:Then I restored my Nandroid of RezRom, just to see what would happen with Ziggy's kernel there. Reinstalled Ziggy's kernel on RezRom, no problems. 3: Flashed the stock kernel on RezRom, same Wifi error. Bizarre. 4:Back to Zig's kernel, Wifi is back.
Thoughts anyone? Why would the stock kernel not work on one ROM, and Ziggy's not work on the other?
Click to expand...
Click to collapse
I am going with...
1: When you flashed ziggy's kernel you skipped a step or some small thing happened to cause an improper flash. You may have forgot to flash a file or the wrong one. (you have to flash 2 files, the kernel .zip file and .img file, if you are using a kernel different than what the ROM is designed for) This meant that when you went back to the stock kernel everything was fine.
2: You already had ziggy's kernel running properly in rezROM before making the backup, so restoring the backup and flashing ziggy's kernel meant everything was golden.
3: You forgot a step or flashed the wrong kernel .zip, pretty easy if you are juggling two different kernels and their respective .zip and .img files.
4: Going back to the prior kernel fixed the issue caused by 3.
The whole custom kernel setup for non S=off phones is a pain.
Nvm sorry about that
Evo4gLI said:
So here's an interesting situation.....let me preface this by saying I know exactly what I'm doing when it comes to flashing things.
I started out running RezRom 1.0, with Ziggy's kernel. I got no problems, no errors. Then I decided to try out Chingy and Newt's ROM Ineffabilis, which comes with the stock kernel. I flashed the new ROM, then the stock kernel, then Ziggy's kernel using Con247's auto installer. When I booted up, I got no Wifi connection. When I went into Wifi settings, it just says error, nothing more. So I went back to the stock kernel, and the Wifi came back.
Then I restored my Nandroid of RezRom, just to see what would happen with Ziggy's kernel there. Reinstalled Ziggy's kernel on RezRom, no problems. Flashed the stock kernel on RezRom, same Wifi error. Bizarre. Back to Zig's kernel, Wifi is back.
Thoughts anyone? Why would the stock kernel not work on one ROM, and Ziggy's not work on the other?
Click to expand...
Click to collapse
I know on the thunderbolt, sometimes if you flashed a kernel, it broke wifi. Wiping the wifi settings fixed it. You could do it with a terminal emulator, but we had an app from adrenaline.
You just need to re-flash ziggy's kernel and that should do the trick.
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
Hi, been trying to flash the faux kernel on my girlfriends amaze. No matter what I do, it comes back with an error. I am s-offed and unlocked and using 4ext. Tried the flash img gui app and that returned an error of missing a file. I have redownloaded over and over, as well as tried different versions of the kernel, all with the same error. This all started because her phone kept rebooting my router and thought it might be tied to the ics wifi problem. Anyone have any ideas? I was able to flash android revolution, but viper would not boot. With revolution, it still reboots my router, but it is still using the htc kernel, so would like to try a different one. Any help would be appreciated. Thanks!
Edit: Saw something that was mentioned in a thread while doing another search: a "First time Kernel for Amaze", but the link didn't work. Do I need to do this first or what?
Well, got everything working. What I had to do was flash an insecure kernel, then I could flash other kernels. Unfortunately, the wifi problem is still there. As soon as I turn on wifi on the phone, my router reboots. Haven't been able to find any info on this. Anyone have any ideas on this issue? Currently using latest viper rom with faux kernel 31. Also, anyone recommend maybe a different rom that might fix the issue? Any others with sense 4 and Bluetooth working? Thanks.
New Kernel?
Been trying to flash the faux kernel myself with the status 7 assertion boot image error. What kernel did you flash first? And did you have to reboot and go back into recovery to flash the faux kernel?
Thanks!