Uboot needed for pw2

[Merlin09]

Flashing uimage worked, but for the time being I can't manage to get the recovery menu... It seems you need to be precise to press enter at the right moment

[Merlin09]

Reminder for myself, first

Fastboot flash kernel uImage

Then access recovery to do :

I - initialize partition table and format FAT
It doesn't say anything about /var/local - but we know that a 'normal' start-up will re-format that if required.
E - export FAT partition
Connect Kindle to PC with the normal USB cable.
Copy the Amazon update package (just as you downloaded it) to the root (highest level directory shown) of user storage.
Safely remove
Disconnect USB cable to PC
U - update (main) system from file on user storage
Reboot
It should 'just work'.

My only problem is that I can't get the hang of the timing to press enter and access recovery

[knc1]

As soon as you see the start of the messages, press and hold key.
That is:
If you want to catch the kernel's initramfs (which you do) start pressing while you still see the u-boot messages, BEFORE you see the "to stop autoboot ..."

[Merlin09]

Ok. I was doing it in the middle of the boot, when the press enter to start recovery appears.
I will try your way as soon as I get home.
I may see the light at the end of the tunnel
Thanks!

[Merlin09]

I tried multiple times, but no luck.

But looking at the logs, here is what I found:

<4>[    4.806630] DEBUG:eink.c:727:eink_draw_sprite():eink_draw_sprite(x0:480,y0:983,s->x_size=24,s->y_size=41,s->x_off=0,s->y_off=0)
<4>[    4.806977] INFO:eink.c:891:eink_printf():BATTERY INVALID: -22
<4>[    5.425266] INFO:recovery-util.c:316:fl_control_fadedown():
<4>[    5.425363] ===FL fadedown success===
<4>[    5.425678] ERROR:recovery-util.c:346:battery_check():
<4>[    5.425700] === BATTERY ID IS INVALID. STOPPING BOOT ===
<4>[    5.429586] DEBUG:module.c:139:insmod():/lib/modules/fsl_otg_arc.ko:loaded 26540 bytes. (26540)
<6>[    5.441176] Freescale USB OTG Driver loaded, $Revision: 1.55 $
<6>[    5.448627] add wake up source irq 75
<4>[    5.468076] INFO:module.c:163:insmod():Loaded module /lib/modules/fsl_otg_arc.ko  (26540 bytes)
<4>[    5.478681] DEBUG:module.c:139:insmod():/lib/modules/ehci-hcd.ko:loaded 78400 bytes. (78400)
<6>[    5.502514] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[    5.513825] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
<6>[    5.513881] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
<6>[    5.534546] fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
<6>[    5.554505] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
<6>[    5.555341] hub 1-0:1.0: USB hub found
<6>[    5.555378] hub 1-0:1.0: 1 port detected
<6>[    5.555784] add wake up source irq 74
<6>[    5.559670] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
<6>[    5.559721] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
<6>[    5.584544] fsl-ehci fsl-ehci.1: irq 74, io base 0x02184200
<6>[    5.604504] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
<6>[    5.605304] hub 2-0:1.0: USB hub found
<6>[    5.605338] hub 2-0:1.0: 1 port detected
<4>[    5.605739] INFO:module.c:163:insmod():Loaded module /lib/modules/ehci-hcd.ko  (78400 bytes)
<4>[    5.606373] DEBUG:module.c:139:insmod():/lib/modules/arcotg_udc.ko:loaded 42072 bytes. (42072)
<6>[    5.608369] ARC USBOTG Device Controller driver (1 August 2005)
<4>[    5.616635] INFO:module.c:163:insmod():Loaded module /lib/modules/arcotg_udc.ko  (42072 bytes)
<4>[    5.617406] DEBUG:module.c:139:insmod():/lib/modules/g_file_storage.ko:loaded 60264 bytes. (60264)
<6>[    5.620022] fsg_bind:3588 unbind
<6>[    5.620275] g_file_storage gadget: File-backed Storage Gadget, version: 1 September 2010
<6>[    5.620304] g_file_storage gadget: Number of LUNs=1
<6>[    5.620322] Suspend udc for OTG auto detect
<6>[    5.666209] boot:USB host cable is already plugged in. Simulating event
<6>[    5.666253] fsl-usb2-udc: bind to driver g_file_storage 
<4>[    5.666334] INFO:module.c:163:insmod():Loaded module /lib/modules/g_file_storage.ko removable=1 vendor=0x1949 product=0x0004 release=0x0100 recovery_mode=1 (60264 bytes)

=== END ===

You see that <4>[ 5.425700] === BATTERY ID IS INVALID. STOPPING BOOT ===. Do you think it is the problem? If so, is there some way to change the battery ID ?

maybe with idme? for now, I just entered sn and board sn with idme, no other thing.

[knc1]

I thought that you needed to stop the process at the autoboot stage, that is the regular kernel starting up.

How did you get the battery to change its id number?
Did you replace the battery when you replaced the screen?

[Merlin09]

Absolutely not. That's what I can't understand. It seems my kindle did a lot of things it shouldn't have.

As seen here
https://www.mobileread.com/forums/sh...=261999&page=2

The battery should fix itself when I will manage to unbrick the unit.

I will try again to enter recovery. Maybe I will use another terminal emulator. I used putty because it's what I use at work, but since I use Linux at home, I'd better use minicom.

[Merlin09]

Well, I can't boot recovery.

Here is the end of my last boot log:

<6>[    5.105317] hub 1-0:1.0: USB hub found
<6>[    5.105354] hub 1-0:1.0: 1 port detected
<6>[    5.105765] add wake up source irq 74
<6>[    5.109651] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
<6>[    5.109698] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
<6>[    5.134485] fsl-ehci fsl-ehci.1: irq 74, io base 0x02184200
<6>[    5.154469] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
<6>[    5.155267] hub 2-0:1.0: USB hub found
<6>[    5.155304] hub 2-0:1.0: 1 port detected
<4>[    5.155797] INFO:module.c:163:insmod():Loaded module /lib/modules/ehci-hcd.ko  (78400 bytes)
<4>[    5.156427] DEBUG:module.c:139:insmod():/lib/modules/arcotg_udc.ko:loaded 42072 bytes. (42072)
<6>[    5.158422] ARC USBOTG Device Controller driver (1 August 2005)
<4>[    5.166700] INFO:module.c:163:insmod():Loaded module /lib/modules/arcotg_udc.ko  (42072 bytes)
<4>[    5.167479] DEBUG:module.c:139:insmod():/lib/modules/g_file_storage.ko:loaded 60264 bytes. (60264)
<6>[    5.170092] fsg_bind:3588 unbind
<6>[    5.170346] g_file_storage gadget: File-backed Storage Gadget, version: 1 September 2010
<6>[    5.170374] g_file_storage gadget: Number of LUNs=1
<6>[    5.170393] Suspend udc for OTG auto detect
<6>[    5.226166] fsl-usb2-udc: bind to driver g_file_storage 
<4>[    5.226252] INFO:module.c:163:insmod():Loaded module /lib/modules/g_file_storage.ko removable=1 vendor=0x1949 product=0x0004 release=0x0100 recovery_mode=1 (60264 bytes)

=== END ===

you can see in the last line recovery_mode=1 , so I guess the key press was taken into account, but for some reason doesn't continue until the menu...
Any ideas?

[Merlin09]

Subsidiary question. I didn't think about that earlier.

My wife has a fully functional PW2 with a 9017 serial.

If I tear it open and install the terminal connection in it, would I be able to extract both kernels and both partitions, and unbrick mine with that?

I know, by that point it feels like a long shot, and I'd prefer a way to fix the battery id...

[knc1]

Originally Posted by Merlin09

Subsidiary question. I didn't think about that earlier.

My wife has a fully functional PW2 with a 9017 serial.

If I tear it open and install the terminal connection in it, would I be able to extract both kernels and both partitions, and unbrick mine with that?

I know, by that point it feels like a long shot, and I'd prefer a way to fix the battery id...

Install the jailbreak and install USBnetworking add-in.
No need to open the device.
There is a script for extracting the kernels if the firmware version your wife is running does not expose them in the file system.

Start in the 'Master Index' sticky to find de-bricking and firmware back-up (of which getkernels.sh is part of that toolset).
A.K.A: "Where Do I Start" thread title.

[Merlin09]

Thanks a lot, I will do this. I don't know when I will be able to, but I'll let you know

[Merlin09]

Hello.

I jailbroke my wife's pw2. I installed kual and mr packages, then usbnetworking.

Now I have to figure out how to connect with ssh. I don't know the root password for ssh over WiFi, but in another post of yours you said it wouldn't be possible to guess it. So I connected over USB, but the network interface doesn't seem to configure itself in my Ubuntu system.

I will look how to use it tomorrow, then I will have to backup her system, and hope to restore my pw2 with these images

Thanks for your help in all this. I'll keep you posted on the next steps

[knc1]

https://www.mobileread.com/forums/sh...d.php?t=204676

[Merlin09]

Thanks!

Here is what I did:

I put the dc3dd binary, arm version, from your package at the root of the pw2's user storage.

Then, from kual, I toggled usbnetworking on.

I plugged the kindle in usb, disconnected the new interface from ubuntu network manager, and used dmesg to identify the interface's name.

I then ran:

sudo ip address add 192.168.15.201 peer 192.168.15.244 dev enp0s26u1u6u2
sudo ip link set up dev enp0s26u1u6u2
telnet 192.168.15.244

and tadaaa! I was in

then, in the kindle's console, I ran:

cd /mnt/us
./dc3dd if=/dev/mmcblk0p1 hof=./mmcblk0p1.img hash=sha1
./dc3dd if=/dev/mmcblk0p2 hof=./mmcblk0p2.img hash=sha1

And since everything went fine, I guess I have a backup of both partitions.

Now, I'll search how to backup the kernels, and I'll be back to my bricked one.

I'll keep you posted

[Merlin09]

ok, I used the getkernels script, and I now have all images.

Let's go back to the bricked one!