Quote:
Originally Posted by davidfor
In that case, I don't think it is a valid image. When you connect a working Kobo ereader by USB, it only presents one partition. That is the partition with the books. It doesn't have the root or kernel or anything. Trying to boot from that would not work. And the size mentioned below agrees with this.
There is some discussion in the forums about using the headers on the PCB to connect to it. I don't remember if they got it to work or not.
If you have a working N905 Touch, you might be able to create an image using that. You should be able to telnet into the working device and us the dd command to create an image of the device on the SD card. Then use that to create the bootable SD car for the non-working device. I think this would work, but, I am not sure. And I don't know the dd command well enough to suggest what the parameters should be. Telnet is turned on when you turn on the developer mode. And that has an option to force WiFi on so it won't go to sleep when executing the commands needed.
As possible test of this is using the image from the N905B Touch. I think this might be close enough to the N905 to boot. I'm not sure of that, but, something in the back of my brain suggests it is. I don't think it will work completely, but, might get further than you currently have. I have sent you a PM with the link to the image if you want to try it.
|
IIRC, the N905B uses a different CPU/SoC (imx508) than the N905 and N905C (imx507). I think it has more chances to work with the N905C image.
Actually, if you can, you could debrick it with a serial connection. U-Boot is normally locked up on those devices (bootdelay=0), but if it can't find a kernel, it will let you type in a command prompt. From there, you can loady/loadx/loadb a kernel uImage from the serial port containing a minimal initrd and reflash the device manually, recovering old partitions as possible (especially recoveryfs).