Hacking [Help] Installed wrong OTP. Am I screwed?

[Kyojin]

Well, Plailect seemed to have a solution for you, I guess you should try and get in touch with him.

This is fixable, but you will need a hardmod and the OTP that you used for the install. If we also know what FIRM version you started with (I'm assuming 9.2, correct me otherwise), then we can do a plaintext firm attack to swap the FIRM in NAND since we know what payload you installed.

 

[Hayleia]

Other people have already said it but I feel the need to say:
Why,why,why? Why did you not have a nand dump? Why did you use the WRONG FRIGGIN OTP?
*Facepalms* smh

I can understand using the wrong OTP. I'm not saying it's something smart, but at least I understand. You went through a long process several times on several systems, you want to go faster on the second one, you copy paste files from the first system's SD (including its OTP) then you install arm9loaderhax...

But yeah no NAND backup I don't understand however.

 

[nooby89]

The NAND backup of other 3DS can be used on a 3DS of the same region adn language?
If yes, he can use a NAND backup form other source.

 

[Arubaro]

The NAND backup of other 3DS can be used on a 3DS of the same region adn language?
If yes, he can use a NAND backup form other source.

Absolutely not

 

[nooby89]

OK, so the author is in trouble.

 

[Hayleia]

The NAND backup of other 3DS can be used on a 3DS of the same region adn language?
If yes, he can use a NAND backup form other source.

If that was the case, there would have been a lot of hardmod downgrade services during the 9.2-10.3 period without downgrading possibilities, or even during the 4.5-9.2 period.

 

[dark_samus3]

I do not have the right OTP file, that's the problem.

All is still not lost, if you still have the FIRM0 file you used, we can simply do a plaintext attack and replace FIRM0 with a regular 9.2 o3ds FIRM, then we can GET A FREAKING BACKUP! Then start the guide over

 

[gkoelho]

Absolutely not

Is actually possible if you XORpad the decrypted nad backup to change the Keys and console unique values, since he has his OTP. But its far away from a easy thing

 

[RedBlueGreen]

What valuable insight people offered yesterday. Good luck with fixing your 3DS.

 

[SanchezTG]

All is still not lost, if you still have the FIRM0 file you used, we can simply do a plaintext attack and replace FIRM0 with a regular 9.2 o3ds FIRM, then we can GET A FREAKING BACKUP! Then start the guide over

This is exactly what I have:

O3DS on 9.2 firmware with hardmod (does not boot)
Messed up NAND backup using hardmod
WRONG OTP file from wrong 3DS
A different 3DS with 9.2 firmware


Is the OTP file the FIRM0 file? And the second I get this working, I will get like 3 frickin backups ha.

 

[GerbilSoft]

FIRM0 is the first NATIVE_FIRM. If you have the FIRM0.bin that you installed when attempting to install A9LH, you should be able to use a plaintext attack to inject the correct 9.2 NATIVE_FIRM into the FIRM0 partition. Since this is O3DS NATIVE_FIRM, the OTP and secret sector don't matter right now. (They're reinstalled when running SafeA9LHInstaller.)

 

[mudassirul]

dark_samus3 seems to know about how the NAND is coded, you could try providing the NAND dump with your hardmod and the OTP you used and ask him nicely to build you a working NAND

 

[SanchezTG]

FIRM0 is the first NATIVE_FIRM. If you have the FIRM0.bin that you installed when attempting to install A9LH, you should be able to use a plaintext attack to inject the correct 9.2 NATIVE_FIRM into the FIRM0 partition. Since this is O3DS NATIVE_FIRM, the OTP and secret sector don't matter right now. (They're reinstalled when running SafeA9LHInstaller.)

I don't have that file. The method I used didn't directly ask for that file. But could I use the AutoFirm program here to get around that?

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

Any suggestions @Plailect @dark_samus3 ?

 

[Xinaman]

I don't have that file. The method I used didn't directly ask for that file. But could I use the AutoFirm program here to get around that?

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

Any suggestions @Plailect @dark_samus3 ?

You have the FIRM0 on your sd card, on the folder a9lh, used by safeA9LHInstaller.

 

[coolfuze]

Also remember if you have a emunand partition on a sd card used by the system you would be able to recover your sysnand with it, hopefully its not on 11

 

[gamesquest1]

Also remember if you have a emunand partition on a sd card used by the system you would be able to recover your sysnand with it, hopefully its not on 11

well now he is hardmodded he could dg from 11.0 anyway (hax game dependent though), unfortunately i think peoples asses being saved by emunand will become quite rare now that everyone suggests using sysnand exclusively, it was a nice last safety net against "no nand backup noobs"

 

[vb_encryption_vb]

Also remember if you have a emunand partition on a sd card used by the system you would be able to recover your sysnand with it, hopefully its not on 11

11.0 don't matter, but, yes, if he has an emunand backup, than he could restore console with that.

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

well now he is hardmodded he could dg from 11.0 anyway (hax game dependent though), unfortunately i think peoples asses being saved by emunand will become quite rare now that everyone suggests using sysnand exclusively, it was a nice last safety net against "no nand backup noobs"

OTPHelper should automatically make a backup ( not optional ) before it does the unbricking process, this would at least save someones ass.

 

[Kyojin]

OTPHelper should automatically make a backup ( not optional ) before it does the unbricking process, this would at least save someones ass.

Meh, I'm pretty sure people would still find a way to delete that backup and then go cry for help.

 

[Raugo]

This is exactly what I have:

O3DS on 9.2 firmware with hardmod (does not boot)
Messed up NAND backup using hardmod
WRONG OTP file from wrong 3DS
A different 3DS with 9.2 firmware


Is the OTP file the FIRM0 file? And the second I get this working, I will get like 3 frickin backups ha.

If the otp you have is the otp used in the bricked 3DS you can fix it. Use this otp to compile the a9lh. Then extract the firm partition (you can use my tool https://mega.nz/#!zg4xxTDD!oaIl_rV47yzaXf-x_G24geTfWJKtFIizjMo2lh0EFSQ command: 3DSFirm.exe -d nand.bin firm0.bin firm1.bin) make xor to the firm0 and the firm1 extracted with the firm0 firm1 maked with a9lh compiler and call it firm0.xorpad and firm1.xorpad. Then obtain the firm.bin of the 9.0 native_firm and make xor to this file and the firm0.xorpad and firm1.xorpad inyect this news firms to the nand.bin and inyect the nand.bin to the 3DS.

PD: My english is too bad if anyone more know the process please explain it better

 

[SanchezTG]

You have the FIRM0 on your sd card, on the folder a9lh, used by safeA9LHInstaller.

I still have it!! Thanks

If the otp you have is the otp used in the bricked 3DS you can fix it. Use this otp to compile the a9lh. Then extract the firm partition (you can use my tool https://mega.nz/#!zg4xxTDD!oaIl_rV47yzaXf-x_G24geTfWJKtFIizjMo2lh0EFSQ command: 3DSFirm.exe -d nand.bin firm0.bin firm1.bin) make xor to the firm0 and the firm1 extracted with the firm0 firm1 maked with a9lh compiler and call it firm0.xorpad and firm1.xorpad. Then obtain the firm.bin of the 9.0 native_firm and make xor to this file and the firm0.xorpad and firm1.xorpad inyect this news firms to the nand.bin and inyect the nand.bin to the 3DS.

PD: My english is too bad if anyone more know the process please explain it better

I used your AutoForm program to downgrade a different 3DS that was on 11.0. So I trust your advice, but it is a little confusing >.<

Could you say it in Spanish? Maybe I will understand a little better.

Also, the OTP I have is from another DS