|
No, it will probably generate the same outcome. Kubrick internally uses k3flasher anyway.
What happens is that the flashing gets flaky - maybe aborting with an error, maybe it's the device resetting (due to problems with the CPU, power source, ...). k3flasher isn't too verbose in why it failed, either - you would only get information about at what point it fails.
You did charge the device with a proper wall charger for a long time, right? Otherwise, there's not a lot you can do. It can be hardware error in a multitude of parts...
|