View Single Post
Old 12-13-2022, 02:14 AM   #563
MllwAlms
Junior Member
MllwAlms began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Dec 2022
Device: Paperwhite 7th Gen
Same Issue here

Quote:
Originally Posted by wilcomir View Post
Hello, I am trying to apply this metod to a PW2, firmware version is 5.15.1

Serial is working fine, but when I try to boot to diagnostics mode via
Code:
bootm 0xE41000
this is what I get:

Code:
uboot > bootm 0xE41000
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2634932 Bytes =  2.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.098642] boot: C def:bcut:batterycut=1
[    0.286352] LPDDR2 MfgId: 0x3 [Elpida]
[    0.290128]
[    0.290131] just text: vaddr c0150d44, va 0xc0150200 pa 0x801000c3 attr 0x6
[    0.302706]
[    0.302709] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.311559]
[    0.311562] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.319897]
[    0.319900] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.330739]
[    0.330742] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.345093]
[    0.345096] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.357240]
[    0.357244] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.367647]
[    0.367650] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.377551]
[    0.377554] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Mon Jun 1 23:54:30 PDT 2015 armv7l
Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    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.
kinit: init not found!
Is there anyone who knows what the issue could be?

Thanks!
V
I'm having the exact same issue. From what I've found, all signs point to bad emmc. In recovery, using bist and then mmcinfo, I received the following message.

Quote:
Card did not respond to voltage select!
Device: FSL_ESDHC
Manufacturer ID: 0
OEM: 0
Name: Revision: 0x0
Tran Speed: 0
Rd Block Len: 0
MMC version 0.0
High Capacity: No
Capacity: 0
Bus Width: 1-bit
Current Partition for boot: Not bootable
Current boot width: 1-bit SDR
According to this thread, this signifies the bad emmc. My device still functions fine and reboots. Is this really bad emmc? I'm wondering if fw 5.12.2 is causing this.

Last edited by MllwAlms; 12-13-2022 at 02:19 AM.
MllwAlms is offline   Reply With Quote