SOLVED thank you joeykrim
i did the fastboot method below. and just a note for anyone with the same problem, the "command" will vary depending on the location you have the rom's zip file (also unzip to gain easier access to the boot.img file. so the command is "fastboot boot <path to the boot.img file>
i just flashed the 3d synergy nightly build rom to my 3d, but the wifi will not turn on. it simply says error.
what can i do to fix this?
i have read that there is something to do with my kernal, but im not positive what.
evo3d-rooted with htc unlock method
Kernal-2.6.35.13-g84f8edd [email protected] #1 (ie stock, i have not flashed anything other than clockwork and the rom.)
3rdsurfer said:
i just flashed the 3d synergy nightly build rom to my 3d, but the wifi will not turn on. it simply says error.
what can i do to fix this?
i have read that there is something to do with my kernal, but im not positive what.
evo3d-rooted with htc unlock method
Kernal-2.6.35.13-g84f8edd [email protected] #1 (ie stock, i have not flashed anything other than clockwork and the rom.)
Click to expand...
Click to collapse
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allows kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D here are some similar posts:
http://forum.xda-developers.com/showpost.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showpost.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
sorry, im less smart than i thought... what do i need to do? reflash the entire rom, flash a new kernal, or something else
3rdsurfer said:
sorry, im less smart than i thought... what do i need to do? reflash the entire rom, flash a new kernal, or something else
Click to expand...
Click to collapse
Essentially there are three options:
1) Flash a custom kernel through Flash Image GUI which will load the custom kernel and the respective modules allowing WiFi and WiMAX to work properly.
Or similar to option #3, extract the boot.img from the ROM and flash this through Flash Image GUI.
2) Fastboot boot the custom recovery which will then properly flash both the ROM and the kernel at the same time properly. command: fastboot boot c:\android\cwm-recovery.img.
3) Flash the ROM through the custom recovery (booted traditionally), then pull out the boot.img file from the ROM and manually flash through fastboot. command: fastboot boot c:\rom\boot.img
Hope that helps clarify the options along with the commands to have them work properly!
Related
I just did the HTC unlock method and flashed clean ROM's latest developer ROM and my Wimax says "failed to start" and my wifi just says "error"
I also flashed trwp 1.1.1 via fastboot
Any help or suggestions?
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1265666
Try this.
Ths says wifi fix... Will it fix Wimax too?
Sent from my PG86100 using XDA App
Thaxx said:
Ths says wifi fix... Will it fix Wimax too?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
...try it and answer it yourself
Sent from my HTC EVO 3D X515m using xda premium
Thaxx said:
I just did the HTC unlock method and flashed clean ROM's latest developer ROM and my Wimax says "failed to start" and my wifi just says "error"
I also flashed trwp 1.1.1 via fastboot
Any help or suggestions?
Click to expand...
Click to collapse
There is one issue here with two potential methods having triggered the one issue. I keep answering this over and over so I should do a better job of documenting these posts.
The kernel loaded and running, on the boot partition, has to match the modules loaded on the system partition. If the kernel or the modules become mismatched, i.e. first method: a custom kernel is loaded but the matching modules are not, or second method: custom modules are loaded but the kernel is not, WiFi and WiMAX will not work. WiFi and WiMAX are both loaded through modules stored in /system/lib/modules/.
HTC unlock method does NOT unlock write access to the boot partition when booted into recovery mode. HTC unlock method only unlocks write access to the boot partition under three circumstances:
1) Booted in normal android mode - can use my Flash Image GUI app to flash a kernel and load modules. My application does both correctly prevening this mismatch issue.
2) Through fastboot booting the custom recovery, not to be confused with fastboot flashing the custom recovery. The correct command is: fastboot boot recovery.img instead of the incorrect commands: fastboot flash recovery recovery.img or fastboot flash boot recovery.img. This is an engineering "feature" HTC programmed into their unlock method. These create the second method listed above, a custom ROM is loaded which copies over the custom modules but the custom kernel is not allowed to be flashed because the custom recovery was installed/operated incorrectly.
3) Booted into the bootloader/hboot - having the bootloader flash a kernel through PG86IMG.zip or using fastboot flash boot boot.img (this method makes it difficult to install the WiFi and WiMAX modules as it only loads the kernel, modules have to be copied over to /system/lib/modules separately)
Hope that helps!
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
alex62157 said:
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
Click to expand...
Click to collapse
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
WiFi whoes
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
radmanz said:
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
Click to expand...
Click to collapse
My app was designed and only tested on the CDMA version of the EVO 3D, as that is what I own. I never had a tester for the GSM version until today. I hope to release an update to my app in a few hours.
In the mean time, if you follow the 2nd method I listed above, it will work for you as long as you've completed the HTC unlock method.
The HTC unlock method does not unlock write protection for the kernel using the traditional custom recovery boot method.
If you want write access to the kernel with a custom recovery, HTC requires you to fastboot boot the custom recovery.
I posted the command above and will repeat it again as it is the key to properly loading the custom recovery in order for HTC to grant write access to the kernel. The command: fastboot boot c:\cwm-recovery.img
Technical details: When you fastboot boot the recovery image, you're technically not in *recovery* mode. You're technically in a temporary fastboot state. This is a unique feature of the HTC bootloaders not found on Samsung devices (outside of the Google phone, Nexus S). It is only designed to temporaroy boot a *kernel* and recovery is essentially a "dumbed" down kernel.
Appreciate the support and hope that helps!
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
Okay thanx, I'll try the methods..
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
I've tried the 2nd method and now it's working right
thanx alot
alex62157 said:
I've tried the 2nd method and now it's working right
thanx alot
Click to expand...
Click to collapse
Hi alex,
Are you able to tell me what version of CWM recovery image you have used? or even post it online for me to use...
I've tried many different img versions, and it keeps locking up on the HTC boot screen... Also, what kernel have you chosen to get your wifi working again!?!?
RadmanzZZZzzZZZ
I am getting a WiFi error with nearly every ROM I install. I had one that worked but it didn't have a custom kernel and I really want to overclock this phone. I came from 2.3.4 with HBOOT 1.5 and have tried multiple kernels hoping to find one that had a working WiFi module.
Any ideas? I am currently trying Revolution with the same error.
You can only flash kernels thru fastboot on 1.5. Maybe flash image GUI....
Sent from my PG86100 using xda premium
mattpedigo said:
I am getting a WiFi error with nearly every ROM I install. I had one that worked but it didn't have a custom kernel and I really want to overclock this phone. I came from 2.3.4 with HBOOT 1.5 and have tried multiple kernels hoping to find one that had a working WiFi module.
Any ideas? I am currently trying Revolution with the same error.
Click to expand...
Click to collapse
I've answered this question quite a few times in this EVO 3D Q&A board. I think I've got the details down pretty well. I'm going to quote from my post yesterday. Feel free to ask if you have any questions or something isn't clear!
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allows kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D here are some similar posts:
http://forum.xda-developers.com/showpost.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showpost.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
Click to expand...
Click to collapse
Figured it out... Thanks for the replies. Turns out that with HBOOT 1.5, you can't turn s-on into s-off. So when I was flashing kernels using TWRP, it wasn't pushing all the kernel into the boot partition.
So what I did is downloaded Revolution, flashed it in TWRP and then booted into fast boot. Then I used got into a command prompt with the ADB stuff (I already had that from HTC's unlocking method) and pushed the boot.img that came with the Revolution ROM download.
In command prompt, this worked to push the boot.img:
fastboot flash boot boot.img
Booted up and everything seemed to work fine! Even got the 1.8Ghz overclock. Now I know. If anybody encounters this issue and needs further direction, let me know.
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Just what are the steps to doing this?
I have tried everything I could think of and wifi still gives me an error.
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Sofocused504 said:
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
Click to expand...
Click to collapse
Not all of your infmration is easy to follow or understand.
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
If flashing a ROM, pull out the kernel file (usually named boot.img), push to sdcard and flash using Flash Image GUI.
If you're away from a computer and want to flash a kernel, this is a great tool.
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
If you're issues are with not entering a custom recovery mode when following step 3, there are a few options. If you're able to boot into normal android mode w/o any issues and you seem familar with ROM manager, flash the custom recovery again from there.
My app, Flash Image GUI, also offers the same feature, select the recovery.img or PG86IMG.zip file off the sdcard and Flash Image GUI will flash it.
Another option is to flash it via fastboot: fastboot flash recovery c:\downloads\cwm-recovery.img
Hope that helps clarify!
flonker said:
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Sofocused504 said:
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Click to expand...
Click to collapse
If the device does not make it past the splash screen this usually indicates a bad kernel (or ramdisk) or bad flash.
Either flash the same recovery file again or download a new recovery file.
Sometimes a bad flash can occur, usually rare. Sometimes the recovery file can corrupt while downloading, usually rare. But these things do occur.
Good luck!
I got my phone from my buddy and I'm not entirely sure if it is rooted or not.. in the bootloader it says unlocked. Hboot 1.50 s-on. Shooter xc. I have a custom ROM installed but have problems trying to flash new ones. Am I supposed to have s off? I'm very confused please help.
Jamesgr86 said:
I got my phone from my buddy and I'm not entirely sure if it is rooted or not.. in the bootloader it says unlocked. Hboot 1.50 s-on. Shooter xc. I have a custom ROM installed but have problems trying to flash new ones. Am I supposed to have s off? I'm very confused please help.
Click to expand...
Click to collapse
Gaining root is two steps on the EVO 3D. First, must have an unlocked bootloader, which you mention you have. Second, need to have the proper files setup/installed for root. Most custom ROMs have root access properly setup. If you're in doubt, grab my free app, Root Check Basic and it will confirm whether or not root access is properly setup. If you want more technical details around the root setup, grab Root Check Pro.
As for flashing new custom ROMs, there is only one limitation to the HTC unlock method compared with the previous hacked methods of s-off, kernel write access is blocked when booted in recovery mode.
This means there are only two methods you're able to gain write access to loading the kernel with HTC unlock method: fastboot and normal android mode.
1) Normal Android Mode: My application, Flash Image GUI, will allow you to select a ROM or kernel .zip file and it will flash the kernel along with the WiFi/WiMAX modules. If a ROM .zip was selected, then reboot into the custom recovery and flash the rest of the ROM.
2) Boot the custom recovery in fastboot mode which grants it write access to the kernel partition. This requires a computer and the android-sdk with inclues adb and you'll need the fastboot binary. The command for this is: fastboot boot c:\downloads\custom-recovery.img. Once you're in the fastboot boot custom recovery, you're able to load any ROM or Kernel .zip file and HTC grants write access to the kernel partition.
Hope that helps! Good luck!