Tutorial Guide: Recover from Frankenfirmware w/o upgrading to 10.3 or higher

[plusminuspoo]

I tried downgrading my n3ds from 9.9.0-26U to 9.2.0-20U and got an error during the process.

I'm able to do most things it seems, but I can't run EmuNAND (just goes from red screen back to menu).

I can run browserhax and themehax to get back into homebrew. I don't have access to Zelda or that ninja game, or another 3DS. Am I out of luck?

This is my log from downgrade_check:

Title ID 0x0004013000003802
  Expected version 0x1800
  Installed version 0x2006
Title ID 0x0004013000003702
  Expected version 0x1400
  Installed version 0x1804
Title ID 0x0004013000003502
  Expected version 0x1803
  Installed version 0x1c00
Title ID 0x0004003020009402
  Expected version 0x000a
  Installed version 0x0c05
Title ID 0x000400300000f602
  Expected version 0x0802
  Installed version 0x0c00
Title ID 0x000400300000ce02
  Expected version 0x2008
  Installed version 0x2c00
Title ID 0x000400300000cb02
  Expected version 0x0c03
  Installed version 0x1000
Title ID 0x000400300000c902
  Expected version 0x0800
  Installed version 0x0c05
Title ID 0x0004003000009e02
  Extra title
Title ID 0x0004013820000002
  Expected version 0x42e0
  Installed version 0x4f26
Title ID 0x0004013020004202
  Expected version 0x0401
  Installed version 0x0804
Title ID 0x0004013020004002
  Expected version 0x0400
  Installed version 0x1006
Title ID 0x0004013020002202
  Expected version 0x2800
  Installed version 0x2c00
Title ID 0x0004013020001e02
  Expected version 0x1000
  Installed version 0x1401
Title ID 0x0004013020001c02
  Expected version 0x2803
  Installed version 0x3006
Title ID 0x0004013020001602
  Expected version 0x2402
  Installed version 0x2802
Title ID 0x0004013000008002
  Expected version 0x3800
  Installed version 0x4400
Title ID 0x0004013000003302
  Expected version 0x2000
  Installed version 0x2806
Title ID 0x0004013000002f02
  Expected version 0x1c00
  Installed version 0x2006
Title ID 0x0004013000002c02
  Expected version 0x2809
  Installed version 0x3008
Title ID 0x0004013000002902
  Expected version 0x3000
  Installed version 0x3406
Title ID 0x0004013000002802
  Expected version 0x1801
  Installed version 0x1c06
Title ID 0x0004013000002402
  Expected version 0x2000
  Installed version 0x2400
Title ID 0x0004013000001d02
  Expected version 0x2400
  Installed version 0x2800
Title ID 0x0004013000001b02
  Expected version 0x0800
  Installed version 0x0c01
Title ID 0x0004013000001a02
  Expected version 0x1400
  Installed version 0x1801
Title ID 0x0004013000001702
  Expected version 0x3002
  Installed version 0x3806

EDIT:

Since I didn't have any of the recommended things, I thought I would just try to run sysupdater again. It had trouble starting up, but on the 4th or 5th try I got it to boot and pressed Y again to downgrade. This time it went through to the end and rebooted the system after 10 seconds.

So it looks like if you can run sysupdater you don't need Zelda and another 3DS to fix this problem.

now my log file is much shorter:

Title ID 0x0004003000009e02
  Extra title
Title ID 0x0004013000001b02
  Expected version 0x0800
  Installed version 0x0c01
Title ID 0x0004013000001a02
  Expected version 0x1400
  Installed version 0x1801

I think I should be good now

 

[EddCase]

Just a quick thank you, saved my n3DS xl using this thread!

 

[b17bomber]

So during step 1 of installing OOThacks on another 3ds. When you say the model, do you mean of the frankenfirmware one,or the one we're installing? My messed up one is an n3dsxl, while my secondary is a regular 3ds xl.

And since my previous firmware on n3ds was 9.6, I assume it goes New 9.6.0u?

 

[Viary]

Tried to DG my N3ds 9.6 to 9.2.....Got all the way to the downgrade installing Cia and a error occured telling me to reboot. I rebooted and removed then removed sd card and she booted up fine etc. Check system Firmware at it says 9.2 atm. Ran DG checker and I have 24 expected vs installed files flagged. I can currently get homebrew launcher up etc.

Now my question is what should I do next.
Am I screwed or do I need to try to run sys updater again to correct these incorrect files? Or try to see if CFW will work? Thanks!

 

[b17bomber]

I'm sitting in about the same bind as you. With my system, I can get menuhax up and running, but trying to fire up mini pasta either from OOT OR from menuhax results in the same thing for me too.


EDIT: I did end up getting my system out of frankenfirmware - I ended up running the memchunkhax2 based sysupdater again and did a downgrade a second time (for anyone else out there thinking of trying this, take note that this was a last ditch attempt, and I'd exhausted all other ways that I'm aware of to try getting an unsigned cia up and kicking in sysnand, to no avail browserhax, menuhax, ninjhax, and OOThax (I'd try the smash brothers one too, but I actually don't own it)- as per with the first time around, this very well might leave your system in a softbricked, or even hardbricked state...try this at your own risk).

I'm at the same problem. So when you used memchunkhax2 sysupdater. did you do it from frankenfirmware, or did you update back to 10.3?



It's what happens if for some reason (usually without you actually doing anything wrong, and almost exclusively with n3ds's) your system update fails, and you end up with a partially downgraded system. You have part of your original firmware, and part of the downgraded one. This causes some exploit points (and in some cases, nearly all exploit points) to not work as expected.

I'm sitting in about the same bind as you. With my system, I can get menuhax up and running, but trying to fire up mini pasta either from OOT OR from menuhax results in the same thing for me too.


EDIT: I did end up getting my system out of frankenfirmware - I ended up running the memchunkhax2 based sysupdater again and did a downgrade a second time (for anyone else out there thinking of trying this, take note that this was a last ditch attempt, and I'd exhausted all other ways that I'm aware of to try getting an unsigned cia up and kicking in sysnand, to no avail browserhax, menuhax, ninjhax, and OOThax (I'd try the smash brothers one too, but I actually don't own it)- as per with the first time around, this very well might leave your system in a softbricked, or even hardbricked state...try this at your own risk).




It's what happens if for some reason (usually without you actually doing anything wrong, and almost exclusively with n3ds's) your system update fails, and you end up with a partially downgraded system. You have part of your original firmware, and part of the downgraded one. This causes some exploit points (and in some cases, nearly all exploit points) to not work as expected.

I'm having the same problem. When you got this to work, did you update to 10.3 first? The only time I ever was able to get sysupdater to work was after I ran the oothaxinstaller on the same 3ds, then immediately booted to sysupdater when I was on 9.6. But it was a partial downgrade.

 

[gzz251]

mini paste wont launch it sends me back to homebrew

 

[BothyBhoy]

Don't worry about it I appreciate you helping out the community. I went from 9.2 to 9.5 back to 9.2 and it still shows In downgrade check that I have title mismatches,I can however launch reinand as I was always able to. Basically I am right back where I started so CFW works but I have no idea if I have a clean install. Is there anyway to pass the downgrade check,I downgraded from 10.3 so while I can access CFW perfectly fine,I am still a little bit OCD about passing the downgrade checks.

i had similar problem. i reinstalled original emunand.bin which i created at startup then used the fork of reinand by Aurora Wright. that fixed all my problems. Best of luck ......

 

[naivegirl2411]

I would like to use safesysupdater to downgrade from 10.3 to 9.2. The newest sysupdater is without memchunkhax 2 and is said to work better as a cia so should I just stick with safesysupdater (i think its 0.42b) or use the latest sysupdater?

And regarding frankenfirmware... im guessing that not formatting before downgrading would result in frankenfirmware but wouldnt the system essentially fix itself after updating again (updated emunand would still be using titles in 9.2 sysnand frankenfirmware and if you use a9lh you would essentially be repairing sysnand). I would like to know what you think of this @Xoo00o0o0o

Also is the community also 100% for menuhax>ironhax with regards to entry points for sysupdater/safesysupdater as I had a better experience exploiting memchunkhax2 in ironhax than menuhax which didnt work and screen glitched a lot

 

[Arkansaw]

Had to try this after sysupdater (from BrowserHax) failed halfway.

minipasta had no effect, so I just tried sysupdater again and this time it worked without issues. Maybe OOT3D is the safer entry point for this whole downgrade to work

 

[Arkansaw]

EDIT:

Since I didn't have any of the recommended things, I thought I would just try to run sysupdater again. It had trouble starting up, but on the 4th or 5th try I got it to boot and pressed Y again to downgrade. This time it went through to the end and rebooted the system after 10 seconds.

So it looks like if you can run sysupdater you don't need Zelda and another 3DS to fix this problem.

now my log file is much shorter:

Title ID 0x0004003000009e02
  Extra title
Title ID 0x0004013000001b02
  Expected version 0x0800
  Installed version 0x0c01
Title ID 0x0004013000001a02
  Expected version 0x1400
  Installed version 0x1801

I think I should be good now

Had the same results. Downgraded (and recovered) from 9.8.0-25U

 

[link270]

AWESOME!

Thanks for this! It worked! Like most others I couldn't get mini pasta to work, so I just ran safesysupdater and it worked perfectly, downgrade checker got the same log as posted in the OP.

It seems that we should be okay to simply re-run sys updater after this as I've seen a few other people note that. I can't confirm 100% though.

 

[TheDuckMan64]

9.9.0-26E to 9.2.0-20E

Safesysupdater only installed 4 system titles before it failed. Whenever I try to launch homebrew (I have tried browserhax, oothax and ninjhax) I get the "An error has occured" screen. With ninjhax, it's the fully black screen with white text, whilst with oothax and browserhax it is only the error on the home menu. I can't figure out for the life of me why I can't launch the hbl. Anyone have any thoughts?

 

[Arkansaw]

9.9.0-26E to 9.2.0-20E

Safesysupdater only installed 4 system titles before it failed. Whenever I try to launch homebrew (I have tried browserhax, oothax and ninjhax) I get the "An error has occured" screen. With ninjhax, it's the fully black screen with white text, whilst with oothax and browserhax it is only the error on the home menu. I can't figure out for the life of me why I can't launch the hbl. Anyone have any thoughts?

Try formatting the system and clearing the SD card of any extra/temp files from previous payloads etc. Since the firmware has already "changed", those payloads will probably fail.

 

[TheDuckMan64]

Try formatting the system and clearing the SD card of any extra/temp files from previous payloads etc

I can't format cause I'm at boarding school atm wifi doesn't support 3ds'. I just had the idea of getting a game with a 10.3 update (Bravely Second: End Layer) and putting it on my Sky3DS.

 

[Arkansaw]

I can't format cause I'm at boarding school atm wifi doesn't support 3ds'. I just had the idea of getting a game with a 10.3 update (Bravely Second: End Layer) and putting it on my Sky3DS.

That's possible too, but you may have less entry points to work with, so do that as a last resort if you cannot run sysupdater again using any of the existing options

 

[TheDuckMan64]

That's possible too, but you may have less entry points to work with, so do that as a last resort if you cannot run sysupdater again using any of the existing options

I can't run any existing entrypoints, and browserhax + ninjhax will work on 10.3. So as soon as it copies over, I'm updating!

 

[DjoeN]

...
EDIT:

Since I didn't have any of the recommended things, I thought I would just try to run sysupdater again. It had trouble starting up, but on the 4th or 5th try I got it to boot and pressed Y again to downgrade. This time it went through to the end and rebooted the system after 10 seconds.

So it looks like if you can run sysupdater you don't need Zelda and another 3DS to fix this problem.

now my log file is much shorter:

Title ID 0x0004003000009e02
  Extra title
Title ID 0x0004013000001b02
  Expected version 0x0800
  Installed version 0x0c01
Title ID 0x0004013000001a02
  Expected version 0x1400
  Installed version 0x1801

I think I should be good now

You can get the:
- Title ID 0x0004013000001b02
- Title ID 0x0004013000001a02

from 9.2 O3DS firmware pack, boot into HBL and use FBI.3dsx to install the 2 firmware titleid's manually to NAND
If that gives an error from FBI, Try NASA (DON'T do it in Emunand)

Next time you check, it would only say:

Title ID 0x0004003000009e02
  Extra title

[EDIT]
Only for N3DS(XL) this is

 

[Arkansaw]

You can get the:
- Title ID 0x0004013000001b02
- Title ID 0x0004013000001a02

from 9.2 O3DS firmware pack, boot into HBL and use FBI.3dsx to install the 2 firmware titleid's manually to NAND
If that gives an error from FBI, Try NASA (DON'T do it in Emunand)

Next time you check, it would only say:

Title ID 0x0004003000009e02
  Extra title

Someone commented that these two titles are actually not critical to the downgrade. So patching them should be regarded as an "extra", in case people mistake this to be part of the recovery process.

 

[DjoeN]

Seems logical, that's why they don't get downgraded.
And to be fully complete, that's for N3Ds only on O3Ds they should be downgraded anyway.

 

[TheDuckMan64]

That's possible too, but you may have less entry points to work with, so do that as a last resort if you cannot run sysupdater again using any of the existing options

Still get the same error.... I even formatted my (2-day old ) 3ds, so I'll troubleshoot and hopefully come up with a solution.