Integrating a kernel - HTC Amaze 4G

Quick question i am using a custom rom and I have to flash a kernel to get my wifi working. Is their a way to flash it into the rom so i don't have to flash it every time i do a wipe. Sort of out box tweak

---

We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium

---

Binary100100 said:
We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.

---

nofroyo said:
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.
Click to expand...
Click to collapse
That's because the kernel modules are different than the rom modules.

---

So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?

---

nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.

---

Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated

---

nofroyo said:
Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated
Click to expand...
Click to collapse
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable

---

I am going to try it right now.
Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse

---

nofroyo said:
I am going to try it right now.
Click to expand...
Click to collapse
Okay just let me know how well it works for you.
You're a tester.

---

Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job.
hopefully i wont have to reflash the kernel every time i need to wipe haha

---

nofroyo said:
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job
Click to expand...
Click to collapse
Thanks for the update. I don't think that I can set it up any easier.

---

Binary100100 said:
Thanks for the update. I don't think that I can set it up any easier.
Click to expand...
Click to collapse
No worries if you need to test anything else i am willing to test

---

Binary100100 said:
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.
Click to expand...
Click to collapse
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
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/bcm4330.ko (bcm4329.ko is for EVO 3D) . 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 allowing 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 on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!

---

joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
Click to expand...
Click to collapse
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko

---

joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!
Click to expand...
Click to collapse
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)

---

Binary100100 said:
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko
Click to expand...
Click to collapse
Yea, definitely not designed to be flashed by the recovery. They're using unique scripts which could easily be modified to follow the same standards as required by a recovery .zip. In fact, it is very easy to package up one .zip file which will do both, be flashable in recovery but also contain all the files and scripts to be flashable from a desktop via adb/fastboot.
Appreciate the link and info. Made it very easy to narrow down the issue!
Will definitely keep this in mind. Good to see/know there are some unique kernel .zip files be distributed which don't follow the "standards".
nofroyo said:
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)
Click to expand...
Click to collapse
Glad the information helped and appreciate the feedback!