Weird R4 Firmware.bin dump

[moon_rabbit]

https://gbatemp.net/threads/proof-t...hc-carts-are-literally-the-same-carts.514539/
At some point, they all look like the same card.
but different layouts existed before that.
Finding compatible firmware can be tricky.

https://gbatemp.net/threads/flashcard-firmware-backups.481268/
This link has a lot of firmware, but I don't know if they have backups of cards with the same layout.

 

[Jammyjoe05]

https://gbatemp.net/threads/proof-t...hc-carts-are-literally-the-same-carts.514539/
At some point, they all look like the same card.
but different layouts existed before that.
Finding compatible firmware can be tricky.

https://gbatemp.net/threads/flashcard-firmware-backups.481268/
This link has a lot of firmware, but I don't know if they have backups of cards with the same layout.

ok I will give this a shot but I fear the problem is the cart not actually being registered anymore. I wonder if it is bricked bricked instead of "wrong software" bricked....

 

[moon_rabbit]

https://github.com/ntrteam/flashcart_core/issues/27#issuecomment-338188590
It's an incomplete dump, but it's the same board (B2-v1.1).
You can try to restore it and use ysmenu.
https://github.com/ntrteam/flashcart_core/files/1401842/r4idump.zip
The file address is wrong because the repository has moved.
kitling -> ntrteam

https://github.com/ntrteam/flashcart_core/issues/14#issuecomment-339474098
https://github.com/ntrteam/flashcart_core/files/1416199/backup.zip
This is B5-v1.1, but appears to be a perfect dump.


It's certainly not like many existing firmwares that start with “20130628ver-6201”.
These firmwares are all identical except for the fact that 0x3000 to 0x3003 and 0x3060 to 0x3083 are different.
But I've restored other firmware and it works fine, so I don't think it's necessary parts.


------------------
https://web.archive.org/web/2017022...-of-R4i-SDHC-V1.4.1-Update-for-DSi-1.4.2.html
https://web.archive.org/web/20110606095417/http://www.r4i-sdhc.com/downloade.asp
If the installer supports card swapping, you may be able to recover.
Or maybe on a DSI, 2DS, or 3DS with hacked firmware.

 

[Jammyjoe05]

https://github.com/ntrteam/flashcart_core/issues/27#issuecomment-338188590
It's an incomplete dump, but it's the same board (B2-v1.1).
You can try to restore it and use ysmenu.
https://github.com/ntrteam/flashcart_core/files/1401842/r4idump.zip
The file address is wrong because the repository has moved.
kitling -> ntrteam

https://github.com/ntrteam/flashcart_core/issues/14#issuecomment-339474098
https://github.com/ntrteam/flashcart_core/files/1416199/backup.zip
This is B5-v1.1, but appears to be a perfect dump.


It's certainly not like many existing firmwares that start with “20130628ver-6201”.
These firmwares are all identical except for the fact that 0x3000 to 0x3003 and 0x3060 to 0x3083 are different.
But I've restored other firmware and it works fine, so I don't think it's necessary parts.


------------------
https://web.archive.org/web/2017022...-of-R4i-SDHC-V1.4.1-Update-for-DSi-1.4.2.html
https://web.archive.org/web/20110606095417/http://www.r4i-sdhc.com/downloade.asp
If the installer supports card swapping, you may be able to recover.
Or maybe on a DSI, 2DS, or 3DS with hacked firmware.

OH you're a star, Thank you!!

I just downloaded them all! I will try these all out now. Also, forgive me I have just had a three hour pure math exam so maybe I'm not as sharp right now, but, in terms of using the chip programmer... provided I use your parameters you suggested, is it just a case of flashing the entire dump to the chip as is?

Also, I was doing some googling and couldn't find anything totally conclusive... Hotswapping is something that works on modded DSi's? I have an ACE3DS+ so my question is for the hot-swap to work, do they need to be identical?

Also what was unclear to me, even on the guides for this was what to do with the kernel. They say that you need the kernel files on "the SD" but does that entail the flashcart that isn't being flashed too?

 

[moon_rabbit]

OH you're a star, Thank you!!

I just downloaded them all! I will try these all out now. Also, forgive me I have just had a three hour pure math exam so maybe I'm not as sharp right now, but, in terms of using the chip programmer... provided I use your parameters you suggested, is it just a case of flashing the entire dump to the chip as is?

Also, I was doing some googling and couldn't find anything totally conclusive... Hotswapping is something that works on modded DSi's? I have an ACE3DS+ so my question is for the hot-swap to work, do they need to be identical?

Also what was unclear to me, even on the guides for this was what to do with the kernel. They say that you need the kernel files on "the SD" but does that entail the flashcart that isn't being flashed too?

I've tried several times, but updates via NDS seem to require the same card.

When the programmer arrives, try each firmware.
It's a 2MB eeprom and each firmware is written at a time.
The file I linked is not a separate file, it is an incomplete dump, so there are multiple dumps.

 

[Jammyjoe05]

I've tried several times, but updates via NDS seem to require the same card.

When the programmer arrives, try each firmware.
It's a 2MB eeprom and each firmware is written at a time.
The file I linked is not a separate file, it is an incomplete dump, so there are multiple dumps.

I noticed when I downloaded it, there were lots individual files. I see, thats annoying but understandable. I gave some of the firmwares you linked a go and they successfully restored, but they would not boot. Whenever I boot, I get the same error (CRC invalid) which leads me to believe that the firmware files may be the correct ones, but the card won't actually flash, and definitely requires a programmer.

When my programmer arrives, I will give it a shot however, is there not a risk of slowly degrading the EEPROM?

 

[moon_rabbit]

I noticed when I downloaded it, there were lots individual files. I see, thats annoying but understandable. I gave some of the firmwares you linked a go and they successfully restored, but they would not boot. Whenever I boot, I get the same error (CRC invalid) which leads me to believe that the firmware files may be the correct ones, but the card won't actually flash, and definitely requires a programmer.

When my programmer arrives, I will give it a shot however, is there not a risk of slowly degrading the EEPROM?

I'm wondering what exactly is crc invalid?

EEPROMs typically have a lifetime of 100,000 writes and 20 years of data retention.
Unless it's a problematic product, environment, etc, it should last for decades.

As long as it's fully validated using a programmer, it should be fine.

 

[Jammyjoe05]

I'm wondering what exactly is crc invalid?

EEPROMs typically have a lifetime of 100,000 writes and 20 years of data retention.
Unless it's a problematic product, environment, etc, it should last for decades.

As long as it's fully validated using a programmer, it should be fine.

ok that addresses my EEPROM concerns. I don't actually know what is invalid. when I first dumped it, I made a copy of the rom it uses to load itself and opened it with dsbuff. it wouldnt open with NSMBe, and when I looked, it reported an invalid CRC thing. Also whats confusing me is initially, the card would appear as "Miami Nights", but now the flash dumps suggest "Bomberland Touch!"?

I don't know for sure but I think the card is spoofing a different game and the firmware header doesn't match anymore.
but I also have no idea what I am talking about too, so all I can do is use logic here :|

I am at a point where I don't think I can progress until this programmer arrives, but I cannot resist trying to make this work tbh.

Post automatically merged: Jun 5, 2024

I'm wondering what exactly is crc invalid?

EEPROMs typically have a lifetime of 100,000 writes and 20 years of data retention.
Unless it's a problematic product, environment, etc, it should last for decades.

As long as it's fully validated using a programmer, it should be fine.

When I boot it as I always used to do with NTRLauncher I get a white-screen then a small red string of text at the bottom which expresses "ERROR: CRC HEADER INVALID".

 

[Jammyjoe05]

MX29 series looks different from a regular SOP-8 EEPROM.
Neoprogrammer will show you how the chip should be connected to the CH341A.
It's easy to get if you google it.


View attachment 440560

The MX25L1635D looks like a normal spi25 connection.

If you have the same card, it will be easier to recover.
I don't expect firmware on the internet to be much different.
Didn't get any firmware?

I have tried everything... and I am currently trying G-Flash. The chip identifies itself automatically but when Flashing it doesn't want to work:

I have no idea what I am doing to be honest, but it didnt work in ASProgrammer or NeoProgrammer- when flashed in either of these two, it would register as flashing successfully however, would fail to verify. the chip would also return back a completely different readout to the backup that was used to flash it too. This is been attempted now on Mac and windows so I am a bit lost!

edit: I tried again with verbose logs enabled and this is what it output:

 

[moon_rabbit]

I have tried everything... and I am currently trying G-Flash. The chip identifies itself automatically but when Flashing it doesn't want to work:
View attachment 442272
I have no idea what I am doing to be honest, but it didnt work in ASProgrammer or NeoProgrammer- when flashed in either of these two, it would register as flashing successfully however, would fail to verify. the chip would also return back a completely different readout to the backup that was used to flash it too. This is been attempted now on Mac and windows so I am a bit lost!

edit: I tried again with verbose logs enabled and this is what it output:
View attachment 442282
View attachment 442362

It is better to use neoprogrammer on windows instead of flashrom.
If your ch341a is not recognized by windows, you will need a usb driver.
They usually come with the programmer files
It's a bit tricky, but it can be solved with programs like zadig or
You can also use another computer or laptop.

If the CH341A is recognized correctly, there may be protection on the chip.
You can try the un-protect function of neoprogrammer.

 

[Jammyjoe05]

It is better to use neoprogrammer on windows instead of flashrom.
If your ch341a is not recognized by windows, you will need a usb driver.
They usually come with the programmer files
It's a bit tricky, but it can be solved with programs like zadig or
You can also use another computer or laptop.

If the CH341A is recognized correctly, there may be protection on the chip.
You can try the un-protect function of neoprogrammer.

Ok well I had too many issues with this programmer which ultimately culminated with it falling off my desk and cracking

This looks promising though so I look forward to trying that!!

I ordered another one but also ordered one of these “EZP” ones which appears to do the same thing. In the mean time I have plenty of Arduino bits and bobs floating about. Would it be possible to use that to flash the chip or is it better to wait for the new programmer to arrive?

 

[moon_rabbit]

Ok well I had too many issues with this programmer which ultimately culminated with it falling off my desk and cracking

This looks promising though so I look forward to trying that!!

I ordered another one but also ordered one of these “EZP” ones which appears to do the same thing. In the mean time I have plenty of Arduino bits and bobs floating about. Would it be possible to use that to flash the chip or is it better to wait for the new programmer to arrive?

https://github.com/Marzogh/SPIMemory
These libraries make it possible.
But I don't know how useful they are because I haven't used them.

Programmers like EZP are not much different from CH341A.
What matters is the coverage and accuracy of the software.

 

[Jammyjoe05]

https://github.com/Marzogh/SPIMemory
These libraries make it possible.
But I don't know how useful they are because I haven't used them.

Programmers like EZP are not much different from CH341A.
What matters is the coverage and accuracy of the software.

Ahh ok. Thank you so much I will look into this

 

[soulpower11]

I am the guy on discord that was having the same problem.

Finally gotten a new SOP8 chip and I managed to restore it back into working condition with a dump I made before messing again.

I am guessing the reason why it didn't work the first time I tried it, is because I didn't erase the chip before programming it.
I attached the firmware dump for anyone who needs it in the future.

 

[Jammyjoe05]

I am the guy on discord that was having the same problem.

Finally gotten a new SOP8 chip and I managed to restore it back into working condition with a dump I made before messing again.

I am guessing the reason why it didn't work the first time I tried it, is because I didn't erase the chip before programming it.
I attached the firmware dump for anyone who needs it in the future.

not joking this might be the only specific working backup on the internet. At least, as far as google and any of the standard method has been able to get me, I have not come across another one!