Hacking R4i wood 3ds not working

  • Thread starter Thread starter Sam S
  • Start date Start date
  • Views Views 3,325
  • Replies Replies 31

Sam S

Well-Known Member
Newcomer
Joined
Mar 28, 2016
Messages
99
Reaction score
11
Trophies
0
Age
39
XP
163
Country
United States
I have a new 3ds xl 11.2.0-35U and i have a wood r4i card, but it gives me an error "An error has occured press and hold the POWER button to turn the system off"
 
That something to be expect since without CFW, some flashcart got blocked.
What is your current FW version (in System Setting)
 
There is 4 things you need to know right now.
  1. 3DS exploit: This is a way allow to run somethings that normally can't run such as homebrew, etc. Example of 3DS exploit are menuhax, arm9loaderhax, fasthax, etc.
  2. 3DS CFW: This is what you want to allow your 3DS to add more function to FW, such as out of region cart load, pirating, ETC. This one need 3DS exploit to be able to run. Example of CFW is Luma3DS. ReiNAND, Corbenik.
  3. SysNAND: This is your System OS that run on the 3DS.
  4. EmuNAND: The clone of your SysNAND that store on SD card. This one is need to allow CFW to run without some exploit such as menuhax getting remove by Nintendo update
The choices you have here are:
  1. Installing Arm9loaderhax (A9LH) Exploit with Luma3DS CFW. Can be done by following this guide: http://3ds.guide/ . This one is the most popular setting and mostly safe from removed by Nintendo.The problem is, this setting require user to hack into 3DS System files. But, So it has a small risk of brick. But, if you're understand and following every step of the guide I gave you correctly. Even though you bricked, it can still be fix by hardmod.
  2. Installing menuhax Exploit with Luma3DS CFW. Can be done by following this guide: How to Autoboot EmuNAND on FW 9.0.0-11.2.0 (without A9LH). This one is more safer in installing state. But, drain SD card space for cloning SysNAND into EmuNAND, and has a chance getting remove if you update to next firmware when you accindently boot to SysNAND.
  3. Buying the new flashcart or update its kernel, since somebody told me that Nintendo stop blocked new DS flashcart kernel for awhile now. This method, I can't guarantee that it will work.
 
  • Like
Reactions: satan89
There is 4 things you need to know right now.
  1. 3DS exploit: This is a way allow to run somethings that normally can't run such as homebrew, etc. Example of 3DS exploit are menuhax, arm9loaderhax, fasthax, etc.
  2. 3DS CFW: This is what you want to allow your 3DS to add more function to FW, such as out of region cart load, pirating, ETC. This one need 3DS exploit to be able to run. Example of CFW is Luma3DS. ReiNAND, Corbenik.
  3. SysNAND: This is your System OS that run on the 3DS.
  4. EmuNAND: The clone of your SysNAND that store on SD card. This one is need to allow CFW to run without some exploit such as menuhax getting remove by Nintendo update
The choices you have here are:
  1. Installing Arm9loaderhax (A9LH) Exploit with Luma3DS CFW. Can be done by following this guide: http://3ds.guide/ . This one is the most popular setting and mostly safe from removed by Nintendo.The problem is, this setting require user to hack into 3DS System files. But, So it has a small risk of brick. But, if you're understand and following every step of the guide I gave you correctly. Even though you bricked, it can still be fix by hardmod.
  2. Installing menuhax Exploit with Luma3DS CFW. Can be done by following this guide: How to Autoboot EmuNAND on FW 9.0.0-11.2.0 (without A9LH). This one is more safer in installing state. But, drain SD card space for cloning SysNAND into EmuNAND, and has a chance getting remove if you update to next firmware when you accindently boot to SysNAND.
  3. Buying the new flashcart or update its kernel, since somebody told me that Nintendo stop blocked new DS flashcart kernel for awhile now. This method, I can't guarantee that it will work.
Thanks! I'll try this tomorrow afternoon, so, is this basically downgrading and installing a CFW?
 
Ok, and the thread said their might be a possibility of a brick, if I do everything correctly, that won't happen?
Most people won't get brick if they really understand the guide and following it without a mistake.
I only saw 1 person brick even following the guide correctly, so the chance is below 0.01%.
Editing System always has a chance of brick in every electronic device such as brick android phone when flashing its OS.

And, the guide will told you to create a NAND Backup that can help you recover if you're in that 0.01%.
So, don't worry unless you really don't want it to brick 100%.
 
  • Like
Reactions: Sam S
I'm looking at the guide site, but I do not see my 3ds tutorial, I click on my 3ds model and it just takes be to the homebrew exploits
Trying to read it until the end, the guide is seperate into many page for each important step with a great explanation.
 

Attachments

  • image.jpg
    image.jpg
    1.7 MB · Views: 211
That's the same one it have, even has r4ids.cn on it. Download this kernel and load that with any other ds (lite or dsi). There will be 2 .nds files. Choose the dsi file if loading from a dsi or the lite version if you have a dslite. Yes, you will need a dslite or dsi to install the new kernel to the flashcart.
 
That's the same one it have, even has r4ids.cn on it. Download this kernel and load that with any other ds (lite or dsi). There will be 2 .nds files. Choose the dsi file if loading from a dsi or the lite version if you have a dslite. Yes, you will need a dslite or dsi to install the new kernel to the flashcart.
I'll try it! maybe tomorrow or tuesday
 
  • Like
Reactions: slaphappygamer

Site & Scene News

Popular threads in this forum