View Single Post
Old 03-08-2012, 08:35 AM   #4
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by wsxhwyy View Post
Call geekmaster for help.
I found these infomation in fastboot.

partitions:
bootloader bootloader, 376KiB
prod overlaps bootloader, 120KiB
bist bist, 256KiB
userdata userdata, 5KiB
userpartition userpartition
mbr master boot record
kernel primary kernel
diags_kernel diags kernel
system main system (root) partition
diags secondary system (diags) partition
data user data

Which partition of my device is broken? I updated it to 5.0.3 and when it finished my kindle stucked and I could not boot into main again.
How did you "recover" mmcblk0p1? You cannot do that from fastboot (it is too big). You can boot to diags use a RUNME.sh script, or you can use fastboot to flash mmcblk0p2_ssh.img to diags and use an SSH shell, then copy mmcblk0p1.img to /dev/mmcblk0p1 (from RUNME.sh or at an SSH shell).

See these other threads for details:

Simple debricking: https://www.mobileread.com/forums/sho...d.php?t=170929

SelectBoot: https://www.mobileread.com/forums/sho...d.php?t=169645


Last edited by geekmaster; 03-08-2012 at 08:49 AM.
geekmaster is offline   Reply With Quote