B9 1.2 ARM9 data abort error

Discussion in '3DS - Flashcards & Custom Firmwares' started by thest, Jun 5, 2017.

  1. thest
    OP

    thest Newbie

    Newcomer
    4
    1
    Jun 5, 2017
    United States
    My 3DSLL is 4.4 with GW(414)
    I had been installed A9, I can successfully boot into sys system( L + power), but when I tryed to boot with emu system( power with no other button) it had an error
    QQ图片20170531164605.jpg
    then I gave up emu system and directly install B9 following this guide
    https://3ds.guide/a9lh-to-b9s
    And I have another error
    QQ图片20170605214353.jpg
    Now I cannot enter system but only D9/godmode/SafeB9Installer/etc.
    My files are latest.

    My question is how can I install B9 rightly? Or how can I roll back to A9 that at least I can enter system.

    I've tryed
    http://gbatemp.net/threads/problem-with-boot9strap-installation.471198/#post-7320771
    and a "b9s-next branch version" method, but it didn't work.

    (I also wonder why my a9 emu system could have that error...)

    And sorry for my bad english. Thank you guys.
     
  2. obito-kun

    obito-kun Newbie

    Newcomer
    3
    0
    Sep 14, 2015
    United States
    the version your using is incompatible with your version of luma try to get the latest version
     
  3. linuxares

    linuxares GBAtemp Psycho!

    Member
    3,285
    1,409
    Aug 5, 2007
    Update your Luma to 8.0 and it will work for you again.
     
  4. thest
    OP

    thest Newbie

    Newcomer
    4
    1
    Jun 5, 2017
    United States
    Thank you but my Luma is already 8.0 and I don't know if there are later versions something like 8.0.x which will fix this problem?
    IMG_5954.png

    I also tryed these option combines, not work.
     
  5. linuxares

    linuxares GBAtemp Psycho!

    Member
    3,285
    1,409
    Aug 5, 2007
    Hmm... you might be missing the firmware.bin file? I'm not sure anymore, ages ago I used Emunand.
     
    thest likes this.
  6. CrispyYoshi

    CrispyYoshi GBAtemp Advanced Maniac

    Member
    1,516
    502
    Mar 20, 2010
    United States
    It could be the firmware.bin, though an even better solution to try would be to perform a ctrnand transfer to 9.2 on sysnand, and maybe even update it to 11.4: https://3ds.guide/9.2.0-ctrtransfer

    Alternatively, if you haven't yet, see if you can move emunand to SysNand: https://3ds.guide/move-emunand

    (imo, if you don't have any data you care about on sysnand, try "Move EmuNand" first)

    EDIT: By the way, how long ago did you upgrade to b9s? Have you already tried Luma 7.1?
     
    Last edited by CrispyYoshi, Jun 5, 2017
    thest likes this.
  7. thest
    OP

    thest Newbie

    Newcomer
    4
    1
    Jun 5, 2017
    United States
    I checked and didn't find a firmware.bin in SD card, where can I get that and where should I put it to? Is this file requires a certain version?
    Thank you, trying~
    I just upgrade to b9s today directly from a9lh but without Luma7.1
    I don't have data on EmuNand so I decide just upgrade to 11.4, good luck for me~
     
    Last edited by thest, Jun 5, 2017
  8. thest
    OP

    thest Newbie

    Newcomer
    4
    1
    Jun 5, 2017
    United States
    It seems work, thank you guys very much!
     
    CrispyYoshi likes this.
  9. Necrogente

    Necrogente Member

    Newcomer
    10
    1
    Jan 29, 2017
    France
    That error is kinda strange, I got it when I was playing Mario 3D Land with a corruption Plugin, normally, the plugin can't crash the 3DS... Only the game