Hacking EZFlash Omega Definitive Edition: Safe Mode always loads/No_Loader_Found

[ssj11mav]

Brand new purchase from the retro gaming repair shop. Worked amazing for 2 weeks and now suddenly it keeps going into safe mode. Tried flashing the kernel+firmware by holding down R after putting ezkernelnew.bin on the root of the SD and it keeps giving No_Loader_Found (see below). Also tried reformatting Micro SD card (4GB Toshiba SDHC) No difference. Really didn't want to have to post here but considering this is a newish product theres not much info via google-fu. I'm gonna try grabbing a new SD card soon to see if it makes a difference but I'm getting scared this is going to be a return/exchange. Any ideas?

 

[Sterophonick]

Try cleaning the pins on your SD card slot, and your SD card with some isopropyl alcohol.

 

[ssj11mav]

Try cleaning the pins on your SD card slot, and your SD card with some isopropyl alcohol.

Just tried, same thing. Also tried some compressed air...

I'll completely reformat a 16GB card I have and report back. It's currently not working but that might just be because it's not formatted correctly (wrong allocation size)

 

[ssj11mav]

New 16GB SD card formatted with 32KB I put the bin file at the root and still doesn't work. I don't understand why it suddenly stopped but I guess I have no choice but to return/exchange now.

 

[Sterophonick]

New 16GB SD card formatted with 32KB I put the bin file at the root and still doesn't work. I don't understand why it suddenly stopped but I guess I have no choice but to return/exchange now.

Oh well. It was worth a shot.
Hope it goes well!

 

[ssj11mav]

Bit of an update. I managed to fix it but I'm unsure if it was the correct way to go. I just took a shot in the dark.

I downloaded the recovery img file that I found on EZFlash's website and even though it was supposed to only be used on the regular EZFlash Omega, it worked on the definitive edition too. From there, once I sacrificed an SD card to a format/write for the img file it FINALLY let me load up 2 boots later while holding R to get the 1.01 firmware for DE reflashed on there.

I had to rename the kernel from ezkernelnew.bin to just ezkernel.bin but it did the trick

What a roundabout way of doing things! From what I read online I thought the "flasher" was built into device so all you had to do was hold R without needing to load up an entirely seperate file. I'm glad I was able to figure it out and hope it helps others in the future!

This also, however, means that the firmware was somehow LOST without me even doing anything... kind of makes me worried.

 

[EZ-Flash2]

Bit of an update. I managed to fix it but I'm unsure if it was the correct way to go. I just took a shot in the dark.

I downloaded the recovery img file that I found on EZFlash's website and even though it was supposed to only be used on the regular EZFlash Omega, it worked on the definitive edition too. From there, once I sacrificed an SD card to a format/write for the img file it FINALLY let me load up 2 boots later while holding R to get the 1.01 firmware for DE reflashed on there.

I had to rename the kernel from ezkernelnew.bin to just ezkernel.bin but it did the trick

What a roundabout way of doing things! From what I read online I thought the "flasher" was built into device so all you had to do was hold R without needing to load up an entirely seperate file. I'm glad I was able to figure it out and hope it helps others in the future!

This also, however, means that the firmware was somehow LOST without me even doing anything... kind of makes me worried.

You have to rename the kernel name every time when you upgrading. until we release a recovery image for Definitive Edition.

 

[BigHard69]

The same thing just happened to mine, but it was completely my fault. I wiped the loader without thinking, so now I'm doing the same thing to upgrade my firmware. I should have been more careful, but at least this workaround works.

 

[EZ-Flash2]

The same thing just happened to mine, but it was completely my fault. I wiped the loader without thinking, so now I'm doing the same thing to upgrade my firmware. I should have been more careful, but at least this workaround works.

You missed this this post

https://gbatemp.net/threads/how-to-make-your-sd-card-to-ez-flash-omega-de-recovery-able.584611/

 

[createthiswaste]

Bit of an update. I managed to fix it but I'm unsure if it was the correct way to go. I just took a shot in the dark.

I downloaded the recovery img file that I found on EZFlash's website and even though it was supposed to only be used on the regular EZFlash Omega, it worked on the definitive edition too. From there, once I sacrificed an SD card to a format/write for the img file it FINALLY let me load up 2 boots later while holding R to get the 1.01 firmware for DE reflashed on there.

I had to rename the kernel from ezkernelnew.bin to just ezkernel.bin but it did the trick

What a roundabout way of doing things! From what I read online I thought the "flasher" was built into device so all you had to do was hold R without needing to load up an entirely seperate file. I'm glad I was able to figure it out and hope it helps others in the future!

This also, however, means that the firmware was somehow LOST without me even doing anything... kind of makes me worried.

Whats the link for the recovery img file? I can't find it

 

[wesmess]

I'M TRYING TO USE WIN32 DISK IMAGER BUT WHEN I TRY TO SELECT omega-recovery.img ON MY MICROSD CARD IT SAYS "Image file cannot be located on the target device". WHAT DO I DO!?

 

[Klappenvanger]

/

 

[Vacko]

Alright boys and girls, I have come to help out as well. After having this exact issue myself and have a heck of a time trying to fix it, I finally found a guide that shows step by step what to do in order to fix this. It looks like the OP has fixed the issue, but I needed a little more direction on exactly what to do and how to do it. Now that I have fixed it for myself, I wanted to post it here. (I cant post URLS so I posted a photo of the URL below.)

For some reason this PDF was far more difficult for me to find than it should have been. This was very simple to follow and completely fixed my issue! (Whew). The only thing I did wrong during this process was that I placed the recovery IMG file inside the SD card that I was using. Make sure to put the .IMG outside of your SD card before you continue on with the guide.

Thanks OP for helping solve this issue! I hope this helps other people that may find this post in the far future. Please let me know if anyone needs any help. Thanks.

 

[Vacko]

Bit of an update. I managed to fix it but I'm unsure if it was the correct way to go. I just took a shot in the dark.

I downloaded the recovery img file that I found on EZFlash's website and even though it was supposed to only be used on the regular EZFlash Omega, it worked on the definitive edition too. From there, once I sacrificed an SD card to a format/write for the img file it FINALLY let me load up 2 boots later while holding R to get the 1.01 firmware for DE reflashed on there.

I had to rename the kernel from ezkernelnew.bin to just ezkernel.bin but it did the trick

What a roundabout way of doing things! From what I read online I thought the "flasher" was built into device so all you had to do was hold R without needing to load up an entirely seperate file. I'm glad I was able to figure it out and hope it helps others in the future!

This also, however, means that the firmware was somehow LOST without me even doing anything... kind of makes me worried.

Thank you!