WH4LE

A debug window is a newly-implemented window type in ChromeOS. This debug window is supposed to be unaccessible by normal means; it\'s only intended to be used by Google employees. Once opened, a debug window has the ability to completely disable any extension, install any extension, edit policies, or unenroll completely.

Since a debug window opening on an enrolled device wouldn\'t be good, Google made it very hard, nearly impossible to open one. Normally, you\'d need to do a very tedious process with Google to even see a debug window, much less use it.

Okay, so what is WH4LE, and how does it work?

Even though Google made it so hard to open a debug window, it\'s surprisingly easy to open one using WH4LE. WH4LE uses a glitch in the way Chrome runs JavaScript to trick it into creating a debug window instead of a normal popup window. In fact, ChromeOS shows the debug window as a normal popup window due to the way it\'s opened. The specifics of this exploit are incredibly hard to explain, so I won\'t explain them here. However, as stated earlier, it\'s surprisingly easy to cause this glitch to occur.

Note that, as stated earlier, debug windows only exist in ChromeOS. WH4LE won\'t work on Windows or Linux computers.

After this debug window opens, it allows you to do nearly anything thinkable on your Chromebook. You can completely unenroll, disable WP, unblock devmode, install any extension, and install completely new OSes from this debug window. Google even has an option to directly flash SH1MMER to the internal storage, I assume to test their patch for it.

How do you even use WH4LE?

Even though WH4LE is incredibly easy to do, there\'s still a decent amount of steps to do it. There isn\'t any rush when performing WH4LE, unless the current step says there is. The fastest you\'ll have to do smth, however, still gives you a few seconds to do it.

Since you now have the file done, you can now open the debug window. However, there is a caveat to this at the moment. After the debug window opens, ChromeOS will immediately detect that you aren\'t allowed to use it, and it\'ll close when you try to use it.

To show you this, here\'s the button that\'ll open the debug window: . Notice how the debug window vanishes after being interacted with? That\'s ChromeOS detecting that you aren\'t allowed to use it and closing it.

There seems to be no way around this... right? There\'s no way Chrome would have a bug that would cause ChromeOS to not detect that you wouldn\'t be allowed to use it... right?

The LankyBypass

I have no idea how or why this works, and why it has to be this URL.

Going to this YouTube URL, https://youtube.com/watch?v=vEHh51zFS28, will cause a memory leak in the Chrome browser. I cannot tell you why this happens. My personal belief is that the video is so cringey that it causes the memory leak. This memory leak, although fixed by Chrome very fast, is exactly what WH4LE needs to function. During the small amount of time this memory leak is occuring, ChromeOS won\'t be able to verify whether you are or aren\'t allowed to use the debug window, and due to Google\'s bad programming, defaults to you being allowed to use it.

That comes up with another issue though. Since you need to open the video and the debug window so quickly in succession, it should still be impossible to do this. You can\'t open a tab and a new window so quick. Unless a website does it for you using JavaScript and some HTML.

The final button.

So... we have done it. We have found a way to open a debug window, and trick ChromeOS into thinking we are allowed to use it(albeit by a very cringey method).

This is the final button. Drag this text into a new tab, than press the button as fast as possible. The memory leak from the video will prevent ChromeOS from finding out you can\'t use the debug window, allowing you to use the debug window.

But wait, how do I use this? There\'s a login!

That was also hard for me to deal with, but I have found a login that works.

User: Matthew.Smith@google.com

Pass: h@Jm#*-_@[}k|m@JmWMO^S./;kQmiw/?*nES3_TADC,&:@|S]/kW;Q}M|k?

Don\'t ask where I got this from, but it works. After you\'re logged in, you have full reign over your Chromebook.

Thanks to @Whar? (Discord: adigitalmoon) for buying the domain whale.mom.

Thanks to Kilo (website: kkilouwu.bio) or (Discord: kbna.) for hosting this site.

Thanks to @Windows XP (Discord: windowsexperience) for the amazing favicon.

Thanks to @NuclearNatoCat (Discord: nuclearnatocat) for writing the HTML for this site.

What even is a debug window?

Okay, so what is WH4LE, and how does it work?

How do you even use WH4LE?

The final button.

But wait, how do I use this? There\'s a login!

🐋