yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] HTCLittleMonster:
Okay, I've done that, however I'm slightly confused as to the two files that are in the modules folder. In another example of a kernel I have there is:

.placeholder PLACEHOLDER File

bcm4329.ko KO File

But, in the Anthrax folder there's:

bcm4329.ko KO File

bcmdhd.ko KO File

Which format is correct?

I've attached the modified zip as an attachment and would greatly appreciate any help in getting the right structure etc to avoid any mishaps :)

Thanks
[HTC EVO 3D] mrbenji:
Can't flash any kernels

Hi,

So... I bought Flash Image GUI from the Market after I saw one of the kernels I wanted to try out (MiRaGe for the EVO 3D CDMA) recommended it over standard recovery-based installs. I got the following error at the "Dumping kernel and partition image" step:

"Flash Error

While attempting to flash an error occurred: null"

HTC EVO 3D, rooted and S-OFF, and F.I.G. has superuser access. In the end I successfully installed the kernel using 4EXT. Now I'm having trouble with the same kernel and a newer version of my ROM, so I wanted to retry F.I.G. -- still getting the error, with both the Market version and the version I downloaded from here, hoping it was more up-to-date.

Help?
[HTC EVO 3D] joeykrim:
Can you provide a link to the exact .zip file you're attempting to flash? Once I can examine the .zip file I'll know more about the type of issue you're experiencing.

The market version and the version listed should be the same. Appreciate the support!
[HTC EVO 3D] mrbenji:
Thanks for the quick response. Here's the URL for a kernel I couldn't flash : http://xdaforums.com/showthread.php?p=40970354
[HTC EVO 3D] joeykrim:
I downloaded the kernel .zip file, MiRaGe_shooter_kernel_76_05022013.zip, and using Flash Image GUI 1.5.2, from Google Play, I was able to flash and load the kernel w/o any issues in Flash Image GUI. I'm running the stock ROM on my EVO 3D.

I'm not able to find any issues with the kernel .zip file itself. Everything in the file appears to be fairly standard and setup properly.

My only other guess is there might be some type of issue with the ROM you're currently using. What kind of ROM are you running right now?

Thanks for the support!
[HTC EVO 3D] mrbenji:
I've had this problem with the last two versions of Angry Bean, a very solid AOSP 10.1/4.2 ROM.

See, what's weird is that there's no problem installing the kernel using 4ext... but I was under the impression that FIG used a better method for kerninstallation.
[HTC EVO 3D] joeykrim:
I haven't had this issue reported on any of the 20+ Android devices Flash Image GUI supports.

A custom recovery, such as 4ext, doesn't run in the Angry Bean ROM environment while Flash Image GUI does making for an unequal comparison. In some cases, Flash Image GUI will use a better method for kernel installation and has more intelligent logic to analyze the environment than the generic updater-script used by most kernel developers.

Since I was able to flash the kernel using the stock ROM and Flash Image GUI on my Sprint EVO 3D, the issue appears related to the custom ROM. The most likely scenario would be that one of the important system essential tools in the ROM that Flash Image GUI uses has been modified in a non-standard way. Unfortunately, Flash Image GUI only has control over a small and specific environment and has to operate inside the ROM environment.

If there are more reports of this issue on Angry Bean with other kernels from other users, or similar reports from other users on different ROMs, I might be able to gather more information and narrow down the issue. Unfortunately, this is the first report and I'm not able to replicate this issue on my EVO 3D device.

You mentioned purchasing through Google Play, which is a 99 cent USD purchase. If you want a refund, please PM me the account used to make the purchase and I'd be more than happy to return the 99 cents USD.

Thanks for the support and information!
[HTC EVO 3D] masfocus:
Saved my wifi

Didn't know what was going on when I got the wifi error.

I just looked around for a stock kernel for ICS, flashed it and my wifi worked.

Thanks!!
[HTC EVO 3D] joeykrim:
The most common root cause of the WiFi error is that the kernel modules, including for WiFi, are loaded onto the phone separately from the kernel.

While using fastboot, the kernel to loaded to the boot partition but the modules are not loaded to the system partition.. After flashing from fastboot and rebooting, this will usually break WiFi.

While using the custom recovery (S-ON users), the boot partition is blocked but the system partition is not. Creating the opposite situation from using fastboot. The modules are loaded by the kernel portion is not, also upon reboot breaking WiFi.

Both the kernel and the kernel modules are loaded by Flash Image GUI preventing the common WiFi error.

Appreciate the support!!
[HTC EVO 3D] ramjet73:
Isn't it the opposite and only when S-ON, at least on the Evo 3D?

My understanding is that the modules are in the system partition (/system/lib/modules directory) and it's the boot partition that is blocked in recovery for S-ON users but maybe I'm not clear on what you are saying. For S-OFF users it shouldn't be a problem unless they are using 4EXT recovery, leave SmartFlash enabled and don't have a bootable kernel installed.

ramjet73
[HTC EVO 3D] joeykrim:
Yea, thanks and good catch. I meant to refer to fastboot and recovery separately, but appears I accidentally merged the ideas. I've edited the reply to clearly detail the issues from using fastboot and the issues from using recovery on the EVO 3D.

On my mind the last week or two has been the issues with the HTC One and the best way to provide support for it in Flash Image GUI. The main concern being that HTC changed the security policy. Some of those concerns slipped into my EVO 3D post!

Takes a bit of effort to support over 20+ devices in Flash Image GUI and keep all of the varying hardware/software security issues separate! Thanks for the support!
[HTC EVO 3D] xMExHKSx:
Hi, can i flash radio using this app? 1.49.0011 hboot. htc evo 3d gsm. if possible, should i choose the recovery image?
[HTC EVO 3D] joeykrim:
No, application doesn't support flashing the radio. As far as I've seen HTC didn't expose access to the radio while booted in Android mode.

Even flashing the radio from recovery, isn't direct, I think it hands off the process to the bootloader to do the actual radio flashing.

If things have changed or a new method has been discovered, please link me to the thread and I'll research out the new details!

Hope that helps and appreciate the support!
[HTC EVO 3D] feng7521267:
it really helps! Thank u!:good:
[HTC EVO 3D] cobyman7035:
can it work with newest 4.4.2 nexus 5? or only on 4.3 nexus 5
[HTC EVO 3D] joeykrim:
Should work fine with 4.4.2 on the Nexus 5! Let me know if you experience any issues! I work hard to maintain the best support possible for the community!

As this is the Evo 3D thread, I have a dedicated thread for the Nexus 5: http://xdaforums.com/showthread.php?p=48753458
[HTC EVO 3D] Febby:
Thanks for the great amazing application! Ill definitely buy it to support you once I get a new credit card.

I strongly suggest everyone gives this a try! :) I wonder if it works for those folks who have hboot 1.5 and used HTC unlock method... hmmm. It might be good for them.

shot by my EVO 3D running AOSP thanks to empiire and team Xron!
[HTC EVO 3D] Febby:
Bump! I had forgotten to mention it works with Hboot 1.5 lol! Thanks for Joey and others on letting it be known.
[HTC EVO 3D] Rogue Gemini:
I have rooted Hboot 1.5 (HTC Unlock Method) with S-on and was able to flash the Tiamat kernel from this app and then boot to recovery and flash 'decks sense ROM with no pc required, Thanks a ton for this.....makes switching ROMS on the fly possible with HTC's unlock methed. My question is would this find a kernel inside of a ROM's .zip file as well or just a seperate custom kernel .zip?
[HTC EVO 3D] joeykrim:
Thanks for posting back the confirmation!

a separate custom kernel is going to be best. the reason is some of the files in the /system partition *might* pose a conflict.

i will add this to my to do list and run through the code to see if i can tweak it to pull the kernel and necessary files out of a ROM .zip or are bare minimum indicate the location of the kernel it found in the .zip file.

thanks for the feedback and questions! appreciate all the support!
[HTC EVO 3D] koltloveshisevo:
Nice app! I hate flashing through hboot
[HTC EVO 3D] H_R_V:
can i use your approach to flash a kernel on S-On GSM Evo 3D?!
[HTC EVO 3D] hellfire8888:
it say "Sorry current device: htc evo 3d x515m is not supported!" help
[HTC EVO 3D] ricky886:
i have the same problem..

plz help~
[HTC EVO 3D] joeykrim:
Need to have a modified version of the application tested on the GSM version of the EVO 3D. I haven't previously had access to a GSM version to test until now.

Once confirmed all works, will post up an updated version!

Hopefully in the next few hours! Thanks for all the support!
[HTC EVO 3D] joeykrim:
If any EVO 3D GSM users are around, I've updated a test version of my application to support the device. I've also enabled debugging output.

If you could load the application, flash the kernel, then extract/pull the logcat *before* rebooting, that would be perfect!

Logcat can be accessed through adb logcat or through an Android Market application called aLogCat.

Same link in topic for beta versions: http://www.joeykrim.com/evo/files/FlashImageGUI.apk

1) Post link to kernel flashed

2) Post link to your logcat output (pastebin.com) (If you want to keep private, PM me the link)

3) Post whether the kernel successfully changed

4) *Optional* Post a screenshot of the application after flashing showing the log output at the bottom

Thank you to all the help and support!
[HTC EVO 3D] usopen:
FYI, I have been able to flash whatever kernel I want using this. Bcblend, Tiamat, Stock Htc, etc.... I have been able to nand restore any backup, flash new rom after booting into recovery right after flashing a kernel without a single problem whatsoever. I am using HTC's half baked half ass unlock method HBOOT 1.5 S-on.
[HTC EVO 3D] :
Thanks Joey!! This makes life so much more easier switching kernels on Hboot 1.50! :)
[HTC EVO 3D] n_god:
1. I flashed I GSM kernels one by one

2. I can't get logcat because every time GUI data get all my internal storage and I got lots of error and I had to wipe data from CWM

3. all kernels succesfully changed my internel storage status from "900mb free" to "0.40 KB free"

I have Hboot:1.49.0009 (S-ON ROOTED)

Baseband versiyon: 10.53.9020.00U_10.13.9020.08_2M

LOGCAT AND SCREENSHOT ADDED
[HTC EVO 3D] joeykrim:
Wow, interesting. Never heard of this issue on any other device.

The logcat file doesn't contain any information regarding my application. probably a timing issue I'm guessing. Perhaps the logcat wasn't taken after my application ran.

Figured I'd try and duplicate this issue you've experienced.

I tricked my device into being recognized as an EVO 3D GSM device and selected the following EVO 3D GSM kernels all while watching the size of my application's data directory: Crypt0kernel.zip, kkernelv01.zip, kkernelv02.zip, kkernel_v02_cwm.zip, kkernel_v03_cwm.zip and UNITY_V1_shooter_u.zip.

the largest the application's data directoy became in size was 16 MB when it unzipped kkernel_v02_cwm.zip which has a 16 MB boot.img file.

I've added a dialog box and error handling for accidentally selecting ROM files or any file over 20 MB, as no kernel or recovery .zip file should ever exceed that size on our devices.

Hopefully that will prevent the directory size from ever growing larger than at most, 20 MB.

Published the newer version, 1.2.6. OP links updated and Market updated.

Keep the feedback and testing coming! Hopefully all the bugs are worked out now!
[HTC EVO 3D] seanybiker:
Hey man, you sir are a legend. I wish i had more hands so I could give you more thumbs up.
[HTC EVO 3D] Ganii:
Flashed this kernel without problems:

http://leedroid.ftp.rshost.eu/Shooter-Kernels/LeeDrOiD_Evo-3D-GSM_V1.0.0-KERNEL.zip

EVO 3D GSM,Crypt0`s v1.3 ROM,rooted and S-Off via Revolutionary.

Kernel now runing and no problems ;)

I used the Release version 1.2.7 of Flash Image GUI!

Picture above from "n_god" about the app,I don`t have this

problem.
[HTC EVO 3D] mildlydisturbed:
Odd bug

Love the thing so far, but we have an interesting bit odd oddness they noticed over on the VP forums today.

Flash Ziggy's dual-core kernel (from here: http://www.androidfilehost2.com/main/EVO_3D_Developers/Virus/Kernels/2.3.4/ ), it appears to take, system reports it as Ziggy's. You go into system tuner / tweaks, you see 1 CPU.

Flash Ziggy's dual-core kernel from fastboot / recovery (fastboot boot x.img), go into system tuner, tweaks, you see 2 cpus.

Looks like *something* is not completing in an in-android flash, even though the kernel does appear to be sticking.

EVO 3D, ViperROM and VP 3D we're seeing this on.

Also, used version 1.2.3 of FlashGUI if I am not mistaken
[HTC EVO 3D] :
+1 Same here as mildlydisturbed. First 2 pics with only cpu0 is with FlashImage GUI and Second pics are from flashing same kernel via Fastboot.
[HTC EVO 3D] Ganii:
Logcat at pastebin:

http://pastebin.com/tyGVRq7Z
[HTC EVO 3D] joeykrim:
Great feedback and the link helped me figure out what was going on. Regarding the above commands, the kernel will always stick (assuming no memory write protection) with an "in Android" flash. At least I've never seen a scenario when it hasn't on the multiple Android devices I've been exposed to.

The comments are right, there is something different. After doing some research, seems there are two issues, both good and bad news.

First, the good news, I was able to fix a small bug, which I think should fix the majority of the issue.

I've updated the version to 1.2.9 and upload on my personal site and on the Market (links in OP). I'm not familiar with the System Tweaks app used in the screenshots and I didn't see a link. If you could flash the kernel again using my updated version and then double check the results, hopefully the issues will be resolved now.

The second issue, the bad news and this is the first time I've come across this issue. Seems one file, /system/bin/mpdecision is modified in this kernel .zip file. The updater-script is requesting this file be copied over when this kernel is flashed. The only issue with copying over this file is that it is currently being run in the background. Linux won't copy over a file which is currently open and active. Killing the pid isn't helpful because it starts again as it is listed/launched/enforced as a service in init.shooter.rc.

The only way to copy over this file would be while the process isn't active, meaning from fastboot/recovery. Not sure what the changes were made to this binary and whether or not they were required changes. Not sure of the impact, if any.

The only method off the top of my head would be seeing if coding the app to kill the process and then copy over is quick enough to beat the auto relaunch. I'll wait on the testing results before implementing anything on this.

Also, if this is part of a ROM, Infected ROM, these /system/bin files should be flashed as part of the ROM and this might end up being irrelevant.

If you could test again with the latest version of the app, I'd really appreciate it!

Thanks for all the testing and support. Look forward to the results!
[HTC EVO 3D] :
Thank you Joey for the quick response. I can give it a test if youd like as well. I am currently on Vaelpak 3D. Would a recorded catlog be of help too?
[HTC EVO 3D] joeykrim:
Logcat won't be as much help since I cut 90% of the debug output in the final release versions.

Feel free to flash the kernel again using the updated version of Flash Image GUI and hopefully you'll see the results you were expecting .. otherwise I might have to chat with Ziggy.

Thanks for the thorough results and your help testing!
[HTC EVO 3D] mildlydisturbed:
the thing we're using to see cpus is system tuner, tweaks tab, CPU.

Can be downloaded here: https://market.android.com/details?id=ccc71.pmw&feature=search_result

Will try experimenting a bit later - going to hang with the wife for a few
[HTC EVO 3D] :
I just flashed back to stock kernel with the updated version 1.2.9 and it says im stock now and i dont have overclock anymore but both cores are still running like i have Ziggys running.

Edit: Fastboot /recovery to flash the stock as well and apparently both cores are still running like Ziggy's........ I just did a nand restore and im only showing cpu0 in System Tuner, so im back to normal. I wonder if it's just that specific kernel and whatever is in it.

Edit2: flashed ziggys regular no overclock kernel via v1.2.9 and all seems well. Its gotta be something in the dual core kernel that doesnt play well with the app possibly?
[HTC EVO 3D] joeykrim:
No, it is not the application. I think the confusion occurs because Ziggy's kernel .zip file not only modifies the standard kernel and kernel modules, but it also modifies system binary files.

Flashing a stock kernel will not return your Ziggy modified system binary files back to stock. This is why, when you flashed a stock kernel through my application and through fastboot, both cores were still running according to Ziggy's configuration loaded during his kernel flash. His system modified binaries are not replaced by the stock kernel.

Ziggy's kernel .zip file not only modifies the kernel but also modifies system binary files. The Ziggy modified system binary files will remain until a stock ROM is restored. Hence, you didn't see any changes to Ziggy's dual core setup until you performed a nand restore, replacing Ziggy's modified system binary files with your previous versions.

In my opinion, and this is where the lines get tricky in the nitty gritty details, technically I think the kernel .zip file should *only* modify the kernel/ramdisk and associated kernel modules, i.e. WiFi, WiMAX, etc.

The ROM is where modifications to system binaries and other files should be made. Ziggy's kernel .zip file modifies not only the standard kernel and kernel modules, but it also modifies system binary files which should be done in a ROM.

Hopefully the technical analysis makes sense and we all understand there is no *official* standard to where certain modified files should be or should not be placed. My suggestions, I think, would eliminate some confusion as people assume flashing one kernel on top of another will either remove or replace all components from a previous kernel. This is generally the case, but not with this specific Ziggy kernel.
[HTC EVO 3D] :
That makes absolute sense now. Thank you sir! :)
[HTC EVO 3D] RulingCzar:
Very nice, thank you!
[HTC EVO 3D] black2rob:
love it really works.
[HTC EVO 3D] physix:
Internal Storage now less than 90MB.

--deleted--
[HTC EVO 3D] n_god:
I don't have that provlem anymore :) thnx to revolutionary :D

Sent from LeeDroid 3D 2.0.0
[HTC EVO 3D] joeykrim:
Appreciate the positive feedback!

Finally fixed a major bug many users were also experiencing in the custom recovery.

Flashing the Anykernel type kernel on top of the stock signed/encrypted kernel would result in the famous Error 7 in recovery mode and in the "Failed to create ramdisk-img" error in my app.

Spent way too many hours today/tonight working on it but it should be all fixed now.

Stock users should be able to flash all kernels as Flash Image GUI will detect signed/encrypted stock kernels and remove the signature allowing custom kernels to correctly load!
[HTC EVO 3D] Alpine-:
Admittedly, I have not read through this entire thread. I am about to purchase your app, looks well worth it to avoid doing the adb method every time.

One question I have though. Is the functionality/stability of this method unaffected by use of custom ROMs / Kernels. If I did use a kernel, it would probably be Tiamat anyway. I know the app works fine with a stock setup, but are there any issued otherwise I should know about before purchasing? Plays nice with latest TWRP recovery and stuff?

If this app is as good as it seems, you deserve to make some money from this!
[HTC EVO 3D] joeykrim:
Great question. I don't think there are any quirks to using Flash Image GUI.

I've done my best to make it as user friendly and simple to use as possible. I know when I first started out using android flashing kernels/ROMs was intimidating so I've tried my best to smooth out the process.

Regarding purchasing, if you need a refund for any reason, let me know. I have no problems granting refunds. I consider all purchases as donations!

Also, the exact same app version in the market is posted in the OP for free. If you're hesitant about purchasing, use the app for free. You can always purchase later!

Flash Image GUI should work on all EVO 3D (CDMA & GSM) ROMs and along with whatever custom recovery is loaded.

Flash Image GUI should also work to flash all custom recovery's and kernels for the EVO 3D.

If you come a recovery or kernel which doesn't flash properly, post up here, PM me, or email me! I always do my best to answer quickly and work hard to resolve/fix any bugs.

Appreciate the support, feedback and questions!
[HTC EVO 3D] carnivalrejectq:
I keep getting an error when using the app to flash a kernel , i have hboot 1.5 . And when i dont get an error ,after i reboot ,it appears simply that nothing happened and i still have stock kernel. Any help?
[HTC EVO 3D] joeykrim:
I've spent a lot of time adding error checking to the application. The error messages should be very specific and provide helpful insight.

Few questions:

1) What version of the application are you using (found by pressing the menu key->about)?

2)What is the exact error message you're receiving? A screenshot could help too

3) Can you provide a link to the kernel .zip file you're flashing?
[HTC EVO 3D] carnivalrejectq:
http://xdaforums.com/showthread.php?t=1224659

The version is 1.3.1 . Ive tried to flash link above kernel that as well as the TWRP recovery from your op. If i use the zip to that kernel it flashes it , appearing to be successful , and then i check the kernel version after reboot and its still stock. When i do get errors it says "while attempting to flash an error occured: null".
[HTC EVO 3D] joeykrim:
The link you provided shows 7 different STOCK kernel .zip files. Can you specific which exact .zip file presents you with an error?

You say when you reboot, it still shows the stock kernel. I'm a little confused. How do you know the stock kernel didn't flash correctly when you reboot it shows stock kernel information? Wouldn't that indicate it did flash correctly?

You mention flashing TWRP recovery but don't mention the outcome? Did that work?

Thanks for your feedback. I will also be testing these on my device to confirm they work.
[HTC EVO 3D] carnivalrejectq:
O sorry i was reffering to the top link	freEVO 3D-StockKernel 2.08.651.2-3.zip . I just kinda picked it at random to see if i could successfuly flash a kernel with the app. I mean when i go into settings , about phone, software information, and then check the kernel it still says its the stock kernel with a date of august 5th. It doesent say	freEVO 3D-StockKernel 2.08.651.2-3. And no when i try to flash TWRP recovery i get that specified error , i tried to flash with the .img file and the .zip file.