Hacking OTP Retrieval Stuck

[Wolfy]

System: New3DS Black
Firmware: 9.2U
Pailect's Guide Steps: Followed multiple times, same result, unable to use One Click Setup as Validation 1 fails.
EmuNAND/RedNAND: Tried using both, no difference.
Hardmodded: Yes

Guide: https://github.com/Plailect/Guide/wiki/Part-4-(2.1.0-Downgrade)
Stuck @Section II, Part 15

And ideas?

 

[Deleted member 366698]

System: New3DS Black
Firmware: 9.2U
Pailect's Guide Steps: Followed multiple times, same result, unable to use One Click Setup as Validation 1 fails.
EmuNAND/RedNAND: Tried using both, no difference.
Hardmodded: Yes

Guide: https://github.com/Plailect/Guide/wiki/Part-4-(2.1.0-Downgrade)
Stuck @Section II, Part 15

And ideas?

Read the troubleshooting https://github.com/Plailect/Guide/wiki/Troubleshooting

 

[Wolfy]

Read the troubleshooting https://github.com/Plailect/Guide/wiki/Troubleshooting

I have looked through this and tried it's "fix" for the issue, but with no positive results.
I have .app errors so it wouldn't help anyway.

 

[Temarile]

I have looked through this and tried it's "fix" for the issue, but with no positive results.
I have .app errors so it wouldn't help anyway.

Just to check, you did this?

THIS APPLIES ONLY TO .TMD RELATED ERRORS, NOT .APP RELATED ERRORS
If you got a .app related error, you should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9..

 

[Tiibz]

Maybe the downgrade of emunand didn't go through, retry that with a different microSD if possible

 

[The Real Jdbye]

System: New3DS Black
Firmware: 9.2U
Pailect's Guide Steps: Followed multiple times, same result, unable to use One Click Setup as Validation 1 fails.
EmuNAND/RedNAND: Tried using both, no difference.
Hardmodded: Yes

Guide: https://github.com/Plailect/Guide/wiki/Part-4-(2.1.0-Downgrade)
Stuck @Section II, Part 15

And ideas?

What CFW are you using? Make sure it doesn't have FIRM blocking enabled (older versions of ReiNAND always have it enabled and I believe rxTools does too)

 

[Wolfy]

Just to check, you did this?

I've tried it, didn't help.

Maybe the downgrade of emunand didn't go through, retry that with a different microSD if possible

I do have the default 4GB microSD that came with the console, should I try again with that? And I'm assuming that the OTP would be fine since the microSD has nothing to do with the actual console's downgrade and retrieval?

What CFW are you using? Make sure it doesn't have FIRM blocking enabled (older versions of ReiNAND always have it enabled and I believe rxTools does too)

Latest ReiNAND, and Luma3DS for first attempt.

 

[Tiibz]

I've tried it, didn't help.



I do have the default 4GB microSD that came with the console, should I try again with that? And I'm assuming that the OTP would be fine since the microSD has nothing to do with the actual console's downgrade and retrieval?



Latest ReiNAND, and Luma3DS for first attempt.

yeah try with this one
once you are downgraded to 2.1 you're fine

 

[Wolfy]

yeah try with this one
once you are downgraded to 2.1 you're fine

Did not give any better results -_-

 

[Tiibz]

Did the downgrade go through ? You should have a message that says the console is rebooting after sysUpdater has finished
You could also try the normal sysUpdater to downgrade Emunand
And also check that you don't have a custom TWL firm or such as it can cause problems

 

[Wolfy]

The downgrade succeeded, it showed the message saying its rebooting.

And what do you mean custom TWL firm?

 

[Tiibz]

Did you installed any patched cia for AGB or TWL in the past ?

 

[Wolfy]

Did you installed any patched cia for AGB or TWL in the past ?

As the guide also said, if you don't know what it is, then you shouldn't need to worry, I have seen posts about AGB and TWL patching, but I have not done anything about it currently.

 

[Tiibz]

Well it's strange that OTPHelper say it's no good even though the downgrade went through.
I see that you have an hardmod so if you're sure that you downgraded with the good files you can just ignore OTPHelper warnings and continue by injecting the o3ds header in the emunand and then flash it to sysnand, if you brick you can restore your sysnand with the hardmod

 

[Wolfy]

Well it's strange that OTPHelper say it's no good even though the downgrade went through.
I see that you have an hardmod so if you're sure that you downgraded with the good files you can just ignore OTPHelper warnings and continue by injecting the o3ds header in the emunand and then flash it to sysnand, if you brick you can restore your sysnand with the hardmod

I tried it, didn't help.

 

[Tiibz]

It's really strange, there's something wrong with your downgrade to 2.1
Re-read the guide and post what you are doing exactly so we can try to identify the cause of the problem