Normal unlaunch uninstalls can cause bricks. This happens from unlaunch corrupting the TMD, but since there aren't many dumps of unlaunch bricked consoles, I tested other possiblilities to see what does what. Here's what I found...
| Issue | What it looks like | Proto TMD recovery? | TMD size | Notes | Unlaunch is corrupted | White screen | No | ~192kb | Corrupted unlaunch will still try to load. Proto TMD won't be used. |
|---|---|---|---|---|
| Launcher is corrupted (no TMD) | Error: 1-2435-8325 | Yes | 0 | |
| Launcher is deleted (no TMD) | Error: 1-2435-8325 | Yes | 0 | |
| TMD is corrupted | Black screen | Yes | 520b | |
| TMD is deleted | Black screen | Yes | 0 | |
| TMD is valid, but for another launcher | White screen | No | 520b | Since the TMD is valid, stage2 will not detect an error to switch the proto TMD |
| TMD first 520b is blank, but unlaunch is okay |
Black screen OR Unlaunch keeps working |
No | ~192kb | @Dash01 had brick from this issue. I tried using the same TMD on my DSis but unlaunch just booted for me... Dash01 had an older DSi so the only thing I can think of is if it used an older WiFi board (DWM-W015). I only tested on newer (DWM-W024). Someone should test the bad TMD pretty please. |
| TMD is blank and not truncated (unlaunch section blank) | Black screen | No | ~192kb | |
| TMD is okay but not truncated (unlaunch section blank) | Black screen | No | ~192kb |
So basically...
NAND:/title/00030017/48434141/content/title.tmd).
However, this only works if the real Launcher's TMD is truncated. All cases of a bad and >520b TMD can't take advantage of the prototype launcher.
It might be a good idea to truncate the TMD if an install/uninstall fails in order to force the backup unlaunch.
If the backup is installed then nothing can really go wrong at that point.
| Issue | What it looks like | Proto TMD recovery? | Notes |
|---|---|---|---|
| HWInfo is broken | Error: 1-2435-8325 | Yes | My region changing guide breaks HWInfo |
There is a drawback to this sadly. v1024 of the launcher (only in 1.4.2 firmwares) will give 'an error has occurred' if the proto TMD isn't a valid TMD (eg. blank, corrupt).
You must check the launcher version before installing the backup unlaunch.
Should probably add that this is an issue both when the backup unlaunch is active and dormant.