EZ-Flash USA Forum

OK. Please check the folder ez5shell. Do you have the file fpath.bin inside ?

MBMax,
I think the problem some of us were having with doing the update had to do with the way the original post looked yesterday. There were multiple links up on the post - the first set sent you to get Kernel 3.0, but under that was another set of post to get Firmware updates. Those posts were divided into two groups: one for 805 and one for 705. What I think was happening was some people were thinking the links for 805 and 705 were taking them to the new firmware update (that would be 101), but they were not. If they were like me, they were looking for two different links for the Kernel and the Firmware - but you have both the new Kernel (3.0) and the new Firmware (101) in the same downloaded zip file.

So, for anyone else confused by this - download the 3.0 OB1 Kernel package, unzip it and you will find the .nds file to update your firmware to 101 in it (ez5i_firmwreUP_V101.nds). I hope this is helpful to someone else and everyone isn't like "Ya, we already know that" because I did not get it till this morning (I have not updated my card yet so I had not unzipped the files).

Seems that i succeded to update. Now wich files should I delete that are useless fr the card to work? (only ez5i_firmwreUP_V101.nds?) thanks

I haven't done the update yet, but if I understand this correctly you shouldn't need the ez5i_firmwreUP_V101.nds after using it. You also shouldn't need the "logs" file or the ez5sys.bin file (only get rid of this one after using the firmware upgrade to v101) because the new firmware will use "ez5isys.bin" to boot. If I am wrong someone please let me know.

What i would do is not delete the files completely, but move them off the card onto your computer, then try booting. If it does not boot, put the file back. If it does boot then you know you don't need it.

Please forgive my double post. I have a Moonshell problem:

Got Hardware 705 and a DS Lite. Just upgraded to yesterday's 101 firmware and 3.0 Beta Kernal. Mostly okay, but now Moonshell is broken for me. I was running a slightly older build (cannot remember which specifically) until yesterday with same hardware and Moonshell was okay.

Tried reformatting my 8G SDHC with the Panasonic formatter - no help.

I get this scary message both on screen and in /moonshl2/logbuf.txt (where it tells me to look):

Start log file. topsector=2461888 size=32768byte
AppName MoonShell Ver 2.09 stable
Dec 30 2009 14:36:35 GMT+09:00
ARM RVCT3.1 [Build 794]
__current pc=0x0200f1fc sp=0x02803eb0
DLDI: active_interface= 0x02016ea0, ID= EZ5i, Name= forEZ5i.
active_interface->ul_Features= 0x23.
BlockWriteLimitSectorsCount=32.
Boot with DSLite.
Shell_FAT_fopen_Root=/MOONSHL2/VERSION.DAT
Shell_FAT_fopen_Internal=/MOONSHL2/INTERNAL/OVERLAY.DLL
CreateBurstList.
Expand MemMgr array. [System] 0->32
OVM_LoadAfterSystem: load=0x02137b04, exec=0x023a1800, size=0x19eec.
Overlay region loaded.
OVM_proc_MainPass: load=0x0202c704, exec=0x023ed000, size=0x516c.
Overlay region loaded.
Shell_FAT_fopen_Root=/MOONSHL2/MOONSHL2.INI
FAT2: Disabled 64k cluster mode. Start fast mode.
Start FPGA Initializer.
Can not found ROMEO2 cartridge on GBA slot.
strpcmSetAudioVolume64(64);
strpcmSetVideoVolume64(64);
Request RTC data from ARM7.
mainloop.
Boot from NDS card.
RawMem:0, DSBM:0, EZ3in1:0, EZ3in1New:0, EZ3in1Plus:0, M3ExtPack:0, SuperCard:0, maxsize=0.
extmem_Init: Not found extend memory cartridge.
extmem: Extention memory was not found.
Setup default code page is '000'.
Loaded font for your language.
pTextPool used.16kbyte remain.2831kbyte
Succeeded memory optimization.
Language materials count= 386
CreateBurstList.
Get RTC data from ARM7.
Initialize random seed.
Not use EUC table. [/MOONSHL2/UNICODE/cp000.tbl]
ResumeDataSectorIndex=2487808.
strpcmSetAudioVolume64(64);
strpcmSetVideoVolume64(64);
Support formats. /.mp1/.mp2/.mp3/.mid/.rcp/.r36/.nsf/.gbs/.hes/.ay/.sap/.kss/.669/.far/.imf/.it/.med/.mod/.mtm/.okt/.s3m/.stm/.ult/.uni/.xm/.spc/.m4a/.mp4/.ogg/.ikm/.wma/.jpg/.jpe/.png/.psd/.gif/.bmp/.wav/.tta
Check current path. [/Video]
finded. [/VIDEO/]
Set NextProc.
ConvertFull_Unicode2Alias: Not find Unicode file item. [EXTLINK.DAT]

shell_ConvertFull.h:218 ConvertFullPath_Unicode2Alias: #13621: ConvertFullPath_Unicode2Alias: Not found path.

Application halted !!
Please refer [/moonshl2/logbuf.txt]

What do y'all think?

Delete the folder moonshl2 and the file moonshl2.nds. Download the last 2.10 at filetrip.net
Unzip on your PC and launch setup.exe with you microsd inserted. Follow instruction.
Yeah i figured out that also and asked fast6191 to remove those link.
People are so weird, why trying to do complex things when it's so simple to unzip the content of the zip and replace all files ? All is provided to do this update if the ezvi already have the tak icon.

And yes you can delete the firmware nds file, the ez5sys.bin after v101 update. No more required after v101 update.

Awesome stuff here for EZVi, lets hope they continue providing updates for ez5sys.bin or the older versions will become obsolete...

So lets say I run an old kernel (2.0 RC16 or OB11) after updating EZVi firmware to v101, will it brick or simply say ez5isys.bin is missing?

Thanks to all...

I think that is no good idea to run older kernels...

Brilliant!

Thank you.

Already tested. Doesn't start at all.
Once in v101 you have a totaly different flashcart. The ez5i is very updatable you know.
If you do the 101 update, you turn the page of old kernels and begin a new one with, i hope, not much game AP to fix by the team.

so i went back and deleted the romdat folder again, and gave it another go...
All seems ok..so yea I dunno what issue I was having before.

Ya, some times it can be like that. As a computer tech I get stuff like that all the time. I think what happens is people expect it to be more difficult than the EZ team and you guys have made it so they make it be as hard as they expect it to be. Either that or they just don't take time to understand how the things work in the first place and get caught up in just following what they think they read. I know it took me a few days of reading this forum to get the hang of the files and all. And I thank you and the others who explained things and helped me get it down. I guess that kind of explaining is just something that will never end - new users will always need help.

Thank you for all of the help.

Thanks guys - all sorted now

This is exactly why I was confused.

It wasn't your English, Mbmax. I very very much appreciate your help and efforts. I got the update installed fine now.

My confusion was what MasonKnightHawk explains.

Thanks for confirming that its possible to update from a NDSi running DSi Menu 1.4.

Now i just gotta remember wher the h*** i left my DSi.

But in the meantime i was wondering if a clean rom thats been trimmed will work the same way as a 100% untouched rom.