Homebrew Firmware downgrade/transfer question

TonsofPuppies

Active Member
Newcomer
Joined
Aug 13, 2017
Messages
25
Reaction score
5
Trophies
0
Age
35
Location
Toronto, Ontario
XP
142
Country
Canada
I'm very new to using Homebrew, so bear with me. Currently, I have two O3DS XL models. One of them is running the current (11.5) firmware. The second hasn't been updated in some time and is running firmware version 11.2. I just purchased a N3DS XL and am planning on giving one of my old models to a friend. He wants to be able to run Homebrew on it for PKSM/PKHex. Is there any way possible that I can downgrade the 11.5 firmware to 11.2, perhaps by using the second O3DS with 11.2/SoundHax already installed on it? I apologize in advance, if this is posted in the wrong section.
 
You have three options to install CFW to the 11.5 3DS, from easiest to hardest:
These three options are your only options. Downgrading is not an option.
 
Last edited by Lacius,
  • Like
Reactions: Quantumcat
You have three options to install CFW to the 11.5 3DS, from easiest to hardest:
These three options are your only options. Downgrading is not an option.

Again, this is all totally new to me, so forgive my ignorance. What method would not require extra hardware purchases? I'm guessing the DSiWare method since I have a second O3DS with 11.2/SoundHax on it?
 
Again, this is all totally new to me, so forgive my ignorance. What method would not require extra hardware purchases? I'm guessing the DSiWare method since I have a second O3DS with 11.2/SoundHax on it?
The DSiWare method is the only method that doesn't require purchasing extra hardware, but it does require that you legitimately purchase a cheap DSiWare game on the CFW 3DS before system transferring.
 
The DSiWare method is the only method that doesn't require purchasing extra hardware, but it does require that you legitimately purchase a cheap DSiWare game on the CFW 3DS before system transferring.

Yeah, I saw that there were game options for $2 or something. That's fine with me. How difficult is the transfer process and what happens to the source 3DS in this case?
 
Yeah, I saw that there were game options for $2 or something. That's fine with me. How difficult is the transfer process and what happens to the source 3DS in this case?
The transfer process is not difficult as long as you follow the guide exactly. As a result of the transfer process, the following will happen:
  • The source 3DS will be formatted, but you will restore a NAND backup you made beforehand. So, your source 3DS is the same as it was before the process.
  • The target 3DS will also be formatted before receiving data from the source 3DS. Games and save files on the target 3DS before the system transfer will be permanently lost after the system transfer if you don't use one of the tedious methods of preserving data on the target 3DS.
  • If there is an NNID on the source 3DS, it will be transferred to the target 3DS. You will need to call Nintendo and have them manually transfer the NNID back to the source 3DS by claiming you don't have access to the target 3DS anymore.
  • Legitimate data on the source 3DS, including the modified DSiWare game, will be transferred to the target 3DS.
  • If the target 3DS has an NNID, it will be removed after the system transfer process. You will have to format the target 3DS to reconnect the old NNID if an NNID transfers over from the source 3DS.
Edit: Because of the logistics involved in the system transfer process, the ntrboot method is considered easier.
 
Last edited by Lacius,
  • Like
Reactions: Quantumcat
The transfer process is not difficult as long as you follow the guide exactly. As a result of the transfer process, the following will happen:
  • The source 3DS will be formatted, but you will restore a NAND backup you made beforehand. So, your source 3DS is the same as it was before the process.
  • The target 3DS will also be formatted before receiving data from the source 3DS. Games and save files on the target 3DS before the system transfer will be permanently lost after the system transfer if you don't use one of the tedious methods of preserving data on the target 3DS.
  • If there is an NNID on the source 3DS, it will be transferred to the target 3DS. You will need to call Nintendo and have them manually transfer the NNID back to the source 3DS by claiming you don't have access to the target 3DS anymore.
  • Legitimate data on the source 3DS, including the modified DSiWare game, will be transferred to the target 3DS.
  • If the target 3DS has an NNID, it will be removed after the system transfer process. You will have to format the target 3DS to reconnect the old NNID if an NNID transfers over from the source 3DS.
Edit: Because of the logistics involved in the system transfer process, the ntrboot method is considered easier.

I'm not worried about the NNID, as the N3DS I just purchased will now become my main console, which will be kept unhacked and I will perform a system transfer (including my NNID) to. There's no data on either console that is important to me, so formatting them is of no concern. With regards to my 11.2 O3DS though, how can I log onto the eShop to download the required DSiWare? Don't you need to be running the current firmware to use the store?
 
I'm not worried about the NNID, as the N3DS I just purchased will now become my main console, which will be kept unhacked and I will perform a system transfer (including my NNID) to. There's no data on either console that is important to me, so formatting them is of no concern. With regards to my 11.2 O3DS though, how can I log onto the eShop to download the required DSiWare? Don't you need to be running the current firmware to use the store?
The old 3ds system when you have the CFW installed will allow you to safely update to 11.5 which will let you use eshop for the transfer. Both systems are going to have full CFW this way as this is how it works. Also, full cfw is needed to even downgrade a system.
 
The old 3ds system when you have the CFW installed will allow you to safely update to 11.5 which will let you use eshop for the transfer. Both systems are going to have full CFW this way as this is how it works. Also, full cfw is needed to even downgrade a system.

When you say CFW (custom firmware), are you referring to boot9strap? Or is any 3DS firmware w/the Homebrew Launcher (SoundHax in my case) considered CFW? Sorry for all the questions. Lol
 
boot9strap = CFW, Soundhax =/= CFW.

Thanks.

I appreciate all who replied and gave me some answers to questions I've had a hard time finding answers to. I'll probably give this a try later this afternoon and will update this thread with the progress. Are there any specific known issues that some people have encountered that I should watch out for, especially since I'm doing this for the first time? Thanks again to you all.
 
boot9strap = CFW, Soundhax =/= CFW.
B9S is not the CFW; it's the entry point, like Soundhax. Luma3DS is the CFW.

Thanks.

I appreciate all who replied and gave me some answers to questions I've had a hard time finding answers to. I'll probably give this a try later this afternoon and will update this thread with the progress. Are there any specific known issues that some people have encountered that I should watch out for, especially since I'm doing this for the first time? Thanks again to you all.
Install B9S and Luma3DS to the 11.2 3DS following the holy Soundhax guide. After that, you should have no problem following the system transfer guide to install CFW to the 11.5 3DS. Don't skip steps, and follow the directions carefully.
 
Last edited by Lacius,
  • Like
Reactions: Quantumcat
B9S is not the CFW; it's the entry point, like Soundhax. Luma3DS is the CFW.


Install B9S and Luma3DS to the 11.2 3DS following the holy Soundhax guide. After that, you should have no problem following the system transfer guide to install CFW to the 11.5 3DS. Don't skip steps, and follow the directions carefully.
I know that boot9strap is not the CFW. :/ But if they have boot9strap, they have some sort of CFW to go along with it. That's what I meant by "boot9strap = CFW". And what I said corresponds to what they were asking. :/ I may be dumb sometimes but I'm not a complete idiot.
 
Last edited by KunoichiZ,
  • Like
Reactions: Quantumcat
I know that boot9strap is not the CFW. :/ But if they have boot9strap, they have some sort of CFW to go along with it. That's what I meant by "boot9strap = CFW". And what I said corresponds to what they were asking. :/ I may be dumb sometimes but I'm not a complete idiot.
That's not what you said. But, no worries.
 
B9S is not the CFW; it's the entry point, like Soundhax. Luma3DS is the CFW.


Install B9S and Luma3DS to the 11.2 3DS following the holy Soundhax guide. After that, you should have no problem following the system transfer guide to install CFW to the 11.5 3DS. Don't skip steps, and follow the directions carefully.

Will do. Thanks again man.
 
  • Like
Reactions: Deleted User
Hey guys,

I haven't been able to update this thread as quickly as I had hoped because I'm in the middle of exam week at school and have been very busy. I've followed the guides very closely and have successfully installed CFW on my 11.2 O3DS and upgraded it to 11.5. I also downloaded SODUKU to do the DSiWare injection. I tested the save exploit and it worked (I have completed up to the final step in Section II of the guide). I have a couple of questions before I proceed.

Am I just meant to do an ordinary system transfer from the source 3DS to the target 3DS? Are there any pitfalls I should be aware of during this process? There seems to be importance surrounding the transfer to a NNID, but seeing as neither the source or the target are linked to a NNID, is there anything else I should know before I continue? Thanks again for the help!
 
Hey guys,

I haven't been able to update this thread as quickly as I had hoped because I'm in the middle of exam week at school and have been very busy. I've followed the guides very closely and have successfully installed CFW on my 11.2 O3DS and upgraded it to 11.5. I also downloaded SODUKU to do the DSiWare injection. I tested the save exploit and it worked (I have completed up to the final step in Section II of the guide). I have a couple of questions before I proceed.

Am I just meant to do an ordinary system transfer from the source 3DS to the target 3DS? Are there any pitfalls I should be aware of during this process? There seems to be importance surrounding the transfer to a NNID, but seeing as neither the source or the target are linked to a NNID, is there anything else I should know before I continue? Thanks again for the help!

do an ordinary system transfer and you will be fine. the biggest thing most people forget is to test the exploit first before transferring and that is what messed them up. You tested it first so that should not be an issue.
 
Last edited by driverdis,
do an ordinary system transfer and you will be fine. the biggest thing most people forget is to test the exploit first before transferring and that is what messed them up. You tested it first so that should not be an issue.

Okay, that's good news. A follow up question for when I continue this process tomorrow; When I get to "Section IV - Restoring the Source 3DS", am I meant to just skip step 2 and move from 1 to 3, since I don't have a NNID associated with either console?
 
Okay, that's good news. A follow up question for when I continue this process tomorrow; When I get to "Section IV - Restoring the Source 3DS", am I meant to just skip step 2 and move from 1 to 3, since I don't have a NNID associated with either console?

yes, you can skip that step as you have no NNID linked.
 

Site & Scene News

Popular threads in this forum