MobileRead Forums

MobileRead Forums (https://www.mobileread.com/forums/index.php)
-   Kindle Developer's Corner (https://www.mobileread.com/forums/forumdisplay.php?f=150)
-   -   PW Bricked Paperwhite 1 (https://www.mobileread.com/forums/showthread.php?t=330231)

r00t65 05-26-2020 02:51 AM
Bricked Paperwhite 1
 
Hi, sorry for taking your time.
I am completely stuck with fixing my bricked PW.

I got my device shortly after release and installed Duokan. I can't recall what and how I did it but everything worked fine for years. After uploading new E-Books from my Smartphone over OTG my Kindle crashed and nothing was working. I connected it to a Serial console and noticed the file system got somehow corrupted. (broken file paths, weird characters and stuff like that).

In a debrick guide I found with google someone used
Code:
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
before writing the new firmware on the Kindle.

After that step I had no more file system errors cause I formated it. Then I connected my PW to my PC copied a fresh update package from Amazon on the Storage and installed it with
Code:
U. Update using update*.bin file on FAT partition
every thing worked fine, the update got installed but after a reboot I'm stuck with the following serial output:
Code:
Starting kernel ...
2.6.31-rt11-lab126 #1 Tue Sep 25 22:13:12 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36956 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51152 bytes)
INFO:eink initialized... (786432 bytes)
INFO:DIAGS MODE
Press [ENTER] for recovery menu...      0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 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/mmcblk0p2"
  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/mmcblk0p2) = dev(179,2)
kinit: root_dev = dev(179,2)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type ext2
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type squashfs
kinit: trying to mount /dev/root on /root with type vfat
kinit: trying to mount /dev/root on /root with type msdos
kinit: Unable to mount root fs on device dev(179,2)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
I can't boot regular and I can't enter DIAGS Mode so I think I did something very stupid I didn't notice or something went not as expected.

Thanks in advance
Patrick

P.S. sorry for my bad english. It's not my main language.

r00t65 05-26-2020 10:16 AM
EDIT: Okay, dumb mistake. I can boot if i remove the bootmode diags var . . .
But still, is there any possibility to restore my diags?

NiLuJe 05-26-2020 11:42 AM
Not without a diags + diags kernel backup ;).

(That's not part of an official update package, they only contain main + main kernel).

r00t65 05-26-2020 01:47 PM
I don't have a backup of my diags. That means there is no chance to get it working? Can someone give me his backup or is there the same problem that both devices can get blacklisted?

Do I need diags or is it only to comfortly debrick my device and how "dangerous" is it to tinker with my Kindle with out it? Is it more like if you screw up you have a spare eink for your next device or more like solder your cables back on and do it like last time?

NiLuJe 05-26-2020 03:34 PM
It's nice to have if you screw up, yeah ;).

knc1 05-26-2020 07:25 PM
Quote:
Originally Posted by r00t65 (Post 3992756)
Hi, sorry for taking your time.
I am completely stuck with fixing my bricked PW.
Code:

 . . . . . . .
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
I can't boot regular and I can't enter DIAGS Mode so I think I did something very stupid I didn't notice or something went not as expected.

Thanks in advance
Patrick

P.S. sorry for my bad english. It's not my main language.
That all reads as if your PW1 has had a long and useful life.
It may be (past) time to put it down for good.
At least it does if you know of a way to euthanize a PW1.

*) File errors;
A sign that your eMMC chip (the "flash") is nearly dead.
Once it finishes using up its spare "erase blocks" it will be time for a new chip.

*) "installed Duokan";
The members of this forum actively dislike how the Duokan project abused Open Source software.
Not something you will find a lot of help for here.

*) Missing diags;
The listing you provided above shows that you where trying to boot diags. You may not have intended that, but that is what the listing shows.
(argv[5]: "root=/dev/mmcblk0p2" )
Two possibilities:*) Duokan did it;
Over the years it has been noticed that the Duokan project has attempted to prevent removal of the installation.
It has been known to leave the device crippled in some way(s).

*) The dying eMMC did it;
Not likely, but possible.

Your PW1 should be old enough to use the old "Debricking Guide by geekmaster" once you find that in the "sticky" section, it will include links to off-site files.
Files that are complete "Main" kernel and system; also "Diags" kernel and system.
Even if you re-install all of them, you may need to erase your /dev/mmcblk0p3 (/usr/local IIRC).
Just "touch" it with some leading zeros and re-boot.
The start-up will test, find unusable, and reformat that system for you.
(Same-Same with mmcblk0p4 - your user visible USB directory system. It is much better to let the start-up system reformat any bad drives.)

r00t65 05-26-2020 08:25 PM
Quote:
Originally Posted by knc1 (Post 3993072)
That all reads as if your PW1 has had a long and useful life.
It may be (past) time to put it down for good.
At least it does if you know of a way to euthanize a PW1.
Indeed it had a very long and useful life. A friend on lonely evenings and good way to spend my free time with way over 10k read pages. I'm about to buy another E-ink device but it was too good for the bin. That's why I wanted to debrick it and it will live a maybe short but good life in the family when my new reader arrives. :)

Quote:
Originally Posted by knc1 (Post 3993072)
*) "installed Duokan";
The members of this forum actively dislike how the Duokan project abused Open Source software.
Not something you will find a lot of help for here.
I didn't knew about their Open Source abuse and now that I know about it I'll definitly read more about it. I'm writing scripts my self and publish them Open Source, too. I know how anoying it can be some times.

Quote:
Originally Posted by knc1 (Post 3993072)
*) Missing diags;
The listing you provided above shows that you where trying to boot diags. You may not have intended that, but that is what the listing shows.
(argv[5]: "root=/dev/mmcblk0p2" )
I wrote an answer to my original post where I mentioned that it was a dumb mistake from me but I was way over the 5 minutes for editing the Post. I forced diags on boot and forgot to remove it. It was intended in the begining but at that point where I tried to boot the new Firmware it wasn't. Shame on me.^^

Quote:
Originally Posted by knc1 (Post 3993072)
Two possibilities:*) Duokan did it;
Over the years it has been noticed that the Duokan project has attempted to prevent removal of the installation.
It has been known to leave the device crippled in some way(s).

*) The dying eMMC did it;
Not likely, but possible.


I tested the eMMC over the whole day by writing and reading files, using the Kindle as intended and every thing else I could think about. I'm not 100% sure but I'd blame Duokan in combination with Android OTG.

Quote:
Originally Posted by knc1 (Post 3993072)
Your PW1 should be old enough to use the old "Debricking Guide by geekmaster" once you find that in the "sticky" section, it will include links to off-site files.
Files that are complete "Main" kernel and system; also "Diags" kernel and system.
Even if you re-install all of them, you may need to erase your /dev/mmcblk0p3 (/usr/local IIRC).
Just "touch" it with some leading zeros and re-boot.
The start-up will test, find unusable, and reformat that system for you.
(Same-Same with mmcblk0p4 - your user visible USB directory system. It is much better to let the start-up system reformat any bad drives.)
At the moment my Kindle is working flawless. Or better the regular Firmware, Kernel and File System are working flawless. The biggest "Problem" I had was that I forgot to switch back to regular boot. I think I formated and reinstalled my Kindle 5 or 6 times until I gave up and went to bed. Today maybe 5 minutes after I sat down and started the serial console I noticed that I'm still forcing it to boot diags and it was fixed in like 5 seconds. :smack:

I'll have a look in the old "Debricking Guide by geekmaster" and i'll try to fix the last missing stuff. Thanks for your long answer.

knc1 05-27-2020 11:28 PM
Thanks.

I noticed that you have been here only a year less than myself (although there is a 17,000+ difference in our post count).

I had to make the reply long because you might not stop by here for another 7 years. :blink:

r00t65 05-28-2020 03:44 PM
I registered here basicly to jailbreak my Kindle and I never had any problems I had to ask questions about. Maybe cause I'm used to tinker with serial consoles (I improvised the serial connection with an old arduino laying on my desk and some spare parts I used to get the TX voltage down to about 1.6V; I'm still working on my serial connector with variable Voltage), micro processors of all kinds and memory chips and the Kindles are awesome as soon as it comes down to de brick and access to the os.

Because I had too many other projects running I never had the spare time to start modding kindles I ended up as silent reader and not as active community member.

lochan 07-09-2020 04:02 AM
Is there hope?
 
5 Attachment(s)
Code:
Welcome to Kindle!                                                                           

kindle login: info filesystems_var_local:runfixup:Running /var/local/system/fixup:           
info jb_bridge:main::i can fix this (r17392)                                                 
info jb_bridge:main::these are not the droids you're looking for                             
info system:emiting_event:mounted_varLocal:                                                   
info milestone:8.12:fs25:                                                                     
info milestone:8.15:vi00:                                                                     
info milestone:8.45:vi99:                                                                     
info display:started:time=8470:                                                               
info system:emiting_event:display_ready:                                                     
info cyttsp:update:vendor=CANDO:                                                             
info system:emiting_event:loaded_touch:                                                       
info userstore:run:time=8790,action=start:                                                   
info userstore:found_bootup_flag::Found BOOTUP flag file                                     
info battery:charged:cap=24,mV=3700,mAH=285:                                                 
info system:emiting_event:battery_ready:                                                     
boot: C def:bcut:batterycut=1,version=213712:                                                 
kernel: E savemsg:Abnormal reset detected but saved buffer invalid:
This is the latter part of the output I'm stuck at on Minicom through serial interface using an Arduino UNO as a USBTTL converter. There seems no key I can press to stop autoboot on the console.

Is this where my long-drawn debricking project on my PW1 ends? I just want to know if there's any hope or if this boy under the tree is really, finally dead. What now?

Thanks for all the support! :)

lochan 07-09-2020 09:45 AM
Also this if it helps:
 
Here's more:
Quote:
boot: C def:bcut:batterycut=1,version=213712:
kernel: E savemsg:--------Kernel Reboot Message Start--------:
kernel: E savemsg:Saved messages are prefixed with a #
# [ 61.198807] kernel: I papyrus:TempExceeded:temp=36:
# [ 121.198804] kernel: I papyrus:TempExceeded:temp=36:
# [ 181.198809] kernel: I papyrus:TempExceeded:temp=36:
# [ 241.198806] kernel: I papyrus:TempExceeded:temp=36:
# [ 293.744198] KERNEL: I pmic: PWRON1 event:
# [ 301.198810] kernel: I papyrus:TempExceeded:temp=36:
# [ 304.937468] bcut: C def:pcut:pending 15 second battery cut:
kernel: E savemsg:--------Kernel Reboot Message End--------:


All times are GMT -4. The time now is 11:14 PM.

Powered by: vBulletin
Copyright ©2000 - 3.8.5, Jelsoft Enterprises Ltd.
MobileRead.com is a privately owned, operated and funded community.