Skip to content

Hotfix 2.2.0 fails when trying to install on PW3 FV 5.16.2.1.1 #9

Open

Description

@viktor-grunwaldt

I can repeatedly crash my PW3 during hotfix installation step.

Device info:

Kindle Paperwhite (7th gen)
Firmware Version: 5.16.2.1.1 (4097470002)
Space Available: 2.92GB free (out of 4 GB)
WinterBreak version: v1.7.0
Hotfix version: 2.2.0

Working Hotfix version: 1.14.0

Steps to reproduce:

  1. (Optional) Factory reset device, assume device is clean
  2. Log in to WiFi and Amazon account
  3. Enable airplane mode
  4. Plug in to PC and copy WinterBreak files
  5. Eject & unplug cable
  6. Reboot device
  7. Launch mesquito by pressing cart icon and disabling airplane mode
  8. jailbreak device (success)
  9. While NOT enabling airplane mode (this will disable the option to update device), copy Update_hotfix_universal.bin to root directory.
  10. Settings > dots on top right > update
  11. device reboots, crash
    Error dialog pops up about Recording a log of the crash and reporting it to https://wiki.corp.lab126.com/(...). When I click close, a booklet appears with details about this crash. I've recovered it from the device:
    https://gist.github.com/viktor-grunwaldt/f015014ee66eddcc96b144ead4bd5fc6

Now, after that I know the device is no longer jailbroken, as the ;log command does nothing.

I have also done the exact same steps, but with version 1.14.0 - and it worked. (Version chosen arbitrarily, I was following a video guide which used 1.13, so I decided to stay on the same major version).
I don't know what's the last working version.

Activity

  1. Surobaki commented on Aug 7, 2025

    @Surobaki

    This happens to me as well, PW3. See crashdump files below.

    pw3-crashdump.tar.gz

  2. mergen3107 commented on Aug 7, 2025

    @mergen3107

    Have you guys tried 2.2.1?

  3. viktor-grunwaldt commented on Aug 20, 2025

    @viktor-grunwaldt
    Author

    Sorry for the late reply. I can't really check, as my device is currently rooted and running the 1.14 hotfix. Root persists Factory reset. For some reason KUAL does not execute applications which means the only other way of resetting the device I know of is gone for me. I tried running the 2.2.1 hotfix in that state however I couldn't perceive any changes. Maybe if other way of flashing existed then I would test the 2.2.1.

    Also, please don't feel pressured to do anything about it, I just wanted to document somewhere that I have this problem and maybe someone stumbles upon this and it helps them.

  4. mergen3107 commented on Aug 20, 2025

    @mergen3107

    Try restarting Kindle twice, then tap on the hotfix "Book" to run it.

    This should fix your KUAL apps - those that rely on scripts only. You need to reinstall all the .bin packages though

  5. picnicbob commented on Oct 23, 2025

    @picnicbob

    Hotfix 2.3.1 same issue on PW3. I tried 1.14.0 and got a white screen for a while... Now I'm not really sure what state I'm in but I am still jailbroken this time. How do I know if the hot fix is applied?

  6. realSchoki commented on Oct 26, 2025

    @realSchoki

    Same here. Tried it with 2.3.2 on my PW3. After running the Booklet and greeting me with a crashdump ;log is not working anymore. I tried the double restart as @mergen3107 said, changed nothing. Run the 'book' -> crashdump -> no ;log.

    After a restart ;log is working again.

    EDIT: Installed now the 1.14.0 Hotfix, since at least one here said it was working. Update was progressed without any crash dumps. Instead i was greeted with a blank screen like @picnicbob mentioned. Had to reboot to get rid of it. KOAL installation afterwards doesnt worked. Tried 2.1.2, same issues like with 2.3.2.

  7. mergen3107 commented on Oct 26, 2025

    @mergen3107

    To reduce crash dumps:

    1. Make sure you are NOT restarting Kindle while connected via cable (sorry, forgot to mention this before)
    2. Drop an empty file with no extension called DISABLE_CORE_DUMP into the visible Kindle USB storage, unplug and restart.
  8. maciejstromich commented on Nov 20, 2025

    @maciejstromich

    Same here.

    Kindle Oasis (8th gen)
    Firmware Version: 5.16.2.1.1 (4097470002)
    Space Available: 2.76GB free (out of 4 GB)
    WinterBreak version: v1.7.0
    Hotfix version: 2.3.2

    Attaching my coredumps:
    KPPMainAppV2_5712_002-juno_16020101_whisky_duet-409755_crash_Nov_20_20.23.37_2025.tgz

    I tried also the Hotfix 1.14.0 and got the same result as @realSchoki where the screen goes blank and only reboot helps to get the device back to UI.

  9. Surobaki commented on Feb 5, 2026

    @Surobaki

    Can confirm same things happen with 1.14.0 as stated above by others. Screen goes blank, can't do anything without a reboot.
    Issue persists on 2.3.7.

  10. ZongbingHou commented on Jun 16, 2026

    @ZongbingHou

    Kindle Oasis (8th gen)
    Firmware Version: 5.16.2.1.1 (4097470002)
    Hotfix version: 3.4
    I'm still getting this message while using the hotfix, and typing ;log doesn't do anything either.

    Does this have anything to do with me jailbreaking again? I reset my ko1, but didn't reinstall the Kindle firmware, I just jailbroke it again.

    Image
  11. mergen3107 commented on Jun 16, 2026

    @mergen3107

    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

  12. ZongbingHou commented on Jun 16, 2026

    @ZongbingHou

    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

    I created two files in the root directory: DISABLE_CORE_DUMP and DISABLE_CORE_DUMP_ALERT. It's fine now, but is this issue a Hotfix-level problem? Can the step of placing the files be skipped by updating the Hotfix?

  13. mergen3107 commented on Jun 16, 2026

    @mergen3107

    Probably, depends on @ThatHackerDudeFromCyberspace

  14. ThatHackerDudeFromCyberspace commented on Jun 16, 2026

    @ThatHackerDudeFromCyberspace
    Member

    cvm core dumps are rather unusual and not something I've seen before, unfortunately there's very little I can do without both logs and the core dumps

  15. ThatHackerDudeFromCyberspace commented on Jun 16, 2026

    @ThatHackerDudeFromCyberspace
    Member

    It's possible that the Hotfix is causing this, though I don't really have much of an idea which component would be causing it, historically sh_integration did cause indexer crashes though those have been fixed for a long time now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions