Hi, again! I'm slowly but surely getting a better understanding of EZ Flash IV. Now, I have another question. When writing to the NOR, I know you hit "Select" and let it write itself, but people say it takes a bit longer, and for me it takes about 30 seconds, depending on the file size (between 16-32). When it writes, nothing happens. Does it have to do with me using a micro-SD card and adapter, maybe the cart itself, or am I just missing something altogether? Thanks in advance!
We have a similar thread going on http://gbatemp.net/threads/ez-flash-iv-nor-not-work.361031/
Unbeknownst to me it seems the EZTeam released a new client pack that might include an updated loader, which would be necessary if they changed the NOR chips/read protocols and would also explain what we have been seeing here. More on that thread if you want to try experimenting.
Unbeknownst to me it seems the EZTeam released a new client pack that might include an updated loader, which would be necessary if they changed the NOR chips/read protocols and would also explain what we have been seeing here. More on that thread if you want to try experimenting.
http://www.ezflash.cn/zip/EZ4_2014.zip
In the sysbin directory is a file called ez_flash.bin
If the EZTeam did it properly you can copy that to the root and hold R when booting (make sure there is no ezfla_up.bin in there), it will then use that to update.
If they were slightly more lax then rename the file to ezfla_up.bin (the underscore is important) and use it to update. I would rather not try such a thing on my launch model EZ4 though just in case (I have pulled things back from the brink before and done very silly things but that was before).
If you are on certain newer versions of windows or with certain setups it might not have the .bin part, this is OK though as they are both the same. Alternatively you can uncheck the option for explorer to "Hide extensions for known file types".
In the sysbin directory is a file called ez_flash.bin
If the EZTeam did it properly you can copy that to the root and hold R when booting (make sure there is no ezfla_up.bin in there), it will then use that to update.
If they were slightly more lax then rename the file to ezfla_up.bin (the underscore is important) and use it to update. I would rather not try such a thing on my launch model EZ4 though just in case (I have pulled things back from the brink before and done very silly things but that was before).
If you are on certain newer versions of windows or with certain setups it might not have the .bin part, this is OK though as they are both the same. Alternatively you can uncheck the option for explorer to "Hide extensions for known file types".
Similar threads
