View Single Post
Old 06-05-2019, 10:21 AM   #2
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
*) Amazon will not fix it.
They don't have a clue, even if it wasn't against company policy.

*) In all of your reading, did you come across the advice "Never try 'Erase All' because it works"?

*) There is a rather long thread here on how to recover from "Erase All".
Lots of attached log files so you can tell when your result begins to deviate from that expected at each point in the thread.

*) Tried multiple update files from Amazon?
List them (in order if possible) please.

*) Did you read about how it is impossible to load the main image file with fastboot?
PS: Where did you get the diag kernel and image you tried to load?
OR: Did you mean you tried to install the main kernel and/or main image with the fastboot command(s) for the diags system?

*) whatever terminal emulator you are using, enable communications logging to a file, reboot the device, when it stops trying to start, compress the communications log and attach to your next post.
knc1 is offline   Reply With Quote