Tools Snapshots of NiLuJe's hacks - Page 42

hius07 · 10-19-2019, 04:17 PM

Alert, 5.12.2 is deploying through the air breaking update.bin.tmp.partial protection.

MaxStirner · 10-20-2019, 08:53 AM

Why not just fill up free space, leaving no more than 200 mb.

Waitingforatrain · 10-20-2019, 07:52 PM

Quote:

Originally Posted by hius07

Alert, 5.12.2 is deploying through the air breaking update.bin.tmp.partial protection.

To be expected. Is this only devices on 5.12.x though or all using the update.bin.tmp.partial? Does Kual Helper "Prevent OTA updates" do anything that would help?

NiLuJe · 10-20-2019, 08:32 PM

@Waitingforatrain: No, it won't help.

I'm confident update.bin.tmp.partial is useless for sure on 5.12.x, but possibly earlier, too.

j.p.s · 10-20-2019, 08:45 PM

Quote:

Originally Posted by NiLuJe

@Waitingforatrain: No, it won't help.

I'm confident update.bin.tmp.partial is useless for sure on 5.12.x, but possibly earlier, too.

It's been reported to work, at the cost of battery life, for the KOA2 with release firmware, by a reputable source that pays attention to details.. Presumably device and particular 5.12.x version need to be taken into account.

kalyy · 10-20-2019, 10:52 PM

I tried extracting the file for the screen savers hack but 7zip shows an error message about the file being corrupted, I download it again but that didn't help.

NiLuJe · 10-20-2019, 10:58 PM

@kalyy: Definitely something on your end. No issues with a fresh download from a secondary laptop here.

(There's approximately a metric-ton of integrity checks involved in the upload process, so a corrupt file making its way to the storage container uncaught is extremely unlikely, FWIW).

Waitingforatrain · 10-21-2019, 02:30 AM

Quote:

Originally Posted by NiLuJe

@Waitingforatrain: No, it won't help.

I'm confident update.bin.tmp.partial is useless for sure on 5.12.x, but possibly earlier, too.

As I feared. I will stay in airplane mode for the time being. At some point I will just let it go and hope that I might be able to downgrade as a few have reported. It was fun and all the hard work is appreciated.

PoP · 10-21-2019, 02:47 PM

Quote:

Originally Posted by MaxStirner

Why not just fill up free space, leaving no more than 200 mb.

Yeah, that's what I do now as last resort:

Code:

#!/bin/sh
x="$(df | grep " /mnt/us" | awk '{print $4}')"  #how much space left in 1024B units
dd if=/dev/zero of=/mnt/us/filler count=1 bs=1 seek="$(($x *1024 - 20 * 1024 * 1024))" #keep 20MB free

Not really convenient and slow (~10 minutes for 1.7GB), but it works.

Waitingforatrain · 10-21-2019, 08:11 PM

Quote:

Originally Posted by PoP

Yeah, that's what I do now as last resort:

Code:

#!/bin/sh
x="$(df | grep " /mnt/us" | awk '{print $4}')"  #how much space left in 1024B units
dd if=/dev/zero of=/mnt/us/filler count=1 bs=1 seek="$(($x *1024 - 20 * 1024 * 1024))" #keep 20MB free

Not really convenient and slow (~10 minutes for 1.7GB), but it works.

How well does your device run when it is that full? Can you do wifi syncing without issue? Just wondering. Sounds like a good workaround for now.

mergen3107 · 10-21-2019, 09:47 PM

That’s what I thought too.
Doesn’t the storage suffer if it has less than 10% of its capacity free?
On SSDs that is definitely the case, it increases the wear level.

hius07 · 10-21-2019, 10:38 PM

I have about 40 MB of free space on PW2, CoolReader runs perfectly.
Installing of the RescuePack required more than 200 MB though.

NiLuJe · 10-22-2019, 12:39 AM

Yup, MRPI will abort if there isn't at least 150MB free. Some packages will implement their own checks and will require more (mainly, Python, which checks for > 325MB).

PoP · 10-22-2019, 07:31 AM

^ That is the idea, isn't it? To inconveniently choke storage so you can get some control back. Then at your choice, erase the filler file, control installs, recreate the filler and re-enable WiFi afterward.

trcm · 10-23-2019, 07:48 AM

Anyone want to try the mount method to prevent removal of the directory ?

Code:

[root@kindle root]# rm -rf /mnt/us/update.bin.tmp.partial
rm: can't remove '/mnt/us/update.bin.tmp.partial': Device or resource busy

10-20-2019, 10:58 PM	#622
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@kalyy: Definitely something on your end. No issues with a fresh download from a secondary laptop here. (There's approximately a metric-ton of integrity checks involved in the upload process, so a corrupt file making its way to the storage container uncaught is extremely unlikely, FWIW). Last edited by NiLuJe; 10-20-2019 at 11:00 PM.

10-23-2019, 07:48 AM	#630
trcm Connoisseur Posts: 96 Karma: 100000 Join Date: Dec 2018 Location: London Device: Kobo Libra H2O	Anyone want to try the mount method to prevent removal of the directory ? Code: [root@kindle root]# rm -rf /mnt/us/update.bin.tmp.partial rm: can't remove '/mnt/us/update.bin.tmp.partial': Device or resource busy

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I removed the hacks, installed 3.1, then new hacks, and now Kindle is dead	cloudyvisions	Amazon Kindle	55	11-29-2023 07:27 PM
Tools Snapshots of Coplate's packages	coplate	Kindle Developer's Corner	104	10-23-2022 11:41 PM
NiLuJe offline?	picree	Kindle Developer's Corner	1	09-28-2016 10:29 PM
Snapshots test in Live version	Michele Clinco	OpenInkpot	7	09-08-2009 02:42 PM

10-19-2019, 04:17 PM	#616
hius07 Wizard Posts: 1,190 Karma: 3592925 Join Date: Sep 2014 Location: Ukraine Device: Kindle	Alert, 5.12.2 is deploying through the air breaking update.bin.tmp.partial protection.

10-20-2019, 08:53 AM	#617
MaxStirner Connoisseur Posts: 71 Karma: 18500 Join Date: Apr 2013 Device: Kindle Touch, Paperwhite	Why not just fill up free space, leaving no more than 200 mb.

10-20-2019, 08:32 PM	#619
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Waitingforatrain: No, it won't help. I'm confident update.bin.tmp.partial is useless for sure on 5.12.x, but possibly earlier, too.

10-20-2019, 10:52 PM	#621
kalyy Enthusiast Posts: 32 Karma: 10 Join Date: Jan 2016 Device: PW3	I tried extracting the file for the screen savers hack but 7zip shows an error message about the file being corrupted, I download it again but that didn't help.

10-21-2019, 09:47 PM	#626
mergen3107 Wizard Posts: 1,555 Karma: 5000046 Join Date: Feb 2012 Location: Cape Canaveral Device: Kindle Scribe	That’s what I thought too. Doesn’t the storage suffer if it has less than 10% of its capacity free? On SSDs that is definitely the case, it increases the wear level.

10-21-2019, 10:38 PM	#627
hius07 Wizard Posts: 1,190 Karma: 3592925 Join Date: Sep 2014 Location: Ukraine Device: Kindle	I have about 40 MB of free space on PW2, CoolReader runs perfectly. Installing of the RescuePack required more than 200 MB though.

10-22-2019, 12:39 AM	#628
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Yup, MRPI will abort if there isn't at least 150MB free. Some packages will implement their own checks and will require more (mainly, Python, which checks for > 325MB).

10-22-2019, 07:31 AM	#629
PoP curly᷂͓̫̙᷊̥̮̾ͯͤͭͬͦͨ ʎʌɹnɔ Posts: 3,021 Karma: 50506927 Join Date: Dec 2010 Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ±₆₀" Device: K3₃.₄.₃ PW3&4₅.₁₃.₃	^ That is the idea, isn't it? To inconveniently choke storage so you can get some control back. Then at your choice, erase the filler file, control installs, recreate the filler and re-enable WiFi afterward.