Hacking Downgrading to 2.1.0 fails

[kristiansja]

i think i have tried downgrading emuNAND to 2.1.0 5 times now and they all fail im using an old 3ds with GATEWAY Emunand with Luma3DS

here is a plaisysupdater error report
http://pastebin.com/c9bzETvN
and this is where it fails

0004003000009802 : v.12288 -> v.02049 ->

//////////////////////////////////////////
Edit
//////////////////////////////////////////
thansk to everyone for the help, i now have arm9loaderhax. The problem was that i werent on 10.7

 

[a9lh-1user]

Did you make the FORMAT part twice before DG?

BTW i read that the GW emunand isn't the "cleanest" to work with

P.S. this is the section for questions like that: http://gbatemp.net/threads/3ds-noob-paradise-ask-questions-here.359035/

Please use it next time

 

[kristiansja]

Did you make the FORMAT part twice before DG?

BTW i read that the GW emunand isn't the "cleanest" to work with

P.S. this is the section for questions like that: http://gbatemp.net/threads/3ds-noob-paradise-ask-questions-here.359035/

Please use it next time

yup, i used tiny format twice and made a bin after that

 

[a9lh-1user]

okay then you have a "backup" if something goes wrong GOOD!
Also you are using this guide : https://github.com/Plailect/Guide/wiki or anything else?
Last question: if you used the Plailect guide did you DG to 9.2.x and made backups after that?
(do you have a CLEAN 9.2.x sysNAND of yur OLD 3DS?)
Or did you use your GW emuNAND?

 

[kristiansja]

okay then you have a "backup" if something goes wrong GOOD!
Also you are using this guide : https://github.com/Plailect/Guide/wiki or anything else?
Last question: if you used the Plailect guide did you DG to 9.2.x and made backups after that?
(do you have a CLEAN 9.2.x sysNAND of yur OLD 3DS?)
Or did you use your GW emuNAND?

i have a 9.2 sysnand and i created a emunand out of that

 

[CrispyYoshi]

Did you disable FIRM0/FIRM1 protection within your CFW? (I believe both Cakes and Luma3DS can do it)
The EmuNand downgrade can't proceed properly if you have it enabled.

 

[a9lh-1user]

That means you are dealing with the Gateway NAND.
Sorry i dont now anything about that from personal experience.
I made 3 OLD 3DS and 4 NEW 3DS till now (with 6 different guides from Plailect because it feels like they change every day like Aureinand / Luma3DS) and NONE had problems by DG to 2.1.0 .
But i dont own a Gateway, but i read that they've done a BAD job by plaing with your NAND (Aurora Wright and others are cleaning that mess for some people!)

So sorry i couldn't help you because of missing knowledge
Hope someone else could help you ...... people with a Gateway and emuNAND experience in getting it to A9LH

--------------------- MERGED ---------------------------

@CrispyYoshi there is no CFW till now he will DG to 2.1.0
@CrispyYoshi OOPS my mistake forgett it!!!!!!

 

[CrispyYoshi]

@CrispyYoshi there is no CFW till now he will DG to 2.1.0

Actually, they need a CFW to boot into their EmuNand, and their first post suggests they are using Luma3DS, which blocks FIRM0/FIRM1 patches by default.

It can be disabled by holding Select in the Luma3DS settings, but they might have to get the dev version of Luma3DS in order to do it.

EDIT: Nevermind, it seems (or is implied) that Luma3DS does not block FIRM0/FIRM1 patches on EmuNAND: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes (CTRL+F "FIRM write-protection")

 

[CrispyYoshi]

@kristiansja I think your next best bet is to get rid of your Gateway EmuNand before you downgrade it. I'm hoping you don't have anything important on your SysNand.

To do this, you should:
- Flash your double-formatted 9.2 emunand or your very first sysnand backup (the one you dumped before using TinyFormat, but otherwise your very first EmuNand backup) to your sysnand using Decrypt9 directly from HBL after a boot. Don't launch Luma3DS when you do this.
- Set up menuhax again if you have to, then follow the guide from the beginning of Part 3: https://github.com/Plailect/Guide/wiki/Part-3-(RedNAND)

(You might have already done part 3, but please re-do it just to be absolutely safe.

 

[kristiansja]

@kristiansja I think your next best bet is to get rid of your Gateway EmuNand before you downgrade it. I'm hoping you don't have anything important on your SysNand.

To do this, you should:
- Flash your double-formatted 9.2 emunand or your very first sysnand backup (the one you dumped before using TinyFormat, but otherwise your very first EmuNand backup) to your sysnand using Decrypt9 directly from HBL after a boot. Don't launch Luma3DS when you do this.
- Set up menuhax again if you have to, then follow the guide from the beginning of Part 3: https://github.com/Plailect/Guide/wiki/Part-3-(RedNAND)

(You might have already done part 3, but please re-do it just to be absolutely safe.

flashed a realy old nand and crated redNAND, still get the error (2 tries) WTF?!

 

[Tiibz]

Got the same problem with a o3ds a few days back, the solution was quite simple: just update your emunand to 10.7 (you can do another format after that to be sure if you want) and the downgrade will go through (it did first time for me after the update)

 

[kristiansja]

Got the same problem with a o3ds a few days back, the solution was quite simple: just update your emunand to 10.7 (you can do another format after that to be sure if you want) and the downgrade will go through (it did first time for me after the update)

Okay will try.

 

[pbanj]

Chances are you have modified twl/agb stuff on your sysnand. So when making the emunand it transfers. The downgrader has issues with that. Updating of emunand to 10.7 should clear it out and let you downgrade to 2.1

 

[kristiansja]

Got the same problem with a o3ds a few days back, the solution was quite simple: just update your emunand to 10.7 (you can do another format after that to be sure if you want) and the downgrade will go through (it did first time for me after the update)

thanks man, finally worked, have restored to 9.2 on sysnand and emunand quick question, when compiling a a9lhx fork do i replace the otp.bin with mine?

 

[pbanj]

thanks man, finally worked, have restored to 9.2 on sysnand and emunand quick question, when compiling a a9lhx fork do i replace the otp.bin with mine?

Yes. You can just use the stuff that's included in the guide https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax-&-Luma3DS) you won't have to compile anything, just put ur otp in the right place.

 

[Deleted User]

thansk to everyone for the help, i now have arm9loaderhax. The problem was that i werent on 10.7

@Plailect could you add this to the Guide?

 

[Plailect]

@Plailect could you add this to the Guide?

You do not have to be on 10.7 to do the downgrade...

 

[pbanj]

@Plailect could you add this to the Guide?

This is why he had to upgrade to 10.7

Chances are you have modified twl/agb stuff on your sysnand. So when making the emunand it transfers. The downgrader has issues with that. Updating of emunand to 10.7 should clear it out and let you downgrade to 2.1

He also could have used a CIA installer to install the unpatched ver of twl and agb.

 

[Ricken]

@Plailect could you add this to the Guide?

You do not have to be on 10.7 to do the downgrade...

To be fair one of the first things you do with RedNand is update it

 

[Deleted User]

You do not have to be on 10.7 to do the downgrade...

Oh ok, my mistake. I've just heard of the select few that have problems if not on 10.7. This is probably just to do with patched TWL and AGB firm that they need to update the firms to normal first to downgrade.