Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 11-27-2015, 11:17 AM   #76
boom1212
Member
boom1212 began at the beginning.
 
Posts: 10
Karma: 10
Join Date: Apr 2014
Device: Kindle paperwhite2
i find the "kindle tool" from here,but i don't know how to build the "update_rescue_pack_install.bin" by myself,can anyone tell me? so that i can build the file in the future when i want, but not use to wait for ixtab update it.
boom1212 is offline   Reply With Quote
Old 11-27-2015, 12:15 PM   #77
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by boom1212 View Post
i find the "kindle tool" from here,but i don't know how to build the "update_rescue_pack_install.bin" by myself,can anyone tell me? so that i can build the file in the future when i want, but not use to wait for ixtab update it.
Why don't you just get the most recent rescue pack?
See:
prefix drop-down box, select 'tools' -
press 'show threads' -
scroll to the entry for this thread:
https://www.mobileread.com/forums/sho...d.php?t=225030
knc1 is offline   Reply With Quote
Advert
Old 11-30-2015, 11:50 AM   #78
boom1212
Member
boom1212 began at the beginning.
 
Posts: 10
Karma: 10
Join Date: Apr 2014
Device: Kindle paperwhite2
Thanks! I get the most recent rescue pack there,but in fact, i really want to learn how to build this file by myself, it's brillant!
boom1212 is offline   Reply With Quote
Old 11-30-2015, 12:15 PM   #79
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by boom1212 View Post
Thanks! I get the most recent rescue pack there,but in fact, i really want to learn how to build this file by myself, it's brillant!
The tool for creating our signed packages is KindleTool, from the same page you linked to above.
The same tool can also take apart either Amazon's or our update packages.

Creating the contents, now that is a much bigger question.
knc1 is offline   Reply With Quote
Old 12-13-2015, 12:57 AM   #80
toothless
Junior Member
toothless began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Dec 2015
Device: Kindle PW3
Hi there,
I have a PW3, v5.6.5, jailbroken, with KUAL installed.

I got the latest version of the rescue pack from the NiLuJe's snapshot thread. This is the one I downloaded:

Rescue Pack | kindle-rp-20131220.N-r12672.tar.xz | 2015-Dec-04 19:51:29 | 436.2K | 2532fa7189fcff64cccc29b26e1d18f9 | Upstream

I installed the .bin file using MRInstaller. I can see that it created an empty folder named 'rp' in the documents folder. However when I create the ENABLE_DIAGS file in the root folder and restart (after disconnecting the USB cable), I am not getting booted into the diags partition.

Am I doing something wrong?
toothless is offline   Reply With Quote
Advert
Old 12-15-2015, 10:07 AM   #81
toothless
Junior Member
toothless began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Dec 2015
Device: Kindle PW3
Can someone help me with my query above? Happy to provide additional details as required.
toothless is offline   Reply With Quote
Old 12-30-2016, 10:06 AM   #82
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 829
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
I just attempted to install the rescue pack to a KT3 (G000K9) running 5.8.7 firmware and it appears to have failed:

Quote:
[2016-12-30 @ 11:17:55 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .

--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Fri, 30 Dec 2016 11:17:55 +0000

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)
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)
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> (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)
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)
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)
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)
sed: /mnt/mmc/opt/factory/system_diags: No such file or directory

Hu oh... Got return code 1 . . .



**** **** **** ****
Interestingly, it appears the Coward's Rescue Pack DID install:

Quote:
[2016-12-30 @ 11:18:30 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_crp_2.N_install.bin' (crp 2.N I) . . .

--
Running 'run.ffs' for 'crp 2.N I' (Update_crp_2.N_install.bin) @ Fri, 30 Dec 2016 11:18:30 +0000

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)
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)
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> (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> (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)

Success!



**** **** **** ****
Do I take another shot at this? Did I grab the wrong version?

Dave
dhdurgee is offline   Reply With Quote
Old 12-30-2016, 10:11 AM   #83
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Depends on where you got it from (and you didn't include the link you used).
Is it this one?
http://mr-public.auth-2ac4bfee353948...-r13408.tar.xz
From NiLuJe's snapshots thread.
Notice the changeset id (-r13408) that is what is significant in the snapshot postings.
knc1 is offline   Reply With Quote
Old 12-30-2016, 10:22 AM   #84
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 829
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Yes, I got it from the snapshots thread and it is the "-r13408" version. Where do I go from here? At this point I will be careful NOT to attempt to use it!

Dave
dhdurgee is offline   Reply With Quote
Old 12-30-2016, 11:15 AM   #85
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by dhdurgee View Post
Yes, I got it from the snapshots thread and it is the "-r13408" version. Where do I go from here? At this point I will be careful NOT to attempt to use it!

Dave
Well, I didn't see any message about it not being packaged for your model of Kindle, so it **should** work.

All I can suggest is to wait until someone comes along to fix it.
(NiLuJe is in school - no available hobby time.)

= = = = =

Perhaps we need to add some Wiki pages on what does not work. We never had to have one before.

PS: Collection Manager got fixed just a day or two ago.
Somebody new, needed it, and fixed it.
Yeah!!!
knc1 is offline   Reply With Quote
Old 12-30-2016, 04:58 PM   #86
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 829
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
I decided to give another shot at installing the RP on its own and may have more data. First I tried from KUAL:

Quote:
[2016-12-30 @ 21:44:52 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .

--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Fri, 30 Dec 2016 21:44:53 +0000

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)
mount: /dev/mmcblk0p2 already mounted or /mnt/mmc/ busy
mount: according to mtab, /dev/mmcblk0p2 is mounted on /mnt/mmc

Hu oh... Got return code 1 . . .
Then I tried via ";log mrpi" in the global search:

Quote:
[2016-12-30 @ 21:50:25 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .

--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Fri, 30 Dec 2016 21:50:25 +0000

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)
mount: /dev/mmcblk0p2 already mounted or /mnt/mmc/ busy
mount: according to mtab, /dev/mmcblk0p2 is mounted on /mnt/mmc

Hu oh... Got return code 1 . . .
In both cases I got a notice about a mounting error. This was not present in the log when running multiple installs. Perhaps this gives a clue to the solution?

In case it helps, I have kterm 2.3 installed for diagnostic purposes.

Dave
dhdurgee is offline   Reply With Quote
Old 12-30-2016, 05:56 PM   #87
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
first, check that error message (in kterm) -
The command to enter is:
Code:
mount
There will be a long list, just watch out for any line that mentions:
/dev/mmc
/dev/mmcblk0p2
You probably want to put kterm in landscape mode (two finger touch to bring up that menu).

At a guess, this reads like a scripting error -
/dev/mmcblk0p2 is the 'other' OS (diags) and RP has to modify the diags image.

But the script may clean up after itself and you will not see any mention in the output.

Can't know until you look.
knc1 is offline   Reply With Quote
Old 12-30-2016, 06:34 PM   #88
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 829
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Attached please find the output from the mount command on the KT3.

Dae
Attached Files
File Type: txt mount-log.txt (3.4 KB, 138 views)
dhdurgee is offline   Reply With Quote
Old 12-30-2016, 08:26 PM   #89
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by dhdurgee View Post
Attached please find the output from the mount command on the KT3.

Dae
Hmm....
The message is correct:
Code:
/dev/mmcblk0p2 on /mnt/mmc type ext3 (rw,relatime,barrier=1,data=ordered)
But probably wasn't expected to be.

Which rises the question:
"Is that a left over from the failed script or did Lab126 change something on us?"

This is an 8th. gen device, I would bet on the second choice but let us confirm. . . .
Be sure USB cable is not connected -
Hold down power button until pop-up, pops up, pick "Restart" -
When it is running again, use kTerm and the same command again -
Look for the line quoted above.

If it is there, we have to re-think how RP should be installed, because Lab126 changed things ;
If it isn't there, we just have to find the error in the RP scripting.
knc1 is offline   Reply With Quote
Old 12-31-2016, 08:09 AM   #90
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 829
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Given that the mount was present I decided to first check the contents of directory referenced in the first error and have attached it to this post. It would appear that the file "/mnt/mmc/opt/factory/system_diags" is indeed not present.

I have also attached the mount output after a restart which unless I am missing it somehow appears to show that the mount was a result of the first error.

I can only conclude at this point that the script will need to be modified to work with 5.8.7 firmware. It might be interesting to see where the problem starts, as it might make sense to downgrade to get the RP installed and then upgrade.

Dave
Attached Files
File Type: txt mount-log.txt (3.4 KB, 146 views)
File Type: txt factory.txt (612 Bytes, 150 views)
dhdurgee is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
How could i re-install rescue pack? tommytian Kindle Developer's Corner 2 06-18-2013 08:41 PM
Touch Rescue a bricked Kobo Touch eyecikjou567 Kobo Reader 2 04-13-2013 05:54 AM
Vietnamese text to speech voice pack kindle touch pspvhp Kindle Developer's Corner 17 03-21-2013 09:53 AM
A problem of rescue pack for KPW szfisher Kindle Developer's Corner 8 03-15-2013 05:50 PM
Microsoft planning to release Windows 7 Touch Pack. Gibbo Alternative Devices 1 12-11-2009 05:33 PM


All times are GMT -4. The time now is 02:37 AM.


MobileRead.com is a privately owned, operated and funded community.