01-28-2017, 11:23 AM
|
#1 |
|
Member
 Posts: 21
Karma: 10
Join Date: Jan 2017
Device: Kindle KT2
|
Cannot install custom update packages via MRPI
I am having some problems while installing installing packages such as USBnet, Custom screensaver hack,m etc.
When i viewed the logs the problem i found was Code:
Package 'Update_linkss_0.24.N_install_pw2_kt2_kv_pw3_koa_kt3.bin' (linkss 0.24.N I WARIO+) is not targeting your device [DD vs. D4 5A D5 D6 D7 D8 F2 17 60 62 5F 61 C6 13 54 53 2A 52 0G1 0G7 0G6 0G2 0G5 0G4 0KB 0KC 0GC 0GD 0GU 0K9 0KA], skipping . . . :( The package's install.sh also includes serial of my app Code:
# Install our hack's custom content
# Check which default screensaver to use...
kmodel="$(cut -c3-4 /proc/usid)"
case "${kmodel}" in
"13" | "54" | "2A" | "4F" | "52" | "53" )
# Voyage...
logmsg "I" "install" "" "using the default voyage custom screensaver"
HACK_EXCLUDE="${HACKNAME}/screensavers/00_you_can_delete_me.png ${HACKNAME}/screensavers/00_you_can_delete_me-pw.png"
;;
"24" | "1B" | "1D" | "1F" | "1C" | "20" | "D4" | "5A" | "D5" | "D6" | "D7" | "D8" | "F2" | "17" | "60" | "F4" | "F9" | "62" | "61" | "5F" )
# PaperWhite...
logmsg "I" "install" "" "using the default paperwhite custom screensaver"
HACK_EXCLUDE="${HACKNAME}/screensavers/00_you_can_delete_me.png ${HACKNAME}/screensavers/00_you_can_delete_me-kv.png"
;;
"0F" | "11" | "10" | "12" | "DD" | "C6" )
# Touch & KT2
logmsg "I" "install" "" "using the default touch custom screensaver"
HACK_EXCLUDE="${HACKNAME}/screensavers/00_you_can_delete_me-pw.png ${HACKNAME}/screensavers/00_you_can_delete_me-kv.png"
;;
* )
 me with this problem, any advice will be helpful in advance
|
|
|
|
01-28-2017, 11:33 AM
|
#2 |
|
Just a Yellow Smiley.
 
Posts: 19,161
Karma: 83862859
Join Date: Jul 2015
Location: Texas
Device: K4, K5, fire, kobo, galaxy
|
Is yours a special offers kindle?
|
|
|
|
| Advert | |
|
|
|
01-28-2017, 12:20 PM
|
#3 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
And did you get the package from NiLuJe's snapshot thread?
See: Current jail break, first post, section: "Release Policy", open, read, and follow the directions in the spoiler. |
|
|
|
|
02-02-2017, 07:48 AM
|
#4 |
|
Member
Posts: 21
Karma: 10
Join Date: Jan 2017
Device: Kindle KT2
|
I have seen this problem with many packages like HackedupReader.
When i view the info about the package using KindleTool it shows: Code:
Checking update package 'update_hackedupreader_0.4.1_install.bin'.
Bundle SP01 (Signing Envelope)
Cert number 0
Cert file pubdevkey01.pem (Developer)
Bundle FD04 (Versionless [vls])
Bundle Type OTA V2
Minimum OTA 0
Target OTA 18446744073709551615
Devices 20
Device Kindle 5 Touch Wifi
Device Kindle 5 Touch Wifi+3G
Device Kindle 5 Touch Wifi+3G Europe
Device Kindle PaperWhite Wifi
Device Kindle PaperWhite Wifi+3G
Device Kindle PaperWhite Wifi+3G Canada
Device Kindle PaperWhite Wifi+3G Europe
Device Kindle PaperWhite Wifi+3G Japan
Device Kindle PaperWhite Wifi+3G Brazil
Device Kindle PaperWhite 2 (2013) Wifi
Device Kindle PaperWhite 2 (2013) Wifi Japan
Device Kindle PaperWhite 2 (2013) Wifi+3G
Device Kindle PaperWhite 2 (2013) Wifi+3G Canada
Device Kindle PaperWhite 2 (2013) Wifi+3G Europe
Device Kindle PaperWhite 2 (2013) Wifi+3G Russia
Device Kindle PaperWhite 2 (2013) Wifi+3G Japan
Device Kindle PaperWhite 2 (2013) Wifi (4GB) International
Device Kindle PaperWhite 2 (2013) Wifi+3G (4GB) Europe
Device Kindle PaperWhite 2 (2013) Wifi+3G (4GB)
Device Kindle Basic (2014)
on Nicknames page Code:
B0C6, 90C6-Kindle Basic (2014) KT2, BASIC [Support added in KindleTool 1.6.3] B0DD, 90DD-Kindle Basic (2014) (Australia) KT2, BASIC [Support added in KindleTool 1.6.5] There can only be a problems: That v1.6.3 of Kindle tool was used to make this package. Is there a way to repack the package for my device using a updated kindle tool.
|
|
|
|
|
02-02-2017, 08:45 AM
|
#6 | |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Any package that is built with the older KindleTool - Using the current KindleTool from NiLuJe's snapshots thread - Extract the desired package - Re-package it, specifying your model. There are examples of doing that posted here. It is a simple sequence of two command line commands. |
|
|
|
|
|
02-03-2017, 06:47 AM
|
#7 |
|
Member
Posts: 21
Karma: 10
Join Date: Jan 2017
Device: Kindle KT2
|
This is where comes the problem
First I converted the .bin file into a gzipped tarball using Code:
./kindletool convert update_ko****.bin Code:
./kindletool create ota2 -d kt2a -p wario -B whitney Komic_converted.tar.gz update_komic_kt2.bin Then I installed the package using MRI but it failed with error code (1) Code:
**** **** **** **** [2017-02-03 @ 15:39:58 +0530] :: [MRPI r13359] - Beginning the processing of package 'update_komic_kt2.bin' (komic kt2) . . . -- Running 'install_komic.ffs' for 'komic kt2' (update_komic_kt2.bin) @ Fri, 03 Feb 2017 15:39:59 +0530 eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800) eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800) Hu oh... Got return code 1 . . . :( Please tell me what I did wrong, Any would be appreciated
|
|
|
|
|
02-03-2017, 08:39 AM
|
#8 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Those eips messages are only warnings, not errors.
They indicate a mis-match between the screen detection and the on-screen messages, not something done wrong in the un-package / re-package process. The "error code 1" is a general purpose error message code. You will have to trouble shoot the scripting to get its model adaption code to work on your model. Once you get the install scripting working, you may find that the application itself does not work on your model of Kindle. These packages are "model locked" for a reason and the author might have intentionally not included your model of Kindle. Last edited by knc1; 02-03-2017 at 08:42 AM. |
|
|
|
|
02-09-2017, 07:54 AM
|
#9 |
|
Member
Posts: 21
Karma: 10
Join Date: Jan 2017
Device: Kindle KT2
|
Some said to try and not to cry
I tried to troubleshoot the script and as far as i can understand the problem is in these lines of code Code:
#!/bin/sh
OTA=com.lab126.blanket.ota
LOG=/mnt/us/Komic_update_log.txt
LOCALSTORAGE=/mnt/us/extensions/komic/bin/resource/LocalStorage/file__0.localstorage
GALLERY="/mnt/us/documents/Komic"
OLDGALLERY="/mnt/us/documents/Gallery"
KOMIC="/mnt/us/extensions/komic"
UPSTART="/etc/upstart/komic_event_handler.conf"
progress()
{
lipc-send-event $OTA otaSplashProgress -i $1
local x=48
local y=11
eips 0 $y " ";
eips $((($x - $(expr length "$2")) / 2)) $y "$2"
sleep 3
}
fail()
{
lipc-send-event $OTA otaSplashError -s "${1}"
sleep 10
exit 1;
}
progress 25 "Checking if Komic is installed"
varkomic=$(sqlite3 /var/local/appreg.db "select handlerId from handlerIds where handlerId='com.silver18.komic001'")
varmemory=$(sqlite3 /var/local/appreg.db "select handlerId from properties where handlerId='com.silver18.komic001' and name='memUnloadLevel'")
mesquite=$(sqlite3 /var/local/appreg.db "select value from properties where handlerId='com.silver18.komic001' and name='command'" | grep mesquite)
varbaseus=$(sqlite3 /var/local/appreg.db "select value from properties where handlerId='com.silver18.komic001' and name='command'" | grep base)
There are no model locks in the ffs file. |
|
|
|
|
02-09-2017, 08:46 AM
|
#10 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
The problem is not with MrPI.
You are trying to run Komic on a Kindle model that Komic does not support. Ref: https://www.mobileread.com/forums/sh...d.php?t=182183 If you intend to update Komic for the newer devices, please keep your posts in the Komic thread. The public repository is here: https://bitbucket.org/silvern18/komic Make your changes in a local clone of the repository and then when working, post a pull request at the public repository. Last edited by knc1; 02-09-2017 at 08:51 AM. |
|
|
|
 |
| Tags |
| mrpi;linkss;usbnet |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Can't update to 5.6.1.1. via MRpi | szymeko | Kindle Developer's Corner | 5 | 12-11-2016 07:54 AM |
| MrPi destroys packages | mitra | Kindle Developer's Corner | 1 | 03-10-2016 01:26 AM |
| Install custom font on 5.2? | Barty | Kindle Developer's Corner | 14 | 11-29-2012 03:25 AM |
| PRS-350 is there a way to install a custom dictionary | vsviridov | Sony Reader | 15 | 04-16-2012 06:21 AM |
| calibre update 0.8.1 to 0.8.2 custom install directory | Dopedangel | Calibre | 5 | 05-21-2011 02:15 PM |
All times are GMT -4. The time now is 12:38 AM.