Tutorial  Updated

OTP Guide

Full Guide Release!

https://plailect.github.io/OTP/

All regions now supported!

If you appreciate this guide and the work I put into maintaining it, I accept donations through both Bitcoin and PayPal.

If you felt like the guide helped you out then I'd really appreciate it! If I get enough I may buy a 2DS for testing hardware stuff so I don't break another N3DS.

If the guide didn't help you out then I'm really sorry about that :(
 
Last edited by Plailect,
That moment you realize you have to reupload several gigs of data on a slow connection just because of a couple of typos.
:P

This is why you support open-source devs people: they go through a shitload of agony just to make you happy -- for free.
 
Last edited by zoogie,
Fixed again.
That moment you realize you have to reupload several gigs of data on a slow connection just because of a couple of typos.
:P

This is why you support open-source devs people: they go through a shitload of agony just to make you happy -- for free.
That's why I switched from mega to git branches. Everything has been updated on git, anyone who redownloads the zip will get the latest update. Hooray!
 
Fixed again.

That's why I switched from mega to git branches. Everything has been updated on git, anyone who redownloads the zip will get the latest update. Hooray!
DAT typo op

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

On section 1 #10/#15, you still have the names as nand.fat16_0x5_.xorpad and nand.fat16_0x4_.xorpad the Windows.py looks for files named nand.fat16.xorpad and nand.fat16.0x4.xorpad Just a heads up
Dam it man I have to rename my xorpads
 
I stuck at Section 2 because of file names. You know, it's kinda fustrating when you've been staring at the same page for hours and then realize there's something wrong, and to make matters worse, when you refresh the page, something isn't what's it used to be.
Nah, never mind about that.Anyway, nice work.
 
MRW fixing the scripts makes all of the sha-256s invalid -_-
IMO, the update (downgrade?) files are the most important. why not put those all into a zip folder inside of your package and have us users check the sha-256 of that instead?
 
IMO, the update (downgrade?) files are the most important. why not put those all into a zip folder inside of your package and have us users check the sha-256 of that instead?
Having a consistent file structure to refer to is easier and makes everything more clear.
 
I have two o3DS on 2.1.0-4E already - is it worthwhile getting their OTPs and waiting until there's a CFW that works with a9lh? My plan with them was to install CFW and resell them. Will CFW using a9lh be a lot better than regular rxTools autobooted with menuhax? Like for example can the user act like they're not even using CFW, and update from prompts on the eShop etc? Or is it just like regular CFW, only a little faster to boot up?
 

Site & Scene News

Popular threads in this forum