Hacking New 5.5.1 Entrypoint, apparently exploit works!

[Bkool999]

Big question, 5.5.0 users, update to 5.5.1 or not? Only reason: Eshop. Is there anything semi-brick code in 5.5.1, like the one for 3DS browser on 9.9+

Probably best to stay on 5.5.0. You never know when you're just gonna get screwed over when it comes to homebrew scenes.

 

[Chuardo]

whats th point? If its patched, there is no reason to keep it private.

The Kernel Exploit is still unpatched, only the Userspace Exploit was patched (Or that is what they thought) so they released it because of that.

 

[tivu100]

Probably best to stay on 5.5.0. You never know when you're just gonna get screwed over when it comes to homebrew scenes.

That's my point in the 2nd question when citing the incident with 3ds 9.9+ browser as people got carried away with Eshop and updated to 9.9+ and got locked for some time leading to Cubic Ninja price sky rocket. Perhaps Yellows8 knows there's a trap in the 5.5.1 that eventually kills off the exploit (Nintendo triggers the time bomb?) so he deemed the exploit as dead , while it's not officially dead yet as we found out today?

So it's basiccally Yellows8's own way to prevent people get too hyped and fall into Nintendo trap on 5.5.1, by releasing the exploit leading people thinking the exploit was patched on 5.5.1. Then some random persistent European dudes just spoilt the plan

 

[gamer4lif3]

Huh what are u saying they released some kind of timed code bomb or remote code Bomb?

 

[Flux0]

I considered updating to have eshop access again, but in the end it isn't worth it.

I got plenty of games to play for now, so I'm waiting and see what happens. I think everyone else should do the same. I got my Wii U set to offline and 5.5.0 at least has an entry point for sure. That alone is more than it had a week ago. So holding off for a while isn't going to hurt anything.

 

[tivu100]

Huh what are u saying they released some kind of timed code bomb or remote code Bomb?

For 3ds 9.9+, Nintendo silently put a browser brick code which went for months without anyone noticed at one time. Then people got carry away keep updating to latest firmware to get access to Eshop while using browserhax! Then one day Nintendo triggered the code which calls home and bricked O3DS browser which required an update to latest firmware which kill browserhax. That went for months until newer browserhax version released in the end of December. And 3DS borwser is made by Yellows8 too!

Perhaps history repeats itself and Yellows who examine code, may knows what we don't?

There was this joke at that time on 3DS section that Nintendo may consider doign something like this

"
To access 3D -> you need to update to latest firmware
To charge your 3DS -> you need to update to latest firmware
To turn on your 3DS -> you need to update to the latest firmware
...
"

 

[justinjustin7]

Yes, my voice is cringy AF, yes the video is shit quality, but it works!

your voice ain't cringy, but then again I like punk singers and their f'd up voices /offtopic

anyways, since we still have userland everybody needs to make sure they don't update, since those who accidentally updated got super lucky this time. /ontopic

 

[gamer4lif3]

For 3ds 9.9+, Nintendo silently put a browser brick code which went for months without anyone noticed at one time. Then people got carry away keep updating to latest firmware to get access to Eshop while using browserhax! Then one day Nintendo triggered the code which calls home and bricked O3DS browser which required an update to latest firmware which kill browserhax. That went for months until newer browserhax version released in the end of December. And 3DS borwser is made by Yellows8 too!

Perhaps history repeats itself and Yellows who examine code, may knows what we don't?

There was this joke at that time on 3DS section that Nintendo may consider doign something like this

"
To access 3D -> you need to update to latest firmware
To charge your 3DS -> you need to update to latest firmware
To turn on your 3DS -> you need to update to the latest firmware
...
"

would emunand prevent such a code?

 

[tivu100]

would emunand prevent such a code?

This off topic from this thread.

For 3DS to have EMUNAND, 3DS need to be 9.2 or lower. Then before yesterday, N3DS EMUNAND only supported up to 9.5 so (no Eshop). O3DS can have EMUNAND up to latest firmware to access Eshop. But N3DS has more power and more potential for homebrew scene, having to be stuck with O3DS is disappointing.

 

[Lucar]

This off topic from this thread.

For 3DS to have EMUNAND, 3DS need to be 9.2 or lower. Then before yesterday, N3DS EMUNAND only supported up to 9.5 so (no Eshop). O3DS can have EMUNAND up to latest firmware to access Eshop. But N3DS has more power and more potential for homebrew scene, having to be stuck with O3DS is disappointing.

Reinand has support for 10.3.

 

[tivu100]

Reinand has support for 10.3.

Read my post again, not until yesterday (publicly). i was talking about months ago. When there were a long down period when browserhax on O3DS got butchered by Nintendo time bomb. We only have the new wave of 3DS hax back in late December.

 

[Lucar]

Read my post again, not until yesterday (publicly). i was talking about months ago.

Oh, OK. Sorry.

your voice ain't cringy, but then again I like punk singers and their f'd up voices /offtopic

Uh, I don't know if I should take that as a complement, or... OK. /offtopic

 

[justinjustin7]

Uh, I don't know if I should take that as a complement, or... OK. /offtopic

well, I am saying that I like your voice, so I'd say it's a compliment /offtopic

would emunand prevent such a code?

I can't imagine that it would need, since emunand *should* be able to stay on the latest firmware.

EDIT: wording

 

[OriginalHamster]

My DNS are ready, snatched enough games from eShop, would enable it again once we know some news about hykem exploit.

 

[JFalcon]

My DNS are ready, snatched enough games from eShop, would enable it again once we know some news about hykem exploit.

You got lucky! Hopefully we hear something soon.

 

[ShadowOne333]

I would love to see Nintendo's face right now.
They'd be like:

"Come on... We just patched this and these little fuckers got an entrypoint to this is less than a week!"
Priceless!

 

[OriginalHamster]

You got lucky! Hopefully we hear something soon.

Heh, yeah! Couldn't get dumb twice in a row! ;p

 

[ihaveahax]

no idea if this is related but...

lol so turns out yellows8's wiiu browser exploit everyone thought had been patched works totally fine on 5.5.1 apparently

woops ?

— smea (@smealum) January 15, 2016

 

[Ichii Giki]

no idea if this is related but...
https://twitter.com/smealum/status/687901109742997504

Pretty sure @smealum is talking about the same thing as this thread.

 

[lonemoonHD]

That's my point in the 2nd question when citing the incident with 3ds 9.9+ browser as people got carried away with Eshop and updated to 9.9+ and got locked for some time leading to Cubic Ninja price sky rocket. Perhaps Yellows8 knows there's a trap in the 5.5.1 that eventually kills off the exploit (Nintendo triggers the time bomb?) so he deemed the exploit as dead , while it's not officially dead yet as we found out today?

So it's basiccally Yellows8's own way to prevent people get too hyped and fall into Nintendo trap on 5.5.1, by releasing the exploit leading people thinking the exploit was patched on 5.5.1. Then some random persistent European dudes just spoilt the plan

It's Yellows8's own exploit. He thought it was patched, so he released it for 5.5.0, but it turned out to also work on 5.5.1, so that's that.
--------------------- MERGED ---------------------------

Pretty sure @smealum is talking about the same thing as this thread.

He was. He sent out the link to the exploit on Twitter to notify people.