Wonder why nobody crawls to the DSiBrew servers? I was completely disrespected and treated awfully there. The rate of the guide working is 40% of the time. I respect dsiguide.me for one thing. It had no ads, and the whole philosophy of the site is way better than the one of dsi.cfw.guide. dsiguide.me was made to provide people with a guide, as there wasn't one. dsi.cfw.guide was made for the reason "I was unsatisfied with the other guides". Like come on, if you rip off another guide, don't add insult to the injury and put four ads on every page. Come on, you can't make a guide and blame the user for every mistake. That isn't user friendly. People only go to that server if they have problems, and it's depressing.
Sure they go to the server if they problems, but look on the bright side. Most of the people's problems are solved!
Another reason why they go there, is because ugopwn isn't working for them, and we have to tell them to use Filpnote Lenny instead.
Filpnote Lenny is made by WinterMute, and putting it on any guide is going against WinterMute's wishes. He has a reason for everything.
Sure, ugopwn's bugs can be fixed, but real life gets in the way of doing that.
Also, why ads? Check
here. This applies to dsi.cfw.guide as well.
It doesn't matter how early the scenes are, it's all the same people. Out of all people, why would you complain about this? Blaming the user for all the problems is a TERRIBLE way to think! If something works for some people, that DOESN'T mean it will work for everyone! Here is a story I made using that logic:
Guy1: Hey! I found this new soda machine hack! To do it, type 1337 and you will get free soda!
Guy2: I'll try that at my local Walmart.
*later*
Hey, it didn't work. I tried twice, and instead I wasted my time.
Guy1: thats ur fault lol not mine u did it wrong
Well, you are right about the fact that if something works for some people, that doesn't mean it will work for everyone.
For example, they've followed the guide correctly, and HiyaCFW just white screens for some people, but, the cause may be that the SD card is bigger than 2GB, or it may be something else we don't know about yet.
Also, there's this one guy who has bricked his DSi by restoring a NAND backup. The cause of the brick was that
he forgot to encrypt his NAND backup, and he found that out himself, if you ask me.
Come on, you're better than this. I've suggested nicely to make a clean backup, and couldn't receive that. Ask many people, they would want that. One ridiculous thing is how the user has to install a lot of programs! Come on, you can avoid most of the programs being used.
Because we've said your NAND backup is already clean. How much cleaner can it get?
I have made lots of NAND backups with fwTool 1.6.0, just to change a file or two in it, and restoring the backups to my DSi was no problem at all.
To avoid the risks of bricking your DSi with a NAND backup, the backup has to be encrypted, and I've always made sure of that.
If you're really worried about bricking your DSi, then just buy another DSi, but buy an XL/LL one, as it'll very likely have Flipnote.
I'm sorry to say this, but if you don't believe what I've said, and/or the fact that your NAND backup is clean, then I have no choice but to ask you to leave, and not bother us (the TWL team and the ones who worked on dsi.cfw.guide) again.
I will not be replying to you again, after this post.