Tools Snapshots of NiLuJe's hacks - Page 46

pete330 · 11-18-2019, 09:46 AM

Hello,

I have a PW4 with FW 5.12.1. I installed the most current (i.e. packages from the first post in this thread) Hotfix, USB Network, and Python packages today successfully, too. I can run KUAL and start apps, etc.

However when trying to install the rescue pack and crp, I get these error messages in the MR Installer log file:

[2019-11-18 @ 16:40:32 +0200] :: [MRPI r16257] - Beginning the processing of package 'Update_rp_20180530.N_install.bin' (rp 20180530.N I) . . .

Package 'Update_rp_20180530.N_install.bin' (rp 20180530.N I) is not targeting your device [2F7 vs. 11 0F 10 24 1B 1C 1D 1F 20 D4 5A D5 D6 D7 D8 F2 17 60 62 5F 61 C6 DD 13 54 53 2A 52 201 207 206 202 205 204 26B 26C 293 294 26E 26F 20C 20D 21C 219 21B 269 26A], skipping . . .

NiLuJe · 11-18-2019, 12:01 PM

@pete330: They're right. RP/CRP is unsupported on the newer partition layout used by those devices.

Someone with said devices and intimate knowledge of their inner workings might want to see how that could be fixed, if possible.

ezdiy · 11-19-2019, 09:59 PM

PSA: Seems like PW4 5.12.2 OTA nukes the JB cert. Update error 007 from hotfix.

NiLuJe · 11-20-2019, 12:02 AM

@ezdiy: Logs, please. U007 has become much more generic than the good old sigcheck failure it used to be.

ezdiy · 11-21-2019, 01:31 PM

Quote:

Originally Posted by NiLuJe

@ezdiy: Logs, please. U007 has become much more generic than the good old sigcheck failure it used to be.

You're right. After debugOn, the behavior is of update is different. After uploading Update_KUALBooklet_hotfix_f54e864_install.bin, the log writes:

Quote:

191121:174731 OTAController[1588]: I UserstoreScannerImpl:scanFile:filname=update-3569660025-36088b99-80fe-4a69-b478-60583ec3e6b6.bin:Parsing update file
191121:174731 OTAController[1588]: I BundleValidator:validateBundle:valid=true,filname=/mnt/us/update-3569660025-36088b99-80fe-4a69-b478-60583ec3e6b6.bin:Adding to update manager
191121:174731 OTAController[1588]: I lipc:evts:name=updateAvailable, origin=com.lab126.ota:Event sent

I have to reboot the device manually via restart in menu (no UYK is offered anywhere), and it jumps into recovery, which does:

Quote:

191121:174939 system: I milestone:10.44:sc05:sc05
191121:174939 <12>[ 4.066018] INFO:[ 4.059558] Found bundle /mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin
191121:174939 <12>[ 4.066403] INFO:get_bdev_sys_info: /sys/class/block/mmcblk1p8/size = 1048576
191121:174939 <12>[ 4.066480] INFO:get_bdev_sys_info: /sys/class/block/mmcblk1p8/size = 1048576
191121:174939 <12>[ 4.291335] *** CHECKING /mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin ***
191121:174939 <12>[ 5.384598] INFO:do_unbundle: filename=/mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin, new_file=0x00011ac8
191121:174939 <12>[ 5.387622] ERROR:do_unbundle: failed to read the entire bundle header.
191121:174939 <12>[ 5.394990] ERROR:Could not unbundle /mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin,error_code=4
191121:174939 <12>[ 5.395937] /mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin MD5SUM: 4b1cc8912e06f54f70216b1ee25cc9ea
191121:174939 <5>[ 5.396054] random: init urandom read with 72 bits of entropy available
191121:174939 <[ 4.059597] 12>[ 7.603389] INFO:removing /mnt-us/update-3569660025-4739c752-d16e-47b3-a185-3f336e2e983c.bin
191121:174939 <12>[ 7.610487] ERROR:*** There was a problem in the updates!
191121:174939 <12>[ 8.697435] INFO:UPDATE ERROR: 4
191121:174939 <12>[ 8.950132] INFO:Rebooting ...

It might be related to http://www.mobileread.mobi/forums/sh...=311613&page=3

as the coplate hotfix that used to work was twice the size.

ezdiy · 11-21-2019, 01:46 PM

Quote:

Originally Posted by ezdiy

You're right...

Just to add, for Update_jailbreak_hotfix_1.16.N_install.bin, the behavior is slightly different:

Quote:

191121:183435 OTAController[1590]: I UserstoreScannerImpl:scanFile:filname=Update_jailb reak_hotfix_1.16.N_install.bin:Parsing update file
191121:183435 OTAController[1590]: I BundleValidator:validateBundle:valid=true,filname=/mnt/us/Update_jailbreak_hotfix_1.16.N_install.bin:Adding to update manager
191121:183435 OTAController[1590]: I lipc:evts:name=updateAvailable, origin=com.lab126.ota:Event sent

191121:183600 <12>[ 4.056691] INFO:Checking for updates... (auto-pilot mode)
191121:183600 <12>[ 4.056903] INFO:find_file:160 Found update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin
191121:183600 <12>[ 4.060433]
191121:183600 <12>[ 4.066062] INFO:Fo[ 4.059592] und bundle /mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin
191121:183600 <12>[ 4.066435] INFO:get_bdev_sys_info: /sys/class/block/mmcblk1p8/size = 1048576
191121:183600 <12>[ 4.066509] INFO:get_bdev_sys_info: /sys/class/block/mmcblk1p8/size = 1048576
191121:183600 <12>[ 4.291014] *** CHECKING /mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin ***
191121:183600 <12>[ 5.384712] INFO:do_unbundle: filename=/mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin, new_file=0x00011ac8
191121:183600 <12>[ 5.392374] ERROR:Unknown bundle type code.
191121:183600 <12>[ 5.392402] ERROR:do_unbundle: parse_sysbundle_header failed with error code 22
191121:183600 <12>[ 5.395013] ERROR:Could not unbundle /mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin,error_code=4
191121:183600 <12>[ 5.397256] /mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin MD5SUM: 3f13ad0556e13706a57ae45f1269223f
191121:183600 <5>[ 5.397380] rand[ 4.059631] om: init urandom read with 72 bits of entropy available
191121:183600 <12>[ 7.602360] INFO:removing /mnt-us/update-3569660025-6796a6ef-3482-4f54-a804-9dd073a23a3f.bin
191121:183600 <12>[ 7.610069] ERROR:*** There was a problem in the updates!
191121:183600 <12>[ 8.697156] INFO:UPDATE ERROR: 4
191121:183600 <12>[ 8.949931] INFO:Rebooting ...

(sorry for bump, doesn't seem like I'm allowed to edit posts)

NiLuJe · 11-21-2019, 02:14 PM

@ezdiy: UYK *means* UYK. The initrd updater never has and never will accept any of our custom packages.

Also, if you were actually using coplate's nomax hotfix package, you're most likely screwed, as that code is very very old, and will not have bridged the update to 5.12 properly.

ezdiy · 11-21-2019, 02:43 PM

Quote:

Originally Posted by NiLuJe

@ezdiy: UYK *means* UYK. The initrd updater never has and never will accept any of our custom packages.

Ah, that explains things. Finally managed to get UYK option after disable/enable airplane mode. It now tries to update from runtime, and says:

Code:

191121:192123 OTAController[1590]: I UserstoreScannerImpl:scanFile:filname=Update_jailbreak_hotfix_1.16.N_install.bin:Parsing update file
191121:192123 OTAController[1590]: I BundleValidator:validateBundle:valid=true,filname=/mnt/us/Update_jailbreak_hotfix_1.16.N_install.bin:Adding to update manager
191121:192123 OTAController[1590]: I lipc:evts:name=updateAvailable, origin=com.lab126.ota:Event sent
191121:192143 OTAController[1590]: I lipc:evts:name=readyToUpdate, origin=com.lab126.ota:Event sent

191121:192143 OTAController[1590]: I lipc:evts:name=readyToUpdate, origin=com.lab126.ota:Event sent

....

191121:192146 system: I ota-update:check:: /keys partition mounted before OTA update
191121:192146 system: I ota-update:check:: Contents of /keys partition are: dha_certificate.pem dha_key

191121:192146 lipc-get-prop[5890]: W def:lipc:method=LipcOpenEx service=(null):Method has been deprecated.
191121:192146 OTAController[1590]: I UpdateManagerImpl:startUpdate:command=start ota-update BUNDLE="/mnt/us/update-3569660025-5df6bd85-3d7f-4936-bff4-11bcb4d15adc.bin",status=0:Command terminated normally.
191121:192147 system: I bundlefuncs:parse_bundle:BundleType=SP01:BundleType=SP01 
191121:192147 system: I bundlefuncs:parse_bundle:BundleType=FC04:BundleType=FC04 

... bunch of unrelated stuff? ....

191121:192151 system: E bundlefuncs:verify_bundle:invalid bundle signature:invalid bundle signature 
191121:192151 system: E update:bundle_checksum:: invalid bundle signature 192

191121:192151 lipc-send-event[7104]: W def:lipc:method=LipcOpenEx service=com.lab126.blanket.ota:Method has been deprecated.
191121:192151 lipc-send-event[7104]: I lipc:evts:name=otaSplashError, origin=com.lab126.blanket.ota, fparam=007:Event sent
191121:192151 lipc-send-event[7107]: W def:lipc:method=LipcOpenEx service=com.lab126.blanket.ota:Method has been deprecated.
191121:192151 lipc-send-event[7107]: I lipc:evts:name=otaSplashError, origin=com.lab126.blanket.ota, fparam=007:Event sent
191121:192151 system: E update:otaup:: otaup error (U007), exiting with code: 7
191121:192151 system: E update:validate_bundle::
191121:192151 init.exe: ota-update main process (5898) terminated with status 7

This doesn't look good.

Full log https://paste.fedoraproject.org/past...FjcNmAZ8MA/raw

NiLuJe · 11-21-2019, 05:46 PM

Yup, that's a sigcheck failure. Probably because of the aforementioned outdated bridge.

NiLuJe · 11-25-2019, 05:39 PM

Another round of updates, mainly around USBNet, with a move to libfuse3 and the matching sshfs version. It's now also linked to its own copy of glib, instead of relying on the old & mismatched version shipped on Kindle.

Waitingforatrain · 11-25-2019, 07:22 PM

Quote:

Originally Posted by NiLuJe

@ezdiy: UYK *means* UYK. The initrd updater never has and never will accept any of our custom packages.

Also, if you were actually using coplate's package, you're most likely screwed, as that code is very very old, and will not have bridged the update to 5.12 properly.

Hmm... on 5.12.1 and have used the booklet from coplate's kual package. On KV, should I be doing something different here?

P.S. Have KV filled to about 150mb free space. Noticed that Amazon was trying to send an update and wanted to install (but couldn't because of lack of space). File in the root was update.bin.tmp.partial (not a folder like the old blocking method).

shamanNS · 11-25-2019, 08:45 PM

You misunderstood how the "old" blocking worked. It being a folder and not a file was exactly the point :d

NiLuJe · 11-26-2019, 12:04 AM

@Waitingforatrain: I meant the nomax hotfix packages, not KUAL

.

ezdiy · 11-26-2019, 01:52 AM

Quote:

Originally Posted by Waitingforatrain

Hmm... on 5.12.1 and have used the booklet from coplate's kual package. On KV, should I be doing something different here?

P.S. Have KV filled to about 150mb free space. Noticed that Amazon was trying to send an update and wanted to install (but couldn't because of lack of space). File in the root was update.bin.tmp.partial (not a folder like the old blocking method).

I should clarify that I've lost JB because I had 0.15 hotfix installed at the time of 5.12.2 went in. If I understand correctly, you need to install 0.16 *before* running 5.12.2 OTA. The coplate thing in my post was just desperate attempt of trying everything after the JB disappeared.

As for update.partial, that stopped working in all 5.12.x. The only surefire way to block updates now is to edit /etc/version.txt, so as to make initrd think any OTA update it finds as "too old".

NiLuJe · 11-26-2019, 10:58 AM

@ezdiy: Yup, timing was key

.

Fudging the version string is deliciously lo-fi, if that actually works, I like it

. c.f., the device_id script in the Helper extension for a tad more details about the format, because it's not entirely obvious how the build number is stored in there.

11-21-2019, 02:14 PM	#682
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@ezdiy: UYK means UYK. The initrd updater never has and never will accept any of our custom packages. Also, if you were actually using coplate's nomax hotfix package, you're most likely screwed, as that code is very very old, and will not have bridged the update to 5.12 properly. Last edited by NiLuJe; 11-26-2019 at 12:04 AM. Reason: Make that clearer

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I removed the hacks, installed 3.1, then new hacks, and now Kindle is dead	cloudyvisions	Amazon Kindle	55	11-29-2023 07:27 PM
Tools Snapshots of Coplate's packages	coplate	Kindle Developer's Corner	104	10-23-2022 11:41 PM
NiLuJe offline?	picree	Kindle Developer's Corner	1	09-28-2016 10:29 PM
Snapshots test in Live version	Michele Clinco	OpenInkpot	7	09-08-2009 02:42 PM

11-18-2019, 09:46 AM	#676
pete330 Connoisseur Posts: 70 Karma: 200233 Join Date: Aug 2013 Device: Kindle Paperwhite	Hello, I have a PW4 with FW 5.12.1. I installed the most current (i.e. packages from the first post in this thread) Hotfix, USB Network, and Python packages today successfully, too. I can run KUAL and start apps, etc. However when trying to install the rescue pack and crp, I get these error messages in the MR Installer log file: [2019-11-18 @ 16:40:32 +0200] :: [MRPI r16257] - Beginning the processing of package 'Update_rp_20180530.N_install.bin' (rp 20180530.N I) . . . Package 'Update_rp_20180530.N_install.bin' (rp 20180530.N I) is not targeting your device [2F7 vs. 11 0F 10 24 1B 1C 1D 1F 20 D4 5A D5 D6 D7 D8 F2 17 60 62 5F 61 C6 DD 13 54 53 2A 52 201 207 206 202 205 204 26B 26C 293 294 26E 26F 20C 20D 21C 219 21B 269 26A], skipping . . .

11-18-2019, 12:01 PM	#677
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@pete330: They're right. RP/CRP is unsupported on the newer partition layout used by those devices. Someone with said devices and intimate knowledge of their inner workings might want to see how that could be fixed, if possible.

11-19-2019, 09:59 PM	#678
ezdiy Zealot Posts: 121 Karma: 156515 Join Date: Oct 2019 Device: KT, KPW4, PB740-2	PSA: Seems like PW4 5.12.2 OTA nukes the JB cert. Update error 007 from hotfix.

11-20-2019, 12:02 AM	#679
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@ezdiy: Logs, please. U007 has become much more generic than the good old sigcheck failure it used to be.

11-21-2019, 05:46 PM	#684
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Yup, that's a sigcheck failure. Probably because of the aforementioned outdated bridge.

11-25-2019, 05:39 PM	#685
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Another round of updates, mainly around USBNet, with a move to libfuse3 and the matching sshfs version. It's now also linked to its own copy of glib, instead of relying on the old & mismatched version shipped on Kindle.

11-25-2019, 08:45 PM	#687
shamanNS Wizard Posts: 1,124 Karma: 12345678 Join Date: Feb 2010 Location: Serbia Device: Kindle PW5, Kobo Libra 2, Kindle PW1	You misunderstood how the "old" blocking worked. It being a folder and not a file was exactly the point :d

11-26-2019, 12:04 AM	#688
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Waitingforatrain: I meant the nomax hotfix packages, not KUAL .

11-26-2019, 10:58 AM	#690
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@ezdiy: Yup, timing was key . Fudging the version string is deliciously lo-fi, if that actually works, I like it . c.f., the device_id script in the Helper extension for a tad more details about the format, because it's not entirely obvious how the build number is stored in there.