Bricked PW1

[inarcs]

Hi there,

FOAll I know that I am not on the rigth place but I have a briked kindle PW1.
There are new post so I ask my problem here.

I do not know the past of it.

Only via serial port I could reach it.

I tried to follow this steps from szfisher:

- attach serial cable
- boot
- immediately after restart enter any key to stop autoboot
- enter "bist" and then "fastboot"
- via fastboot tool flash data and diags partitions on PC(windows or linux), img files is here: http://snipurl.com/debrick
- reboot
- immediately after restart enter any key to stop autoboot
- enter "run bootargs_diags ; bootm 0xE41000" to boot to diags
- get login prompy (menu "D) Exit, Reboot or Disable Diags" and then "L) Exit to login prompt")
- login as root (password:fiona2bc)
- enter "echo 0 > /var/local/upstart/lab126_gui.restarts"
- reboot
- after a while, press Enter to enter Recovery Menu
- select "E. Export FAT partition" to export U disk
- copy update_kindle_5.3.1.bin to U disk.
- press 1 to back Recovery Menu
- select "U. Update using update*.bin file on FAT partition" to update root partition.
- select "Q. quit" to boot

I could go until step:
enter "run bootargs_diags ; bootm 0xE41000" to boot to diags

Then I got error message:

uboot > bootm 0xE41000
## Booting kernel from Legacy Image at 70800000 ...
Image Name: Linux-2.6.31-rt11-lab126
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4608576 Bytes = 4.4 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
uboot > bootm
## Booting kernel from Legacy Image at 70800000 ...
Image Name: Linux-2.6.31-rt11-lab126
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4608576 Bytes = 4.4 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

Straingly:
If I boot then there is no problem to boot but just until like that:

uboot > boot
## Booting kernel from Legacy Image at 70800000 ...
Image Name: Linux-2.6.31-rt11-lab126
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4608576 Bytes = 4.4 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
2.6.31-rt11-lab126 #1 Fri Sep 28 14:59:26 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko (38984 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_u pdate_mode=1 (51140 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu... 0 /INFO:!!! Checking MBR /dev/mmcblk0 ! !!!
INFOartition 2, start sector is 782336
INFOartition 3, start sector is 913408
INFOartition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/44736 size=1465909248 bytes
flag type first last lba first lba size
Partition p1:
0x00 0x0b 16 <large> 16 2863088
CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
argc == 11
argv[0]: "kinit"
argv[1]: "consoleblank=0"
argv[2]: "rootwait"
argv[3]: "ro"
argv[4]: "ip=off"
argv[5]: "root=/dev/mmcblk0p1"
argv[6]: "quiet"
argv[7]: "eink=fslepdc"
argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
argv[9]: "mem=256M"
argv[10]: "console=ttymxc0,115200"
argc == 4
argv[0]: "IP-Config"
argv[1]: "-i"
argv[2]: "Linux kinit"
argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
boot: I def:rbt:reset=user_reboot,version=175016:


So far I could reach this stage.
Can anybody help me?
Thank you very much in advance.

[knc1]

kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)

The system appears to be running the "main" system (device is dual-boot).

So what is your problem?

[NiLuJe]

Your diags kernel is b0rked, or mismatched at the very least, but that's not critical, unless you rely on diags mode ;D.

At first glance, I don't see anything wrong in your main bootlog, since the reboot appears to be user-triggered. So: what's broken, and what did you do to break it?

[knc1]

Great minds think alike.

[NiLuJe]

The MR hive-mind has taken over! .

[inarcs]

Originally Posted by NiLuJe

Your diags kernel is b0rked, or mismatched at the very least, but that's not critical, unless you rely on diags mode ;D.

At first glance, I don't see anything wrong in your main bootlog, since the reboot appears to be user-triggered. So: what's broken, and what did you do to break it?

Hi!!!

Thanks for your really FAAAASSST replay!

My problem that this PW can not boot up. It stops:

kinit: Mounted root (ext3 filesystem) readonly.
boot: C def:bcut:batterycut=1,version=175016:
kernel: E wdog:Abnormal reset detected but saved buffer invalid:

and do nothing any more


I could upload:
diag kernel 5.2.0
main kernel 5.2.0
and
mmcblk0p2
But
mmcblk0p1 because it is too big to upload via fastboot
so I need the diag mode to do it.
I do not know the "past" of this PW.

THX!!

[Glorfindel]

Originally Posted by inarcs

[...]INFOartition 2, start sector is 782336
INFOartition 3, start sector is 913408
INFOartition 4, start sector is 1044480[...]

this is when it is better to use the

code

thing

[inarcs]

Originally Posted by Glorfindel

this is when it is better to use the

code

thing

Sorry Glorfindel I just dont understand what you mean at all.

Actually this is the last sentence:

kernel: E wdog:Abnormal reset detected but saved buffer invalid:

[NiLuJe]

The fact the hardware watchdog gets tripped doesn't sound all that promising, to be honest.

[Glorfindel]

Originally Posted by inarcs

Sorry Glorfindel I just dont understand what you mean at all.

you can put stuff in [code] tags so it doesn't turn into smiles
just make sure that the second one has a / in front of the code part

[inarcs]

Originally Posted by Glorfindel

you can put stuff in [code] tags so it doesn't turn into smiles
just make sure that the second one has a / in front of the code part

Ok thanks.

[inarcs]

Originally Posted by NiLuJe

The fact the hardware watchdog gets tripped doesn't sound all that promising, to be honest.

Is there any chance to get alive?

I can go into recovery mode and I even can see the books as well.

[Glorfindel]

np