Originally Posted by TCCPhreak
I didn't. Once there was enough battery to boot correctly into fastboot, I could flash the kernels via fastboot and boot into diags again.. Unfortunately
I am back at my old problem: Some seconds after the system (diags) is booted, it freezes whatever it is doing. Serial output told me something about mxc_rtc and that the reboot is automated 61s after a stuck CPU.
I already found it and read it (http://www.mobileread.com/forums/sho...d.php?t=164018
). This is very interesting for when I should ever get into that situation but at the moment my MMC seems okay (apart from the main partition p0)
I really appreciate your help but I think you're missing my point:
- fastboot works.
- diags boots (so diags kernel is fine and diags partition is fine) but freezes after some time.
- main partition cannot be written by fastboot (size limitation) and not by diags (not enough time before freezing) and even if I was able to re-flash it, I'd bet that it would still freeze with the mxc_rtc-problem on the "Boy reading under tree"-screen.
I've traced the mxc_rtc into the linux-kernel where it's responsible for accessing rtc-functions on the freescape-CPU. As the kernel image is fine (there is a checksum check at booting), this problem should not arise from the filesystem/mmc.
Try erasing /var/local, which contains the boot counter (just to see if it helps):
dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1024
That should be quick, especially if run from RUNME.sh