Hacking Hardmod downgrade issue: Plailect's AUTOFIRM or my mistake

[mvmiranda]

SOLVED... sort of...
A second pass resolved the issue... Thx @cravas for the tip!
But PlaySysUpdater fails all the time...
If I pass a third time, blue screen, forth time, ir works boots but fails on PlaySysUpdater.
So every even time I pass autofirm it blue screens, and every odd times it boots but fails in PlaySysUpdater.
----------------------------------------------

Hello all,

Some of you know me for some time. I'm one of the Brazilian hardmodders most of you suggest to ppl seeking out for services around here.

The last two weeks I was out and I could not test 11.1 hardmod downgrade so I'm doing it this week.
Today a 11.1 N3DS XL came in and I proceeded to downgrade it.
- Got two copies of the NAND (they match).
- Downloaded latest Plailect's autofirm and the 11.1 to 10.4 N3DS firms.
- Started autofirm.bat and make sure I pick 11.1 NEW 3DS/XL.

But after the process ended and I flashed the new nand.bin, when I turn on the console all I get is a blue screen with the last line all 0 (which means a bad NAND, as far as I know).

The console is indeed 11.1 (I personally updated it online for testing purposes).

I'm wondering if someone else ever faced this before?

PS: A couple of additional information:
1) When the fake SD is plugged in just the bottom screen turn on with blue screen
2) The board is a "Chinese replacement"
3) eShop works (completely unrelated but I decided to mention)

Any thoughts are welcome!

EDIT: When I reflash one of the NAND backups the console works again. This proves the NAND backup I have is OK!

EDIT 2: I'm tagging @Plailect just in case he decides to shed some light!

 

[swabbo]

Chinese replacement mobo? I'd focus on that myself, but I have no hard modding experience

 

[mvmiranda]

Chinese replacement mobo? I'd focus on that myself, but I have no hard modding experience

I have used many before... basically when some customer messes up the only way of fixing this with a somewhat cheap way is to buy a chinese motherboard replacement. Never had any issues though...

 

[Alex658]

That chinese mobo... Does it use usa/eur files? There's a proper twn-chn system version which is a different region all together. Maybe they're not compatible with the autofirm?

 

[mvmiranda]

That chinese mobo... Does it use usa/eur files? There's a proper twn-chn system version which is a different region all together. Maybe they're not compatible with the autofirm?

It's a USA mobo. The version reads 11.1.0-34U.

Tested eShop and it works, which means the region was not somehow changed...

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

I tried the recovery menu, just in case it was something wrong in this 11.1 FW and it says the console is already updated, meaning the firmware is healthy...
I don't have any other ideas...

 

[cravas]

That chinese mobo... Does it use usa/eur files? There's a proper twn-chn system version which is a different region all together. Maybe they're not compatible with the autofirm?

NATIVE_FIRMs are region indiferent. It doesn't matter which region you have, it will work.

At OP. I think I remember seeing someone using the autofirm 2x on the NAND and flashing it after that.(Sorry, can remember who or where).
Or maybe removing the mod and booting it after.
Maybe you can try to dump more than two NANDs (3 or 4) and confirm it's all good.

Other than that, I'm fresh out of ideas.

Other than this

 

[mvmiranda]

NATIVE_FIRMs are region indiferent. It doesn't matter which region you have, it will work.

At OP. I think I remember seeing someone using the autofirm 2x on the NAND and flashing it after that.(Sorry, can remember who or where).
Or maybe removing the mod and booting it after.
Maybe you can try to dump more than two NANDs (3 or 4) and confirm it's all good.

Other than that, I'm fresh out of ideas.

Other than this

I think I was that "someone" (or one of those "someone" hahaha).
I always dump 2 times and compare them. If they match I proceed... they did match indeed.

I'll try passing autofirm two times...

EDIT:
@cravas, guess what?!! A second pass solved it... Go figure it....
Thx for the tip, bruh!

 

[mvmiranda]

@cravas, PlaySysUpdater always fails, so I guess there's something really fishy going on wither with this board or autofirm...

Any other clues?

 

[cravas]

@cravas, PlaySysUpdater always fails, so I guess there's something really fishy going on wither with this board or autofirm...

Any other clues?

Use this to downgrade,

https://github.com/Plailect/Guide/wiki/9.2.0-Downgrade