Endless loop of "Collecting Debug Info" after jailbreak

[sancancan]

I've just used WinterBreak on my 7th Gen Kindle Basic (KT2 5.12.2.2) following the guide. Installed the Hotfix, KUAL etc.

However, I'm getting a constant pop-up message that says "Collecting Debug Info" that makes the Kindle unusable.

It just keeps generating these "core dump files". Would I need a factory reset? Has anyone encountered this before?

[tekkasit]

Don't do a factory reset; otherwise, you Kindle will brick. There is a way to disable application dump generation.

[sancancan]

That makes me glad that I asked before trying to reset . Any pointers on how I could disable it? I was able to find this:

Originally Posted by mergen3107

Update:

I found some hints in /usr/bin/dump-stack and created two files in /mnt/us/ :
DISABLE_CORE_DUMP and DISABLE_CORE_DUMP_ALERT

No more heavy dump files!

Only things that are created from time to time are Indexer_ files and some small html and tar.gz files.

This usually happens after Kindle UI freezes for a minute or so, after I enable Wi-Fi. I suspect that it freezes when trying to check for OTA, and I blocked OTA binaries (and otaup script). So maybe because of that

All this happened on FW 5.16.21

I’ll try to replace ota scripts with some dummy empty scripts later, so that command “will work” keeping Kindle UI happy.

But I really don't know how to go about trying it

[BionicGecko]

Originally Posted by sancancan

That makes me glad that I asked before trying to reset . Any pointers on how I could disable it? I was able to find this:



But I really don't know how to go about trying it

Just connect you Kindle via USB and create two empty files with the following filenames directly in the root:

• DISABLE_CORE_DUMP
• DISABLE_CORE_DUMP_ALERT

Make sure those files are named exactly as above, without an extension (i.e. "DISABLE_CORE_DUMP.txt" wouldn't work). To achieve this you can create them as .txt files first and delete the ".txt" part once the files are created.

[sancancan]

Originally Posted by BionicGecko

Just connect you Kindle via USB and create two empty files with the following filenames directly in the root:

• DISABLE_CORE_DUMP
• DISABLE_CORE_DUMP_ALERT

Make sure those files are named exactly as above, without an extension (i.e. "DISABLE_CORE_DUMP.txt" wouldn't work). To achieve this you can create them as .txt files first and delete the ".txt" part once the files are created.

Thanks a lot! Tried it and the pop-ups are gone.

However, I still endlessly generate smaller log files. But at least the device is usable again without the pop-up messages.

[demeryth]

Hi. I have exactly the same problem. Installed winterbreak on my paperwhite 2. It started to generate dump files. The problem was partly resolved by creating those 2 empty files in the root. But Kindle is still creating indexer_dump files every minute or two. I tried to switch to airplane mode. Didn't help. It's draining battery a lot and my home screen is very messy. Any way to fix that?https://file.io/rFr79wl2VtBJ

[mergen3107]

Did you by chance restart (simple reboot) your Kindle while it is connected to PC?
If so, disconnect it and restart again.

Kindles, for some reason, are allergic to that

[bugmen00t]

Originally Posted by sancancan

However, I still endlessly generate smaller log files.

Some error concerning documents/run_bridge.sh is mentioned in these small log files. So I just renamed it, and these tiny annoyances are finally gone.

The Kindle is not in my possession right now, so I can't check if my actions caused the newest jailbreak/hotfix to stop functioning...

[demeryth]

Originally Posted by mergen3107

Did you by chance restart (simple reboot) your Kindle while it is connected to PC?
If so, disconnect it and restart again.

Kindles, for some reason, are allergic to that

No. I did not.

Originally Posted by bugmen00t

Some error concerning documents/run_bridge.sh is mentioned in these small log files. So I just renamed it, and these tiny annoyances are finally gone.

The Kindle is not in my possession right now, so I can't check if my actions caused the newest jailbreak/hotfix to stop functioning...

I'll try this now. See what happen. Thank you.

[sancancan]

Originally Posted by bugmen00t

Some error concerning documents/run_bridge.sh is mentioned in these small log files. So I just renamed it, and these tiny annoyances are finally gone.

The Kindle is not in my possession right now, so I can't check if my actions caused the newest jailbreak/hotfix to stop functioning...

Confirming that this worked on my Kindle Basic 7th Gen. Didn't seem to cause any issues with the jailbreak. Thanks!

[demeryth]

I can confirm that changing name name of run_bridge.sh fixed the issue. Thanks @bugmen00t for help.

[HackerDude]

I have identified the cause of this error and am pushing a new hotfix version

[HackerDude]

v1.11.0 is now live

[DNSB]

One oddity is that I had to install 1.11.0 twice. After the first install, the Run Hotfix book had disappeared. The second install restored it and the JB ran successfully.

This was on a PW4 that was already jailbroken.

[mergen3107]

Originally Posted by DNSB

One oddity is that I had to install 1.11.0 twice. After the first install, the Run Hotfix book had disappeared. The second install restored it and the JB ran successfully.

This was on a PW4 that was already jailbroken.

Tested on Kindle Scribe 2022 FW 5.17.2, I too ended up with the ssh script missing. Needed to add it by hand and run it.

Works great so far! I removed the DISABLE_CORE_DUMP file and haven't seen any dumps