From 9660074ba591bd0e2269ed048e247a903a72f545 Mon Sep 17 00:00:00 2001 From: legoskid <94498086+legoskid@users.noreply.github.com> Date: Wed, 15 Jan 2025 19:22:26 -0800 Subject: [PATCH 1/2] Nasume --- index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/index.html b/index.html index e109178..2a4885c 100644 --- a/index.html +++ b/index.html @@ -47,6 +47,7 @@

what do i need to do this?

3. (PREFERABLY) access to chrome://network#logs
4. A leaked shim, a USB drive, and another pc to flash it 4.1. if you have a keyrolled dedede then you can buy a suzy qable(highly recommend this seller, bought from them and they're highly reputable) and use alternative steps i can provide/walk you through + 5. A device with CR50 (security) chip. You can check by looking up your board on cros.tech and seeing if there is only a codename and not a codename&board. BR1CK will work but you will get stuck at the sh1mmer step as gsctool doesn't exist on these chromebooks. A much much easier way to unenroll would be using BadRecovery while in developer mode.

From ee53349c86affcb31ed16b37f85fc76b534e7ffc Mon Sep 17 00:00:00 2001 From: legoskid <94498086+legoskid@users.noreply.github.com> Date: Wed, 15 Jan 2025 19:29:31 -0800 Subject: [PATCH 2/2] Nasume has hana --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 2a4885c..e7182ce 100644 --- a/index.html +++ b/index.html @@ -47,7 +47,7 @@

what do i need to do this?

3. (PREFERABLY) access to chrome://network#logs
4. A leaked shim, a USB drive, and another pc to flash it 4.1. if you have a keyrolled dedede then you can buy a suzy qable(highly recommend this seller, bought from them and they're highly reputable) and use alternative steps i can provide/walk you through - 5. A device with CR50 (security) chip. You can check by looking up your board on cros.tech and seeing if there is only a codename and not a codename&board. BR1CK will work but you will get stuck at the sh1mmer step as gsctool doesn't exist on these chromebooks. A much much easier way to unenroll would be using BadRecovery while in developer mode. + 5. A device with CR50 (security) chip. You can check by looking up your board on cros.tech and seeing if there is only a codename and not a codename&board (hana included). BR1CK will work but you will get stuck at the sh1mmer step as gsctool doesn't exist on these chromebooks. A much much easier way to unenroll would be using BadRecovery while in developer mode.