Homebrew [DSi] DSiBrowserHax VS. ugopwn (FlipNoteHax)

[driverdis]

To clear up: no3.

the leak from a while back is NOT SAFE. please don't attempt to install it (yes, there are reports of success, it is still very dangerous to use this early build)



If for whatever reason you still have your heart set on tracking it down and risking your DSi, fine.

and how does the leak brick a DSi exactly? The answer is ; It does not brick it. all the bricking problems are caused by people flasing a corrupt (includes leaving the no$gba header by accident) or decrypted dump.
These are operator errors, and not the fault of the leak. The entry point only works on USA region consoles and takes a few steps to run, but the entry point/exploit itself does NOT brick a DSi.

to sum it up,
running the leaked ugopwn exploit itself (as in just executing the exploit, as in not running FwTool at all or running FwTool and doing nothing with it other than powering ) will not brick a DSi.
if someone wanted to, they can run ugopwn all day if they want without bricking their DSi. I understand people's feelings about the leak but using scare tactics to convince others that the exploit itself is not safe is just plain wrong.

 

[jamezfat]

I think the leak’s been removed anyways

yea, but it's the internet. if you want to find it, you can.
I'd advise against it still...

 

[MrMcTiller]

yea, but it's the internet. if you want to find it, you can.
I'd advise against it still...

Well all the noobs won't take your advice and use it anyway. Then they make millions of posts ranting about how it broke their system.

 

[jamezfat]

Well all the noobs won't take your advice and use it anyway. Then they make millions of posts ranting about how it broke their system.

yea, while like driverdis said: it in itself won't neccicarily brick, it still isn't safe to use in it's entirety...

the reason we are just leaving it at:
"dangerous" is to keep it simple and to the point so as to avoid confusion and such... if one wishes to know more, they can ask.
but at this point in time it still isn't useful for much anyway...

 

[Billy Acuña]

To clear up:



no.1

yes, it is still happening

(as at least so far, it's yet to be cancelled)

no.2

the original date was an estimate and for all we know, it May come out tomorrow, or 3 years from now, we will say if it gets a set in stone release date, and say if it is scrapped.

(please stop spamming questions about such)

no3.

the leak from a while back is NOT SAFE. please don't attempt to install it (yes, there are reports of success, it is still very dangerous to use this early build)



If for whatever reason you still have your heart set on tracking it down and risking your DSi, fine.



but don't come back and blame it on the original creator(s) as that will only cause unnecessary drama and prolong the official release.





Its coming, *eventually*.



have



p a t i e n c e

Not happening anyways.

 

[jamezfat]

Not happening anyways.

I'm confused, is this some kind of inside joke? are you trolling? or do you have *any* concrete proof that it has been cancelled?

 

[Deleted member 424658]

yea, while like driverdis said: it in itself won't neccicarily brick, it still isn't safe to use in it's entirety...

the reason we are just leaving it at:
"dangerous" is to keep it simple and to the point so as to avoid confusion and such... if one wishes to know more, they can ask.
but at this point in time it still isn't useful for much anyway...

The exploit itself is 100% safe to use. Running the exploit has literally no chance in causing harm to your system.
Editing your nand? That's got a good chance of bricking if you do something wrong or use the wrong tool. Other than that, you can't brick (software wise).

 

[lordkaos]

obviously the one that works better, i don't know why you decided to make a thread with a tittle like this when none of the 2 exploits have been officially released yet.

 

[jamezfat]

The exploit itself is 100% safe to use. Running the exploit has literally no chance in causing harm to your system.
Editing your nand? That's got a good chance of bricking if you do something wrong or use the wrong tool. Other than that, you can't brick (software wise).

the exploit itself is safe, yes.
but what people would be using it to run is not ready either.
we don't want someone to think that they can start using stuff now, so we keep it simple and say it's "not ready" or "unsafe" .
as it is indeed not ready, and while mostly safe, not in it's entirety.
If someone wishes to learn more into it, they can. the info isn't that hard to find.
if someone feels that they really want to install it now, they can... if they take it a step too far and screw it up that's on them...

but unfortunately, a lot of times when that happens it gets blamed on a poor product / programing rather than a user mistake or otherwise.

an early project doesn't have as much backup when someone complains as less people are using it and fully understand it...

and it's in an unfinished state, meaning it's always changing: wich causes even more confusion over what is "safe" and "not safe"

and on top of this, shutterbug2000 has gone to many lengths to remove early builds and leaks...

so even if you completely disagree with all my other above arguments, this one is just courtesy.

it's a free exploit made by someone in their own time while receiving no money for such.

they have respectfully asked that early copies be taken down and not used.
while no-one can stop you, it is the creators asking.


so until it has a concrete cancellation
where such problems don't really apply anymore, just hold off?




maybe

but again no-one can stop you.
soooo yeah