I lost CFW LUMA 11.2 (BS9 installed) after updating 11.4

Discussion in '3DS - Flashcards & Custom Firmwares' started by Aliik, May 28, 2017.

  1. Aliik
    OP

    Aliik Member

    Newcomer
    17
    0
    May 21, 2017
    France
    hi everyone !
    I thought it was safe to update with BS9 installed just I updated my 2DS
    I completely followed the 3ds guide and even updating to bootstrap9. It worked perfectly.
    Then I decided to update from 11.2 to 11.4
    Now when rebooting I lost payloads and when appearing on home menu, I can see my stuff but when touching it said " download from eshop"

    did I lose my CFW ?
    Is there a way to go back ?
    i have all my nand backup

    thanks in advance
     
  2. sora10pls

    sora10pls Official GBAtemp Trashâ„¢

    Member
    172
    196
    Oct 25, 2015
    Canada
    If they're in .bin format, they can not be loaded by Luma3DS 7.1 onward, as it's B9S exclusive (.firm format only).

    Ensure inside SD:/luma/payloads/ you only have files with the .firm extension.
     
  3. Aliik
    OP

    Aliik Member

    Newcomer
    17
    0
    May 21, 2017
    France
    thank for reply
    I know all of that. My luma payloads were all in .firm

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

    it was working fine! by pressing selected button, i could load whatever payload I want, now it's all gone. I even did the transfer of boot.firm into sysnand ctr...and luma file into sysnand rw...
     
  4. Quantumcat

    Quantumcat Dead and alive

    Member
    11,821
    6,350
    Nov 23, 2014
    Australia
    Canberra, Australia
    What happens when you hold Select on boot? (Press it before pressing power).
     
  5. Aliik
    OP

    Aliik Member

    Newcomer
    17
    0
    May 21, 2017
    France
    nothing happens, whatever I use select or start on boot.

    cfw is completely gone :(
     
  6. Quantumcat

    Quantumcat Dead and alive

    Member
    11,821
    6,350
    Nov 23, 2014
    Australia
    Canberra, Australia
    So you definitely followed 3ds.guide in the past and had either a9lh or b9s? Impossible to lose your exploit just by updating. There's something you're not telling us.

    Either you :
    - restored a NAND backup using Decrypt9 without the "keep a9lh" option, or GodMode9 without the "safe" option,
    - never had a9lh/b9s and instead only had menuhax,
    - were using Gateway on sysNAND mode
     
    KunoichiZ, a9lh-1user and KiiWii like this.
  7. Aliik
    OP

    Aliik Member

    Newcomer
    17
    0
    May 21, 2017
    France
    nonz of your three options.
    i did have gateway but i had emunand for it
    now i trying to follow the 3ds guide but when mounting it cannot copy savedata because the fat image is 60 kb and the savadata from dsi sudoku is 64 kb :(
     
  8. Quantumcat

    Quantumcat Dead and alive

    Member
    11,821
    6,350
    Nov 23, 2014
    Australia
    Canberra, Australia
    Which page and step are you on exactly? I'm not super familiar with the DSiWare installation guide, but this could help someone else.
     
  9. NoNAND

    NoNAND GBAtemp Advanced Fan

    Member
    684
    156
    Aug 22, 2015
    Ireland
    Pikachu City
    Well this is the "ultimate bootrom exploit" guy. :sleep:
     
    toto621 likes this.
  10. Aliik
    OP

    Aliik Member

    Newcomer
    17
    0
    May 21, 2017
    France
    It is working now
    I followed the 3ds guide. => it worked. => am on cfw 11.4
    Then, I simply restore with godmode9 (safe) and got back to 11.2 (working perfectly)
    I turned out when I push select button, I didn't see I had tick autoboot on emunand / enable emunand firm when booting with R (I was tired, I guess) / show nand in setting....
    The previous hack was still there, i could navigate and see boot.firm and luma payloads were there in sysnand ctrnand.

    So i guess, either after updating if one of those options is enabled, it simply disable cfw luma and its chainloader.

    or
    my second thought is when putting luma/ payloads (Godmode, emunand9, hourglouss, gateway.bin etc...) files in sysnand ctr, perhaps it is messing with