TiVo Community Forum banner
1 - 20 of 35 Posts

·
Registered
Joined
·
33 Posts
Discussion Starter · #1 ·
Does anyone know exactly what files have been changed between 2.5.5 and 2.5.5a.

I'd read on another thread that the only difference was a 1 byte change to the file tivoapp. However, blindlemon has just helped me out by providing tivoapp from a 2.5.5a TiVo and it seems that this file is identical to tivoapp on my 2.5.5 TiVo :-o

I'm trying to avoid requesting a 2.5.5a update from TiVo customer services because I don't want to have to contend with the hassles of reinstalling LBA48 etc, so was wondering if anyone knows which files have change between 2.5.5 and 2.5.5a so I can just manually copy over these files. Thanks
 

·
TiVoer since 11/2000
Joined
·
6,341 Posts
One byte in tivoapp changes, that's it. It's the same size. If the one blindlemon sent you is identical, maybe he sent you the wrong one.

My tivoapps have other hacks in, so I can't tell you the exact byte to change.
 

·
tivoheaven.co.uk
Joined
·
5,577 Posts
OK, I have double-checked and have verified that the original file was from a 2.5.5a image.

I have also extracted the tivoapp from a second, unrelated, 2.5.5a image - and that too is identical to both the others!

So maybe the 1 byte difference you saw Stuart was not the 2.5.5a change?

I've posted a complete tarball of the 2.5.5a system partition for Dougal to investigate...
 

·
Registered
Joined
·
345 Posts
If I'm allowed to post it then I can tell you how to change it....

I didn't need to do mine in the end as the new TV worked fine so I havn't tested it!
 

·
Registered
Joined
·
345 Posts
AFAIK this should do it:

echo -n '1' | dd conv=notrunc of=tivoapp bs=1 seek=5137975


If this is not allowed I'm sure my post will be edited, and I apologize :)
 

·
tivoheaven.co.uk
Joined
·
5,577 Posts
Dougal,

What did you find from the tarball I sent you?
 

·
Registered
Joined
·
33 Posts
Discussion Starter · #8 ·
Thanks for the 2.5.5a system partition blindlemon. Well using MD5 checksums, I can confirm that the only 2 files of any significance that are different are:

/lib/modules/pxmpegdecode.o
/etc/build-version

(The only other differences were different CacheCard drivers, network drivers, ftp daemon etc + your rc.sysinit file and the like).

So, I copied over the pxmpegdecode.o file from the 2.5.5a version. The file /etc/build-version is just a text file with the software build and version info in it - I presume this is what the TiVo looks at to decide what software version it thinks is installed (so I left my old version of this file in place).

And Hey Presto, it worked - great, thank you very much for your help!

I assume that if I had changed /etc/build-version as well, I would have experienced the problem referred to by 6022Tivo in this thread:
http://www.tivocommunity.com/tivo-vb/showthread.php?t=248173

So, to fix the "teletext bug" just copy over pxmpegdecode.o with the 2.5.5a version (and leave /etc/build-version alone so that the TiVo still thinks its a 2.5.5)

Mini__me: thanks for the command to make the 1 byte change to tivoapp. I never tried this in the end as I had already sorted the problem by using the 2.5.5a version of pxmpegdecode.o. I can only assume that the 1 byte change trick is another way that someone worked out for disabling the teletext output.
 

·
tivoheaven.co.uk
Joined
·
5,577 Posts
Dougal,

Great stuff - and thanks for posting your results :)

In case anybody else needs them, here are the two 2.5.5a version files mentioned above.

255a.zip
 

·
Tivo Evangelist
Joined
·
332 Posts
As I understand things:

Patching tivoapp fixes the MWSTATE bug. There are 2 references to MWSTATE in tivoapp, and if two programs try to write to the same thing at the same time, it can cause a problem.

So patching tivoapp just changes the second instance of MWSTATE to say MWSTAT1.

This is needed for the very useful merge.tcl program, as found in this post

This is nothing to do with 2.5.5a of the Tivo software, which just affects the Teletext output.
 

·
Sedentary Member
Joined
·
387 Posts
Dougal said:
So, to fix the "teletext bug" just copy over pxmpegdecode.o with the 2.5.5a version (and leave /etc/build-version alone so that the TiVo still thinks its a 2.5.5)
Another alternative is the hardware fix (so far undocumented I believe) which I've used. 'Simply' remove the TV's offending Philip's Teletext card. This will of course necessitate locating it in the first place and possibly invalidate your warranty. If anyone really needs/wants to go down this route, I can dig into the innards of my TV where I left the board in a convenient corner, retrieve it and photograph it.
 

·
A Happy Member
Joined
·
2,062 Posts
Great advice, I had not thought of that, I have done a little work in Phillip's sets and this is a really easy fix.

I can not remember the last time I ever used teletext..
 

·
Registered
Joined
·
142 Posts
Hi Sorry for the complete ignorance, but it is a long time since I did anything softwarewise inside my TIVO.

I'm networked with backdoors open. Could someone provide this idiot with an idiot's line by line instruction as to what I have to do. My shiny new tv keeps turning itself off and the wife is not impressed with my buying decision!

I will be eternally grateful. Send beer vouchers etc etc.

Cheers
 

·
A Friend of Dot
Joined
·
752 Posts
As posted by Dougal above.....

So, to fix the "teletext bug" just copy over pxmpegdecode.o with the 2.5.5a version (and leave /etc/build-version alone so that the TiVo still thinks its a 2.5.5)


I would suggest you download the files posted above then telnet to your TiVo, cd to /lib/modules and rename pxmpegdecode.o to something like pxmpegdecode.org and then ftp the new version to that location (binary mode) and then restart the TiVo. Unless I'm mistaken, that should do it.

HTH

Mike
 

·
Registered
Joined
·
142 Posts
Thanks - will try that tonight when I get home. Fingers crossed.
 

·
A Friend of Dot
Joined
·
752 Posts
Don't forget to let us know how it goes.

Thinking on, you will most likely have to make the file system read/write first and then make it read only afterwards.

Good luck

Mike
 

·
Registered
Joined
·
142 Posts
Help!

I've telneted in, changed directory and can see pxmpegdecode.o.

1) It says it is read only. I've tried chmod 755 * to no avail.
2) What is the copy command?
 

·
Registered
Joined
·
142 Posts
It works.

copy pxmpegdecode.o file from attachment above (it needs renaming to delete everything after the 0)

telnet into TIVO using Run: telnet [IP address]
cd /lib/modules
mount -o rw -o remount /
cp pxmpegdecode.o pxmpegdecode.old
Leave telnet open.

ftp into TIVO using Run: ftp [IP address]
cd /lib/modules
bin
put c:\pxmpegdecode.o [It should confirm file transfer has been done]
quit

Back to open telnet:
mount -o ro -o remount /
exit

Reboot the TIVO and it should now be okay.

If anything is wrong in this please correct it.
 

·
from tivoland.com
Joined
·
944 Posts
Generally whenever I want a 2.5.5a O/S , I simply restore a 255a image from archive.

I experimented with the above (to try and create a 255a from a 2555 image) by copying BOTH of the files (pxmpegdecode.o and build-version) to the appropriate directories.

In this case I would have expected the System Information screen to report 2.5.5a and should I have called into Tivo without their database knowing I had 2.5.5a, the system would have forced and update back to 2.5.5.

but copying those files over may well have cured the teletext bug (I don't know) but the System Information screen still reports 2.5.5

I thought it should only do that if I left the original build-version file intact!?!??!
 
1 - 20 of 35 Posts
Top