![]() |
#1 |
Junior Member
![]() Posts: 8
Karma: 10
Join Date: Apr 2016
Device: Scribe, Voyage & iPad Mini
|
Any way to block OTA updates in the hope for future jailbreak?
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. |
![]() |
![]() |
![]() |
#2 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 964
Karma: 10500008
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
|
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.
|
![]() |
![]() |
Advert | |
|
![]() |
#3 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 256
Karma: 2059433
Join Date: Aug 2016
Location: Czech Republic
Device: Voyage, Oasis, Scribe, Libra Colour
|
Quote:
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. Code:
For /L %i in (1,1,6554) do fsutil file createnew D%i.tmp 10485760 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 ![]() |
|
![]() |
![]() |
![]() |
#4 |
Junior Member
![]() Posts: 8
Karma: 10
Join Date: Apr 2016
Device: Scribe, Voyage & iPad Mini
|
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)? |
![]() |
![]() |
![]() |
#5 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 39,084
Karma: 153098470
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
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. |
|
![]() |
![]() |
Advert | |
|
![]() |
#6 | |
Junior Member
![]() Posts: 8
Karma: 10
Join Date: Apr 2016
Device: Scribe, Voyage & iPad Mini
|
Quote:
|
|
![]() |
![]() |
![]() |
#7 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,347
Karma: 16297052
Join Date: Sep 2022
Device: Kobo Libra 2
|
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.
|
![]() |
![]() |
![]() |
#8 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 39,084
Karma: 153098470
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
|
|
![]() |
![]() |
![]() |
#9 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,421
Karma: 99236514
Join Date: Apr 2011
Device: pb360
|
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.) |
![]() |
![]() |
![]() |
#10 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,421
Karma: 99236514
Join Date: Apr 2011
Device: pb360
|
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.
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Block OTA by removing ota related binaries | Hzj_jie | Kindle Developer's Corner | 107 | 07-21-2024 04:21 PM |
Tools BinaryRenamer - Block OTA Updates & Device Logging | Daviteusz | Kindle Developer's Corner | 51 | 07-09-2024 01:24 PM |
Kindle Scribe: any way to block firmware updates for potential jailbreak? pointless? | arooni | Amazon Kindle | 6 | 10-25-2023 05:45 PM |
Can /etc/hosts be used to block OTA updates? | zaoqi | Kindle Developer's Corner | 1 | 08-18-2019 09:35 AM |
PW1: How to disable OTA updates without jailbreak? | EbokJunkie | Kindle Developer's Corner | 2 | 03-06-2014 03:29 PM |