View Single Post
Old 07-23-2016, 11:31 AM   #12
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: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
...
I guess we have to wait for someone who knows what that error code means.
...
Googling "kindle u004" found this (highlights added):
Quote:
Originally Posted by NiLuJe View Post
@geniusliu26:
U006: General failure (for official updates, generally a checksum error)
U004: No bundlefile (in the JB context, you used the wrong file for your FW version)
U007: Signature verification failure (JB is not installed)

You're gonna need to remember what you installed to 'fix' the official update. Checking the logs might help (;debugOn => ;dumpMessages => ;debugOff in the Home search bar).
Quote:
Originally Posted by prakashbala View Post
Here I see checksum are different, I believe the file is corrupted. Thanks for your help!! I'm going to download again!!
It was probably a corrupt firmware file that caused this U004 error (a side-effect of the bundelfile missing from download file truncation).

Based on successful downgrades by other users using this update file, a good copy (with correct MD5) should fix this problem.

Last edited by geekmaster; 07-23-2016 at 11:46 AM.
geekmaster is offline   Reply With Quote