Hacking after installing CFW 4.5 what now?

  • Thread starter Thread starter miamore
  • Start date Start date
  • Views Views 11,795
  • Replies Replies 65
My biggest error is not configuring the wifi configuration before making an emuNAND of it. So what happens is that your sysNAND has the correct wifi settings but your CFW/emuNAND doesn't have a valid wifi connection.

You can boot into your CFW without pressing L and then configure the Wireless connections. That's what I did.
 
Basically I went through this same issue when I was helping my older brother with CFW. A few key things to remember:

- Do NOT use Govanify's CFW. Please use Palantine's. From what I have heard, it includes his own Network Calls that could "cause you harm" (no idea what the harm could possibly be, especially since I've just been warned about the NC's).
- Make sure your 3DS is properly configured in its wireless settings (personally I like to assign my devices specific IP's so that I can easily set up access to my removable hard drive on my network that I use as a shared drive for my devices). If it is not, do what others above have said and change your network settings to fit those you like. It's easy to get your Default Gateway, etc. through



since you're running a Windows machine. This also worked for me at my university since I wasn't allowed into the router's settings. Please re-assign your device properly; it makes a world of a difference.
- Restart. I'm serious. When I was doing this with my brother he got stuck at the same position you're at. Don't do a full-fledged restart, but:

- Re-install the DS profile exploit, then remove EVERYTHING (but do not format) from your SD Card ESPECIALLY your "dbs" folder that includes your "import.db" and "title.db."
- Create the software management data by putting your SD card in your 3DS
- Re-create the "dbs" folder and the files within
- Go to Settings -> 3DS -> Software -> Reset the settings, as it'll prompt you to.
- Put Palantine's CFW on the SD, renaming "Launcher_GW.dat" to "Launcher.dat," adding all of the arm9, arm11, boot .bin files to the root directory of the SD Card.
- Try and see if it boots into CFW by holding L at the DS Profile screen
- See if it works and re-do the guide in case I missed something vital here.

- Enable wireless, go into the internet browser. Edit "run.bat" to include the IP you assigned the 3DS to have. If you have Devmenu_2x, save the run.bat file and try to send it over.

If it fails:

- Try and send over the .cia without having the SD Card in, this will help you know if there is a problem with the network. I don't think there is any danger in this, but it still helps to be careful and research before trusting my word.

If it succeeds and gives you a funky error code, reboot and try again with the SD card in. If the ctr client can't connect then there's a big problem here. Disable firewalls and etc in order to help send over the file.

You can't boot into the CFW without SD Card, because you have no Launcher.dat on your sd card. Also you shouldn't remove the SD card while the 3DS is on (espacally in EMUnand) because it can corrupt the SD card.
 
Is OP using his phone to boot in CFW? This could be the issue.

edit: try to ping the ip address of the 3ds from the cmd line on your laptop. Also ensure you're firewall is off. Make sure you are using cmd in admin mode.
 
Got it. I know you can't boot into CFW without the card but I was fully aware you could remove the card while in CFW. I didn't think it would corrupt. Maybe I shouldn't do that anymore...thanks for the advice.


Think about it like this, Your pc/laptop has a harddrive, you remove that hard drive while its its on then what happens?
 
The first time it took me a few days to get it working, mostly because I was using an improperly configured wifi hotspot, which had the CFW crash every time.
Since then I've reinstalled the CFW like 10-20 times to try different things, and it wasn't that much of a hassle.

so after configuring the correct settings for the hotspot. it finally worked for you? I'm guessing the network connection is my problem. I'll try playing with my network connection
 
so after configuring the correct settings for the hotspot. it finally worked for you? I'm guessing the network connection is my problem. I'll try playing with my network connection


This is what I'm getting at right now, you need to try what I posted about pinging the ip of the 3ds.
 
This is what I'm getting at right now, you need to try what I posted about pinging the ip of the 3ds.
Yes.. I'll try when I get home.. tried the pinging on my office. and and access denied error shp
This is what I'm getting at right now, you need to try what I posted about pinging the ip of the 3ds.

ping is ok. but no luck :-p. is this the only way to install .cia files?
 
ive been struggling with this part for 2 days. i get an error "ctrclient.exe not a valid win32 application" so im guessing i need a newer OS. im on win xp. can anybody help please??? i didnt think this would be so stressful....
 
In reply to your thread title, the obvious answer is 'get a gateway'.

Don't write me off as a fan boy; i love and openly support a 'free option' as much as the next person. But i was left a broken man after 20+ forum posts and 2 x 8 hour sessions of trying to get the CFW to work......
 
Sadly it doesn't work in my Windows XP 32-bit laptop. It works in my Windows 7 64-bit desktop though...
 
In reply to your thread title, the obvious answer is 'get a gateway'.

Don't write me off as a fan boy; i love and openly support a 'free option' as much as the next person. But i was left a broken man after 20+ forum posts and 2 x 8 hour sessions of trying to get the CFW to work......

You're very apparently not following instructions if it's taken you 16 hours of attempts and still don't have this ironed out. It's not the easiest thing in the world to get set up, but it certainly shouldn't take more than a single afternoon.

As far as those who are having difficulty pushing over dev menu, make SURE that your windows firewall is turned off, as well as your router firewall. Both of these can and will interfere with the process, as it's not normal to just push binary data like this, and it can and will cause firewalls to freak out, and kill the transfer before anything makes it over the network. Obviously turn these back on immediately after the transfer's done though.
 

Site & Scene News

Popular threads in this forum