Any way to block OTA updates in the hope for future jailbreak?

[maakies]

So, I have a Scribe and I'm on 5.16.9, well past jailbreak as an option. Would like to be able to jailbreak in the future as I despise the home page. Used KOReader on my Voyage which would be much better.

I use sendtokindle, so indefinite airplane mode isn't an option.

Thank you for your time.

[shamanNS]

Fill out device storage with junk data and leave only ~100 MB of free space? So it doesn't have enough space to completely download firmware update bin file.

[BionicGecko]

Originally Posted by shamanNS

Fill out device storage with junk data and leave only ~100 MB of free space? So it doesn't have enough space to completely download firmware update bin file.

I'm in the same situation as maakies, and while looking for an easy way to achieve this in Windows I stumbled upon this method; I'm posting it here in the odd chance it might be helpful to someone else.

In a nutshell, I used the command below to create 64GB's worth of 10MB files, copied them over to my Scribe (in a new folder) until there was less than 10MB left, and then deleted the last 10 files copied to the Scribe to free up around 100MB.

For /L %i in (1,1,6554) do fsutil file createnew D%i.tmp 10485760

This way I can control the available space by deleting files in 10MB increments as I download more books onto the Scribe in the future.

It's obviously overkill to create the full 64GB as the OS and existing books already take space, but the creation of the files is very fast and I wasn't in the mood to compute

[maakies]

thank you both for the suggestions. is there another way where I'm not filling up the hard drive?

Maybe my hard disk knowledge is from 20 years ago, but aren't we supposed to keep 10% or thereabouts empty? Or did that change with SSDs (which I presume is inside the Scribe)?

[DNSB]

Originally Posted by maakies

thank you both for the suggestions. is there another way where I'm not filling up the hard drive?

Maybe my hard disk knowledge is from 20 years ago, but aren't we supposed to keep 10% or thereabouts empty? Or did that change with SSDs (which I presume is inside the Scribe)?

Not without jailbreaking the device.

The recommendation was, AFAIR, to allow for defragmenting the hard drive. Defragmenting is not an option on an SSD since they have a limited write life. Most SSD implementations these days do some form of wear levelling to extend the life of the the SSD.

[maakies]

Originally Posted by DNSB

Not without jailbreaking the device.

The recommendation was, AFAIR, to allow for defragmenting the hard drive. Defragmenting is not an option on an SSD since they have a limited write life. Most SSD implementations these days do some form of wear levelling to extend the life of the the SSD.

Thank you so much. That makes sense.

[Aleron Ives]

Defragmenting SSDs is useless. The reason you need to defragment HDDs is that there are moving parts that can access data faster and more efficiently when it's stored contiguously. SSDs have no moving parts, so there is no performance penalty associated with fragmentation.

[DNSB]

Originally Posted by Aleron Ives

Defragmenting SSDs is useless. The reason you need to defragment HDDs is that there are moving parts that can access data faster and more efficiently when it's stored contiguously. SSDs have no moving parts, so there is no performance penalty associated with fragmentation.

And as mentioned, SSDs have a limited write life so defragmenting would give no performance increase and would reduce the usuable life.

[j.p.s]

Originally Posted by Aleron Ives

Defragmenting SSDs is useless.

It's worse than useless without even considering wear since even OS level flash memory device drivers have no visibility into or control of the actual location of data on the drive. That is, "defragmenting" doesn't even happen if more than half of the sectors on the drive have previously been written.

(Of course the wear is a much more important consideration.)

[j.p.s]

Originally Posted by DNSB

The recommendation was, AFAIR, to allow for defragmenting the hard drive. .

Unix like OS tend to recommend reserving 5% at the partition level for use as scratch space during updates and other routine operations. That is "used" plus "free" adds up to 95% of partition size. I tend to reserve 0% for purely data partitions.