Mobileread
PW2 Help to debrick
#1  mash.m 01-10-2019, 09:50 AM
Hi,

i got a faulty PW2 from a friend. Hey says that he jailbrake it to allow the custom screensver. But now it won´t boot up. So i added a serial port to see what happens:

Code
U-Boot 2009.08-lab126 (Jan 24 2018 - 12:49:03)
CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature: 37 C, calibration data 0x5895055f
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 2GB
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 02E2201135230DVD
S/N: 90D422xxxxxxxxxxxxxx
I2C: ready
DRAM: 256 MB
Using default environment
In: serial
Out: serial
Err: serial
Quick Memory Test 0x80000000, 0xfff0000
POST done in 57 ms
Battery voltage: 4094 mV
Hit any key to stop autoboot: 0
## Booting kernel from Legacy Image at 80800000 ... Image Name: Linux-3.0.35-lab126 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2951744 Bytes = 2.8 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.097156] boot: C def:bcut:batterycut=1
[ 0.101946]
[ 0.276584] LPDDR2 MfgId: 0x1 [Samsung]
[ 0.280446]
[ 0.280449] just text: vaddr c0132fdc, va 0xc0132200 pa 0x801000c3 attr 0x6
[ 0.292919]
[ 0.292922] nmx6sl_wfi_iram: vaddr d084e000, va 0xd084e200 pa 0x904043 attr 0x2
[ 0.301774]
[ 0.301777] mx6sl_ddr: vaddr d0856000, va 0xd0856200 pa 0x905043 attr 0x2
[ 0.310106]
[ 0.310109] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[ 0.320946]
[ 0.320948] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[ 0.335299]
[ 0.335301] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[ 0.347442]
[ 0.347444] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[ 0.357787]
[ 0.357790] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[ 0.367678]
[ 0.367680] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
DEBUG:recovery-util.c:1703:setup_die_signals():Installed signal handlers.
3.0.35-lab126 #2 PREEMPT Tue Dec 4 17:14:27 PST 2018 armv7l
[ 0.545584] FAT-fs (loop1): bogus number of reserved sectors
[ 1.584554] imx_epdc_fb imx_epdc_fb: Failed to load fw! (err -2) Trying fallback fw
[ 1.633686] panel_get_upd_modes: Unknown waveform mode. Using MODE_07!
Press [ENTER] for recovery menu... 0 /BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(179,1)
kinit: init not found!
Ok, after this i download a new image from amazon for the german pw2 from here:
https://www.amazon.de/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201307450

i extract with the kindletool and flashed the new kernel with fastboot

Code
fastboot flash kernel uimage
Code
X:\Kindle>fastboot.exe flash kernel uimage
downloading 'kernel'...
OKAY [ 0.146s]
writing 'kernel'...
OKAY [ 0.845s]
finished. total time: 0.992s
after reboot a enter the recover menu followed by:

I - initialize partition table and format FAT

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

But after pressing U nothing happens:

Code
USB CONNECTED!!
Charge: 97% [#########################################################:]
[FAT32]
1. done
R. reboot
Choose: /1
Charge: 97% [#########################################################:]
Menu
====
3. Load MMC over USB storage
4. Erase MMC
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose: 9 -U
Charge: 97% [#########################################################:]
Menu
====
3. Load MMC over USB storage
4. Erase MMC
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose: 8 \U
Charge: 97% [#########################################################:]
Menu
====
3. Load MMC over USB storage
4. Erase MMC
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose: 7 |q
Any idea where to start?
Reply 

#2  knc1 01-10-2019, 10:57 AM
Why are you using a "German" update image on an International/USA (90D4) device?
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers

Using a current KindleTool taken from NiLuJe's current snapshot thread, on a terminal on the PC, do:
kindletool.exe convert --info <... package_name.bin ...>, capture and post the result (quoted as "code").
Reply 

#3  mash.m 01-10-2019, 12:06 PM
Code
X:\Kindle\Kindletool>kindletool.exe convert --info update_kindle_paperwhite_v2_5.10.2.bin
Checking update package 'update_kindle_paperwhite_v2_5.10.2.bin'.
Bundle SP01 (Signing Envelope)
Cert number 2
Cert file pubprodkey02.pem (Official 2K)
Bundle FB03 (Fullbin [OTA?, fwo?])
Bundle Type Recovery V2
Target OTA 3374520058
MD5 Hash 6a18faf316eb2c0aeacadf554392aa76
Magic 1 2048630901
Magic 2 1897089723
Minor 1
Platform Wario
Header Rev 0
Board Unspecified
Devices 14
Device Kindle PaperWhite 2 (2013) (Unknown Variant 0xF4)
Device Kindle PaperWhite 2 (2013) (Unknown Variant 0xF9)
Device Kindle PaperWhite 2 (2013) WiFi+3G Japan
Device Kindle PaperWhite 2 (2013) WiFi+3G Russia
Device Kindle PaperWhite 2 (2013) WiFi+3G Europe
Device Kindle PaperWhite 2 (2013) WiFi+3G Canada
Device Kindle PaperWhite 2 (2013) WiFi+3G
Device Kindle PaperWhite 2 (2013) WiFi
Device Kindle PaperWhite 2 (2013) WiFi+3G (4GB)
Device Kindle PaperWhite 2 (2013) WiFi+3G (4GB) Brazil
Device Kindle PaperWhite 2 (2013) WiFi+3G (4GB) Europe
Device Kindle PaperWhite 2 (2013) WiFi+3G (4GB) Canada
Device Kindle PaperWhite 2 (2013) WiFi Japan
Device Kindle PaperWhite 2 (2013) WiFi (4GB) International
Reply 

#4  mash.m 01-14-2019, 06:27 AM
Hi,

i start again from the beginning with initialize the partition table and format, type E for export, but windows now recognize it as blank partition. formating with windows works, but still no luck to update the system.
after several failes i format the partition with mkdosfs for windows:

Code
mkdosfs.exe -F 32 -s 16 -n Kindle f:
now it flash´s the main system.

Kindle is now back to life...
Reply 

#5  mash.m 01-14-2019, 06:56 AM
Hi,

now diag Kernel is missing. I think i have access to an other pw2 where i can download the missing files. any help on this?
Reply 

#6  mash.m 01-14-2019, 10:03 AM
Hi,

after backup from a pw2 with serial connection i get all running now. backup done with:

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

flashing diags_kernel and diags partition done with fastboot.

thx
Reply 

#7  knc1 01-14-2019, 10:54 AM
Quote mash.m
Hi,

after backup from a pw2 with serial connection i get all running now. backup done with:

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

flashing diags_kernel and diags partition done with fastboot.

thx
Not one of my more popular contributions (although I use it myself).
Reply 

#8  mash.m 01-15-2019, 03:43 AM
@knc1
thanks for this!

I had another problem with this kindle. cause this one have a faulty touch i will use it as digital picture frame that will change the screen after a while. but it never woke up from deep sleep with:

Code
echo "mem" > /sys/power/state
i figured out that i had to set the clock/date first with:

Code
date MMDDHHMMYYYY
Code
date 011411002019
and then sync to the rtc/hardware clock:

Code
hwclock -w
Reply 

Today's Posts | Search this Thread | Login | Register