Homebrew Please RECONSIDER it good to install UNLAUNCH !!!

[NightScript]

Maybe if unlaunch wasn't closed source proprietary garbage we wouldn't have issues like this

1. It wouldn't matter if it were open source or not, since everything is in ASM either way.
2. Can you not act like a dick and call it garbage? It isn't; it helps us so much in a multiload of ways (dumping slot 1, launching hiyaCFW, autobooting homebrew, etc).

 

[IC_]

1. It wouldn't matter if it were open source or not, since everything is in ASM either way.
2. Can you not act like a dick and call it garbage? It isn't; it helps us so much in a multiload of ways (dumping slot 1, launching hiyaCFW, autobooting homebrew, etc).

The exploit and the things you mentioned are the only good things about it, everything else about it is garbage, sorry but I am not going to support this kind of a***e proprietary software that """improves""" things in the DSi system and doesn't let you change or disable it and also has that ugly background in it's menu that you'll never be able to change or just get a solid color background
If it really is all assembly it still makes a huge difference to be messing with raw machine code or anything you can decompile from it compared to the original assembly code that's probably split into multiple files and has human readable labels and comments

 

[KleinesSinchen]

The exploit and the things you mentioned are the only good things about it, everything else about it is garbage, sorry but I am not going to support this kind of a***e proprietary software that """improves""" things in the DSi system and doesn't let you change or disable it and also has that ugly background in it's menu that you'll never be able to change or just get a solid color background
If it really is all assembly it still makes a huge difference to be messing with raw machine code or anything you can decompile from it compared to the original assembly code that's probably split into multiple files and has human readable labels and comments

In general I agree with you (though "garbage" is a pretty harsh word). Even when dealing with assembly it's a huge difference if somebody tries reverse engineering or if there is commented assembly code. And open source is always better (my opinion).

I like the patches to "Launcher" (No H&S screen, no noise music and sound → faster booting) but they should be optional.
The pictures… seems nobody likes them. I wouldn't even care if it wasn't for bad readability in File Menu. So yes, it would be better to have a solid color background.

However it's up to the developer to decide open/closed source. He offers a free software (free beer, not freedom). This is a "take it or leave it". For me unlaunch is a HUGE improvement over the stock firmware. It boots right away into TWilight Menu++ or when holding a button to SysNAND launcher (allowing DSiWare without tickets). The ugly picture is nowhere to be seen. I would never ever even think about uninstalling it on a DSi used for gaming. I'm pretty happy with unlaunch (and would like to give a "Thank You!" to nocash at this point).

When it comes to uninstalling CFW: I'm always against this – especially if it is one of the "I want to sell and not mention previous modification"-cases.
==================

Back to the main topic: It would be nice if somebody was able to find out what causes unlaunch to brick a DSi (systematic tests with a hardmodded unit). The most frequent cause was uninstallation. But it seemingly can happen on initial installation which is pretty bad. I think I will try hardmodding my test DSi as well and start a test series myself if I succeed.

 

[NightScript]

also has that ugly background in it's menu that you'll never be able to change or just get a solid color background

If you read the write-up, you'd know that the background is needed due to padding of the title.tmd file. You're just too busy worrying about "proprietary" that you'd never read it though (like whenever someone sends a screenshot and you just say "windows")

compared to the original assembly code that's probably split into multiple files and has human readable labels and comments

Any proof that there is comments and it's split into multiple files? Cause otherwise, it'd be quite pointless to have the source code.

 

[IC_]

If you read the write-up, you'd know that the background is needed due to padding of the title.tmd file. You're just too busy worrying about "proprietary" that you'd never read it though (like whenever someone sends a screenshot and you just say "windows")


Any proof that there is comments and it's split into multiple files? Cause otherwise, it'd be quite pointless to have the source code.

I did read that a long time ago, why not just make the padding anything else like a solid background or just pad it with random numbers or 0's that will never be read by the program?
No proof but there's no way any human would write such a large program in only a single file and without comments or human readable/variable names because they also need to find themselves in the code and not be as lost as any random person with decompiled machine code
Did you read my full previous post? I'm not just "worrying about proprietary", I'm complaining about it because the proprietary program forcefully does things you might not want it to do and you don't have the freedom to disable it and change how the program works

 

[ManuEcheveste]

A little update with the hardmod I'm making to my DSi, it's hard as hell, a lot more than I tough, so don't expect me making the post with the results soon (maybe in a month or less, probably in two weeks), but so far I'm having good results, I've soldered the cables to the micro SD adapter and a male 4 pin connector, the only thing that I still haven't done yet is solder cables in the tiny, microscopic Nintendo DSi pins, because I don't have the right tool to do it (mine instead of solder 1 pin, it will solder 3!), so I'll have to order another thing so I can solder the subatomic pins to the cables, then solder the cables to a female 4 pin connector and then, make a hole in the DSi case to put the female conector, and then test if i can recover my NAND'S backup.
How are you doing with your hardmod @alexander1970 ? (I think you're doing one too), Are you having better results than mine?

 

[KleinesSinchen]

A little update with the hardmod I'm making to my DSi, it's hard as hell, a lot more than I tough, so don't expect me making the post with the results soon (maybe in a month or less, probably in two weeks), but so far I'm having good results, I've soldered the cables to the micro SD adapter and a male 4 pin connector, the only thing that I still haven't done yet is solder cables in the tiny, microscopic Nintendo DSi pins, because I don't have the right tool to do it (mine instead of solder 1 pin, it will solder 3!), so I'll have to order another thing so I can solder the subatomic pins to the cables, then solder the cables to a female 4 pin connector and then, make a hole in the DSi case to put the female conector, and then test if i can recover my NAND'S backup.
How are you doing with your hardmod @alexander1970 ? (I think you're doing one too), Are you having better results than mine?

That is also my problem and the reason why I did not yet attempt a hardmod myself for experiments.
I do have an soldering iron with very fine tip… but my shaking hands make this nearly impossible. Will try nevertheless when I have one of the better days (less shaking hands).

 

[Alexander1970]

A little update with the hardmod I'm making to my DSi, it's hard as hell, a lot more than I tough, so don't expect me making the post with the results soon (maybe in a month or less, probably in two weeks), but so far I'm having good results, I've soldered the cables to the micro SD adapter and a male 4 pin connector, the only thing that I still haven't done yet is solder cables in the tiny, microscopic Nintendo DSi pins, because I don't have the right tool to do it (mine instead of solder 1 pin, it will solder 3!), so I'll have to order another thing so I can solder the subatomic pins to the cables, then solder the cables to a female 4 pin connector and then, make a hole in the DSi case to put the female conector, and then test if i can recover my NAND'S backup.
How are you doing with your hardmod @alexander1970 ? (I think you're doing one too), Are you having better results than mine?

Thank you,I am waiting for the Adapters (should arrive today/tomorrow).


I have ordered 2 Pieces,in Case something goes "wrong".
Yes,I looked on the Manual Pictures and then on the DSi,smaller as I had in Mind (it must be 3-4 Years,when I assembled the Black/Red one from the 2-3 DSi´s..it gives me a litte "shiver" honestly.....).

Weather seems "rainy" the next Days,so I (hope) think all goes well.

I wish you good Luck on yours,my Friend.

 

[ManuEcheveste]

my shaking hands make this nearly impossible

I have the same problem since I was a kid, I know the body is in constant movement, but apparently ours is in an earthquake always, and my solder isn't very confortable to use, so I'm thinking if I should do it myself, or give it to someone that has more experience.

I wish you good Luck on yours,my Friend.

I'm happy to see that everything is going well for you, I wish you good luck too and hopefully everything goes well.

 

[removedcables]

Over on various subreddits I've recommended people follow the Nintendo DSi Custom Firmware guide when they ask about which flash card to buy if they say they've got a DSi. Ever person I've recommended that to has ended up with a bricked DSi. From now on I'm just going to recommend they just use memory pit with TWiLight menu++ or get a R4i Gold 3DS. I had no idea unlaunch wasn't opensource. I thought everything in the homebrew community that wasn't being sold for a profit was open source. It really makes no sense for a program like this to not be opensource. I don't see how a program like this could be monetized. There is more benefit for unlaunch to be opensource. It would allow the community to improve upon it and figure out this bricking issue.

As for the political message, I never noticed it until it was mentioned in this thread. I had to look up videos of unlaunch to see it. I think we should keep politics out of homebrew. It comes off as immature, a program like this is not the venue for spreading political ideas. I'm not taking sides on the message because I don't get involved in politics at all. I spend my free time and effort on video games not politics.

 

[KleinesSinchen]

Over on various subreddits I've recommended people follow the Nintendo DSi Custom Firmware guide when they ask about which flash card to buy if they say they've got a DSi. Ever person I've recommended that to has ended up with a bricked DSi. […]

What? That sounds a bit strange and exaggerated. Many people followed dsi.cfw.guide and did not end up with a bricked device – even before unlaunch was made an "optional step" on the guide. Not every unlaunch (un)installation ends up with a brick. That is complete misinformation and would have resulted in many, many, many threads here on the forum.

Spoiler: off topic

Over on various subreddits I had no idea unlaunch wasn't opensource. I thought everything in the homebrew community that wasn't being sold for a profit was open source. It really makes no sense for a program like this to not be opensource. I don't see how a program like this could be monetized. There is more benefit for unlaunch to be opensource. It would allow the community to improve upon it and figure out this bricking issue.

As for the political message, I never noticed it until it was mentioned in this thread. I had to look up videos of unlaunch to see it. I think we should keep politics out of homebrew. It comes off as immature, a program like this is not the venue for spreading political ideas. I'm not taking sides on the message because I don't get involved in politics at all. I spend my free time and effort on video games not politics.

I also prefer open source software and am a happy Linux user since about 2006 or 2007. I'm not dead set against using closed source software (NVIDIA drivers for example) if it provides any benefit for me. Yes, this is opportunistic.

Not every homebrew developer decides using open source licenses and I can understand their arguments: Loosing control, code being used without giving proper credits or even for monetization. Guess why the Wii HackMii Installer wasn't released open source and has it's own DRM included: To prevent greedy people from deriving their own version and selling it as a commercial hacking tool.

But this has literally nothing to do with this thread. Discussing whether unlaunch should be open source and if it carries any unnecessary messages does nothing for finding out what goes wrong on (un)installation. If you don't like unlaunch or nocash's attitude or closed source software in general: Stay away from it. Unlaunch proved to be extremely useful for me and a friend and we have several DSi consoles with this bootcode exploit in use since Memory Pit as initial entrypoint has been released. As long as one does not touch a working unlaunch (uninstall, update) there does not seem to be any risk. Prove me wrong. I'm always interested in learning. If you have any sources for spontaneous, unlaunch related bricks of a previously working DSi not involving an uninstallation or upgrade: Please share it.

 

[NightScript]

and NoCash seems a little "uninterested" to Answer the Situation (@Robz8 and a User asked him but got no Answer) so I think it HAS to do with V2.0:

http://forums.nesdev.com/viewtopic.php?f=23&t=17581&start=195

You mean me? (I'm NightScript)

As for the political message, I never noticed it until it was mentioned in this thread. I had to look up videos of unlaunch to see it. I think we should keep politics out of homebrew. It comes off as immature, a program like this is not the venue for spreading political ideas. I'm not taking sides on the message because I don't get involved in politics at all. I spend my free time and effort on video games not politics.

What political message?

even before unlaunch was made an "optional step" on the guide.

Actually, I made unlaunch optional on the guide simply because a) It isn't that needed and b) At the time of writting, I got 3 users who reported bricks. Then again, I've helped a lot of people and yeah, none of them had bricks except for those 3 users.

 

[banjo2]

What political message?

"No one is illegal" I assume

 

[Alexander1970]

Update:

- soldered the SD Adapter
- soldered the DSi

seems ok,but no Device detected in Windows

Tried 3 different Card Readers included the recommended Anker Modell.
Tried 2 Windows 10 (32 and 64bit) and Windows 7 (32bit).
Tried different USB Connectors (Front/Rear)
Tried first connect the Reader/SD Adapter and powered the DSi on and vice versa.


A little Pictures (do not expect Profi Work please....):






A little Word about microSD Adapters:

"Some" says,there are no Difference.....

maybe...


The first was a SANDISK and it brokes after Opening....


Thank you for Reading.

 

[KleinesSinchen]

Can we get a better picture of the motherboard? Your camera is not able to deal with low light situations and has far tooooo long exposure times for holding it in your hands

Either use a tripod with self-timer to minimize in-movement unsharpness… or more light (best go outside and use bright daylight).

As you already know: I failed trying to solder to R113 and lost the resistor.

 

[Alexander1970]

Can we get a better picture of the motherboard? Your camera is not able to deal with low light situations and has far tooooo long exposure times for holding it in your hands

Either use a tripod with self-timer to minimize in-movement unsharpness… or more light (best go outside and use bright daylight).

As you already know: I failed trying to solder to R113 and lost the resistor.

Did you get the Screen with "0000FE00" ?
Anyways,Project is actual "dead"...
(PM,Sinchen).

 

[susi91]

Update:

- soldered the SD Adapter
- soldered the DSi

seems ok,but no Device detected in Windows

Hey^^
Picture quality is bad
Besides that, you should keep the cables as short as possible, in order to avoid connection problems, interferences and so on.
Regards^^

 

[KleinesSinchen]

Did you get the Screen with "0000FE00" ?
Anyways,Project is actual "dead"...
(PM,Sinchen).

Yes. As far as I know the bootloader error is expected while the DSi is connected to the computer. Though I've read from hardmod attempts that resulted in permanent error even after removing the cables (NAND shorted while trying to connect to computer??)

I can't even continue my attempt until I get a new resistor and/or another cheap motherboard. Not a big loss. My test DSi was pretty much unusable before my failed soldering attempt. Great way to get some experience anyway.

 

[Alexander1970]

Hey^^
Picture quality is bad
Besides that, you should keep the cables as short as possible, in order to avoid connection problems, interferences and so on.
Regards^^

Yes,my Camera and me are not really good Photographers.

But it is also a "shame" that no one ever really posted good Pictures.
Many Users had seemly doing the Mod but nobody posted Pictures here.....

 

[ManuEcheveste]

Ok, so your hardmod doesn't working is a little bit scary for me xd
I haven't done de hardmod, because I was busy with other stuff and that, but at this point I'll try my best.
Also, I got a little theory here, listen (or read xd):
Since I've a backup of my NAND, and with the tutorial I've been following, this guy (that made the tutorial) decrypted his NAND, that got me thinking... "If the hardmod doesn't works, why I don't decrypt my nand, and encrypt it in the other mother board's code"
What do you think? Do you think it can work? To use it like the last resource