View Single Post
Old 10-23-2018, 03:23 AM   #3259
Antinoos
Groupie
Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!Antinoos rocks like Gibraltar!
 
Antinoos's Avatar
 
Posts: 168
Karma: 100329
Join Date: Apr 2017
Location: Leipzig/Germany
Device: PW3, KT3 (fw 5.8.11 with jb)
Just a short remark: The current implementation is too intricate - the following shortened version in bridge.sh would do the same more strict version check for fw < 5.4, but still making sure that any two (or even more... ) digit sub version numbers will correctly be recognized as fw >= 5.4:

Spoiler:
Code:
case "${khver}" in
			5.0.* | 5.0 )
				K5_ATLEAST_54="false"
			;;
			5.1.* | 5.1 )
				K5_ATLEAST_54="false"
			;;
			5.2.* | 5.2 )
				K5_ATLEAST_54="false"
			;;
			5.3.* | 5.3 )
				K5_ATLEAST_54="false"
			;;	
			5.* )
				K5_ATLEAST_54="true"
			;;
			* )
				# Given the previous checks, this shouldn't be reachable, but cover all bases anyway...
				logmsg "W" "check_version" "" "couldn't detect the kindle version!"
				# Poor man's last resort trick. See if we can find a new feature of FW 5.4 on the FS...
				if [ -f "${ROOT}/etc/upstart/contentpackd.conf" ] ; then
					logmsg "I" "check_version" "" "found a fw >= 5.4 feature"
					K5_ATLEAST_54="true"
				fi
			;;


Besides the above-mentioned remark, this fix is extremely helpful for those who believe that they MUST always run the very latest official firmware on their Kindle devices. Those, like me, who stick with the good old 5.8.11 fw, wouldn't run into this problem, but they should update their hotfix code anyway, just to make sure in the case the guys at Lab126 find a method to circumvent the OTA blocker dir trick in future...
Antinoos is offline   Reply With Quote