MobileRead Forums - View Single Post - geekmaster's data.tar.gz and K4NT FW 4.1.1

Skeeve · 11-10-2013, 07:22 AM

Hi!

Yesterday I wanted to activate the screensavers without jailbreaking my K4NT. I already was told in another thread that it's not possible, but still do not understand why it shouldn't be possible. So maybe someone can explain to me?

Here is what I understand:

There is a data.tar.gz file which the Kindle will extract upon boot. The content goes to /var/local/system and is the mntus.param file. This one should be executed by the kindle.

I looked into the file and tried to understand it.

Code:

MNTUS_PART_START=16
MNTUS_PART_OFFSET=8192
MNTUS_FATSIZE=32

## use actual size from fdisk (minus 8KB offset):
let MNTUS_PART_SIZE="`fdisk -l|grep FAT32|awk '{print $4}'`-8"

## if invalid size (normal during main boot),
## then use known size for each serial number:
if [ $MNTUS_PART_SIZE -lt 1000000 ]; then
  SER4=`grep Serial /proc/cpuinfo|cut -b12-15`
  case $SER4 in
  "B004"|"B005"       ) MNTUS_PART_SIZE=3567224 ;; # DX
  "B006"|"B008"|"B00A") MNTUS_PART_SIZE=3205336 ;; # K3
  "B009"              ) MNTUS_PART_SIZE=3510232 ;; # DXG
  "B00E"              ) MNTUS_PART_SIZE=1423352 ;; # K4 (mini)
  "B00F"|"B011"       ) MNTUS_PART_SIZE=3377144 ;; # K5 (touch)
  *)
    ## unknown size, exit may erase USB Drive!
    eips -c
    eips  5 28 "This $SER4 Kindle is not supported..."
    eips 10 30 "(${MNTUS_PART_SIZE}KB USB Drive)"
    eips  7 32 "Removing installer files..."
    sleep 8
    ;;                   
  esac
fi

mount -o rw,noatime,nodiratime,offset=8192 /dev/mmcblk0p4 /mnt/us
[ -f /mnt/us/RUNME.sh -a ! -f /mnt/us/RUNME.done ] && (
  touch /mnt/us/RUNME.done
  sh /mnt/us/RUNME.sh 2>&1 >/mnt/us/RUNME.out
)
umount -d /mnt/us

I'm not sure whether or not the file is really executed. If it were I should have a RUNME.done, which I do not get.

So the question is, whether the file gets executed or if the file simply refrains from executing RUNME.sh because the preliminary tests fail. But wouldn't I see the messages printed with eips then?

Could someone please help me understand this? I especially do not understand why jailbreaking should work (as I'm told), when it's using the same approach, namely putting mntus.param into the filesystem.

Another question is: Does the mntu.params stay on the device? Have I now lost my original mntu.params?

11-10-2013, 07:22 AM	#1
Skeeve Zealot Posts: 142 Karma: 669192 Join Date: Nov 2013 Device: Kindle 4.1.1 no touch	geekmaster's data.tar.gz and K4NT FW 4.1.1 Hi! Yesterday I wanted to activate the screensavers without jailbreaking my K4NT. I already was told in another thread that it's not possible, but still do not understand why it shouldn't be possible. So maybe someone can explain to me? Here is what I understand: There is a data.tar.gz file which the Kindle will extract upon boot. The content goes to /var/local/system and is the mntus.param file. This one should be executed by the kindle. I looked into the file and tried to understand it. Code: MNTUS_PART_START=16 MNTUS_PART_OFFSET=8192 MNTUS_FATSIZE=32 ## use actual size from fdisk (minus 8KB offset): let MNTUS_PART_SIZE="`fdisk -l\|grep FAT32\|awk '{print $4}'`-8" ## if invalid size (normal during main boot), ## then use known size for each serial number: if [ $MNTUS_PART_SIZE -lt 1000000 ]; then SER4=`grep Serial /proc/cpuinfo\|cut -b12-15` case $SER4 in "B004"\|"B005" ) MNTUS_PART_SIZE=3567224 ;; # DX "B006"\|"B008"\|"B00A") MNTUS_PART_SIZE=3205336 ;; # K3 "B009" ) MNTUS_PART_SIZE=3510232 ;; # DXG "B00E" ) MNTUS_PART_SIZE=1423352 ;; # K4 (mini) "B00F"\|"B011" ) MNTUS_PART_SIZE=3377144 ;; # K5 (touch) *) ## unknown size, exit may erase USB Drive! eips -c eips 5 28 "This $SER4 Kindle is not supported..." eips 10 30 "(${MNTUS_PART_SIZE}KB USB Drive)" eips 7 32 "Removing installer files..." sleep 8 ;; esac fi mount -o rw,noatime,nodiratime,offset=8192 /dev/mmcblk0p4 /mnt/us [ -f /mnt/us/RUNME.sh -a ! -f /mnt/us/RUNME.done ] && ( touch /mnt/us/RUNME.done sh /mnt/us/RUNME.sh 2>&1 >/mnt/us/RUNME.out ) umount -d /mnt/us I'm not sure whether or not the file is really executed. If it were I should have a RUNME.done, which I do not get. So the question is, whether the file gets executed or if the file simply refrains from executing RUNME.sh because the preliminary tests fail. But wouldn't I see the messages printed with eips then? Could someone please help me understand this? I especially do not understand why jailbreaking should work (as I'm told), when it's using the same approach, namely putting mntus.param into the filesystem. Another question is: Does the mntu.params stay on the device? Have I now lost my original mntu.params?