yeah, but you shouldn't need to anywayfollowed that guide. is the version of unlaunch in it the one that lets you enter data management safely?
you can just go ahead to installing hiyacfw
yeah, but you shouldn't need to anywayfollowed that guide. is the version of unlaunch in it the one that lets you enter data management safely?
i wouldnt want to accidentally brick my console for forgetting that checking data management would brick ityeah, but you shouldn't need to anyway
you can just go ahead to installing hiyacfw
Seems 0.6 can still result in bricks. Launcher SRL needs the write protect flag too. But this one is recoverable. Seems exploit still works because Stage2 doesn't even get far enough along to check that the SRL even exists. TMD file is loaded first.
Makes sense since TMD file determines file name of the .app file. It's how it would know what file name to expect for the .app.
dont! I think 0.7 has some issues. I got bricked from it despite following the correct steps!is it necessary to update from unlaunch 0.6 to 0.7?
do i need to uninstall it first ?
the 1.4.5 softbrick has been fixed in 0.8dont! I think 0.7 has some issues. I got bricked from it despite following the correct steps!
How do I fix the 0.7 softbrick? I have it .0.8 seems to fix the 1.4.5 soft brick issue and it also write protects Launcher and TMD and the folder it's in. There shouldn't be any bricking issues now as long as you use the installer properly.
How do I fix the 0.7 softbrick? I have it .
I personally can’t boot to the DSI menu. It gets stuck on the Unloader splash screen. If you press any buttons it says a error has occurred. An identical thing happened to another user with the exact same color DSi XL (the burgundy one) also on Unloader 1.7.Just run the 0.8 unlaunch installer as bootcode.dsi on your SD card. It will upgrade/replace an existing Unlaunch installation just fine.
I personally can’t boot to the DSI menu. It gets stuck on the Unloader splash screen. If you press any buttons it says a error has occurred. An identical thing happened to another user with the exact same color DSi XL (the burgundy one) also on Unloader 1.7.
Ohhh. Alright. Would it be possible to use bootcode.dsi to finish the HiyaCFW install if you lost your SD card? Just curious.You don't need to boot DSi menu to update Unlaunch. As I said, just download unlaunch.dsi and rename it to bootcode.dsi. Put to root of SD card and then start DSi. Unlaunch will launch that instead of DSi Menu where your error was coming from.
you mean the unlaunch one? no way to remove that but uninstalling unlaunch, but if you mean the hiyaCFW one, yea, you can disable that, which you can even disable every splash screen, so that it boots straight into the menuHey I attempted to install unlaunch and succeeded but I actually didn't like the splash screen when you power on the dsi. I was wondering if there was anyway to disable that and restore to original dsi boot or to uninstall unlaunch completely.
Thanks if anyone knows
Also I already deleted the dsi boot
I was trying to install hiyacfw but my nand didn't have the no gba footer and I couldn't complete the downloadyou mean the unlaunch one? no way to remove that but uninstalling unlaunch, but if you mean the hiyaCFW one, yea, you can disable that, which you can even disable every splash screen, so that it boots straight into the menu
once you boot into emunand, you get to choose whatever you put at startup, whether it be the hiya splashscreen, the the DSi splashscreen or bothI was trying to install hiyacfw but my nand didn't have the no gba footer and I couldn't complete the download
Also by straight to the menu do you mean the nintedno bot menu or will it show the unlaunch or jiyacfw boot screen?
--------------------- MERGED ---------------------------
Also how do you create the NAND with the No GBA footer?
i didnt, i dont even know what you are talking aboutBut how do you add the no gba footer to the backup NAND?