Originally Posted by iNDEX3
Thank you for trying to help!
>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.063s
ok, so next option is to write the boot.img to recovery,
fastboot flash recovery <boot.img>
if that works then you will have to get to recovery with
fastboot boot <recovery.img>
not ideal, but if you can do a normal boot via a 'boot to recovery' you have no option
thinking about I have another option, but its a little bit more complicated
write a custom zImage to /boot
this kernel has its own mtd map, with a new partition where system normally starts ( or maybe cache or data ), and get it to load the ramdisk from that address
This assumes that the problem area is towards the end of boot partition
BUT, tbh , it seems like you have an actual hardware problem, it might be better to return it under warranty, less fun but better solution.