New problem 11.2 New3ds

Discussion in '3DS - Flashcards & Custom Firmwares' started by Stranger93, Dec 15, 2016.

  1. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States
    So I'm running into a new issue. Got OoT hax working with cart I went out and bought (Messed up steel diver transfer from old 3ds). Only problem is, that even though LoE says the exploit was successful, my kernel is still showing up as 2.51 and not 2.50. So when I try to run sysdowngrade it gives me a, "Did not get am:u handle, please reboot."

    What am I doing wrong?
     
  2. jupitersj

    jupitersj Advanced Member

    Newcomer
    55
    20
    Oct 10, 2016
    United States
    Verify that the following:
    • Kernel version: 2.50-11
    • FIRM version: 2.50-11
    • If either of these do not display the versions above, make sure you used the correct NFIRM zip and try flashing NFIRM again
     
    Stranger93 likes this.
  3. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States
    Yeah, They display:
    -Kernel version: 2.52-0
    -FIRM version: 2.52-0

    So the issue should be the NFIRM zip I used? Is there more than one available?
     
  4. jupitersj

    jupitersj Advanced Member

    Newcomer
    55
    20
    Oct 10, 2016
    United States
    Yes, there is separate nfirm files for old3ds and new3ds, and also based on which sysnand version you are currently on.

    If you're using slow/waithax, it doesn't work on 11.2; if you have 11.2 you have to transfer from a cfw 3ds to the one you want to hack, make sure you downgrade NFIRM with dgtool using the correct NFIRM files, old for old, new for new, there is a different package for 11.0, 11.1, 11.2 and each of these packages has a different one for old3ds and new 3ds.

    You need "New 3DS 11.2.0 to 10.4.0" from 3ds.guide if you used the system transfer method, for a New3ds (xl) on 11.2
     
    Last edited by jupitersj, Dec 15, 2016
    Stranger93 likes this.
  5. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States
    yes, I did use the system transfer method. Thanks, I'll give it a shot. Possible problem was, I decided to update to 11.2.0 from 11.0.0 halfway through I think and possibly didn't change it.
     
  6. jupitersj

    jupitersj Advanced Member

    Newcomer
    55
    20
    Oct 10, 2016
    United States
    No worries, everytime I downgraded I forgot to redo Oothax for the firmware I was on lol. Also, before you downgrade the sysnand to 9.2 it's recommended to format the system cause sometimes n3ds will brick. I highly reccomend it. Also, n3dsxl's for some reason usually give a ctrnand mount error after installing a9lh/luma while on 2.1, once you upgrade back to 9.2 again with your nand backup the problem will dissappear.
     
    Stranger93 likes this.
  7. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States
    Success, baby!

    Kernel/FIRM: 2.50-11

    Almost done. Geez, this one was a pain for some reason. Never used this method admittedly though.
     
  8. jupitersj

    jupitersj Advanced Member

    Newcomer
    55
    20
    Oct 10, 2016
    United States
    Yeah it could be nail biting the first time
     
    Stranger93 likes this.
  9. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States
    More frustrating. Usually bang the single system ones out in two hours and I've spent 6+ on this one because of weird errors, or me just not taking a break from it to clear my head.

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

    SO, I'm on section 2 of the 9.2.0 downgrading portion of the guide, successfully completed the downgrade (well at least thats what it says), but in system settings it still shows me being on 11.2. Is this normal?
     
    jupitersj likes this.
  10. Stranger93
    OP

    Stranger93 Member

    Newcomer
    33
    8
    Dec 12, 2016
    United States



    EDIT:I'm an idiot, was pressing x, not y. Not my day. hehe, stupid xbox :P