![]() |
#1 |
rm -rf /
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 219
Karma: 3333683
Join Date: Nov 2019
Location: United Kingdom
Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5
|
How-to: Booting 5.14.1 on KV
Description
This how-to covers the process of manually flashing a Kindle Voyage with a rootfs image from the 5.14.1 update for PW3. Compatibility This how-to is ONLY applicable to KV models with 512MB of RAM. Even then, you should use caution - the PW3 rootfs boots successfully without modification but there is presumably a reason why 5.14.1 was not released for KV. Process Download a copy of the 5.14.1 update for PW3 and extract it using Kindletool: Code:
kindletool extract ~/Downloads/update_kindle_all_new_paperwhite_5.14.1.bin /tmp/pw3 Code:
gzip -d /tmp/pw3/rootfs.img.gz Code:
uboot > bootm 0xE41000 Code:
usb export Code:
cp /tmp/pw3/rootfs.img /media/user/Kindle sync Code:
x ICE-WARIO-WFO-512 - USB EXPORT - 71 ~~~~ 1.16.614.264341 ~~~~ pcbId:04XXXXXXXXXXXX USB device exported Once you are done Eject the USB device from the PC then Battery capacity 71 (Q)-to continue (X)-Exit x Code:
exit login Code:
[root@[192_168_15_244] root]# dd if=/mnt/us/rootfs.img of=/dev/mmcblk0p1 bs=4096 112500+0 records in 112500+0 records out 460800000 bytes (439.5MB) copied, 95.986967 seconds, 4.6MB/s Code:
reboot |
![]() |
![]() |
![]() |
#2 |
Enhtusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 52
Karma: 2332557
Join Date: Dec 2018
Device: K3 DxG PW1 KV PW4
|
I'm wondering (as my KV is still a serial-virgin) if we can create a FB03 (Recovery v2) update - that is designed exactly for flashing system partitions.
I'll brick... I mean I'll test it tomorrow ![]() EDIT: Code:
> kindletool extract update_kindle_all_new_paperwhite_5.14.1.bin tmp > rm tmp/*.sig tmp/*.dat # signature rubish > rm -r tmp/imx60_wario # bye bye uboot+kernel! > cd tmp && kindletool create recovery2 -d voyage . ../update_kindle_all_new_voyage_5.14.1.bin ![]() Last edited by MrTick; 12-01-2021 at 05:44 PM. |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
You'd need a patched initrd for that (c.f., @katadelos' previous post on that front
![]() All of that *should* be doable via KindleTool, but, obviously, has never been tested (to my knowledge) ![]() Or @yifanlu's old FW-3.x-on-DXg posts/scripts, which might have been doing something of the sort way back in the day ![]() |
![]() |
![]() |
![]() |
#4 | |
rm -rf /
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 219
Karma: 3333683
Join Date: Nov 2019
Location: United Kingdom
Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5
|
Quote:
![]() I had a look and managed to find the script that I was using to patch recovery-util, it's just a simple find and replace: Spoiler:
|
|
![]() |
![]() |
![]() |
#5 | |
Enhtusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 52
Karma: 2332557
Join Date: Dec 2018
Device: K3 DxG PW1 KV PW4
|
Quote:
Posting link to @yiafanlu's solution: https://yifan.lu/2011/04/02/recoveri...rupt-kindle-2/ |
|
![]() |
![]() |
Advert | |
|
![]() |
#6 | |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Quote:
EDIT: Or `-c 1`, actually, unless you pass an actual custom 2K key to -k, otherwise shit happens ![]() (Also, fixed the docs). Last edited by NiLuJe; 12-02-2021 at 11:27 AM. |
|
![]() |
![]() |
![]() |
#7 |
Enhtusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 52
Karma: 2332557
Join Date: Dec 2018
Device: K3 DxG PW1 KV PW4
|
Yup, works like a charm with:
Code:
kindletool create recovery2 -c 1 -d voyage -p wario rootfs.img.gz ../update_kindle_all_new_voyage_5.14.1.bin I've built the custom kernel according more or less to katadelos guide: https://www.mobileread.com/forums/sh...d.php?t=343310 Did my first very own kernel bricked KV?... maybe (no more serial virgin!) Did one of the screws jumped through fourth dimension to some inaccessible universe?... I don't really want to talk about that ![]() Anyway, thanks again to both of you guys! |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
PW Booting to CELESTE_WFO | autumnhasfallen | Kindle Developer's Corner | 1 | 09-28-2018 07:53 AM |
H2O not booting | boriar | Kobo Developer's Corner | 41 | 02-05-2015 08:11 AM |
iLiad booting error, | tigerszheng | iRex | 1 | 05-24-2011 07:09 AM |
Opus Opus not booting | ixcoatl | Bookeen | 5 | 02-28-2010 05:56 PM |
booting time | bugsbunny14 | Sony Reader | 11 | 09-18-2006 11:03 AM |