PW3 Is "JAILBREAK SQUASH JB" startup message supposed to be there with LanguageBreak?

gt346 · 10-28-2025, 03:59 PM

When I restart, it always shows the message "**** JAILBREAK ****" followed by "**** SQUASH JB ****" at the bottom of the startup screen under the guy reading by the tree. Is that normal? I have a few other Kindles jailbroken with other methods and they don't show any messages.

I just jailbroke it (PW3 running 5.16.2.1.1) using LanguageBreak (WinterBreak didn't work). Everything seems to work fine, although I did upgrade the hotfix to the latest 2.3.2 because I got some core dumps and shell scripts weren't showing up in the Library.

Are those messages supposed to be there after the jailbreak is completed?

Thanks!

mergen3107 · 10-28-2025, 04:05 PM

They should go away after the second restart after JB.
If they persist, hotfix is having a bad tome trying to plant itself in the system files

gt346 · 10-28-2025, 04:27 PM

Unfortunately it wasn't going away. I actually found another post of yours which led me to replace the hotfix with a different one (Update_jailbreak_hotfix_1.16.N_install.bin), and after that one removed the SQUASH JB message, I installed the latest one (Update_hotfix_universal.2.3.2.bin). Aside from a core dump after it rebooted from running the hotfix, all seems good now.

Thanks for pointing me in the right direction!

mergen3107 · 10-28-2025, 10:01 PM

Nice! I am glad I helped (in the past

)

To reduce core dump files generation:
1) Make sure you don’t restart Kindle when plugged in.
2) Drop an empty file with no extension named DISABLE_CORE_DUMP in the visible USB root and restart

10-28-2025, 03:59 PM	#1
gt346 Member Posts: 13 Karma: 10 Join Date: Sep 2025 Device: Kindle	Is "JAILBREAK SQUASH JB" startup message supposed to be there with LanguageBreak? When I restart, it always shows the message "** JAILBREAK " followed by " SQUASH JB **" at the bottom of the startup screen under the guy reading by the tree. Is that normal? I have a few other Kindles jailbroken with other methods and they don't show any messages. I just jailbroke it (PW3 running 5.16.2.1.1) using LanguageBreak (WinterBreak didn't work). Everything seems to work fine, although I did upgrade the hotfix to the latest 2.3.2 because I got some core dumps and shell scripts weren't showing up in the Library. Are those messages supposed to be there after the jailbreak is completed? Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
stuck in bootloop on pw 11 gen with "squash jb" message	elermo	Kindle Developer's Corner	3	10-28-2025 01:26 PM
iRex DR800 - bypass "stylus calibration" in startup?	sneakyspider	iRex	2	11-09-2015 12:04 PM
UK Ebook startup calls on publishers to "do a Pottermore"	stonetools	News	62	05-23-2012 05:14 PM
0.7.56 Crash on startup: "'QWidget' Object has no attribute 'fillier'"	MrAndreBB	Calibre	0	04-17-2011 02:44 PM
Error message : "Invalid Format" " Do you want to format your internal memory"	narbeauchamp	Sony Reader	11	07-22-2009 01:39 PM

10-28-2025, 04:05 PM	#2
mergen3107 Wizard Posts: 1,559 Karma: 5000046 Join Date: Feb 2012 Location: Cape Canaveral Device: Kindle Scribe	They should go away after the second restart after JB. If they persist, hotfix is having a bad tome trying to plant itself in the system files

10-28-2025, 04:27 PM	#3
gt346 Member Posts: 13 Karma: 10 Join Date: Sep 2025 Device: Kindle	Unfortunately it wasn't going away. I actually found another post of yours which led me to replace the hotfix with a different one (Update_jailbreak_hotfix_1.16.N_install.bin), and after that one removed the SQUASH JB message, I installed the latest one (Update_hotfix_universal.2.3.2.bin). Aside from a core dump after it rebooted from running the hotfix, all seems good now. Thanks for pointing me in the right direction!

10-28-2025, 10:01 PM	#4
mergen3107 Wizard Posts: 1,559 Karma: 5000046 Join Date: Feb 2012 Location: Cape Canaveral Device: Kindle Scribe	Nice! I am glad I helped (in the past ) To reduce core dump files generation: 1) Make sure you don’t restart Kindle when plugged in. 2) Drop an empty file with no extension named DISABLE_CORE_DUMP in the visible USB root and restart