- Joined
- Jun 27, 2017
- Messages
- 734
- Trophies
- 0
- Location
- The Ruins of GBATemp (3DSTemp.net)
- XP
- 1,999
- Country
Correct.But first we decrypt our nand, right?
Happy to helpVery FAST! thank you very much for your effort!
DSi's on eBay are only $20-$35mine toooo.........
my both DSi XL eur... Need to buy 3rd? Maybe laterDSi's on eBay are only $20-$35
Because a lot of people installed it and no longer want it. Remember, it's not removable via Data Management. It's basically an installable System Application.Why you need/want to remove the 3ds transfer tool?
Your best chance is using flipnotehax/ugopwn with the Flipnote app that you already have.I'm confused as to where to start...
My DSi is empty since I did the system transfer from it to my 3DS years ago, but I have the browser and Flipnote, and it's on 1.4.5 firmware. I have a 1GB SD card in it, but can go bigger if needed. Hardmod is not an option for me, and I don't get my R4i 3DS Gold cart until tomorrow. So where do I go from here?
I get that, but I don't know anything about it, where to download the files I need for it, or if there's a tutorial somewhere to set that up. the OP's tutorial steps are half-assed and vague at best, and assumes we just *know* this stuff. So any help is appreciated.Your best chance is using flipnotehax/ugopwn with the Flipnote app that you already have.
The leak exists, but there is a high chance of brick if you use it. The best way is to just wait for the official release of Flipnotehax and not use the ugopwn leak. I blame the P guy on that one.I get that, but I don't know anything about it, where to download the files I need for it, or if there's a tutorial somewhere to set that up. the OP's tutorial steps are half-assed and vague at best, and assumes we just *know* this stuff. So any help is appreciated.
Do you mean you are running the downgrader from a drive other than C:/ ? Switching to the C drive ( the C: command ) is hardcoded into the program.@dpad_5678 The downgrader doesn't work when I use it from disk drive D:/. First I typed my NAND letter in uppercase, then when I tested the NAND in NO$GBA it threw up an error code 1-2435-8325. I tried typing my letter in lowercase, then it started printing system files and plugins for whatever reason. All I know is that it deleted the titles that it was supposed to downgrade and copied Frodo files from the C:/ root to their directories.
I've used ugopwn on 30+ consoles without bricking. It's perfectly safe, just propaganda from the dev's who were angry about the leak (which I can understand). Ugopwn is just the entrypoint. Restoring a broken NAND can brick, but that's not ugopwn doing the bricking. Always test your NAND in No$Cash before restoring it to real hardware, and you'll be fine. I've done 100+ NAND restores between 30+ consoles without issues.Okay, I'll wait. Thank you. I don't want to brick my only DSi in the house. They still go for around $60 used at gamestop, so I rather not brick.
Alright, I ran the downgrader from C:/, and it worked perfectly.Do you mean you are running the downgrader from a drive other than C:/ ? Switching to the C drive ( the C: command ) is hardcoded into the program.
Nice to know. Thank you for your feedback. I'll add a note to OP.Alright, I ran the downgrader from C:/, and it worked perfectly.
There's no chance of bricking using the exploit. The only chance of brick is user error modifying the nand backup. Such as: Using an old build of TWLTool which doesn't work properly, failing to modify files on the nand properly, using files that aren't the proper files, (edit) also flashing decrypted nand, the list probably goes on.The leak exists, but there is a high chance of brick if you use it. The best way is to just wait for the official release of Flipnotehax and not use the ugopwn leak. I blame the P guy on that one.
Exactly. In almost any case, the entrypoint is never the cause of a brick.There's no chance of bricking using the exploit. The only chance of brick is user error modifying the nand backup. Such as: Using an old build of TWLTool which doesn't work properly, failing to modify files on the nand properly, using files that aren't the proper files, the list probably goes on.