R4iSDHC Gold Pro 2015 firmware expire.

Discussion in 'R4 DS' started by olshrimpeyes, Sep 3, 2015.

  1. olshrimpeyes
    OP

    olshrimpeyes Your question is bad and you should feel bad

    Member
    454
    283
    Jul 30, 2015
    United States
    GNU/Somewhere
    I bought a Gold Pro 2015 from http://www.r4isdhc.com/ and its been okay until today when a error message popped up that the firmware expired. It was remedied by setting the date back on my DS, but I don't want have to set the date back on my 3DS. Is there anything I can do?
     
  2. Pedro Vieira

    Pedro Vieira Member

    Newcomer
    18
    2
    Sep 3, 2015
    Brazil
    Same problem. Was wondering if I can change some line in the firmware files so I don't have to wait for the next one when this happens
     
  3. Rezatron

    Rezatron Advanced Member

    Newcomer
    81
    8
    Oct 12, 2012
    Canada
    They will update the kernel in a few days to fix this issue. You can work around this by setting a date in your system settings to any date before September 3 2015. Fixing the kernel yourself would require hex editing or FPGA programming there is no easily changed line in a settings file for this.
     
    Technicmaster0 likes this.
  4. WaffleWafer

    WaffleWafer GBATemp Novice Lurker

    Member
    239
    120
    Aug 1, 2015
    Mexico
    Works flawlessly.
     
  5. Pedro Vieira

    Pedro Vieira Member

    Newcomer
    18
    2
    Sep 3, 2015
    Brazil
    I see. Well I'll wait for their fix patiently then. Thanks
     
  6. NuttyS

    NuttyS Advanced Member

    Newcomer
    67
    24
    Apr 30, 2015
    Reading, UK
    So glad I'm not the only one with this problem!

    Will there really be an update though? The last one was last year =/
     
  7. Rioluwott

    Rioluwott GBAtemp Advanced Fan

    Member
    650
    92
    Feb 23, 2014
    Mexico
    i have the same problem but in a r4i sdhc dual core 2014 i already downloaded the latest frimware but it doesn´t work im going to wait for now im going to set the date to 2014
     
  8. NekoKat

    NekoKat Advanced Member

    Newcomer
    85
    20
    Oct 18, 2013
    Mexico
    Ah, I remember this happened last year as well. Exact same date, too, if memory doesn't fail me. Last year, they had the firmware update 2 days afterwards (September 5th), so chances are the same is going to happen again this year.

    ...why does this firmware expire thing keeps happening though?
     
  9. Adeka

    Adeka Beta Tester

    Member
    4,127
    1,284
    Mar 19, 2013
    United States
    tested in 3ds and i get this error. does not get this error in dsi.

    — Posts automatically merged - Please don't double post! —

    double post because I found the fix. Set your 3ds date back to 2014
     
  10. NekoKat

    NekoKat Advanced Member

    Newcomer
    85
    20
    Oct 18, 2013
    Mexico
    Yeah, having it on any date before September 3, 2015 will do the trick.

    Last year, this EXACT same thing happened, that's why the last update was last year, September 5, 2014.

    What I wonder is why this firmware expire thing keeps happening on the 3DS...? It's strange. Quite strange.
     
  11. Adeka

    Adeka Beta Tester

    Member
    4,127
    1,284
    Mar 19, 2013
    United States
    I have the 2012 model (says new on the sticker) but it runs wood firmware (its a clone im pretty sure). It never has this problem.

    The funny part is the card arrived in the mail yesterday. Planned to give it to my sisters boyfriend to reinstall rxtools.
     
  12. NekoKat

    NekoKat Advanced Member

    Newcomer
    85
    20
    Oct 18, 2013
    Mexico
    as long as his sysnand's date is any day prior September 3, 2015, it'll do the trick anyway. For running rxTools.

    Once you have an emuNAND on yer console, I dont think date on sysnand matters anymore, does it? Much like languages (english in emunand, spanish in sysnand in my case).
     
    elmuchogamer likes this.
  13. NuttyS

    NuttyS Advanced Member

    Newcomer
    67
    24
    Apr 30, 2015
    Reading, UK
    Odd that your dsi doesn't get the error as mine does, as does my Mum's xl.
    We've done the date trick for now and remembered to set Animal Crossing to the proper one before starting up!
     
  14. CKCésar000

    CKCésar000 Newbie

    Newcomer
    1
    0
    Sep 4, 2015
    Brazil
    I am thinking in use an alternative firmware to fix this, but i can't found anyone... I want keep with today date to continue playing PKMN online :/
     
  15. Technicmaster0

    Technicmaster0 GBAtemp Psycho!

    Member
    3,144
    648
    Oct 22, 2011
    Gambia, The
    There are no alternative firmwares and the team programmed into the kernel that it can expire. Normally it shouldn't expire.
     
  16. Rezatron

    Rezatron Advanced Member

    Newcomer
    81
    8
    Oct 12, 2012
    Canada
    New kernel update 3.6b is up on the official site now. Just tested and new expiry is September 3, 2018. Seems so pointless just delete the expiry date or if they can't/don't know how make it the year 2500 of whatever. :rolleyes:
     
    NuttyS likes this.
  17. kuwanger

    kuwanger GBAtemp Regular

    Member
    227
    89
    Jul 26, 2006
    Well, testing and the key seems to be R4.dat. Doing a diff of R4.dat v3.4 -> v3.5 gives me:

    Warning: Spoilers inside!

    And a diff of R4.dat v3.5 -> v3.6 gives me:

    Warning: Spoilers inside!

    Disassembling the earlier area and it seems to be adding up a 32-bit value in to a register and I presume is some representation of a time (based on the value seeming getting larger each newer version). Trying to direct hexedit the value and it gets stuck at the "Loading ..." screen. Further, the second part seems almost random and I presume is either an encrypted something or a hash. I've not done enough testing but simply changing the third part (the version string) and it'll boot fine so I presume whatever the check is, it's not done over the whole file.

    In short, I'll look further into it and perhaps work something out. But if anyone else happens to recognize a pattern to this that I don't and could help, it'd be appreciated.

    PS - One big hint that I don't see any "expired" string in R4.dat makes me think that it's the firmware that is doing the checking. It's why I haven't been so quick to try looking further in the disassemble, even if it might contain the key checking code.
     
    ihaveamac and Rezatron like this.
  18. NekoKat

    NekoKat Advanced Member

    Newcomer
    85
    20
    Oct 18, 2013
    Mexico
    So they're intentionally programming this expiring thing? Damn...

    Eugh, too bad I know nothing about programming.
     
  19. kuwanger

    kuwanger GBAtemp Regular

    Member
    227
    89
    Jul 26, 2006
    Not really much progress made so far. I've gotten as far as figuring out that my PS was wrong. R4.dat includes the "Loading ..." as one big image and although I still don't understand how it constructs it it generates the strings in memory (with 6-bytes between each letter) which I presume (probably incorrectly) has something to do with multi-language support. In any case, the code is copied to WRAM and so the actual hash/decryption/whatever check seems to reside at 0x2035344 (in ROM 0x8035544); this was all deduced by taking a memory dump and figuring out where the relevant "hash" was copied into RAM and then searching for where its memory address is used.

    Unfortunately, I'm not sure how much real progress I'll make from here. As much use as No$gba's debugger has been, it really has a long list of unfortunately quirks that make it less useful given its intended audience. Even if it were perfect, the real issue is the real hardware will obviously play differently, so it's very slow going. I'll still keep trying, but again if anyone else is interested... Unfortunately, with a 2018 deadline it's hard to be TOO motivated to a solution.
     
    Sleet likes this.