Bypass the "Set up your Kindle" screen on a Kindle Scribe?

[vendo232]

I have not registered my Kindle Scribe at all.

Is it possible to disable this pop up when going to Library?

[vendo232]

I just discovered that i did the JB in airplane mode and now Im locked out. Any way to unlock it or I have to update to the 5.16.2 fw and start the JB all over again?

Unable to turn on wifi, this is the msg I get

[nar001]

Originally Posted by vendo232

I just discovered that i did the JB in airplane mode and now Im locked out. Any way to unlock it or I have to update to the 5.16.2 fw and start the JB all over again?

Unable to turn on wifi, this is the msg I get

You need to install the hotfix

[vendo232]

Originally Posted by nar001

You need to install the hotfix

the fact the WIFI is not working is not an issue perhaps it is a good precausion to avoid update. I`m also reading that the Cloud Register pop up can not be removed, again not an issue once you get to KOreader you don`t really care.

but just to clarify, what hotfix I should install because

I have installed these two:

1. LanguageBreak Hotfix: update_hotfix_languagebreak-{language you want to end up with}.bin

then

2. KUAL hotfix: K5 JailBreak Hotfix | JailBreak-1.16.N-FW-5.x-hotfix.zip | 2024-Apr-21 13:37:00 | 150.2K | when installing KUAL + KOreader

is there any other hotfix I need to install?

[Marek]

Originally Posted by vendo232

the fact the WIFI is not working is not an issue perhaps it is a good precausion to avoid update. I`m also reading that the Cloud Register pop up can not be removed, again not an issue once you get to KOreader you don`t really care.

but just to clarify, what hotfix I should install because

I have installed these two:

1. LanguageBreak Hotfix: update_hotfix_languagebreak-{language you want to end up with}.bin

then

2. KUAL hotfix: K5 JailBreak Hotfix | JailBreak-1.16.N-FW-5.x-hotfix.zip | 2024-Apr-21 13:37:00 | 150.2K | when installing KUAL + KOreader

is there any other hotfix I need to install?

You are in "managed mode" you can exit it by following after jailbreak tutorial in languagebreak, the popup CAN be removed but it requires modifying Hermes bytecode (someone has already made a post about it here) as for hotfix questions i recommend nilujes hotfix (2. Here) since it's more up to date.

[JSWolf]

It's a lot easier to just stop being paranoid and register.

[nar001]

Originally Posted by JSWolf

It's a lot easier to just stop being paranoid and register.

It's a lot easier to stop repeating this ad nauseam when it's out of scope of the question too

[vendo232]

Originally Posted by Marek

You are in "managed mode" you can exit it by following after jailbreak tutorial in languagebreak, the popup CAN be removed but it requires modifying Hermes bytecode (someone has already made a post about it here) as for hotfix questions i recommend nilujes hotfix (2. Here) since it's more up to date.

Thank you Marek!, will give it a try

[vendo232]

Originally Posted by Marek

You are in "managed mode" you can exit it by following after jailbreak tutorial in languagebreak, the popup CAN be removed but it requires modifying Hermes bytecode (someone has already made a post about it here) as for hotfix questions i recommend nilujes hotfix (2. Here) since it's more up to date.

Ahoj Marek

1.
I have reinstalled the Post JB fix multiple times and the WIFI is still restricted.
When I entered ;demo in the search bar and confirmed YES to enter demo mode and it reset the device and JB and I had to start over.

2.
I have updated the device to 5.16.2.0.1 and install the LB JB again. Now this time after the START button restart the device landed in the main menu and I followed with POST JB steps and installed ENG hotfix. ALl went well.

3. Installed KUAL and KOreader , again no issues

4. installed this hitfix, hotfix: K5 JailBreak Hotfix | JailBreak-1.16.N-FW-5.x-hotfix.zip | 2024-Apr-21, again all OK

The WIFI is again disabled, see in the picture.

There is a crash when restarting the device, attached the reports in rar

[john1980]

I’d like to share the method I used to bypass the “Set up your Kindle” screen, also known as the Out-of-Box Experience (OOBE) or SUYK, on a Kindle Scribe 2022 (1st generation) running firmware version 5.16.2.

After powering on the device for the first time, I set up a captive Wi-Fi hotspot using a router flashed with OpenWrt and running nodogsplash.

I connected the Kindle to this hotspot from the initial setup screen (the one that prompts for Amazon account registration). The captive portal had no internet access on purpose, to prevent any OTA updates from being downloaded or triggered.

Despite the lack of internet, this setup allowed me to access the Kindle’s built-in browser. From there, I could begin the LanguageBreak jailbreak tutorial. The browser access also allowed me to trigger demo mode, which is essential for proceeding with the jailbreak.

During the LanguageBreak process, certain steps require that the device is past the setup screen and not in demo mode.

To achieve this, I reconnected to the captive Wi-Fi hotspot and executed the command ;demo

This triggered a dialog asking whether I wanted to enter demo mode. I selected NO, and the device exited to the Home screen, as if the setup process had been successfully completed.

At that point, I was able to continue the LanguageBreak steps without issues.

Once KUAL was installed, I proceeded to install USBNetwork. I then enabled USB SSH access from boot, allowing me to connect to the device via SSH as soon as it powered on.

Next, I installed fakereg and used it to create a fake registration. However, this caused a problem: after rebooting, the Kindle would become stuck on the "Loading, please wait" screen, without progressing.

Interestingly, for some reason, if I connected via SSH and ran:

lipc-probe -av

the device would immediately exit the “Loading, please wait” screen and land directly on the official Kindle Home menu, as if the boot process had been completed successfully. However, this workaround was not persistent across reboots.

To permanently resolve the issue, I deleted the following file with rm from SSH:

rm /var/local/decanter/RESUME_OOBE_FOR_OTA

After deleting that file, the device booted normally and the SUYK/OOBE was definitively bypassed.

Later on, I decided I wanted the Kindle to be completely unregistered, not even with a fake registration.

To do this, I executed the following commands via SSH:

chmod 777 /var/local/java/prefs/reginfo
chattr -i /var/local/java/prefs/reginfo
rm /var/local/java/prefs/reginfo

After rebooting, the Kindle started directly into the official Amazon home menu, with no registration and no SUYK/OOBE prompt.

To complete the setup and preserve privacy, I used the following tool to disable OTA updates and block logging:

https://www.mobileread.com/forums/sh...d.php?t=357438

This ensures that no data or logs are sent to Amazon, and that no automatic firmware updates occur.

I now have a Kindle Scribe 2022 (1st gen) that is Jailbroken, bypassed SUYK/OOBE, fully unregistered, OTA-blocked and logging-disabled.

This was exactly the level of privacy and control I was aiming for. Huge thanks to the MobileRead community for the tools, documentation, and support that made this possible, I hope this guide is helpful to others trying to achieve full control over their Kindle devices.

[john1980]

I’m also adding some details about the steps I followed that I forgot to mention:

It’s important that when you start the device (when you power it on), it is not connected via USB, because if it is, in my case it started to constantly fail with "Collecting Debug Info" messages, even though the file /mnt/us/DISABLE_CORE_DUMP was present, and USBNetwork stopped working (meaning I couldn’t connect to SSH via USB).

Simply restarting the device without the USB cable connected stopped the "Collecting Debug Info" messages and made USBNetwork work again.

You can safely connect the USB cable once you reach the SUYK/OOBE/Home screen.

I also emphasize that it is important to use USBNetwork and keep SSH via USB enabled from boot as soon as it’s possible to do so, because it allowed me to delete the file /var/local/decanter/RESUME_OOBE_FOR_OTA easily without having to use the captive portal again when it got stuck on "Loading, please wait".

After completing all the previously mentioned steps, USBNetwork can be safely disabled, and you can continue using usbms (or SSH via Koreader, but only to transfer books: I wouldn’t touch anything related to rootfs/mntroot without having SSH via USB enabled from boot).

[Frogm4n]

Excellent work! Since the Scribe is so tied to Amazon servers, how does it act when trying to create or use Notebooks?