So what happened to Pichaxx method? I remember last year I modded 3 systems and they all used teh Pichaxx method , now it's bannerbomb ?
11.16.0-48 patched universal-otherapp, and thus PichaxxSo what happened to Pichaxx method? I remember last year I modded 3 systems and they all used teh Pichaxx method , now it's bannerbomb ?
Tyvm for the fast response. So for software hacks, purely software, we only have Seedminer (I understood it's impossible to patch) + Bannerbomb left?11.16.0-48 patched universal-otherapp, and thus Pichaxx
This is the easiest way https://gbatemp.net/threads/kartdlphax-a-mario-kart-7-semi-primary-exploit.587755/Tyvm for the fast response. So for software hacks, purely software, we only have Seedminer (I understood it's impossible to patch) + Bannerbomb left?
Quite a noob but trying to learn, thanks
Setting up another 3DS console (so you have to own multiple) isn't exactly easier than seedminer + bannerbomb iMHO....This is the easiest way https://gbatemp.net/threads/kartdlphax-a-mario-kart-7-semi-primary-exploit.587755/
Pichaxx should still work fine, just change the otherapp to *hax version (the cfg:s ones I made) and use slotTool.3dsx to install usm.
Here's a guide.
https://wiki.hacks.guide/wiki/3DS:Alternate_Exploits/Homebrew_Launcher_(PicHaxx)
Note that you don't have to get your movable.sed or replace the Picross save file, that's already done.
Hint, do all of Section I, and then skip down to Section II, and continue with step 9.
I honestly don't know where that stupid rumor pichaxx got fixed came about. People assuming because one part of an exploit chain gets fixed, they all must be fixed, I guess.
Yeahis it safe to transfer to pokemon bank from CIA games?
chkdsk X: /r
(X your driveletter) to check for file and sector errors and correcting them."firmware backing-up step"? You mean the nand? If so, 250mb is definitely insufficient, you'd need atleast 1.4GB free on your sd card..Hello.
What could be the origin of a failure at the firmware backing-up step? (My n3DSis on the penultimate official system update, Luma11, and the Safe9BS was the latest version (redownloaded to be sure). There are 250 free Mo on the SD.)
Well it's not working for me that circle just keeps loading and it doesn't show any assetsThe Download works without any problem. Just 317KB..
Directly from github ist best source ..... . . .. ... ..
... How in the world did you come up with that!? If it was that easy to fix the db, I expect there would already be instructions for doing so. Don't you think it's a bad idea to suggest methods that are completely unproven?This step is not verified by me and need tested on its own, (it maybe delete every installed stuff on SD):
- Force recreating the dbs on SDCard, because the databases are stored in Nand and SDCard.
- Create 2 empty txt files and rename to title.db and import.db in the "Nintendo 3DS/<longID0>/<longID1>/dbs" folder. Or open them in Notepad++ and empty them.
- go to data management in settings, 3DS Software, and it should cry about repairing your title.db, then repair it. You should be able to install stuff to SD again.
@Sono wrote
That's why we need to repair the empty title.db after installing CFW
create 2 empty files named title.db and import.db in the "Nintendo 3DS/randomstuff/randomstuff/dbs" folder, go to data management in settings, 3DS Software, and it should cry about repairing your title.db, then repair it.
If the above files exist, then you should be able to install stuff to SD
Despite the name, the "CTRTransfer Type D9" script does a lot of other things that are not directly related to CTR Transfer, including rebuilding the DB on the SD card.And he dont need to recreate the title.db in Nand, only on SD Card because this is corrupted. So a suggestion doing a CTRTransfer with Decrypt9 isnt a bit big !?!
I see, I thought that the SafeBSinstaller merely wanted to make a backup of the previous custom firmware file. ^^""firmware backing-up step"? You mean the nand? If so, 250mb is definitely insufficient, you'd need atleast 1.4GB free on your sd card..
Oh, you were trying to update B9S to the latest 1.4 version?I see, I thought that the SafeBSinstaller merely wanted to make a backup of the previous custom firmware file. ^^"
It's the 6th step, saying: "BACKUP STATUS - XXXXX" (here being written in red that it failed).