OOT3dhack issue

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

  1. codemartin
    OP

    codemartin Newbie

    Newcomer
    9
    1
    Aug 1, 2008
    United States
    hello I just recently got a new 3ds with firmware with firmware 11.0.0-33u and I am having issues running oot3dhack. Now I also have powersaves.

    So I grab the starter kit from here http://smealum.github.io/3ds/ and unzip the file onto my sd card. Boot.3ds is in the root of my sd card along with the 3ds folder. So I have that setup I grab the latest powersave files from here https://github.com/yellows8/oot3dhax/releases/tag/09-15-16 and using power saves put the save file on my game. Run the game I see the hax file open it up hit a get a black screen for a few seconds saying I think the robin is ready....and then it crashes back to my home screen.

    Any advise or help?

    Thank you very much.
     
  2. Sketchy1

    Sketchy1 gbatemp's shadiest warez dealer

    Member
    1,426
    340
    Aug 9, 2016
    United States
    Are you sure your not on 11.2? They only have the ropbin for 11.1 and less and oothax only crashes if your using the wrong payload in the cart.

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

    Plus, double check your actually loading the n3ds payload onto the cart. There is a difference, just double check plz
     
  3. Xiphiidae

    Xiphiidae [ˈzifɨˌdeɪ]

    Member
    2,034
    986
    Sep 13, 2009
    Australia
    The 11.1 payload works on 11.2.

    Double check that you're using the save file for your region, system version and system type (Old/New).
     
  4. jupitersj

    jupitersj Advanced Member

    Newcomer
    55
    20
    Oct 10, 2016
    United States
    I had weird issues with my 11.1 n3dsxl, oot3dhax would always crash me out to home menu with error screen, even though I used the ABXY trick to delete the cart first before installing the hax. I noticed I originally had 3 save files, so I installed the payload in slot 1, ABXY, then slot 2, ABXY, then slot 3, ABXY delete. Finally I reinstalled the payload to slot 3 again, and now the oot3dhack worked.

    It still crashes on me if i click the touch screen, the ocarina, etc. but if I interact with the sign next to Link's bed with the A button, it works everytime.
     
  5. codemartin
    OP

    codemartin Newbie

    Newcomer
    9
    1
    Aug 1, 2008
    United States
    hmm thanks for your responses I"m on 11.0.0-33u firmware. using here I see the file is u_25600_usa so going back here https://github.com/yellows8/oot3dhax/releases/tag/09-15-16 I select the matching powersave and upload that to my cart. Open up the game see the hax file in slot 1 launch the game see link hit a on the control pad. The game crashes see a back screen with some text for a bit think it says robin is ready is ready then bam back on my homescreen.
     
  6. Xiphiidae

    Xiphiidae [ˈzifɨˌdeɪ]

    Member
    2,034
    986
    Sep 13, 2009
    Australia
    Make sure that you're using the right file for your console type (Old/New). Also note that oot3dhax won't have a 100% boot rate, so be sure to try a number of times before concluding that it doesn't work.
     
  7. codemartin
    OP

    codemartin Newbie

    Newcomer
    9
    1
    Aug 1, 2008
    United States
    good advise however I'm using new and making sure i'm selecting new. Also I've tried oh about a dozen times so far and sadly still no good.
     
  8. codemartin
    OP

    codemartin Newbie

    Newcomer
    9
    1
    Aug 1, 2008
    United States
    Hello I see this thread is basically dead however thankfully I was able to figure it out. Just posting this here so if others are having a similar issue they can see the answer. Well I'm embarrassed to say it was a PEBKAC error. I was picked the wrong save file. I was selecting POST5_U_25600_usa_9221 when I should have used N3DS_U_25600_usa_9221 for the save file. Same file one for O3DS one for N3ds it loaded the file and delte the save file on load but it never opened up the homebrew app. Thankfully its fixed.