Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard - Page 4

curb · 03-08-2012, 12:15 PM

k4nt, never upgrade, Window 7 platform, unfamiliar with linux,

i tried diagnose mode,copy runme.sh and data.tar.gz into kindle throug usb export, magic restart,and nothing happend.

it remains what it was this morning, freeze at the tree screen, 50%.
i have no idea about ssh, what do you mean by enter ssh mode?

murz_07 · 03-08-2012, 02:33 PM

Woohoo!!!!
I recovered my Kindle after almost loosing my hope!!!
Geekmaster, you are GOD!!!

geekmaster · 03-08-2012, 02:53 PM

Quote:

Originally Posted by murz_07

Woohoo!!!!
I recovered my Kindle after almost loosing my hope!!!
Geekmaster, you are GOD!!!

Okay, success report added to first post. It is getting a bit long, I think...

geekmaster · 03-08-2012, 03:02 PM

Quote:

Originally Posted by curb

k4nt, never upgrade, Window 7 platform, unfamiliar with linux,

i tried diagnose mode,copy runme.sh and data.tar.gz into kindle throug usb export, magic restart,and nothing happend.

it remains what it was this morning, freeze at the tree screen, 50%.
i have no idea about ssh, what do you mean by enter ssh mode?

If you have a RUNME.done file on the kindle, you need to delete that before RUNME.sh can be run again. It is there to prevent a bad RUNME.sh file from causing an infinite reboot loop, and prevents RUNME.sh from running until you delete RUNME.done. When RUNME.sh runs, another RUNME.done file will be created on your kindle USB drive.

SSH means "Secure Shell", which is a modern replacement for the old Telnet protocol. It lets you connect to your kindle and get a root shell command prompt, where you can type linux commands that tell the kindle what to do. You can repair you kindle from there using linux commands, but if you feel uncomfortable with that, you can instead use my data.tar.gz from the "Select Boot" first post, and one of the various RUNME.sh scripts that contain linux commands to obtain status messages and do the repair for you.

You can replace damaged of missing scripts in your main system boot partition, or you can replace that entire partition with a "factory original" backup copy. You can zero the /var/local partition if it was filled from indexing too many books. These things are documented in multiple places, but I recommend the "simple debricking" and "select boot" threads.

hostar · 03-08-2012, 03:10 PM

-- DELETED --

(is it possible to delete whole post?)

murz_07 · 03-08-2012, 03:12 PM

Quote:

Originally Posted by geekmaster

Okay, success report added to first post. It is getting a bit long, I think...

Oh, sorry, a bit early

That was my happyness about flashing diags and making it work. USBnetwork works.
But I can't boot in main mode after "dd" mmcblk0p1. I forgot "bs=4K". Tryed again with it, no change.
Hard reset -> nothing happens.
The same with MgfTool.
"dd" mmcblk0p3 doesn't help too.

geekmaster · 03-08-2012, 04:06 PM

Quote:

Originally Posted by murz_07

Oh, sorry, a bit early

That was my happyness about flashing diags and making it work. USBnetwork works.
But I can't boot in main mode after "dd" mmcblk0p1. I forgot "bs=4K". Tryed again with it, no change.
Hard reset -> nothing happens.
The same with MgfTool.
"dd" mmcblk0p3 doesn't help too.

Can you get an SSH shell in diags? If so, there are some commands to try. You can find out why it cannot finish booting from the startup messages in the logs, using the "dmesg" command (and others).

On the dd, the bs=4K just makes it run faster, but other than speed there is no difference. Where did you get the image you wrote to the main partition? Did you use SSH or a RUNME.sh script? Can you access the diags menus? Can you access your kindle as a USB drive? Can you talk to it with the fastboot program? What errors are reported in the startup logs?

Unless you have a hardware problem, one of the methods mentioned in the debricking threads has to work. We need more information to know exactly why you are having problems with your kindle.

murz_07 · 03-08-2012, 04:14 PM

Quote:

Originally Posted by geekmaster

Can you get an SSH shell in diags? If so, there are some commands to try. You can find out why it cannot finish booting from the startup messages in the logs, using the "dmesg" command (and others).

On the dd, the bs=4K just makes it run faster, but other than speed there is no difference. Where did you get the image you wrote to the main partition? Did you use SSH or a RUNME.sh script? Can you access the diags menus? Can you access your kindle as a USB drive? Can you talk to it with the fastboot program? What errors are reported in the startup logs?

Unless you have a hardware problem, one of the methods mentioned in the debricking threads has to work. We need more information to know exactly why you are having problems with your kindle.

I got image here http://gitbrew.org/~dasmoover/kindle/touch/forensic/
I used SSH, I can access diags menus, I can access Kindle as a USB device, I can talk to it with fastboot program.
I didn't understang how exactly can I get startup logs.

geekmaster · 03-08-2012, 04:19 PM

Quote:

Originally Posted by murz_07

I got image here http://gitbrew.org/~dasmoover/kindle/touch/forensic/
I used SSH, I can access diags menus, I can access Kindle as a USB device, I can talk to it with fastboot program.
I didn't understang how exactly can I get startup logs.

in SSH, type

dmesg

which will display them. These are the same messages you see if you connect to the serial port during startup. Or do:

dmesg > /mnt/us/dmesg.log

to save them to the USB drive.

murz_07 · 03-08-2012, 04:35 PM

Quote:

Originally Posted by geekmaster

in SSH, type

dmesg

which will display them. These are the same messages you see if you connect to the serial port during startup. Or do:

dmesg > /mnt/us/dmesg.log

to save them to the USB drive.

dmesg.log:

Code:

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 254500KB available (3716K code, 373K data, 1076K init, 0K highmem)
NR_IRQS:368
MXC IRQ initialized
cko2_set_rate, new divider=5
MXC_Early serial console at MMIO 0x53fbc000 (options '115200')
console [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xd0840000
CPU is i.MX50 Revision 1.1
MXC GPIO hardware
Configure EMI_CS1 for whitney
Using SDMA I.API
MXC DMA API initialized
bio: create slab <bio-0> at 0
mxc_spi mxc_spi.0: can't setup spi1.0, status -22
CSPI: mxc_spi-0 probed
CSPI: mxc_spi-1 probed
mxc_spi mxc_spi.2: chipselect 0 already in use
CSPI: mxc_spi-2 probed
MXC I2C driver
MXC I2C driver
MXC I2C driver
PMIC Light driver loading...
mc13892 Rev 2.1 FinVer 2 detected
Setting ichrg to 1
Initializing regulators for mx50 yoshi.
regulator: SW1: 600 <--> 1375 mV
regulator: SW2: 900 <--> 1850 mV
regulator: SW3: 900 <--> 1850 mV
regulator: SW4: 1100 <--> 1850 mV
regulator: SWBST: 0 mV
regulator: VIOHI: 0 mV
regulator: VPLL: 1050 <--> 1800 mV
regulator: VDIG: 1200 mV
regulator: VSD: 1800 <--> 3150 mV
regulator: VUSB2: 2400 <--> 2775 mV
regulator: VVIDEO: 2775 mV
regulator: VAUDIO: 2300 <--> 3000 mV
regulator: VCAM: 2500 <--> 3000 mV fast normal
regulator: VGEN1: 3000 mV
regulator: VGEN2: 1200 <--> 3150 mV
regulator: VGEN3: 1800 mV
regulator: VUSB: 0 mV
regulator: GPO1: 0 mV
regulator: GPO2: 0 mV
regulator: GPO3: 0 mV
regulator: GPO4: 0 mV
PMIC ADC start probe
PMIC Light successfully loaded
Device spi3.0 probed
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
Initializing MX50 Yoshi Accessory Port
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
msgmni has been set to 497
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
regulator: DISPLAY: 0 mV
regulator: GVDD: 20000 mV
regulator: GVEE: -22000 mV
regulator: VCOM: 0 <--> 2749 mV
regulator: VNEG: -15000 mV
regulator: VPOS: 15000 mV
regulator: TMST: 0 mV
papyrus 1-0048: PMIC PAPYRUS for eInk display
Amazon MX35 Yoshi Power Button Driver
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale MXC
console handover: boot [ttymxc0] -> real [ttymxc0]
mxcintuart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a Freescale MXC
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale MXC
mxcintuart.3: ttymxc3 at MMIO 0x53ff0000 (irq = 13) is a Freescale MXC
loop: module loaded
mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0
Probing mxc_rtc done
mc13892 rtc probe start
pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc1
mc13892 rtc probe succeed
i2c /dev entries driver
MXC WatchDog Driver 2.0
MXC Watchdog # 0 Timer: initial timeout 127 sec
MXC Watchdog: Started 10000 millisecond watchdog refresh
PMIC Character device: successfully loaded
pmic_battery: probe of pmic_battery.1 failed with error -1
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 273 irq 2 INTERNAL DMA
mxsdhci mxsdhci.1: dmabounce: registered device
mxsdhci: MXC SDHCI Controller Driver.
mmc1: SDHCI detect irq 0 irq 3 INTERNAL DMA
Registered led device: pmic_ledsr
Registered led device: pmic_ledsg
Registered led device: pmic_ledsb
Advanced Linux Sound Architecture Driver Version 1.0.20.
wm8962_i2c_probe
wm8962 1-001a: customer id 0 revision D
kernel: I papyrus:TempExceeded:temp=29:
input: WM8962 Beep Generator as /devices/virtual/i2c-adapter/i2c-1/1-001a/input/input0
No device for DAI imx-ssi-1-0
No device for DAI imx-ssi-1-1
No device for DAI imx-ssi-2-0
No device for DAI imx-ssi-2-1
DMA Sound Buffers Allocated:UseIram=0 buf->addr=7e360000 buf->area=f9e27000 size=131072
DMA Sound Buffers Allocated:UseIram=0 buf->addr=7e420000 buf->area=f9e47000 size=131072
asoc: WM8962 <-> imx-ssi-2-0 mapping ok
mmc0: queuing CIS tuple 0x01 length 3
mmc0: queuing CIS tuple 0x1a length 5
mmc0: queuing CIS tuple 0x1b length 8
mmc0: queuing CIS tuple 0x14 length 0
mmc0: queuing CIS tuple 0x80 length 1
mmc0: queuing CIS tuple 0x81 length 1
mmc0: queuing CIS tuple 0x82 length 1
mmc0: new high speed SDIO card at address 0001
input: imx-yoshi Headset as /devices/platform/soc-audio.1/sound/card0/input1
ALSA device list:
  #0: imx-yoshi (WM8962)
nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
kernel: I perf:kernel:kernel_loaded=0.55 seconds:
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
regulator_init_complete: disabling TMST
regulator_init_complete: disabling VCOM
regulator_init_complete: disabling GPO4
regulator_init_complete: disabling GPO3
regulator_init_complete: disabling GPO2
regulator_init_complete: disabling GPO1
regulator_init_complete: disabling VGEN3
regulator_init_complete: disabling VGEN1
regulator_init_complete: disabling VCAM
regulator_init_complete: disabling VAUDIO
regulator_init_complete: disabling VVIDEO
regulator_init_complete: disabling VSD
regulator_init_complete: disabling SWBST
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 01:23:44 UTC (5024)
Freeing init memory: 1076K
emmc: I def:mmcpartinfo:vendor=samsung, ddr=0, host=mmc1:
mmc1: new high speed MMC card at address 0001
mmcblk0: mmc1:0001 M4G1FA 3.72 GiB
 mmcblk0: p1 p2 p3 p4
mxc_epdc_fb_init_hw: 06_05_0078_3c_159221_03_3c_00000969_85.wbf
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
EXT3 FS on mmcblk0p2, internal journal
elevator: type  not found
ARC USBOTG Device Controller driver (10/08/2009)
pmic_event_subscribe: 0
USB/Charger detected
g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
g_file_storage gadget: Number of LUNs=1
fsl-usb2-udc: bind to driver g_file_storage
fuse init (API version 7.12)
PPP generic driver version 2.4.2
input: whitney-button as /devices/platform/whitney-button/input/input2
input: zforce as /devices/platform/zforce.0/input/input3
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mmcblk0p3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
wm8962_process_req
mxc_keyb: I def:drv::Keypad driver loaded
clk: Unable to get requested clock: kpp_clk
input: mxckpd as /devices/virtual/input/input4
input: mma8453 as /devices/virtual/i2c-adapter/i2c-0/0-001c/input/input5
check mma8453 chip ID
mma8453 0-001c: build time Nov  3 2011 11:21:40
add mma8453 i2c driver
EXT3 FS on mmcblk0p2, internal journal
check_portsc_bits: 0x18000205
Connected to a HIGH speed Host
g_file_storage gadget: high speed config #1
mxc_rtc: saved=0x0 boot=0x29
boot: C def:bcut:batterycut=1,version=000000:
unregistered gadget driver 'g_file_storage'
fsl-usb2-udc fsl-usb2-udc: dma_pool_destroy udc_td, fbd01000 busy
ARC USBOTG Device Controller driver unregistered
ARC USBOTG Device Controller driver (10/08/2009)
pmic_event_subscribe: 0
USB/Charger detected
usb0: MAC ee:59:00:00:00:15
usb0: HOST MAC ee:29:00:00:00:15
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
fsl-usb2-udc: bind to driver g_ether
EXT3 FS on mmcblk0p2, internal journal
check_portsc_bits: 0x18000205
Connected to a HIGH speed Host
g_ether gadget: high speed config #2: RNDIS
kernel: I papyrus:TempExceeded:temp=29:

But isn't it diags mode startup log? I think I need main mode startup log..

geekmaster · 03-08-2012, 04:52 PM

That just shows successful booting to diags. Perhaps better to do it in a RUNME.sh with no ENABLE_DIAGS, so we can see what problems main system startup has...

And be sure to edit out your Serial, PCBSN, and MAC address before posting, if they are in your log file (to prevent identity theft / unathorized amazon purchases).

murz_07 · 03-08-2012, 04:59 PM

Quote:

Originally Posted by geekmaster

That just shows successful booting to diags. Perhaps better to do it in a RUNME.sh with no ENABLE_DIAGS, so we can see what problems main system startup has...

And be sure to edit out your Serial, PCBSN, and MAC address before posting, if they are in your log file (to prevent identity theft / unathorized amazon purchases).

So I need to take your data.tar.gz from "Select boot.." thread and make RUNME.sh

Code:

dmesg > /mnt/us/logs/dmesg.log

Then send it to Kindle and do hard reset. Is it right?
Or I need another data.tar.gz?

BTW: how can I turn Kindle off complitely with SSH?

geekmaster · 03-08-2012, 05:30 PM

Quote:

Originally Posted by murz_07

So I need to take your data.tar.gz from "Select boot.." thread and make RUNME.sh

Code:

dmesg > /mnt/us/logs/dmesg.log

Then send it to Kindle and do hard reset. Is it right?
Or I need another data.tar.gz?

BTW: how can I turn Kindle off complitely with SSH?

No need to add my data.tar.gz if it has already been installed.

I do not think there is a "halt" or "shutdown -h now" command in there, but you could try. It has "reboot" but that just reboots.

You could try "idme -d --bootmode fastboot" then "reboot" to put it in fastboot mode, where it seems to charge well over a usb connection (no fastboot program needed).

P.S. your dmesg will fail if there is no "logs" folder on your USB drive. Either create one or remove it from the dmesg path.

murz_07 · 03-09-2012, 01:01 AM

Quote:

Originally Posted by geekmaster

No need to add my data.tar.gz if it has already been installed.

I do not think there is a "halt" or "shutdown -h now" command in there, but you could try. It has "reboot" but that just reboots.

You could try "idme -d --bootmode fastboot" then "reboot" to put it in fastboot mode, where it seems to charge well over a usb connection (no fastboot program needed).

P.S. your dmesg will fail if there is no "logs" folder on your USB drive. Either create one or remove it from the dmesg path.

I made RUNME.sh:

Code:

test -f /mnt/us/RUNME.done && exit
mkdir /mnt/us/logs
dmesg > /mnt/us/logs/gmesg.log
touch /mnt/us/RUNME.done

sent it to Kindle in USB device mode, hard reset and nothing. LED didn't turn on after releasing power button. I tryed MgfTool to load main u-boot, but after "Operation complited" nothing happend. So I booted in diags as USB device and there is no dmesg.log anywhere.

I added data.tar.gz and it dissapeared, but RUNME.sh didn't run.

curb · 03-09-2012, 03:41 AM

Quote:

Originally Posted by geekmaster

You can replace damaged of missing scripts in your main system boot partition, or you can replace that entire partition with a "factory original" backup copy. You can zero the /var/local partition if it was filled from indexing too many books. These things are documented in multiple places, but I recommend the "simple debricking" and "select boot" threads.

well, still questions.

i suppose the mmcblk0p1.img of 350mb is the backup, isn't it ?
then ,i should boot in diag mode, export usb, copy rumme.sh, and data.tar.gz

but, where should i put this mmcblk0p1?
copy to kindle, or to my pc, and where?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Which one Nook simple touch or Kobo mini?	capuchino71	Which one should I buy?	18	07-12-2013 05:09 PM
Sell Kindle Keyboard 3G, Nook Simple Touch	austinmitchell	Flea Market	5	03-01-2013 11:34 AM
I have some questions about K4 touch debricking	drjonvargas	Kindle Developer's Corner	4	04-22-2012 03:46 PM
kindle touch simple debricking for help	non_fox	Amazon Kindle	4	04-18-2012 08:32 PM
Troubleshooting simple kindle touch (and k4nt) debricking method	geekmaster	Amazon Kindle	0	03-02-2012 10:31 PM

03-08-2012, 12:15 PM	#46
curb Junior Member Posts: 9 Karma: 10 Join Date: Mar 2012 Device: Kindle 4 not touch	k4nt, never upgrade, Window 7 platform, unfamiliar with linux, i tried diagnose mode,copy runme.sh and data.tar.gz into kindle throug usb export, magic restart,and nothing happend. it remains what it was this morning, freeze at the tree screen, 50%. i have no idea about ssh, what do you mean by enter ssh mode?

03-08-2012, 02:33 PM	#47
murz_07 Connoisseur Posts: 67 Karma: 10 Join Date: Feb 2012 Device: Kindle Touch SO	Woohoo!!!! I recovered my Kindle after almost loosing my hope!!! Geekmaster, you are GOD!!!

03-08-2012, 03:10 PM	#50
hostar Zealot Posts: 138 Karma: 12324 Join Date: Dec 2011 Location: CZ Device: Kindle 4 non-touch	-- DELETED -- (is it possible to delete whole post?)

03-08-2012, 04:52 PM	#56
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773668 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	That just shows successful booting to diags. Perhaps better to do it in a RUNME.sh with no ENABLE_DIAGS, so we can see what problems main system startup has... And be sure to edit out your Serial, PCBSN, and MAC address before posting, if they are in your log file (to prevent identity theft / unathorized amazon purchases).

Advert

Advert