KPW2 - 5.6.1.0.6 - Rooting/Jailbreaking

[knc1]

Originally Posted by fctools

So Kubrick doesn't work on the latest firmware? And what does AFAIR mean? Afraid I'm a bit of a NOOB at this, worse for me.

Hint: Read the title of the Kubrick thread and, if your info block is up to date, see if you can find PW2 in the title.

As far as I recall, you will have to google AFAIR.

- - - - -

What do you see over the serial port while the Kindle starts up?

**IF** lab126 has fixed a long standing bug in the "erase all" command, you might still have u-boot installed.


Otherwise: Advertise it on e-bay as PW2 spare parts.

[fctools]

U-Boot 2009.08-lab126 (Aug 05 2014 - 04:37:39)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature: 44 C, calibration data 0x59e5265f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock : 66000000Hz
ipg per clock : 66000000Hz
uart clock : 80000000Hz
cspi clock : 60000000Hz
ahb clock : 132000000Hz
axi clock : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock : 396000000Hz
usdhc1 clock : 198000000Hz
usdhc2 clock : 198000000Hz
usdhc3 clock : 198000000Hz
usdhc4 clock : 198000000Hz
MMC: FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Pinot WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 0272XXXXXXXXXX
S/N: 9017XXXXXXXXXXXX
I2C: ready
DRAM: 256 MB
Using default environment

In: serial
Out: serial
Err: serial
Quick Memory Test 0x80000000, 0xfff0000
POST done in 59 ms
Battery voltage: 3788 mV

Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot >

Here's the boot log. Uboot does seem to be working I can run commands from it. I'm going to try to follow the instructions provided here. https://gist.github.com/TobiasWooldr...ca75190b9a473f Any suggestions would be appreciated.

[knc1]

Originally Posted by fctools

Here's the boot log. Uboot does seem to be working I can run commands from it. I'm going to try to follow the instructions provided here. https://gist.github.com/TobiasWooldr...ca75190b9a473f Any suggestions would be appreciated.

Those images are for a PW1 !!

Hold foot up, aim carefully, pull trigger, see what happens.

- - - -

Wrong model Kindle, wrong model SoC, wrong model cpu, ah ...
are you getting the picture yet?

- - - -

When you did the "erase all" it most likely also erased the device and user specific data which resides **outside** of the file system and outside of the partitioned area.

If you don't have a copy of that data area, you will still be SOL.

Translation: It is still good as spare parts.

[fctools]

Originally Posted by knc1

If you don't have a copy of that data area, you will still be SOL.
.

Afraid I don't. I did say I'm a NOOB at this is there any way of getting another image? The place I referenced before seems to have kernel images. ?

[fctools]

Also is there any chance of sweet talking Amazon into reflashing it? Anybody have any experience?

[knc1]

Originally Posted by fctools

Afraid I don't. I did say I'm a NOOB at this is there any way of getting another image? The place I referenced before seems to have kernel images. ?

Then the device will probably be useless after you restore what you erased (unless lab126 fixed the bug in "erase all").

Is this a PW2?
If so, then:
http://ixtab.tk/kindle-touch-images/PW2/

Start by reading the README.txt file.
Then read the threads that the readme.txt file points to.

Yes - you do need (both) kernel images and (both) partition images.
The Kindles are "dual boot" devices (two operating systems).

[eschwartz]

Originally Posted by fctools

Also is there any chance of sweet talking Amazon into reflashing it? Anybody have any experience?

You're funny.

Amazon has been known to replace stuff, which is more economic than fixing them on an individual basis but I question whether you can get a replacement after completely erasing the flash chip, which indicates you Meddled.

[fctools]

I know, I'm grasping at straws. I mean come on your supposed to be the Optimist can't you say anything brighter than that?

[eschwartz]

On the other hand, if you tell them it "broke", they may very well replace it. They might not bother to check what is wrong with it before binning it. (They definitely aren't spending a lot of time, at most they will try to turn it on....)
Seems a bit shady to do that...

[fctools]

I know I prefer fixing my own problems if possible.
Do you have any instructions on how to flash the images via fastboot? From my reading that seems to be the way to go but I can't find anything on exactly how to do it. I do have putty installed on a Linuxmint 17.1 system.

[eschwartz]

Get in via the serial port, flash the diags partition and kernel via fastboot (contained in the Kubrick LiveCD) and then use SSH to flash the main partition and kernel from the diags system.

Of course, since the extra data outside the partitions was erased, you can never get that back, which makes the device... less useful. I suppose it could work just without a serial number and registration info and stuff, but the loss might stop the Kindle from booting at all. I don't know, I've never tried it.

[knc1]

Well, we will see if Lab126 ever fixed their "erase all" bug - -

As part of "erase all" - the command re-writes u-boot with the u-boot image executing the command
AND
is (or was) intended to save and then restore that device and owner specific data.

I.E: If the device has a serial number after the ixtab (4) images are used, then the "erase all" command has been fixed.

If not - -
Then buy a used PW2 (look for one that works but has a broken screen) -

Then you have a choice -
Put your screen in the broken one -
or
Copy the device data from the broken one into yours.
Then discard the broken one - if two devices hit the 'net with the same "private" information - Amazon's system will black list the pair of them. Ask Twobob, it happened to him.

[fctools]

Whoohoo! I did it! using Geekmaster's fasboot thread from here https://www.mobileread.com/forums/sho...d.php?t=170929 and the fastboot program for linux from here https://www.mobileread.com/forums/att...6&d=1331834773. But I can't get Kual to start yet and I'm afraid to sync it until I get backdoor lock installed. Any suggestions would be appreciated & thanks for the help guys.

[knc1]

Originally Posted by fctools

Whoohoo! I did it! using Geekmaster's fasboot thread from here https://www.mobileread.com/forums/sho...d.php?t=170929 and the fastboot program for linux from here https://www.mobileread.com/forums/att...6&d=1331834773. But I can't get Kual to start yet and I'm afraid to sync it until I get backdoor lock installed. Any suggestions would be appreciated & thanks for the help guys.

OK, so far - - -
Now go to the settings page and see if you have a reasonable looking serial number. (Don't post the entire number - just tell us)

[fctools]

Yeah, as matter of fact I changed the serial # back to the one I posted before because the number changed and I was afraid of having someone else's.