Kindle PW2 error says Battery Invalid: -22

[adonis]

Originally Posted by knc1

Sorry, Monday was a very bad day for me.

No problem ;-)
Same here, but today I had more luck, at least I hope so.
I flashed kernel and main image this time over kindle prompt not with fastboot, now it seems to work. I restarted my kindle to test if it's auto updating itself, but it did not.

Thank you so much knc1. You helped me a lot ;-)

[adonis]

Here is a summary how to solve the "BATTERY INVALID: -22" problem.

What I did:
- Overwrite the diags-images via fastboot
- Overwrite the main-images via USB

What you need:
CP2102 USB to TTL converter. I've got this one: http://www.amazon.de/USB-TTL-Konvert...FU/ref=sr_1_1?
Kindle images: http://ixtab.tk/kindle-touch-images/PW2/
Fastboot for kindle:

Fastboot for kindle:
Here you'll find some instructions how to get fastboot for kindle working on Windows or OS X.

OS X: https://github.com/TobiasWooldridge/Fastboot-Kindle
Windows: http://www.mediafire.com/view/?xrn3v3ln6cn2n75

Prepare your kindle:
1. Solder wires to the kindle serial pins. https://www.mobileread.com/forums/sho...25&postcount=3
2. Get a CP2102 USB to TTL converter. I've got this one: http://www.amazon.de/USB-TTL-Konvert...eywords=cp2102
3. Connect the soldered wires to the CP2102
4. Plug the USB into a USB 2.0 of your computer. *Don't use USB 3.0*

Overwrite diags-images:
I don't know if this is neccessary, but if you can't get your kindle into USB-mode, you should definitely do it

1. Connect with a terminal via serial to the TTL adapter.
2. Reboot your kindle and continuously hit ESC on your keyboard until you enter uboot on your kindle.
3. In uboot run "bist fastboot" and press enter
4. In a new terminal window navigate to the fastboot-executible on your computer (OS X or Windows and run "./fastboot devices", if you don't see anything, you haven't installed fastboot correctly.
5. If you see a device you can run

./fastboot flash diags mmcblk02p.bin
./fastboot flash diags_kernel diags_kernel.bin

Overwrite main-images:
1. Establish a serial connection to your kindle, because you will need it in the last step.
2. Reboot your kindle into diags mode. There are several ways how to do this.
If you're already in fastboot you can do this on your computers terminal

./fastboot setvar bootmode diags
./fastboot reboot

The other is via serial in uboot.

bist
idme bootmode diags
reset

3. When your kindle boots up in diags mode, hit "U" for USB device mode. Now your kindle should show up as a USB storage.

4. Copy mmcblk01p.img and main_kernel.bin into the root folder of your kindle.
5. Now hit "D" to go to "Exit, Reboot or Disable Diags" and there hit "L" to enter the login prompt.
6. You should be able to login as "root" with "mario" as password
7. Run these commands to flash the main images

A) if the partition image is gzipped (ends with .gz):

zcat /mnt/us/mmcblk01p.img.gz | dd of=/dev/mmcblk0p1 bs=4096

B) if the partition image is NOT gzipped:

 dd if=/mnt/us/mmcblk01p.img of=/dev/mmcblk0p1 bs=4096

8. Run these commands to flash the main kernel
A) if the kernel image is gzipped (ends with .gz):

zcat /mnt/us/kernel_main.bin.gz | dd of=/dev/mmcblk0 bs=4096 seek=65

B) if the kernel image is NOT gzipped:

dd if=/mnt/us/kernel_main.bin of=/dev/mmcblk0 bs=4096 seek=65

9. Set the bootmode back to main

idme -d --bootmode main

10. Reboot your kindle

reboot

Your kindle should now be fixed and should start normally.

[geekmaster]

As I recall, fastboot does not report errors when flashing, even if it is a large image like mmcblk0p1. The only way to know it failed is if it reports "success" too early. We learned from experience that the large main partition needs to be written with 'dd' from diags, but even since then I have seen it done by official amazon firmware update scripts as well.

You cannot trust fastboot (at least not the kindle versions) to report errors.

Your repair instructions are pretty standard, as we described in the "simple debricking" thread, except it appears you did a serial port login from diags instead of a usbnetworking login (which required flashing a diags partition that had usbnetworking added back into it, such as the images from ixtab that are also in the kubrick distros.

Congratulations on your debricking success. I think your "battery" problem may have been due to corrupt firmware (only partly-flashed with fastboot), or other firmware corruption. The important think is that it works now...

[bingofuel]

I did what Adonis said but now I can't enter anymore in the diags mode. The kernel hang up with


[ 2.547807] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[ 2.607084] mmc0: unrecognised EXT_CSD revision 7
[ 2.611812] mmc0: error -22 whilst initialising MMC card
[ 3.525155] KERNEL: I pmic:fg battery id check::wario_battery_valid=1

Perhaps the memory of the kindle is damaged?

[knc1]

Originally Posted by bingofuel

I did what Adonis said but now I can't enter anymore in the diags mode. The kernel hang up with


[ 2.547807] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[ 2.607084] mmc0: unrecognised EXT_CSD revision 7
[ 2.611812] mmc0: error -22 whilst initialising MMC card
[ 3.525155] KERNEL: I pmic:fg battery id check::wario_battery_valid=1

Perhaps the memory of the kindle is damaged?

Adonis has multiple posts in this thread - please post a link.
or at least some clue as to which post(s) you mean by: "Adonis said".

[bingofuel]

There is only one post that give a series of instructionts that solves the problem. Since, apparently, I was not clear enough,
I am talking about the post number 17 of this thread https://www.mobileread.com/forums/sh...1&postcount=17

[knc1]

Originally Posted by bingofuel

There is only one post that give a series of instructionts that solves the problem. Since, apparently, I was not clear enough,
I am talking about the post number 17 of this thread https://www.mobileread.com/forums/sh...1&postcount=17

Not only that, but you did not post enough of the boot-time message content to make even an educated guess of the answer to your question.

The people here are pretty good at what they do, but ...
We can not see over your shoulder ...
None of us can channel into your mind ...
So we are limited to forming our answers based on what you post.

If you received an "invalid battery" message, then your battery is most likely invalid.
Put in a new, official Amazon, battery and try again.

[bingofuel]

Of course I have bought a new battery and it didn't work. And of course I know that in this forum there are pople who knows a lot a try to help others, Adonis for example. But your superiority tone I don't think it helps.

If I am writing here and I soldered wires to the kindle in order to get serial access to the device, of course I have tried the others solutions I found online. I asked a question in order to recieve a feedback about what other information should I give.

Perhaps someone has the same problem, perhaps I made a mistake. I was asking trying to understand.

Your "what are you talking about?" and your "buy a new battery" answers look like a way to reinforce your ego in an forum, that in addition it is anonymous.

P.S.: knc1 relax. Tomorrow I'm going to buy a new one. You don't have to worry anymore

[Cinisajoy]

Originally Posted by bingofuel

Of course I have bought a new battery and it didn't work. And of course I know that in this forum there are pople who knows a lot a try to help others, Adonis for example. But your superiority tone I don't think it helps.

If I am writing here and I soldered wires to the kindle in order to get serial access to the device, of course I have tried the others solutions I found online. I asked a question in order to recieve a feedback about what other information should I give.

Perhaps someone has the same problem, perhaps I made a mistake. I was asking trying to understand.

Your "what are you talking about?" and your "buy a new battery" answers look like a way to reinforce your ego in an forum, that in addition it is anonymous.

P.S.: knc1 relax. Tomorrow I'm going to buy a new one. You don't have to worry anymore

Please do not tell knc1 to relax. That gets my blood pressure up.
In your first post, you did not give anything other than invalid battery and someone said.
Without a link how am I supposed to know what the heck you are talking about.
Why should I take my unpaid time to look up every one of someone's posts because you need help?
This is a development forum. This means we don't have the time to try and figure out what you did or didn't do. Next time you need help in any development forum, give complete steps to what you did.
Oh and by the way on a battery if you connect it backwards, it makes a pretty arc.

We are not mind readers nor can we see into your device.

Note knc1 has been working on electronics since before man landed on the moon.

[knc1]

Originally Posted by bingofuel

- - - -
P.S.: knc1 relax. Tomorrow I'm going to buy a new one. You don't have to worry anymore

Who? What? Me Worry?
You have mistaken me for someone else.


And yes IzzyBird it is less than 600x600
@cinisajoy: As long as GM has built Corvettes (introduced: Jan 17, 1953).

In March, President Eisenhower offered increased aid in Vietnam to France.
Those recognizing the 50th anniversary of the Tet Offensive this month know how that worked out.
(Yes, I was there at the time.)

[adonis]

Hey guys... just got a notification email on the threads revival

First of all I'd like to say that the biggest mistake one can make on this forum is to tell *knc1* to calm himself down.

Since this thread has only 2 pages and most of the debugging stuff is discussed on the first page, one can clearly see, that without knc1's help I wouldn't have gotten very far.

I basically provided him with as much information as he needed to help me. At the end I wrote a summary that worked for me, hoping that it's going to help everyone else having the same problem.

Secondly, and back to the problem. Unfortunately, I'm not that experienced to provide help here. But from a beginners point of view, I can provide two very important suggestions here:

1. Focus: Read instructions carefully word by word. If something in an instruction is not clear - feel free to ask
2. Repeat: Don't assume, if you follow instructions, that it's gonna work for the first time. Even if you're sure, that you followed them correctly. There's always a chance that you missed something. Try again, and again... and every time with more and more focus on the instructions
3. Trial & Error: feel free to try out some logical steps, even if they're not provided in the instructions. Re-plug the device, Re-start it in between of steps ... etc.

If you're 100% sure that you did exactly what was provided and it doesn't work as expected, feel free to ask. Tell the community exactly where your problem is. I know it's hard, because the one who asks often assumes that the others who help know what one is talking about. But it's never like that.

PS: I ended up throwing the broken kindle into my spare-parts storage and bought a new one. But I still had fun fiddling around :P

Cheers,
Adis

[javimixet]

Wow!!! Thank you very much!!!!
It is ALIVE!!!!

Bought a used Paperwhite for 50€ with loose charging port. Charged it, connected to wifi to download my kindle books (I think it made an automatic update) turn it off and tear it apart to see what the problem was with the micro-usb. It was rusty inside, maybe put by error in washing machine. Usb pins was rusty and with a whiteish, don't know if soap of some kind of rust, matter. Cleaned it with soft brush and tested the pins, +5 was failing. Resoldered it and turned on: BATTERY INVALID: -22

Turned out I had some problems with fastboot because the +5 was not properly soldered. Once this was done the instructions in this thread went smooth as silk... even with the name and extension of the downloaded images varying a bit.

So, don't know if it was the usb problem or the update that caused the mess... reading *adonis* seems the update is the culprit. And I understand that I have to do nothing else to avoid autoupdating. Is that correct?

Thanks, thanks, THANKS!!!

[stmusic]

I wipe off boot for kindle pw 3, on putty menu u put to format memory (options 1 or 2 not remember) how to back boot ?

U-Boot 2009.08-lab126 (Oct 24 2017 - 12:16:03)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   39 C, calibration data 0x57a5025f
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: Muscat WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 0670209152240419
S/N: G090G105522507V5
I2C:   ready
DRAM:  512 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0x1fff0000
POST done in 111 ms
BOOTMODE OVERRIDE: DIAGS
Battery voltage: 3778 mV

Hit any key to stop autoboot:  0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot >

[knc1]

Please do not double post.
Read my reply in the other thread you posted this question too.

Best that you start your own thread for your PW3 problems, rather than post in threads marked PW2.

[Techtype]

Hi, I hope this thread isn't too old to even get a reply to this.

I have a very similar issue to the one described by bingofuel in post #19 on this thread. I have followed Adonis's guide in post #17 aswell.

I originally had a "BATTERY INVALID -22" error, replacing the battery also did not fix this.

I got the diags_kernel.img and mmcblk0p1.bin files from this thread's post #4: https://www.mobileread.com/forums/sh...d.php?t=348137

After flashing the diags_kernel.img and mmcblk0p1.bin via fastboot and rebooting, now the kindle won't even boot to the error screen in either diags or main bootmode.

This is the full log of booting in diags mode:

U-Boot 2009.08-lab126 (Mar 02 2021 - 17:14:13)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   30 C, calibration data 0x59c5205f
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: 0272201145060JKR
S/N: 9017220145240BC8
I2C:   ready
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0xfff0000
POST done in 57 ms
BOOTMODE OVERRIDE: DIAGS
Battery voltage: 4030 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:    2420496 Bytes =  2.3 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Linux version 3.0.35-lab126 (jenkins-official@jbuild01) (collect2: ld returned 1 exit status) #1 Tue Sep 3 03:12:16 PDT 2013
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Freescale i.MX 6SoloLite based Wario Board
[    0.000000] Ignoring unrecognised tag 0x54410011
[    0.000000] Will try to place printk log at 8fffc000
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU identified as i.MX6SoloLite, silicon rev 1.2
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c04dcc94, node_mem_map c2000000
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 8128 pages, LIFO batch:0
[    0.000000]   Normal zone: 448 pages used for memmap
[    0.000000]   Normal zone: 56896 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p2 ro ip=off debug video=mxcepdcfb:E60,bpp=8,x_mem=3M
[    0.000000] Prink buffer will be relocated to physical address: 8fff2000
[    0.000000] log_buf_len: 32768
[    0.000000] early log buf free: 31293(95%)
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 254652k/254652k available, 7492k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xfde00000 - 0xffe00000   (  32 MB)
[    0.000000]     vmalloc : 0xd0800000 - 0xf2000000   ( 536 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .init : 0xc0008000 - 0xc010b000   (1036 kB)
[    0.000000]       .text : 0xc010b000 - 0xc04aa000   (3708 kB)
[    0.000000]       .data : 0xc04aa000 - 0xc04dd7c0   ( 206 kB)
[    0.000000]        .bss : 0xc04dd7e4 - 0xc0504540   ( 156 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:624
[    0.000000] MXC GPIO hardware
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] arm_max_freq=1GHz
[    0.000000] MXC_Early serial console at MMIO 0x2020000 (options '115200')
[    0.000000] bootconsole [ttymxc0] enabled
[    0.000000] Console: colour dummy device 80x30
[    0.263046] Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896)
[    0.321375] pid_max: default: 32768 minimum: 301
[    0.326254] Mount-cache hash table entries: 512
[    0.331165] CPU: Testing write buffer coherency: ok
[    0.336192] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.351148] print_constraints: dummy:
[    0.355099] NET: Registered protocol family 16
[    0.363367] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
[    0.370945] print_constraints: vddcore: 725 <--> 1300 mV at 1475 mV fast normal
[    0.378644] print_constraints: vddsoc: 725 <--> 1300 mV at 1475 mV fast normal
[    0.386310] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
[    0.394042] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
[    0.401720] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
[    0.410616] LAB126 Board id - 0272201145060JKR
[    0.419152] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.425994] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
[    0.433329] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.439201] L310 cache controller enabled
[    0.443226] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B
[    0.459497] bio: create slab <bio-0> at 0
[    0.467123] max77696> regulator init
[    0.471603] spi_imx imx6q-ecspi.0: probed
[    0.476188] usbcore: registered new interface driver usbfs
[    0.481797] usbcore: registered new interface driver hub
[    0.487303] usbcore: registered new device driver usb
[    0.494441] Reboot Reason - Standard Reporting
[    0.498917] kernel: I max77696-irq:evtrcrd: evt=MR_FRSTRT: Manual Reset Full Restart
[    0.506680] Reboot Reason - Metric Framework Reporting
[    0.511838] kernel: kernel_metric_generic,counter,event_recorder,ercflags,MR_FRSTRT,1,
[    0.519774] Reboot Reason - Legacy Metric Reporting
[    0.524666] boot: C def:bcut:batterycut=1
[    0.530287] MAX77696 TOPSYS 1.0.0 Installed
[    0.537152] max77696-gpio max77696-gpio.0: gpio#0 -- -- func-0 in
[    0.544628] max77696-gpio max77696-gpio.0: gpio#1 -- -- func--1 in
[    0.552403] max77696-gpio max77696-gpio.0: gpio#3 -- -- func-0 in
[    0.560441] MAX77696 GPIO Driver 1.0.0 Installed
[    0.566143] buck mode: 4
[    0.569416] buck mode: 4
[    0.572889] print_constraints: max77696_buck1: 900 <--> 1300 mV at 1250 mV fast normal idle standby
[    0.582526] buck mode: 4
[    0.586005] print_constraints: max77696_buck1dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
[    0.595805] buck mode: 4
[    0.599074] buck mode: 4
[    0.602546] print_constraints: max77696_buck2: 900 <--> 1300 mV at 1200 mV fast normal idle standby
[    0.612157] buck mode: 4
[    0.615633] print_constraints: max77696_buck2dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
[    0.625422] print_constraints: max77696_buck3: 600 <--> 3387 mV at 1300 mV fast normal idle standby
[    0.635208] buck mode: 4
[    0.638478] buck mode: 4
[    0.641745] print_constraints: max77696_buck4: 1200 mV fast normal idle standby
[    0.649597] buck mode: 4
[    0.653074] print_constraints: max77696_buck5: 600 <--> 3387 mV at 1800 mV fast normal idle standby
[    0.662689] buck mode: 4
[    0.666166] print_constraints: max77696_buck6: 600 <--> 3387 mV at 3200 mV fast normal idle standby
[    0.675276] MAX77696 Buck Regulators Driver 1.0.1 Installed
[    0.681638] print_constraints: max77696_ldo1: 800 <--> 3950 mV at 3300 mV normal idle standby
[    0.690769] print_constraints: max77696_ldo2: 800 <--> 3950 mV at 3000 mV normal idle standby
[    0.699852] print_constraints: max77696_ldo3: 800 <--> 3950 mV at 2500 mV normal idle standby
[    0.708963] print_constraints: max77696_ldo4: 800 <--> 2375 mV at 1800 mV normal idle standby
[    0.718028] print_constraints: max77696_ldo5: 800 <--> 2375 mV at 1800 mV normal idle standby
[    0.727147] print_constraints: max77696_ldo6: 800 <--> 3950 mV at 3200 mV normal idle standby
[    0.736229] print_constraints: max77696_ldo7: 800 <--> 3950 mV at 3200 mV normal idle standby
[    0.745336] print_constraints: max77696_ldo8: 800 <--> 2375 mV at 1100 mV normal idle standby
[    0.754409] print_constraints: max77696_ldo9: 800 <--> 2375 mV at 1100 mV normal idle standby
[    0.763541] print_constraints: max77696_ldo10: 2400 <--> 5550 mV at 5200 mV normal idle standby
[    0.773069] MAX77696 Linear Regulators Driver 1.0.2 Installed
[    0.779422] print_constraints: max77696_lsw1:
[    0.784234] print_constraints: max77696_lsw2:
[    0.788987] print_constraints: max77696_lsw3:
[    0.793728] print_constraints: max77696_lsw4:
[    0.798234] MAX77696 Load Switches Driver 1.0.0 Installed
[    0.804860] print_constraints: max77696-display:
[    0.810344] print_constraints: max77696-vcom:
[    0.815123] print_constraints: max77696-vee:
[    0.819843] print_constraints: max77696-vneg:
[    0.824624] print_constraints: max77696-vpos:
[    0.829381] print_constraints: max77696-vddh:
[    0.834871]
[    0.834874] EPD vreg probe complete!
[    0.840526] print_constraints: max77696_vddq: 240 <--> 984 mV at 600 mV
[    0.847306] MAX77696 LPDDR2 Termination Supply Driver 1.0.1 Installed
[    0.855031] MAX77696 I2C Driver 1.0.0 Installed
[    0.862102] i2c-core: driver [max17135] using legacy suspend method
[    0.868390] i2c-core: driver [max17135] using legacy resume method
[    0.874636] Switching to clocksource mxc_timer1
[    0.889691] NET: Registered protocol family 2
[    0.894149] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.901245] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.908417] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.914950] TCP: Hash tables configured (established 8192 bind 8192)
[    0.921328] TCP reno registered
[    0.924480] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.930343] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.936962] NET: Registered protocol family 1
[    0.941683] RPC: Registered named UNIX socket transport module.
[    0.947621] RPC: Registered udp transport module.
[    0.952359] RPC: Registered tcp transport module.
[    0.957075] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.967760] etb: probe of etb failed with error -2
[    0.972808] etm: probe of etm.0 failed with error -2
[    0.978041] Static Power Management for Freescale i.MX6
[    0.983303] wait mode is enabled for i.MX6
[    0.987589] cpaddr = d0820000 suspend_iram_base=d081c000
[    0.992977] PM driver module loaded
[    0.996732] IMX usb wakeup probe
[    1.000004] the wakeup pdata is 0xce1387c0
[    1.004444] IMX usb wakeup probe
[    1.007692] the wakeup pdata is 0xce1388c0
[    1.012001] cpu regulator mode:ldo_bypass
[    1.016224] _regulator_get: get() with no identifier
[    1.021217] mx6_cpu_regulator_init: failed to get pu regulator
[    1.027263] i.MXC CPU frequency driver
[    1.044109] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.051153] msgmni has been set to 497
[    1.055266] io scheduler noop registered
[    1.059305] io scheduler cfq registered (default)
[    1.064513] MAX77696 Backlight Driver 1.0.0 Installed
[    1.070359] imx-sdma imx-sdma: loaded firmware 1.1
[    1.079737] imx-sdma imx-sdma: initialized
[    1.254128] Serial: IMX driver
[    1.386282] console [ttymxc0] enabled, bootconsole disabled
[    1.386282] console [ttymxc0] enabled, bootconsole disabled
[    1.401790] loop: module loaded
[    1.405001] MAX77696 32kHz Oscillator Driver 1.0.0 Installed
[    1.411319] input: max77696-onkey as /devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-onkey.0/input/input0
[    1.424515] MAX77696 ONKEY Driver 1.0.0 Installed
[    1.450584] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.0 as rtc0
[    1.470543] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.1 as rtc1
[    1.499851] MAX77696 RTC Driver 1.0.2 Installed
[    1.505263] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc2
[    1.511998] i2c /dev entries driver
[    1.519882] max77696-battery max77696-battery.0: Voltage alert     3400mV ... 4260mV
[    1.528032] max77696-battery max77696-battery.0: SOC alert         (disabled)
[    1.536081] MAX77696 Fuel Gauge Driver 1.0.0 Installed
[    1.542954] MAX77696 USB Interface Circuit Driver 1.0.0 Installed
[    1.550768] max77696-adc max77696-adc.0: ADC average rate: 32 sample(s)
[    1.557388] max77696-adc max77696-adc.0: ADC delay: 0 nsec
[    1.562893] max77696-adc max77696-adc.0: ADC cur src: 50 uA
[    1.568469] MAX77696 ADC Driver 1.0.1 Installed
[    1.573683] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
[    1.582103] sdhci: Secure Digital Host Controller Interface driver
[    1.588287] sdhci: Copyright(c) Pierre Ossman
[    1.592770] mmc0: no vmmc regulator found
[    1.598089] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA
[    1.606225] mmc1: no vmmc regulator found
[    1.612627] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
[    1.620389] Registered led device: max77696-leds.0
[    1.625189] MAX77696 LED Driver #0 1.0.0 Installed
[    1.634272] Registered led device: max77696-leds.1
[    1.639070] MAX77696 LED Driver #1 1.0.0 Installed
[    1.644402] nf_conntrack version 0.5.0 (3978 buckets, 15912 max)
[    1.653123] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.658496] TCP cubic registered
[    1.661752] NET: Registered protocol family 17
[    1.666213] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    1.674019] LPDDR2 MfgId: 0x1 [Samsung]
[    1.678159] Bus freq driver module loaded
[    1.684207] Bus freq driver Enabled
[    1.688683] mxc_dvfs_core_probe
[    1.695130] max77696-adc max77696-adc.0: adc conversion timed out
[    1.702388] DVFS driver module loaded
[    1.725288] regulator_init_complete: max77696_ldo10: incomplete constraints, leaving on
[    1.740557] regulator_init_complete: max77696_ldo7: incomplete constraints, leaving on
[    1.750735] regulator_init_complete: max77696_ldo6: incomplete constraints, leaving on
[    1.769954] max77696-adc max77696-adc.0: adc conversion timed out
[    1.777476]
[    1.777479] ADC value out of thermistor range! setting display temp to 43 deg C
[    1.787331] regulator_init_complete: max77696_buck6: incomplete constraints, leaving on
[    1.795583] regulator_init_complete: max77696_buck5: incomplete constraints, leaving on
[    1.804060] regulator_init_complete: max77696_buck2dvs: incomplete constraints, leaving on
[    1.812410] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    1.818424] regulator_init_complete: max77696_buck1dvs: incomplete constraints, leaving on
[    1.841156] mmc0: unrecognised EXT_CSD revision 7
[    1.845868] mmc0: error -22 whilst initialising MMC card
[    1.853645] max77696-rtc max77696-rtc.0: setting system clock to 2000-01-01 02:01:02 UTC (946692062)
[    1.892315] MAX77696 Main Charger Driver 1.0.0 Installed
[    1.951220] MAX77696 Energy Harvester Driver 1.0.0 Installed
[    1.971337] Freeing init memory: 1036K
3.0.35-lab126 #1 Tue Sep 3 03:12:16 PDT 2013 armv7l
[    2.050390] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.079325] mmc0: unrecognised EXT_CSD revision 7
[    2.084056] mmc0: error -22 whilst initialising MMC card
[    2.280911] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.317397] mmc0: unrecognised EXT_CSD revision 7
[    2.322144] mmc0: error -22 whilst initialising MMC card
[    2.391958] add wake up source irq 104
[    2.552535] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.611811] mmc0: unrecognised EXT_CSD revision 7
[    2.616539] mmc0: error -22 whilst initialising MMC card
[    3.529882] KERNEL: I pmic:fg battery id check::wario_battery_valid=1

And this is the full log of booting in main mode:

U-Boot 2009.08-lab126 (Mar 02 2021 - 17:14:13)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   36 C, calibration data 0x59c5205f
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: 0272201145060JKR
S/N: 9017220145240BC8
I2C:   ready
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0xfff0000
POST done in 57 ms
Battery voltage: 4021 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:    2420416 Bytes =  2.3 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.094347] boot: C def:bcut:batterycut=1
[    0.098367]
[    0.258830] LPDDR2 MfgId: 0x1 [Samsung]
[    0.279801] max77696-adc max77696-adc.0: adc conversion timed out
3.0.35-lab126 #1 Wed Aug 28 15:30:45 PDT 2013 armv7l
[    0.374999] mmc0: unrecognised EXT_CSD revision 7
[    0.379724] mmc0: error -22 whilst initialising MMC card
[    0.593841] mmc0: unrecognised EXT_CSD revision 7
[    0.598568] mmc0: error -22 whilst initialising MMC card
[    0.821901] mmc0: unrecognised EXT_CSD revision 7
[    0.826628] mmc0: error -22 whilst initialising MMC card
[    1.086362] mmc0: unrecognised EXT_CSD revision 7
[    1.091108] mmc0: error -22 whilst initialising MMC card

I saw someone get a similar message in this thread's post #5 https://www.mobileread.com/forums/sh...d.php?t=348137

Might this be a dead eMMC or is the diags_kernel.img incompatible with my eMMC. Or what else could this be?

After letting it sit, in the serial logs I also keep recieving this message, like in post #1 of this thread: https://www.mobileread.com/forums/sh...d.php?t=290861

[   62.017489] max77696-adc max77696-adc.0: adc conversion timed out
[   62.047565] max77696-adc max77696-adc.0: adc conversion timed out
[   62.054040]
[   62.054048] ADC value out of thermistor range! setting display temp to 43 deg C

If more information is needed, I will try to provide it.