View Single Post
Old 12-10-2012, 05:19 PM   #15
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by hawhill View Post
And if you did this, waiting till the music stops, that would also be an explanation for a worn-out battery. It's not really made for this, I think. Lots of people have the problem of interrupted flashing attempts (sometimes it doesn't even start) and in all cases a dead battery seemed to be the explanation.
One possible workaround for flashing with a low-capacity battery is if it could be flashed in smaller segments, with a recharge in between flashes.

Perhaps k3flasher could be modified for multi-segmented flashing. And it would use much less energy to only flash the erase blocks that actually changed (read each block before deciding whether to flash it). Flashing an image that is the same version as the bricked one could be much faster and use a lot less battery.
geekmaster is offline   Reply With Quote