Homebrew HiyaCFW Discussion

  • Thread starter Thread starter CatmanFan
  • Start date Start date
  • Views Views 235,705
  • Replies Replies 1,385
  • Likes Likes 39

Are you excited for DSi CFW?

  • Yes

    Votes: 335 85.9%
  • No

    Votes: 55 14.1%

  • Total voters
    390
I feel your pain ;-;
Well if by unlocking the arm7 without rocket launcher you need a flash card or r4 than yes you are out of luck unless you can buy one online. Rocket launcher runs on the SD card without R4 though I believe a twl cartridge is needed as well.
 
Well if by unlocking the arm7 without rocket launcher you need a flash card or r4 than yes you are out of luck unless you can buy one online. Rocket launcher runs on the SD card without R4 though I believe a twl cartridge is needed as well.
I'm probably wrong, but wouldn't DSiWare work too?
 
I'm probably wrong, but wouldn't DSiWare work too?
Well that is the only way rocket launcher could launch and be able to install hiyacfw on your ds. So yes, but you need certain dsiware in order to run homebrew on your SD card.
 
Well to be fair, ugopwn took a while but still got a release.
but to be fair if anyone has a 3ds at this second then you can pretty much hack it now without a flash cart (seedminer)
but i also want this cfw for my dsi even tho its useless to me now.
 
An R4 is literally something not recommended. The only reason you would want a flashcard is for autobooting into RocketLauncher, and that's only been confirmed working on AceKard2i iirc.

That would be true if it was actually possible for anyone to install rocket launcher or hiyacfw. But AFAICT it's still heavily hoarded.
 
That would be true if it was actually possible for anyone to install rocket launcher or hiyacfw. But AFAICT it's still heavily hoarded.

I wonder what the big deal is for not releasing it. even if it were something like packaging up a friendly method of installing it, people with DSis here would not care since the only ones who will be modding those will be the same people who have the skills needed to follow a few (dozen) steps.
 
I wonder what the big deal is for not releasing it. even if it were something like packaging up a friendly method of installing it, people with DSis here would not care since the only ones who will be modding those will be the same people who have the skills needed to follow a few (dozen) steps.
People pester for release. gets release but users need to compile it theirself
People pester for easier method, some idiot writes a guide, guide bricks tens of hundreds who can't follow steps/because the guide is written badly
People now blame devs for bricking because they used their software instead of blaming their own stupidity/stupidity of guide creator

Quick Hypothetical
 
People pester for release. gets release but users need to compile it theirself
People pester for easier method, some idiot writes a guide, guide bricks tens of hundreds who can't follow steps/because the guide is written badly
People now blame devs for bricking because they used their software instead of blaming their own stupidity/stupidity of guide creator

Quick Hypothetical
This is what happens whenever cfw is released so I can't really disagree with you at all. That is just like when the bans on 3ds were happening and they blamed Nintendo but, they were told not to go online with unreleased games. The cycle continues.
 
  • Like
Reactions: CatmanFan
People pester for release. gets release but users need to compile it theirself
People pester for easier method, some idiot writes a guide, guide bricks tens of hundreds who can't follow steps/because the guide is written badly
People now blame devs for bricking because they used their software instead of blaming their own stupidity/stupidity of guide creator

Quick Hypothetical

This is nothing new, any release regardless of how polished it is ends in the same way. People will always be lazy and will always find a way to brick no matter how brickproof it is. People will almost always blame the dev for stuff that goes wrong so I think devs should just ignore them. People do this with consumer electronics all the time, blaming the manufacturer or sellers of electronics when they fail even though the sellers have no control and the manufacturers use parts made by other manufacturers so even they have limited control over build quality.
 
This is nothing new, any release regardless of how polished it is ends in the same way. People will always be lazy and will always find a way to brick no matter how brickproof it is. People will almost always blame the dev for stuff that goes wrong so I think devs should just ignore them. People do this with consumer electronics all the time, blaming the manufacturer or sellers of electronics when they fail even though the sellers have no control and the manufacturers use parts made by other manufacturers so even they have limited control over build quality.
Except, in the state that the exploit is in, it's hard to setup for a "consumer." It's also partially dangerous since the user has to modify their nand (manually, as the exploit is contained in the whitelist which is copyrighted, or potentially an xdelta patch could be used for distributing patches early on).
And (I'm 90% sure I'm wrong about this) if the whitelist ends up corrupted then the DSi might brick. The devs wouldn't want to release a buggy product without rigorous testing to make sure it works properly (see: OTPless A9LH).
 
  • Like
Reactions: AL_16

Site & Scene News

Popular threads in this forum