HowTo Update Paperwhite to 5.3.0 WITHOUT locking yourself out!

[h1uke]

Originally Posted by NiLuJe

@rogerinnyc (and others): Thanks for the feedback

Any thoughts regarding my case?

I jailbroke a fresh unregistered 5.2.0 unit (got the "JailBreak!" banner and a "you're jailbroken" icon)
and immediately upgraded it to 5.3.0. This resulted to the situation when
all subsequent attempts to install usbnet_0.4N fail with error code 007.

Didn't try any other hack, just because the USBnet is all what I need.

I have a serial console connected and working, so can break into uboot and manually enter the diag mode.
Didn't get shell access yet, because all passwords generated based on serial number do not work.

Das Uboot has also significantly changed comparingly to what I'm familiar with, so I still
cannot specify kernel parameters when booting.

Any suggestion would be greatly appreciated.

[eureka]

Originally Posted by h1uke

Didn't get shell access yet, because all passwords generated based on serial number do not work.

Oh, BTW:

$ cat 530/etc/shadow 
root:!:10933:0:99999:7:::
daemon:*:10933:0:99999:7:::
bin:*:10933:0:99999:7:::
sys:*:10933:0:99999:7:::
sync:*:10933:0:99999:7:::
operator:*:10933:0:99999:7:::
sshd:*:10933:0:99999:7:::
messagebus:*:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default:!:10933:0:99999:7:::
framework:!:14033:0:99999:7:::

Yep, root can't login.

[twobob]

Originally Posted by eureka

Oh, BTW:

$ cat 530/etc/shadow 
root:!:10933:0:99999:7:::
daemon:*:10933:0:99999:7:::
bin:*:10933:0:99999:7:::
sys:*:10933:0:99999:7:::
sync:*:10933:0:99999:7:::
operator:*:10933:0:99999:7:::
sshd:*:10933:0:99999:7:::
messagebus:*:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default:!:10933:0:99999:7:::
framework:!:14033:0:99999:7:::

Yep, root can't login.

OUCH. just ouch.

[h1uke]

Originally Posted by eureka

Yep, root can't login.

thanks, that saved me some time..

The u-boot which comes up by default looks like stripped down
to a bare minimum. It doesn't support memory commands and
doesn't allow to redefine any boot parameters. In fact, it supports the
setenv command, but all definitions made this way are ignored during
actual boot.

Now it looks like I bricked the unit just by quickly pressing the "space"
while trying to break into u-boot prompt.
The console is frozen, the screen shows kindle tree and "Please wait
a moment while your Kindle starts up". It doesn't react on power button
manipulation, but shows the light when connected to a charger.

I'll try pulling out the battery later today.

[msg7086]

Originally Posted by h1uke

Any thoughts regarding my case?

I jailbroke a fresh unregistered 5.2.0 unit (got the "JailBreak!" banner and a "you're jailbroken" icon)
and immediately upgraded it to 5.3.0. This resulted to the situation when
all subsequent attempts to install usbnet_0.4N fail with error code 007.

If you didn't go with the jailbreak_bridge, you might have locked yourself out.

[h1uke]

Originally Posted by msg7086

If you didn't go with the jailbreak_bridge, you might have locked yourself out.

FYI:

Originally Posted by NiLuJe

EDIT: The file (update_jailbreak_bridge_1.7.N_install.bin) has moved to the full 1.7.N release of the JailBreak .

Thanks anyway. I'll doublecheck.

Yes, that was the case: I read the 1.7 guideline, but applied the 1.6 JB...

Re-applied the JB 1.7 data.stgz; the USBNet installation went smoothly.
So, now I'm up and running, and root _can_ login from the console

Thanks, everyone!

[dos1]

Originally Posted by h1uke

FYI:


Thanks anyway. I'll doublecheck.

Yes, that was the case: I read the 1.7 guideline, but applied the 1.6 JB...

Re-applied the JB 1.7 data.stgz; the USBNet installation went smoothly.
So, now I'm up and running, and root _can_ login from the console

Thanks, everyone!

Reapplied? AFTER upgrading to 5.3.0?

[h1uke]

Originally Posted by dos1

Reapplied? AFTER upgrading to 5.3.0?

Correct. i.e.

• 5.2.0->JB_1.6->upgrade_to_5.3.0->JB_1.7

worked for me.

[dos1]

Originally Posted by h1uke

Correct. i.e.

• 5.2.0->JB_1.6->upgrade_to_5.3.0->JB_1.7

worked for me.

Are you sure you haven't done anything else in between?

[ixtab]

Originally Posted by h1uke

Correct. i.e.

• 5.2.0->JB_1.6->upgrade_to_5.3.0->JB_1.7

worked for me.

That sounds strange indeed. JB 1.7 shouldn't normally be installable on a "vanilla" (=official) 5.3.0, and the 5.3.0 update should have wiped all prior modifications to the main partition.

[knc1]

The only thing that makes any sense is what h1uke is calling JB_1.6, is not JB_1.6
So...
@h1uke: Please post the md5sum of the file you are calling JB_1.6
I.E: the full output, md5sum and path/filename.

[knc1]

Originally Posted by h1uke

Any thoughts regarding my case?
- - - -
Das Uboot has also significantly changed comparingly to what I'm familiar with, so I still
cannot specify kernel parameters when booting.

Any suggestion would be greatly appreciated.

Please capture a listing of the u-boot commands and post the full listing.

Hmm...
A 'show environment' might help also.

[thomass]

Originally Posted by knc1

The only thing that makes any sense is what h1uke is calling JB_1.6, is not JB_1.6

AFAIU after the jailbreak there is still a need to use the update_jailbreak_bridge_1.7.N_install.bin

[NiLuJe]

@h1uke: Glad you got it figured out .

@thomass: Actually, the data.stgz from 1.7.N also installs the bridge (though I'd still recommend to run the proper bridge update before doing the official update, just in case) .

@all: Since he mentioned being able to boot into diags via serial, I'm assuming the jailbreak actually installed from diags, which makes sense .

[h1uke]

Originally Posted by dos1

Are you sure you haven't done anything else in between?

tried installing USBnet 2 or 3 times... played with Diag mode.. nothing more.