KPW2 maybe bad MMC0？

hd5062 · 08-31-2016, 10:17 AM

kpw2,4G rom,only can show first page(boy under tree) with led light.
I connection kpw2 with SecureCRT:

Please use spoiler tags for such a lengthy post - MODERATOR

Spoiler:

hd5062 · 08-31-2016, 10:20 AM

recover menu
choose:I. Initialize Partition Table (fdisk) and format FAT

Spoiler:

Dr. Drib · 08-31-2016, 12:04 PM

Moved OUT of the general Kindle Forum and INTO the Developer's Corner.

Don
(Moderator)

knc1 · 09-01-2016, 08:52 AM

Yes, you can believe that message.

Bembela · 09-05-2016, 09:20 AM

Hi guys.
I got a pile of faulty PW2 motherboards here. Most of them has uppermentioned issue. But some of them has "SE Blank Megrez" problem. If I understend well "Megrez" problem should be related to processor. I was thinking about possibility to bring at least few boards to life by combine those chips. I have to find somebody who can help me with BGA´s cause I have no BGA rework station. Do you think it is going to work if I replace NAND from "SE BLANK MEGREZ" to bad NAND device (or vice versa)? Or am I completely out? Thx for your opinions.

knc1 · 09-05-2016, 09:37 AM

No one can say without the individual test results.

The general problem is you will have to deal with the information stored in the eMMC outside of the file systems that is device specific.

We have a thread here on replacing the eMMC (with a larger capacity model).

Here you are talking about removing and then re-using BGA devices, not an easy task because the used part has to be re-balled.

Better to just buy new eMMC devices (perhaps of a larger capacity to make them more attractive on re-sale) and replace the faulty ones.

And you will still have to find a way to read-out the device specific information from the 'bad' devices so that you can transfer that information to the replacement device

Such "test jigs" do exist, since in manufacturing the eMMC is programmed before being soldered in place on the board.
But they are not cheap, nor easy to make.

Bembela · 09-06-2016, 03:10 AM

Ok.I get it.
I´ll give it a shot and let you know if I get any result. Thank you for your response!

08-31-2016, 10:17 AM	#1
hd5062 Junior Member Posts: 2 Karma: 10 Join Date: Aug 2016 Device: kindle paperwrite 2	KPW2 maybe bad MMC0？ kpw2,4G rom,only can show first page(boy under tree) with led light. I connection kpw2 with SecureCRT: Please use spoiler tags for such a lengthy post - MODERATOR Spoiler: U-Boot 2009.08-lab126 (Nov 16 2013 - 00:08:09) CPU: Freescale i.MX6 family TO0.0 at 996 MHz Temperature: 45 C, calibration data 0x5915125f 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 Boot Reason: [ POR ] Boot Device: NAND Board Id: 02722011345600A1 S/N: 905A220634860EDP I2C: ready DRAM: 256 MB Using default environment In: serial Out: serial Err: serial Quick Memory Test 0x80000000, 0xfff0000 POST done in 60 ms Battery voltage: 3831 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: 2425788 Bytes = 2.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... [ 0.095304] boot: C def:bcut:batterycut=1 [ 0.268186] LPDDR2 MfgId: 0x1 [Samsung] 3.0.35-lab126 #1 Sat Nov 16 00:25:44 PST 2013 armv7l Press [ENTER] for recovery menu... 0 //dev/mmcblk0p4: CHS=4/16/104512 size=3424649216 bytes flag type first last lba first lba size Partition p1: 0x00 0x0b 16 <large> 16 6688752 CHS: 0/1/1 - <large> Partition p2: Partition p3: Partition p4: BOOTING DEFAULT. IP-Config: no devices to configure kinit: Mounted root (ext3 filesystem) readonly. info sytem:mounted_proc:: info system:mounted_sys:: info system:mounted_dev:: info milestone:6.77:49.1: info milestone:6.83:49.2: info milestone:6.85:49.3: info milestone:6.89:49.4: info milestone:6.92:49.5: info sytem:mounted_tmpfs:: info milestone:6.98:sy50: info system:start:time=7010: info hardware:no_wan::WiFi only device. No WAN found info system:configlatform=wario,board=pinot,rev=34,pr oto=Y,wifi=Y,wan=N: info milestone:7.19:sy51: lipc-send-event[817]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) lipc-send-event[814]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) lipc-send-event[817]: C def:dbusi::Failed to init dbus lipc-send-event[814]: C def:dbusi::Failed to init dbus lipc-send-event[817]: E defpen::Failed to open LIPC lipc-send-event[814]: E defpen::Failed to open LIPC lipc-send-event[817]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed lipc-send-event[814]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed info milestone:8.17:sy99: info system:done:time=8210: init.exe: Faileto spawn sshd macrond[849]: crond: crond (busybox 1.17.1) started, log level 8 init.exe: recevent pre-start process (852) terminated with status 1 info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesystem images: warn system_cramfs_loopbacks:mountpointmissing:Image /lib/firmware/cyttsp.cramfs.img not mounted, non existing mounting point: info system_cramfs_loopbacks:mounted:Image /usr/share/X11/xkb.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/java/lib/fonts.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /etc/kdb.src.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/lib/locale.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/share/keyboard.cramfs.img mounted: info system:emiting_event:mounted_cramfs_loopbacks: debug sytem:event_emitted:mounted_cramfs_loopbacks: info milestone:8.90:fs75: info system:emiting_event:loaded_modules_dependencies: debug sytem:event_emitted:loaded_modules_dependencies: info modules:modprobe:loading module g_file_storage: info system:emiting_event:loaded_g_file_storage: debug sytem:event_emitted:loaded_g_file_storage: info modules:modprobe:loading module fuse: info system:emiting_event:loaded_fuse: debug sytem:event_emitted:loaded_fuse: info hardware:no_wan::WiFi only device. No WAN found info system:emiting_event:loaded_ppp_async: info milestone:9.13:fs00: debug sytem:event_emitted:loaded_ppp_async: info system:emiting_event:loaded_fakekey: debug sytem:event_emitted:loaded_fakekey: [ 14.643332] mmcblk0: error -110 transferring data, sector 963090, nr 4, cmd response 0x900, card status 0xd00 [ 14.653332] end_request: I/O error, dev mmcblk0, sector 963090 [ 14.659193] Buffer I/O error on device mmcblk0p3, logical block 24841 [ 14.666593] end_request: I/O error, dev mmcblk0, sector 963092 [ 14.672446] Buffer I/O error on device mmcblk0p3, logical block 24842 [ 240.149610] INFO: task mount:988 blocked for more than 120 seconds. [ 240.155882] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 360.159606] INFO: task mount:988 blocked for more than 120 seconds. [ 360.165880] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 480.169621] INFO: task mount:988 blocked for more than 120 seconds. [ 480.175894] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 480.184276] INFO: task sh:996 blocked for more than 120 seconds. [ 480.190296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 480.198557] INFO: task sh:997 blocked for more than 120 seconds. [ 480.204575] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 600.209617] INFO: task mount:988 blocked for more than 120 seconds. [ 600.215890] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 600.224269] INFO: task sh:996 blocked for more than 120 seconds. [ 600.230288] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 600.238543] INFO: task sh:997 blocked for more than 120 seconds. [ 600.244561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Last edited by Dr. Drib; 08-31-2016 at 10:27 AM.

08-31-2016, 10:20 AM	#2
hd5062 Junior Member Posts: 2 Karma: 10 Join Date: Aug 2016 Device: kindle paperwrite 2	recover menu choose:I. Initialize Partition Table (fdisk) and format FAT Spoiler: =========================== U-Boot 2009.08-lab126 (Nov 16 2013 - 00:08:09) CPU: Freescale i.MX6 family TO0.0 at 996 MHz Temperature: 47 C, calibration data 0x5915125f 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 Boot Reason: [ POR ] Boot Device: NAND Board Id: 02722011345600A1 S/N: 905A220634860EDP I2C: ready DRAM: 256 MB Using default environment In: serial Out: serial Err: serial Quick Memory Test 0x80000000, 0xfff0000 POST done in 60 ms Battery voltage: 3819 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: 2425788 Bytes = 2.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... [ 0.095348] boot: C def:bcut:batterycut=1 [ 0.268229] LPDDR2 MfgId: 0x1 [Samsung] 3.0.35-lab126 #1 Sat Nov 16 00:25:44 PST 2013 armv7l Press [ENTER] for recovery menu... 0 /Charge: 14% [#########::::::::::::::::::::::::::::::::::::::::: ::::::::] Menu ==== 3. Load MMC0 over USB storage 4. Erase MMC0 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: 3 \| Unknown option '3' Charge: 14% [#########::::::::::::::::::::::::::::::::::::::::: ::::::::] Menu ==== 3. Load MMC0 over USB storage 4. Erase MMC0 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: 5 -i /dev/mmcblk0: CHS=4/16/120832 size=3959422976 bytes flag type first last lba first lba size Partition p1: 0x80 0x83 <large> <large> 65536 716800 CHS: <large> - <large> Partition p2: 0x00 0x83 <large> <large> 782336 131072 CHS: <large> - <large> Partition p3: 0x00 0x83 <large> <large> 913408 131072 CHS: <large> - <large> Partition p4: 0x00 0x0b <large> <large> 1044480 6688768 CHS: <large> - <large> Rereading partition information ... [ 25.487349] mmcblk0: error -110 transferring data, sector 65536, nr 64, cmd response 0x900, card status 0xd00 [ 25.497340] end_request: I/O error, dev mmcblk0, sector 65536 [ 25.503109] Buffer I/O error on device mmcblk0, logical block 8192 [ 25.510248] end_request: I/O error, dev mmcblk0, sector 65544 [ 25.516015] Buffer I/O error on device mmcblk0, logical block 8193 [ 25.523058] end_request: I/O error, dev mmcblk0, sector 65552 [ 25.528822] Buffer I/O error on device mmcblk0, logical block 8194 [ 25.535850] end_request: I/O error, dev mmcblk0, sector 65560 [ 25.541614] Buffer I/O error on device mmcblk0, logical block 8195 [ 25.548642] end_request: I/O error, dev mmcblk0, sector 65568 [ 25.554404] Buffer I/O error on device mmcblk0, logical block 8196 [ 25.561433] end_request: I/O error, dev mmcblk0, sector 65576 [ 25.567196] Buffer I/O error on device mmcblk0, logical block 8197 [ 25.574218] end_request: I/O error, dev mmcblk0, sector 65584 [ 25.579981] Buffer I/O error on device mmcblk0, logical block 8198 [ 25.586997] end_request: I/O error, dev mmcblk0, sector 65592 [ 25.592759] Buffer I/O error on device mmcblk0, logical block 8199 Last edited by Dr. Drib; 08-31-2016 at 10:28 AM.

09-05-2016, 09:37 AM	#6
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	No one can say without the individual test results. The general problem is you will have to deal with the information stored in the eMMC outside of the file systems that is device specific. We have a thread here on replacing the eMMC (with a larger capacity model). Here you are talking about removing and then re-using BGA devices, not an easy task because the used part has to be re-balled. Better to just buy new eMMC devices (perhaps of a larger capacity to make them more attractive on re-sale) and replace the faulty ones. And you will still have to find a way to read-out the device specific information from the 'bad' devices so that you can transfer that information to the replacement device Such "test jigs" do exist, since in manufacturing the eMMC is programmed before being soldered in place on the board. But they are not cheap, nor easy to make. Last edited by knc1; 09-05-2016 at 09:46 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to unbrick my Kindle？	yuwang	Kindle Developer's Corner	10	09-26-2015 08:40 PM
[HELP] Erased mmc0 accidentally, is there a way to debrick it?	whlweb	Kindle Developer's Corner	7	12-27-2014 01:28 PM
Debrick a K3 (mmc0 cleared without backup)	tthsn	Kindle Developer's Corner	13	02-17-2014 09:04 PM
Bad mmc0 ?	Pumpa	Kindle Developer's Corner	1	07-25-2012 10:23 AM
scanned PDF？？？？？	xtdn20008	enTourage eDGe	6	06-18-2011 01:48 PM

08-31-2016, 12:04 PM	#3
Dr. Drib Grand Sorcerer Posts: 45,437 Karma: 59592133 Join Date: Jan 2007 Location: Peru Device: KINDLE: Oasis 3, Scribe (1st), Matcha; KOBO: Libra 2, Libra Colour	Moved OUT of the general Kindle Forum and INTO the Developer's Corner. Don (Moderator)

09-01-2016, 08:52 AM	#4
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Yes, you can believe that message.

09-05-2016, 09:20 AM	#5
Bembela Member Posts: 10 Karma: 14 Join Date: Aug 2012 Device: None	Hi guys. I got a pile of faulty PW2 motherboards here. Most of them has uppermentioned issue. But some of them has "SE Blank Megrez" problem. If I understend well "Megrez" problem should be related to processor. I was thinking about possibility to bring at least few boards to life by combine those chips. I have to find somebody who can help me with BGA´s cause I have no BGA rework station. Do you think it is going to work if I replace NAND from "SE BLANK MEGREZ" to bad NAND device (or vice versa)? Or am I completely out? Thx for your opinions.

09-06-2016, 03:10 AM	#7
Bembela Member Posts: 10 Karma: 14 Join Date: Aug 2012 Device: None	Ok.I get it. I´ll give it a shot and let you know if I get any result. Thank you for your response!

Advert

Advert