View Single Post
Old 02-25-2017, 03:18 PM   #8
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
Giving your description some more thought -
What you describe is (hardware) write errors to the eMMC chip (hardware failures, internally).

Changing the screen should not have created a battery error - that was a certain sign that things where not "normal" with the device.

Somewhere here I have attached an archive containing both a script and a binary that does a: Write, Read-back, Verify type of copy - -
Which is what you need when trying to copy things (correctly) to a failing eMMC.

Sorry, I can't find the link to my post with that attached archive.
knc1 is offline   Reply With Quote