3.1-3.3 Update Failed (Need original files)

pyvlad · 02-13-2013, 12:57 PM

A long, long time ago, I patched /usr/bin/showlog, entirely forgetting what I changed and what the original was. When trying to update to 3.3, I get

Code:

130213:092315 ota_install: I def:patch:patchinfo="/usr/bin/showlog":patching file
130213:092315 ota_install: C def:patch:patchinfo="/usr/bin/showlog":checksum failure
130213:092315 ota_install: I def:patch:current_md5=8d5c0917914f5aff3d7a394987a16b02,expected_md5=36c803187d903dcef23b3f1d008a1f13,patch_md5=fd058e5dabcc2cf428453ab9923284a3:checksum verify

I looked here, where all the solutions to the problem link to, but all the uploads are dead, and copying the source doesn't work. Does anybody have this file? If so, please send to removed@removed.com!

knc1 · 02-13-2013, 01:02 PM

Quote:

Originally Posted by pyvlad

A long, long time ago, I patched /usr/bin/showlog, entirely forgetting what I changed and what the original was. When trying to update to 3.3, I get

Code:

130213:092315 ota_install: I def:patch:patchinfo="/usr/bin/showlog":patching file
130213:092315 ota_install: C def:patch:patchinfo="/usr/bin/showlog":checksum failure
130213:092315 ota_install: I def:patch:current_md5=8d5c0917914f5aff3d7a394987a16b02,expected_md5=36c803187d903dcef23b3f1d008a1f13,patch_md5=fd058e5dabcc2cf428453ab9923284a3:checksum verify

I looked here, where all the solutions to the problem link to, but all the uploads are dead, and copying the source doesn't work. Does anybody have this file? If so, please send to vlad345@gmail.com!

Look in the "References and Links" section of the debricking sticky at top of this forum index.

twobob · 02-13-2013, 01:53 PM

the patch was to point it to /dev/null IIRC?

and the original hmm.... STDOUT?

something like that IIRC.

Will have a dig around.

Honestly??? I would just use k3flasher. flash it clean. upgrade.
you would be done by now.

those are my thoughts.

pyvlad · 02-13-2013, 09:48 PM

Thank you very much knc1! I should have gone straight there after nothing else worked, but I got the update working. And yes twobob, I got the patch from one of those "Stop Big-Brother Mode" posts years ago.

Just in case anybody has the same problem, the debricking sticky pointed to this thread to debrick. However, instead of going through the whole flashing process (I'm in linux, without access to a 32 bit Windows computer), I just found the file I had patched (/usr/bin/showlog) in the downloadable firmware image in pastebin (3.0.2 factory image). I'll leave it up to you to get files out of the .img, but it worked for me.

knc1 · 02-13-2013, 09:53 PM

Quote:

Originally Posted by pyvlad

Thank you very much knc1! I should have gone straight there after nothing else worked, but I got the update working. And yes twobob, I got the patch from one of those "Stop Big-Brother Mode" posts years ago.

We do it a bit differently now - by setting the device firewall to block any connections to the Amazon network.

RSN, will have KUAL buttons for the "Big Brother Blocker".

KUAL is the newest application launcher.

**ALL** done from the USB storage area, without modification of system files (preventing the problems like yours).

02-13-2013, 12:57 PM	#1
pyvlad Junior Member Posts: 2 Karma: 15220 Join Date: Feb 2013 Device: Kindle 3	3.1-3.3 Update Failed (Need original files) A long, long time ago, I patched /usr/bin/showlog, entirely forgetting what I changed and what the original was. When trying to update to 3.3, I get Code: 130213:092315 ota_install: I def:patch:patchinfo="/usr/bin/showlog":patching file 130213:092315 ota_install: C def:patch:patchinfo="/usr/bin/showlog":checksum failure 130213:092315 ota_install: I def:patch:current_md5=8d5c0917914f5aff3d7a394987a16b02,expected_md5=36c803187d903dcef23b3f1d008a1f13,patch_md5=fd058e5dabcc2cf428453ab9923284a3:checksum verify I looked here, where all the solutions to the problem link to, but all the uploads are dead, and copying the source doesn't work. Does anybody have this file? If so, please send to removed@removed.com! Last edited by pyvlad; 05-04-2013 at 12:29 AM.

02-13-2013, 01:53 PM	#3
twobob ( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr Posts: 5,134 Karma: 5328985 Join Date: Jun 2012 Location: uti gratia usura (Yao ying da ying; Mo ying da yieng) Device: PW, K5 B011, K3 us, K4, DXG, XDA I&II, Omnia, Ematic E6 + E8 :) etc.	the patch was to point it to /dev/null IIRC? and the original hmm.... STDOUT? something like that IIRC. Will have a dig around. Honestly??? I would just use k3flasher. flash it clean. upgrade. you would be done by now. those are my thoughts. __________________ Audiophile and electron bully. My tunes (for free) soundcloud.com/twobob. DONATE TO KUAL BY CLICKING THIS SIMPLE LINK Kung-Fu. Hard work over time to accomplish skill. A painter can have kung-fu... The musician can have kung-fu, or the poet who paints pictures with words and makes emperors weep. This, too, is kung-fu. Formless, nameless, the true master dwells within. Only you can free him. The album I'm headlining on at the moment: s.beatport.com/OCp9dT - FREE: 2012 Award winning set

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
My kindle touch update from 5.0.1 to 5.0.3 failed	vc384	Kindle Developer's Corner	4	02-12-2012 09:10 AM
KSO, begging for some original files to update	blazeblue	Kindle Developer's Corner	1	11-02-2011 03:29 PM
update from 3.1 to 3.3 failed, beg for some original files	bsdcpp	Kindle Developer's Corner	1	10-27-2011 03:23 AM
Failed 0.4.84 update	AprilHare	Calibre	3	09-19-2008 11:20 PM
iLiad How I failed to catch the update process	arivero	iRex Developer's Corner	10	08-09-2006 05:05 AM

02-13-2013, 09:48 PM	#4
pyvlad Junior Member Posts: 2 Karma: 15220 Join Date: Feb 2013 Device: Kindle 3	Thank you very much knc1! I should have gone straight there after nothing else worked, but I got the update working. And yes twobob, I got the patch from one of those "Stop Big-Brother Mode" posts years ago. Just in case anybody has the same problem, the debricking sticky pointed to this thread to debrick. However, instead of going through the whole flashing process (I'm in linux, without access to a 32 bit Windows computer), I just found the file I had patched (/usr/bin/showlog) in the downloadable firmware image in pastebin (3.0.2 factory image). I'll leave it up to you to get files out of the .img, but it worked for me.


Advertisement Enthusiast