Originally Posted by murz_07
I did "dd" mmcblk0p1 with your backup file.
I did as you said and NOTHING happend again. LED turned off and that's all.
What problem can I have and how cam I fix it using SSH?
If SSH works, it is probably not a hardware problem. If you used dd to write a good image file that is not damaged and not the wrong one, and you have the idme bootmode var and ENABLE_DIAGS removed as needed for booting to main,
then perhaps your main linux kernel is damaged.
As mentioned before, I plan to write a script to extract kernel images from mmcblk0.img backups.
There is a kernel image in the 5.0.4 update that you could extract, and burn that (but make sure it has the correct flash header on it). Or if you have access to another device, you can make a backup copy of the first 32MB of /dev/mmcblk0 and extract the main kernel from that (offset 0x41000, length in the flash header rounded up to the next 4KB block size).
Or... wait for somebody else to do it for you...