Homebrew Yellows8's Browserhax thread

  • Thread starter Thread starter teampleb
  • Start date Start date
  • Views Views 322,187
  • Replies Replies 812
  • Likes Likes 30
Status
Not open for further replies.
I've messed up... I updated. I ddn't know it would stop the hax. Is there ayway to remove the update or do I have to buy a new 2ds?
If you're just wanting to get regular homebrew back you could buy cubic ninja. (or wait for more entry points from smea & co)
If you were on 9.2, and didn't backup the nand, then you'll have to replace the 2ds.
 
Hm, what a picky exploit.
It worked just fine on my 9.8 o3ds after I cleared history/cookies/settings, but I've been trying for two and a half hours on a 9.2 2ds unsuccessfully.
I have the latest boot.3dsx at the root of a memory stick (I've tried several different sd cards) with themehax installer ready to go if I do get in. I've tried with both the payload on and off the memory stick.

Most of the time it makes it to flashing yellow when I click on the right side of the slider before it crashes to home menu, less frequently it crashes without changing to yellow.
I've tried zooming in, spamming a, hitting down+B when I throw my pokeball, still nothing.

Any tips or alternative ideas?
 
Hm, what a picky exploit.
It worked just fine on my 9.8 o3ds after I cleared history/cookies/settings, but I've been trying for two and a half hours on a 9.2 2ds unsuccessfully.
I have the latest boot.3dsx at the root of a memory stick (I've tried several different sd cards) with themehax installer ready to go if I do get in. I've tried with both the payload on and off the memory stick.

Most of the time it makes it to flashing yellow when I click on the right side of the slider before it crashes to home menu, less frequently it crashes without changing to yellow.
I've tried zooming in, spamming a, hitting down+B when I throw my pokeball, still nothing.

Any tips or alternative ideas?
Yeah, same. I'm having a load of trouble getting it to run. It flashes yellow and then changes to gray before crashing, and sometimes it won't even turn yellow before crashing.
 
Hi

So this is how I do it and my success rate seems to be about 70-80%. I'm running O3DS 10.1.0-27E.
I have the exploit URL, saved as a bookmark in my browser. First I open the browser clear cookies and history and exit the browser. I open it again and then open the bookmark with the browserhax exploit which uses a slider control. I zoom in and tap it a couple of times my screen goes yellow, then gray then finally red and homebrew launcher opens. My theme is set to a plain one like standard black. This has to be repeated every time. I'm not updating to 10.2!!
 
Yeah, same. I'm having a load of trouble getting it to run. It flashes yellow and then changes to gray before crashing, and sometimes it won't even turn yellow before crashing.
That doesn't sound the same. Getting to grey is a good sign, "At the start of this ROP-chain, the sub-screen colorfill is set to display yellow, at the end it's set to display gray." I cannot get to grey.

So this is how I do it and my success rate seems to be about 70-80%. I'm running O3DS 10.1.0-27E.
I have the exploit URL, saved as a bookmark in my browser. First I open the browser clear cookies and history and exit the browser. I open it again and then open the bookmark with the browserhax exploit which uses a slider control. I zoom in and tap it a couple of times my screen goes yellow, then gray then finally red and homebrew launcher opens. My theme is set to a plain one like standard black. This has to be repeated every time. I'm not updating to 10.2!!
Gave your method a try verbatim, and I'm achieving the same nonresults, yellow and crash.
I too have close to a 75% success rate with browserhax on my Old3ds, it's only on this 2ds I'm having issues, so I don't think I'm doing anything wrong..

If anyone has any ideas to help, the 2ds is on 9.2.0-12U upgraded from a Smash cart, Browser is 1.7552.

Are there any other homebrew entrypoints for 9.2 aside from having to buy cubic ninja, OoT, or relying on preexisting eshop content?
Smashhax is only for New3ds to my knowledge or I'd do that.
 
Can't you update the 2DS to 10.1 ?
I'm not sure how I'd go about doing that when the current firmware is 10.2, and even if I could, why would I want to lose the potential for kernel access?
 
I've messed up... I updated. I ddn't know it would stop the hax. Is there ayway to remove the update or do I have to buy a new 2ds?
ironhax, smashax, oot3dhax and ninjhax work fine under 10.2 if you had them installed already (with 10.1 payloads). Otherwise, you're screwed and need to pray for a new hax to be discovered.
 
Huh, from what I can tell 9.2.0-12U might actually be one of the less common 9.2 firmwares you end up on with a 9.2 smash cart. 9.2.0-17U seems to be the more commonly reported firmware.
My Smash Cart reads AXCE152***
DP H-3 D01-10
From what I can tell from https://gbatemp.net/threads/smash-brothers-4-us-with-9-2-0-recognizing-the-cartridge.383499/
the DP seems to be an unusual marking

I'm wondering if I just ended up on an unusually stubborn to exploit combo of FW/browser.
Trying to turn up more information led me to a five month old (before browserhax became such a necessity) reddit post from someone on the AC hacking subreddit.
Here are specs I've collected from people on tumblr and here on /achacking:

UNABLE:

  • Ver 9.2.0-12U, 1.7552 = UNABLE TO HACK
  • Ver 9.2.0-11E, 1.7552 = UNABLE TO HACK
  • Ver 9.4.0-21U, 1.7567 = UNABLE TO HACK
  • Ver 9.4.0-10U, 1.7498 = UNABLE TO HACK
  • Ver 9.2.0-11E, 1.7552 = UNABLE TO HACK
  • Ver 9.2.0-15U, 1.7552 = UNABLE TO HACK
  • Ver 9.2.0-12U, 1.7552 = UNABLE TO HACK
  • Ver 9.2.0-15U, 1.7552 = UNABLE TO HACK
  • Ver 9.4.0-12U, 1.7552 = UNABLE TO HACK
ABLE:

  • Ver 9.4.0-21U, 1.7567 = ABLE TO HACK
  • Ver 9.2.0-20U, 1.7567 = ABLE TO HACK
  • Ver 9.4.0-21U, 1.7567 = ABLE TO HACK
I’ve documented less “able to hacks” since that wasn’t really an issue, but started doing so now that we’ve had people with CORRECT software unable to hack.
https://www.reddit.com/r/achacking/comments/33v0ei/update_some_systems_cant_hack/

How accurate this information is, I'm not sure, but it makes me wonder if it explains some of the claims of people unable to get browserhax working.
 
Last edited by jaksy,
I just want to point out, and maybe this is just me, but when I try to run this on my o3DS on GW 9.8, I normally have to click on the top left corner of my browser to initiate the hax. On my N3DS on 10.1, it starts up by itself.

The thing with the O3ds, the thing I normally click on to make the hax work looks like this in the top right corner:

---|---

Like a volume slider gone only halfway. Just wanted to make sure this was normal, or if there's a way that this can help others.
 
Yup, the o3ds browserhax is often called sliderhax.
Old3DS: 3dsbrowserhax_webkit_r158724.php, aka "sliderhax".
To trigger it, wait for the page to fully load. Then ideally zoom in all the way, so that the slider is displayed as large as possible. Then touch the far right of the slider at the exact location where the slider ends, within the slider bar(the location you touch might(?) be related to how reliable the exploit is).
 
If your 2ds crashes to menu after gray in 10.1, go inmediately to dns settings, put it to manual (no auto) and modify the first dns ip. The system settings crashes.
 
Does anyone know what the results of trying to launch this properly on a 3ds with a pre9.0 firmware and therefore unsupported browser would be?
I'm wondering if the results would be similar to what I'm experiencing (can only get as far as yellow before crashing), as that would help me to know if I somehow ended up on an unusual browser/firmware combo that is unable to launch the browserhax spider exploit.
 
Does anyone know what the results of trying to launch this properly on a 3ds with a pre9.0 firmware and therefore unsupported browser would be?
I'm wondering if the results would be similar to what I'm experiencing (can only get as far as yellow before crashing), as that would help me to know if I somehow ended up on an unusual browser/firmware combo that is unable to launch the browserhax spider exploit.
Result at this moment is only crash!... Because there's not payloads for those FW versions.
 
Result at this moment is only crash!... Because there's not payloads for those FW versions.
Oh, that unfortunately doesn't clarify if they would respond the same way if they were loading the improper payload, or if they were being fed the incorrect exploit by some possible oversight in the user-agent identification process.
 
Oh, that unfortunately doesn't clarify if they would respond the same way if they were loading the improper payload, or if they were being fed the incorrect exploit by some possible oversight in the user-agent identification process.
Sorry, I don't understand what you want to get exactly with that!... Maybe another person can respond more accurately to your answer/words.
 
Sorry, I don't understand what you want to get exactly with that!... Maybe another person can respond more accurately to your answer/words.
Oh no worries, since there were more reports of these kind of unhackable consoles floating around months ago (when browserhax was just the spiderexploit and these odd fw/browser combos were easier to achieve), I'm just trying to figure out if this is some kind of isolated error on my end, or a legitimate issue carried over from spiderexploit that has been overlooked and needs to be addressed on the github page.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum