EZ-FLASH new github repos and air kernel release

[sam2895]

Post automatically merged: Jan 15, 2026

Test card ok.
But still white screen when booting game on NOR

Do u have air kernel 1.02 or 1.03?

Post automatically merged: Jan 15, 2026

Test card ok.
But still white screen when booting game on NOR

try plug your gba/nds to charger then format it and write your roms again

 

[Kenpham]

Post automatically merged: Jan 15, 2026

Do u have air kernel 1.02 or 1.03?

Post automatically merged: Jan 15, 2026

try plug your gba/nds to charger then format it and writ your roms again

there's no matter with the power. I also test with charger plug in but still have white screen after booting game. Rarely has a game boot normally, most of the case are white screen or glitch

 

[zspate40]

Is anyone using the Air with an Analogue pocket? It seems to work fine on the latest firmware with standard games but whole point for buying it for me was the play Pokémon rom hacks that require RTC. Currently trying to boot a hack results in glitched textures and then a freeze. Playing these hacks on original gba/nds seems to work fine

 

[ceciel93]

there's no matter with the power. I also test with charger plug in but still have white screen after booting game. Rarely has a game boot normally, most of the case are white screen or glitch

I'm having the same problem with my ezflash air. Are you find any solution? My NOR test is ok, same as yours.

 

[sam2895]

Unfortunately, we lost access to github.com/ez-flash due to the loss of the F2A credential. so we had to recreate a new GitHub account for subsequent code pushes, and along with this change, we pushed out the kernel source code for the EZ-FLASH Air at the same time.

The new ezflash team Github repos is https://github.com/ezflash-team

Don't worry, we're keeping the F2A credentials safety this time.

U should work more on kernel and file fragmentation because when I write many games on nor flash the games start gliching and won't start

 

[sam2895]

All ez flash air kernels are here

 

[m45t3r]

I got the Air kernel to build on Arch Linux here: https://github.com/m45t3r/air-kernel/tree/fix-build.

Sadly after flashing the result kernel it just boots with a blank screen. Maybe because I am using devkitARM_r67 instead of the devkitARM_r53. Anyway the source code above may be useful to someone.

Edit: just an update, the issue seems to be that the built kernel is too big, probably because the fact I am using devkitARM_r67 instead of devkitARM_r53. I made a commit that disabled the support for Chinese characters in the FatFs module and now I got a working (but still broken, e.g., the graphics are garbage) kernel: https://github.com/m45t3r/air-kernel/commit/20390b1bf088c3999200d87a7d724978437d11cd.

The resulting "ezairkernel.gba" needs to be less 1048576 before running the "Link_kernel_image.exe" or my "make link-kernel-image" command, otherwise this will cause the blank screen issue that I described before.

 

[Flame]

I got the Air kernel to build on Arch Linux here: https://github.com/m45t3r/air-kernel/tree/fix-build.

Sadly after flashing the result kernel it just boots with a blank screen. Maybe because I am using devkitARM_r67 instead of the devkitARM_r53. Anyway the source code above may be useful to someone.

maybe this is helpful for @metroid maniac

 

[m45t3r]

I got the Air kernel to build on Arch Linux here: https://github.com/m45t3r/air-kernel/tree/fix-build.

Sadly after flashing the result kernel it just boots with a blank screen. Maybe because I am using devkitARM_r67 instead of the devkitARM_r53. Anyway the source code above may be useful to someone.

Edit: just an update, the issue seems to be that the built kernel is too big, probably because the fact I am using devkitARM_r67 instead of devkitARM_r53. I made a commit that disabled the support for Chinese characters in the FatFs module and now I got a working (but still broken, e.g., the graphics are garbage) kernel: https://github.com/m45t3r/air-kernel/commit/20390b1bf088c3999200d87a7d724978437d11cd.

The resulting "ezairkernel.gba" needs to be less 1048576 before running the "Link_kernel_image.exe" or my "make link-kernel-image" command, otherwise this will cause the blank screen issue that I described before.

One more update: it seems that linking the "image.bin" is not strictly necessary, just renaming the resulting "ezairkernel.gba" to "ezairkernel.bin" also works. This means we can ignore the size limit above. After rebooting the EzFlash Air will ask to update the FW image from V2 to V3, but applying this does nothing (at least it doesn't seem to break the flashcard either).

Anyway, it seems the initial source code release is maybe slightly broken, I noted at least 2 issues:
- Garbage graphics in the NOR rom page list
- If you go to the about menu the kernel seems to crash (I get a black screen)

But at least booting the roms that I already had flashed did work. I did not try to flash a new image with my compiled image though.

Post automatically merged: Apr 5, 2026

More updates: I figured out that it is possible to disable the FW update here: https://github.com/m45t3r/air-kernel/commit/bf43c72cba929d9ebd8c3dc2096943fb812fb32c. So now it will stop trying to update the FW file. I think this logic for update is broken anyway (or actually, it is commented-out for some reason), it seems that the FW versions are hardcoded but it is not checked if the FW is actually newer than the old version, so even if you update the version it will try to update again. Also, the FW update seems dangerous since if a broken "image.bin" is flashed it is very likely the flashcard will become a brick, so it seems more safe to always update from official releases.

About what I said before that "image.bin" not being necessary is not strictly correct. The assets used by the kernel seems to be embedded in "image.bin", so for the firmware to work without the "image.bin" it would be necessary to extract the embedded assets from the "image.bin" and add it to the C source code using bin2c or something similar, otherwise the menu will render in a broken state. I think this is an approach similar to https://gbatemp.net/threads/new-theme-for-ez-flash-omega.520665/.

 

[sam2895]

I'm having the same problem with my ezflash air. Are you find any solution? My NOR test is ok, same as yours.

Ez flash air is a garbage don't buy it, superchis is way better

 

[Darksabre72]

i hope you guys release the kernel for the ez flash omega definitive edition B. the product is great so far.

 

[sam2895]

i hope you guys release the kernel for the ez flash omega definitive edition B. the product is great so far.

The kernel already realeased ,visit ezflash website

 

[Darksabre72]

The kernel already realeased ,visit ezflash website

i meant on their github

 

[sam2895]

EZ FLASH AIR NEW UPDATE :
Firmware 4/Kernel 1.05
1.Updated NOR Management, freely delete and re-burn ROMs.
(no need to delete starting from the last ROM)
Check NOR usage in real time.

2.Updated flashing and reading ROMs compatibility.

Note: After updating FW4 K1.05, FORMAT or completely DELETE ROMs before re-burn on the FIRST use please!!!

 

[VinsCool]

Is the EZ Flash Jr. firmware code still maintained or it's been abandoned since the last update?

Just asking out of curiosity, mine still does work fine but I might need to replace the little battery inside someday.

 

[ceciel93]

I tried to update and always shows crc32 error. Did anyone manage to update?

 

[sam2895]

I tried to update and always shows crc32 error. Did anyone manage to update?
View attachment 580702

works fine for me, try another memory card

 

[ceciel93]

works fine for me, try another memory card

I tried 4 microsd. The 1.04 update dont show that error, just the new update

 

[sam2895]

I tried 4 microsd. The 1.04 update dont show that error, just the new update

try the new update i.e fw 4 k1.05

 

[ceciel93]

try the new update i.e fw 4 k1.05

It's the new update that's causing this error. The older versions don't have this issue.