HMO patch on 4.0.1b (NOT 4.0.1)

[SledgeHammer]

Now that its been deemed legal discussion... has anyone gotten the HMO superpatch ported to 4.01b? I searched the forums, but nada...

[mrblack51]

Now that its been deemed legal discussion... has anyone gotten the HMO superpatch ported to 4.01b? I searched the forums, but nada...

just so we all are clear on the matter, you are not so much asking wether there has been a port, but rather that you are asking if someone has posted a publically available port which you can download? If thats the case, there is no generally publically available port for 4.0.1b. However, a direct port won't work on your SA s2 if you are subscribing to the tivo service.

[iwantmydtvnow]

I'm not a SA user but rather a newbie Dtv'er running a Monte'd 4.01b on an HDVR2 (have had a hard time locating a 4.0 image). I understand the SA and DTV version of the 4.01 software is the same, but was wondering if Mr. Black or anyone out there has had any luck getting the Superpatch to run on a 4.01 DTivo?

Either way, any info suggestions, help etc. would be hugely appreciated. If there isn't any version of the Superpatch for 4.01 would you recommend just sitting tight for now or is it likely to be a no-go with this version?

Also, to the veterans of this site, I offer a REALLY big thank you - I've been reading, lurking, and learning for some time now and all of your efforts & knowledge here has helped tremendously. :) Few of us newbies could've done anything without it, and the Tivo experience wouldn't have been the same!

[alldeadhomiez]

Either way, any info suggestions, help etc. would be hugely appreciated.

My 4.0 tivoapp has 45 separate patches applied (many hacks, especially HMO, account for more than one patch). If you don't want to port all of the patches you need to 4.0.1, 4.0.1a, 4.0.1b, or whatever 4.x variant you're running, install 4.0 instead. If you do want to port them, read my post in the big 3.1.0c thread.

The 4.0.1b kernel modules all run just fine with 4.0.

[iwantmydtvnow]

Thanks allot for your reply Alldeadhomiez - I think I'll try both your suggestions, although learning how to port to 4.01 sounds like a bit of a challenge. I'll definitely get back to some more reading, begining with your post. Thanks again! :)

[SledgeHammer]

The patch has been released guys... http://www.dealdatabase.com/forum/showthread.php?p=174831#post174831

[Haderak]

I run the superpatch401b.tcl and get the following error:

tivo:/tvbin$ bash /var/hack/install/HMO-Superpatch/superpatch401b.tcl
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: array: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 822036: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 939756: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 1544984: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 1702044: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 4222720: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 6863864: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 7835504: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8618248: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8618532: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8618540: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8618548: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8670008: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8673832: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8675716: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 8677816: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 12581956: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: 12583412: command not found
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: line 21: syntax error near
unexpected token `}'
/var/hack/install/HMO-Superpatch/superpatch401b.tcl: line 21: `}'
tivo:/tvbin$

[SledgeHammer]

Haderak,

run the script as follows:

1) remount the partition as read/write with:

mount -o remount,rw /

2) give the script execute permission with:

chmod 755 superpatch401b.tcl

3) execute it with:

superpatch401b.tcl

4) remount as read only with:

mount -o remount,ro /

5) reboot

repeat the same steps for setmrvname.tcl except run it like so:

setmrvname.tcl <box name>

where <box name> is the name you are assigning to that tivo, so if its in your bedroom you might do it like so:

setmrvname.tcl Bedroom

also, since tivoapp is always running, what you might want to do is make a copy of it in a different directory and execute the script there, then copy it back making sure to keep the permissions intact.

[Haderak]

I will try that. I did all of that including making a copy of TivoApp and then changing the script to run against the copy, but what I didn't do was check permissions of the script itself.

[SledgeHammer]

I will try that. I did all of that including making a copy of TivoApp and then changing the script to run against the copy, but what I didn't do was check permissions of the script itself.

How did you edit/upload the file? the TCL interpreter is pretty sensitive to the formatting I've noticed. If changing the permissions and running it normally (you were running it through bash in the above capture) still gives you the errors I would suggest redownloading it and running it as is.

[Haderak]

I got the same errors before and after changing it. I used vi to modify it and only changed the reference to the filename frmo tivoapp to tivoapp.hmo (my backup copy).

I am going to try again in the next hour and let you know if there are problems. From the error results though it looks like its treating the array statement as an actual command. I know nothing about the TCL language so I don't know if it is supposed to be a command and I am lacking the tools or if it should be interpreted by TCL internally. Either way in an hour I should know...

[SledgeHammer]

I got the same errors before and after changing it. I used vi to modify it and only changed the reference to the filename frmo tivoapp to tivoapp.hmo (my backup copy).

I am going to try again in the next hour and let you know if there are problems. From the error results though it looks like its treating the array statement as an actual command. I know nothing about the TCL language so I don't know if it is supposed to be a command and I am lacking the tools or if it should be interpreted by TCL internally. Either way in an hour I should know...

it may have been because you were running it with the bash command.

[Haderak]

Your right. The problem was I was running it from bash. I next problem is that it looks like I don't have a virgin 4.0.1b. The only patchs so far to TivoApp is from Sleeper ISO to get the network and such. I don't know what sort of error this is, still hunting it down. Maybe something from kmem?

tivo:/var/hack/install$ superpatch401b.tcl
At offset 12581952, expected 0x00c93021 but got 0x8c820004
Aborting...
tivo:/var/hack/install$

[SledgeHammer]

Your right. The problem was I was running it from bash. I next problem is that it looks like I don't have a virgin 4.0.1b. The only patchs so far to TivoApp is from Sleeper ISO to get the network and such. I don't know what sort of error this is, still hunting it down. Maybe something from kmem?

tivo:/var/hack/install$ superpatch401b.tcl
At offset 12581952, expected 0x00c93021 but got 0x8c820004
Aborting...
tivo:/var/hack/install$

sleeper doesn't do any binary patches. the kmem commands that sleeper installs should be commented out because they are wrong for 4.01b. But they dont change the file on disk only in memory.

hey, do me a favor, telnet to your box and on your "original" tivoapp, type:

md5sum tivoapp <or whatever the filename is>

I'm getting on my "original" file:

2591ce649a71e28d1255ac86f651c95b

Its possible that maybe I built the patch against a tivoapp that had a patch... hmm... I just want to see what your starting file md5s at.

[Haderak]

tivo:/tvbin$ md5sum tivoapp
e257d2323bf513a30d82f8be442be1d2 tivoapp
tivo:/tvbin$

That is a tivoapp that has gone through the surgery and hack phases on Sleepers ISO but nothing else. Here is my rc.sysint.author file. If you want to PM me I can make the box avialable via telnet over the internet also. If it at all helps. Hopefully its not just user error...

The setmrvname works fine btw...

#!/bin/bash
date>>/var/hack/log/hackinit.log

#Enviroment Variables
export PATH=/sbin:/bin:/tivobin:/busybox:/tvbin:.
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
export IGNOREEOF=1000
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib/modules
export TERM=xterm
export PS1='\h:\w$ '

#Start BASH
/bin/bash</dev/ttyS2&>/dev/ttyS2&

#Setup HOSTNAME
/bin/hostname tivo

#Set the IP address
ifconfig eth0 10.0.0.5 broadcast 10.0.0.255 netmask 255.255.255.0
route add default gw 10.0.0.1 netmask 0.0.0.0 metric 1

sleep 300

#Load telnet daemon and ftp dameon
tnlited 23 /bin/bash -login &
tivoftpd
cd /usr/mfs_ftp
/usr/mfs_ftp/mfs_ftp.tcl &
cd /

#Load kmem to prevent scrambling
#kmem 800bf958 00001021

/usr/scripts/callfixsub.sh /usr/scripts &
/usr/scripts/sps30
/usr/scripts/sort
tivo:/etc/rc.d$

[SledgeHammer]

Nothing in there that would cause the error you are getting. The address that you are getting the error at is only used for the HMO hack, so even if I did have some other hack, it shouldn't get that error there.

I'm showing:

tivoapp Aug 19, 2003 16449528 bytes

as my original...

Your system information screen shows 4.01b as the version?

[Haderak]

Image filename: 40g-s2-4.0.1b.mfs
Image version according to Tivo: 4.0.1b.2003.12.02-1731-01-2-240

tivo:/tvbin$ ls -l tivoapp*
-rwxr-xr-x 1 0 0 16449560 Jul 23 23:33 tivoapp
-rwxr-xr-x 1 0 0 16449560 Jul 24 00:27 tivoapp.bak
tivo:/tvbin$

tivoapp.bak should be the original, as I attempted to overwrite tivoapp with the setmvrname script, but not sure it did. The entire box was reimaged about 3 hours ago. I can do it again and skip the surgery/hacks section if that would help.

I never lookced the the 2003 part of the version, I have see discussions on 4.0.1b2 but I am nore sure if thats the same as what I have or not. I didn't think it was...

[Haderak]

I also have image file: S2-40-4-0b.bak but I am pretty sure thats 4.0b. Not 4.0.1b. I could try it though...

[SledgeHammer]

hmm... seems we have different versions. It would be nice if we could get info from others... I haven't had anyone else report any problems or confirm that its working, but we'll see what happens this weekend :).

P.S. I got my image from a brand new Phillips Stand Alone Tivo we bought at Best Buy in May or June 04. So it should be the latest code.

[Haderak]

Yes please someone else confirm if it works. Or if my image is wrong...

[SR712]

On the only virgin tivoapp 4.01b I have:

e257d2323bf513a30d82f8be442be1d2 tivoapp.orig

came from a file Tivo_40g-s2-4.0.1b.rar

[Haderak]

Same as mine, from the same file. So the HMO patch does not work on that image.

[SledgeHammer]

Weird...

Like I said, I got my image off a brand new, never powered up phillips stand alone tivo a month or two ago, so I am 100% sure it is the latest factory original code.

The images you guys got on eDonkey/eMule may have been tampered with.

Haderak, I'll grab your tivoapp on monday and compare it against mine and see what the changes are. I dunno whats up with the extra 32 bytes.

I PM'ed you a test file... we will see what happens with that :)

[alldeadhomiez]

Like I said, I got my image off a brand new, never powered up phillips stand alone tivo a month or two ago, so I am 100% sure it is the latest factory original code.

What assurances do you have that the factory immediately switched to 4.0.1b-02 when it was released?

Or that the unit you bought didn't sit in a warehouse for a while?

Anyway, to add to the confusion, here is what I have, pulled directly from slices:

4.0.1 (GZtvbin-15400810): 16449528 bytes, md5 77358c6a31511b770bc28cc728177061
4.0.1b-0[12] (GZtvbin-19371175): 16449560 bytes, md5 29dc76ac2f27212f49a3f72c2b72f337

For reference, my GetTivoConfig binary from 4.0.1 and 4.0.1b has md5 373e7930eebc3be5e35f6585eceba62b.

Check your /SwModule contents to see if your serverid matches up. You can pull out the original .cpio.gz containing tivoapp with FromMfs.

[SledgeHammer]

Well, there you go... mystery solved. So there are 3 different 4.01b's? 4.01b-00, 01 and 02?

[mrblack51]

Well, there you go... mystery solved. So there are 3 different 4.01b's? 4.01b-00, 01 and 02?

no, there is 4.0.1b-01, 4.0.1b-02, and 4.0.1b-2003-whatever the date is (im being lazy)

[SledgeHammer]

I have uploaded an updated version of the script for the build in question. You can find it here (http://www.dealdatabase.com/forum/showthread.php?t=36335).

[SledgeHammer]

So the superpatch allows my directivo2 to support HMO if I upgrade it to 4.0.1b? Are there any good threads to reference here?

Thanks!

Yes, you can upgrade your series 2 to 4.01b and get HMO using the superpatch. Assuming you have an HDVR2, DVR39 or a DSR7000. Other Series 2 units are "RID" units and wont work.

Haderak has posted a newbie guide here: http://www.dealdatabase.com/forum/showthread.php?t=36361

[mrblack51]

I have uploaded an updated version of the script for the build in question. You can find it here (http://www.dealdatabase.com/forum/showthread.php?t=36335).

please adjust your post to indicate that the tivoapps correspond to a given version. ie: if you are running 4.0.1b-XX, where XX is 01 or 02, then your md5sum is foo. thanks

[iwantmydtvnow]

Just to add my 2 cents to the fray...

Interestingly, on an HDVR2 with a monted 4.01b-01-2-140 (via Sleepers) and NOT the 4.0.1b-2003-xxxx version, I get the same offset error when running the 1'st 4.01b Superpatch:

At offset 12581952, expected 0x00c93021 but got 0x8c820004
Aborting...

When I run the 2'd superpatch file (4.01b-1.tcl) Tivoapp is changed without any error reports, and in Tivo's System Information screen, the HMO settings show as active. Unfortunately, the Music and Photos option on the main menu never appears :(

Also, md5sum tivoapp indicates the same result as others with the 2003-xxxx versions:

e257d2323bf513a30d82f8be442be1d2 tivoapp

I take it from another one of your posts SledgeHammer, you're still looking into another superpatch release? Anyhow, thanks allot for your hard work - I began reading up on porting the original file but didn't have enough time to climb the learning curve! I can definitely appreciate the time involved - thanks!

[Haderak]

The 4.0.1b superpatch doesn't work correctly yet. He has it close though. At least it shows up as active and the nameing works. But the HMO itself doesn't actually work. I have verified the same results you got.

Just to add my 2 cents to the fray...

Interestingly, on an HDVR2 with a monted 4.01b-01-2-140 (via Sleepers) and NOT the 4.0.1b-2003-xxxx version, I get the same offset error when running the 1'st 4.01b Superpatch:

At offset 12581952, expected 0x00c93021 but got 0x8c820004
Aborting...

When I run the 2'd superpatch file (4.01b-1.tcl) Tivoapp is changed without any error reports, and in Tivo's System Information screen, the HMO settings show as active. Unfortunately, the Music and Photos option on the main menu never appears :(

Also, md5sum tivoapp indicates the same result as others with the 2003-xxxx versions:

e257d2323bf513a30d82f8be442be1d2 tivoapp

I take it from another one of your posts SledgeHammer, you're still looking into another superpatch release? Anyhow, thanks allot for your hard work - I began reading up on porting the original file but didn't have enough time to climb the learning curve! I can definitely appreciate the time involved - thanks!

[tivo88]

I'm in the same boat 4.0.1b.2003.12.02-1731-01-2-240 done with Sleepers .ISO and latest Superpatch, shows enabled in Sys Info, but "Music and Photos" doesn't appear on the main menu.

[SledgeHammer]

I sent an updated script to a few of the members to test. We shall soon know the results :cool:

[Haderak]

The updated script works on my HDVR2 running 4.0.1b-2003-xxxx. I have verified with with JavaHMO. Everything seems ok, its currently on 2 hours running...

[SledgeHammer]

I have released the files here (http://www.dealdatabase.com/forum/showthread.php?t=36335).

[NutKase]

sleeper doesn't do any binary patches. the kmem commands that sleeper installs should be commented out because they are wrong for 4.01b. But they dont change the file on disk only in memory.

Actually, the kmem offset sleeper included in his iso works fine with 4.0.1b-01 and 4.0.1b-02. So does the kmem method 4.0.1 tivoapp patch location.

-----------------------------

That clarified, everyone newly hacking their tivo should use Alphawolf's NoCSO or the superpatch SledgeHammer beat me to releasing.

I'll confirm that it (superpatch) works on 4.0.1b-02 soon.

NutKase

[iwantmydtvnow]

Sledge, if I may call you Sledge, just wanted to say - YOU ROCK! Thanks alot dude - your ported version seems to work great. Haven't tried all the features out yet, but even tho I'm not a betting man, I'd be willing to bet that this'll do the trick. Thank you! :)

[dB02]

Hey, stupid question.. but what does this patch do? I hear alot about it but dont see what it does.. thanks

[mrblack51]

Hey, stupid question.. but what does this patch do? I hear alot about it but dont see what it does.. thanks

search: hmo superpatch

enables hmo on s2 units running 4.x software

[Haderak]

Anyone running this patch can you check something. In your Now Playing, does it display correctly? Mine sometimes shows 1-2 recordings (I only have 2) but mostly it shows blank and lets me scroll continously.

If I let it play Live TV for awhile and hit the button to go to the list it is there. If I go to the main menu then back into the list, its empty... I am trying to see if this is from the HMO patch or something else...

[SledgeHammer]

Anyone running this patch can you check something. In your Now Playing, does it display correctly? Mine sometimes shows 1-2 recordings (I only have 2) but mostly it shows blank and lets me scroll continously.

If I let it play Live TV for awhile and hit the button to go to the list it is there. If I go to the main menu then back into the list, its empty... I am trying to see if this is from the HMO patch or something else...

I noticed in your FAQ that you are doing some other patches via command line (not a good method IMO since there is no sanity checking). Can you check if you see this behavior on a clean tivoapp and then add only the HMO patch and check it again? That'll tell us if its the HMO patch or one of the others you are applying.

[Haderak]

I am going to check that right now. I had this problem the other night prior to working HMO patch, TivoWebPlus and HMO being the only ones. Also modifing the fact to suggest using patches where better for "sanity check reasons".

[Haderak]

Clean tivoapp works fine. I also tried disabling tivowebplus to make sure it wasn't an issue. It appears to happen only after I apply the HMO patch. The only patch that stayed with the system through this was USB2.0 which had no effect either way.

[mrblack51]

Image filename: 40g-s2-4.0.1b.mfs
Image version according to Tivo: 4.0.1b.2003.12.02-1731-01-2-240

tivo:/tvbin$ ls -l tivoapp*
-rwxr-xr-x 1 0 0 16449560 Jul 23 23:33 tivoapp
-rwxr-xr-x 1 0 0 16449560 Jul 24 00:27 tivoapp.bak
tivo:/tvbin$

tivoapp.bak should be the original, as I attempted to overwrite tivoapp with the setmvrname script, but not sure it did. The entire box was reimaged about 3 hours ago. I can do it again and skip the surgery/hacks section if that would help.

I never lookced the the 2003 part of the version, I have see discussions on 4.0.1b2 but I am nore sure if thats the same as what I have or not. I didn't think it was...

you are running an outdated version of the software, most likely an engineering build meant to allow specific users test functionality before it hits prime time. get yourself the latest software, which is 4.0.1b-02-2-XXX.

[Haderak]

And here I thought it was the latest version :(

you are running an outdated version of the software, most likely an engineering build meant to allow specific users test functionality before it hits prime time. get yourself the latest software, which is 4.0.1b-02-2-XXX.

[SledgeHammer]

Hmmm... my test box at work is running 4.0.1-01-2-240. I'll check if it has the same issue, but its an older build then what you are running.

[roach]

Hmmm... my test box at work is running 4.0.1-01-2-240. I'll check if it has the same issue, but its an older build then what you are running.

I'm running the exact same version. I get:

$ md5sum tivoapp.orig
2591ce649a71e28d1255ac86f651c95b tivoapp.orig

which appears to be the same that you have. When I run the latest and greatest version of the scripts that you posted I get:

$ tivosh /var/hack/superpatch401b-FINAL.tcl
At offset 12581952, expected 0x8c820004 but got 0x00c93021
Aborting...

which appears to be simliar to what Haderak is getting. If went through and edited the various offsets (that one mentioned and a couple of others) and the patch finally "succeeded" but I get the same symptom of listed as Active in system information, but no photos, music, etc. in the main menu. Any ideas?

[SledgeHammer]

The script posted was, as indicated, only for the 4.0.1b-2003-xxxx version. I was under the mistaken impression that was the latest code when it was really a beta version. Haderak also mentioned this version has a bug in the Now Playing list.

My test box at work is at version 4.0.1-01-2-240. After the discovery of the Now Playing bug, I didn't bother upgrading, but instead updated the script to work on that version to see if it had the same problem.

I could not duplicate the Now Playing bug on the "01" version. I don't know if it exists in the "02" version since I dont have it.

When someone comes forward who has a "02" version installed and is willing to do some testing, I will update the script for that version too if needed. (I just don't have the patience to wait a week to download it off eMule/eDonkey :D )

Roach, don't go editing the script haphazardly, this could destroy your tivoapp! That would mean doing a drive pull or re-imaging to fix it.

FYI: several of the key patch points are different in the "01" version, so it is no surprise it didn't work. The updated script I have that I will post tommorow morning works perfectly with the "01" build and no Now Playing bug.

I'm running the exact same version. I get:

$ md5sum tivoapp.orig
2591ce649a71e28d1255ac86f651c95b tivoapp.orig

which appears to be the same that you have. When I run the latest and greatest version of the scripts that you posted I get:

$ tivosh /var/hack/superpatch401b-FINAL.tcl
At offset 12581952, expected 0x8c820004 but got 0x00c93021
Aborting...

which appears to be simliar to what Haderak is getting. If went through and edited the various offsets (that one mentioned and a couple of others) and the patch finally "succeeded" but I get the same symptom of listed as Active in system information, but no photos, music, etc. in the main menu. Any ideas?

[NutKase]

When someone comes forward who has a "02" version installed and is willing to do some testing, I will update the script for that version too if needed.

I'm testing it now. The superpatch you posted completed with no errors.

However, I got a "Failed during processing" error after downloading data...

I'll double-blind test it soon and ensure I can repeat it.

I've replaced it with my other tivoapp and now the processing completes without error.

As I said, I was about halfway through finding all the offsets for 4.0.1b-02 when you posted your superpatch and will continue or just report back on yours.

NutKase

[Haderak]

I will be able to test -2 later tonight or tomorrow morning..

[SledgeHammer]

I'm testing it now. The superpatch you posted completed with no errors.

However, I got a "Failed during processing" error after downloading data...

I'll double-blind test it soon and ensure I can repeat it.

I've replaced it with my other tivoapp and now the processing completes without error.

As I said, I was about halfway through finding all the offsets for 4.0.1b-02 when you posted your superpatch and will continue or just report back on yours.

NutKase

I think porting either the "2003" or "01" version to "02" is trivial. Shouldn't take more then a few minutes once I get my hands on the tivoapp. The patch points are likely to be within spitting distance.

if superpatch401b-FINAL.tcl ran without any errors (or modifications to the script), it should be working. The error checking is such that it would be unlikely for it to patch in the wrong place by chance unless "forced".

Once we get all three versions going, I am planning (when I'm bored :)) to merge all three scripts into one .tcl file to avoid confusion. Maybe even merge in the setmrvname portion.

[NutKase]

I will be able to test -2 later tonight or tomorrow morning..

Here's one early discrepancy...

OFFSET ORIGINAL NEW VALUE 4.01b OFFSET
870548 "00408021 24100001" 00868148

I came up with:
942028 "00408021 24100001" 00939759

You came up with:
939756 "00408021 24100001"

NutKase

[EDIT (reference below)] Admittedly, I'm not the greatest at this and I' was doing brute hex attacks... and not dissassembly yet... but 00939759 is what I came up with...

Don't waste too many brain cells yet, I was probably drinking when I was hacking on it :).

[SledgeHammer]

Here's one early discrepancy...

OFFSET ORIGINAL NEW VALUE 4.01b OFFSET
870548 "00408021 24100001" 00868148

I came up with:
942028 "00408021 24100001" 00939759

You came up with:
939756 "00408021 24100001"

NutKase

Not questioning you Nutkase, just looking for clarification :)

What is the 939759? Is that your patch location? or is it 942028?

939759 doesn't sound right... all the patches are DWORDs aligned on 4 byte boundaries.

If 942028 is your offset, that seems like a very big discrepancy for a minor version change. Thats over 2000 bytes off. How many bytes is tivoapp in the "02" version? The patch locations that changed in the "01" version were only about 20 to 30 bytes off.

[roach]

Roach, don't go editing the script haphazardly, this could destroy your tivoapp! That would mean doing a drive pull or re-imaging to fix it.

Gee that's half the fun ;). Thanks again for the scripts and the pointers. Looking forward to the version you mentioned.

[NutKase]

Not questioning you Nutkase, just looking for clarification :)

I tried to clarify above...

NutKase :)

[mhartman]

I installed the patch on two S2 SA's last night running 4.0.1b-02-2-240. Installation went without a hitch. I did run into a problem on one of the machines with the Now Playing screen not having any shows on it (you can scroll around, but there is nothing there). This problem came along with a network crash during a show transfer(not sure why the wireless network crashed - it has happened before, though, so I don't think it is related to the patch). Based on this, the Now Playing bug may be related to whether there is an active network connection between the two machines or if the network goes down during a transfer.

Once I reset the network and rebooted the "bugging" Tivo, everything has been working fine for the last 12 hours.

I hope this helps.

Mike

[SledgeHammer]

Thanks mike... but I thought Tivo is giving HMO out for free on S2 SAs??

I installed the patch on two S2 SA's last night running 4.0.1b-02-2-240. Installation went without a hitch. I did run into a problem on one of the machines with the Now Playing screen not having any shows on it (you can scroll around, but there is nothing there). This problem came along with a network crash during a show transfer(not sure why the wireless network crashed - it has happened before, though, so I don't think it is related to the patch). Based on this, the Now Playing bug may be related to whether there is an active network connection between the two machines or if the network goes down during a transfer.

Once I reset the network and rebooted the "bugging" Tivo, everything has been working fine for the last 12 hours.

I hope this helps.

Mike

[mhartman]

Thanks mike... but I thought Tivo is giving HMO out for free on S2 SAs??

They are, but for some reason MRV does not work with video that is not scrambled (i.e., MRV does not work after appying noCSO/noscramble2 patch). So, I went ahead and tried your patch to see if I could keep on noscrambling and do MRV. So far, it seems to work.

Mike

[SledgeHammer]

Thanks guys, I have updated the post in the files area mentioning that this is working on the "2003" version and the "02" version. I will post the script for the "01" version in about another hour or so.

[NutKase]

They are, but for some reason MRV does not work with video that is not scrambled (i.e., MRV does not work after appying noCSO/noscramble2 patch). So, I went ahead and tried your patch to see if I could keep on noscrambling and do MRV. So far, it seems to work.

Mike

Force a daily call to check if you get the "Failed during processing error" I mentioned.

NutKase

[SledgeHammer]

The 4.0.1-01-2-240 version of the script has been posted in the files section.

[mhartman]

Force a daily call to check if you get the "Failed during processing error" I mentioned.

NutKase

I will try this when I get home tonight (it may have already tried it for me).

[NutKase]

I will try this when I get home tonight (it may have already tried it for me).

Nevermind. I just tested it and now there's no problem. My second tivo has a hd crapped out so I actually haven't test MRV but everything shows up fine.

NutKase

[mhartman]

Nevermind. I just tested it and now there's no problem. My second tivo has a hd crapped out so I actually haven't test MRV but everything shows up fine.

NutKase

Cool, glad to hear it is working.

[SledgeHammer]

Force a daily call to check if you get the "Failed during processing error" I mentioned.

NutKase

You aren't using fixsub? ;)

[NutKase]

You aren't using fixsub? ;)

No, SA S2's only.

NutKase

[mhartman]

I forced daily calls on my machines and they work fine. I am having a problem though. When I try to transfer a show between machines, it transfers 10 to 25 minutes of the show and then the transfer stalls and the receiving machine no longer has a network connection. I have to reboot to fix the network connection.

I have determined that the problem is in the Tivo and not the network because I have tried wired and wireless connections and I have tried two different routers. Has anyone else run into this problem? I am running USB 2.0 drivers. I'm wondering if the higher speeds are too much for the machine? Any ideas?

Thanks,
Mike

[jonnydeath]

Hello,
One of my tivos (running 4.01b-02-240) has an invisible now-playing. sometimes it shows up, but usually it doesn't or it takes a long time. I can view the now-playing from the other tivo (running 4.01b-01-240) and even watch shows across the network. I used the most recent patch files.

opps. Saw this has been posted before but I thought the FINAL version was supposed to fix this.

e257d2323bf513a30d82f8be442be1d2 /tvbin/tivoapp.tmp

This (I think) is my orriginal file that was put on by a tivo update (not from am image)

I also reset my hub to account for the network traffic (only thing on it is laptop, and the two tivos. turned the xbox and everything else off). It still takes a while for the now showing to appear.

[philhu]

ok, 3 quick hmo questions:

I see that the patch does the same thing for descrambling that the noscramble patch does. Is this true? If I uninstall the noscramble and apply the hmo superpatch, will mfs_ftp and tytools still work correctly? In other words, does the noscramble built in the superpatch handle ann stuff the noscramble standalone patch does?

Also, I am running 4.01b-02-240, and I see some have found a problem with this and empty 'now playing' screens. Is this happenning to alot or is it a network glitch causing this artifact?

And lastly, does the bufferhack patch get in the way of this hmo patch?

[Haderak]

Yes it does the same as the noscramble patch. Uninstall the noscramble. It should work with mfs_ftp and tytools but I haven't verified that yet, although I plan to in the next few days myself. One way know for sure and that is to just do it.

Only two reports of the empy now showing screen. By myself and one other, both of us have the exact same problem. I think it may be related to a specific version of tivoapp though and not necessarily an issue with the HMO Superpatch. I am trying different versions of 4.0.1b to see where it exists. Its just been difficult getting the three flavors of 4.0.1b (I have two of them but not the third).

No idea what the bufferhack is, my guess is that it doesn't.

If I am wrong on ay of this please correct me.

ok, 3 quick hmo questions:

I see that the patch does the same thing for descrambling that the noscramble patch does. Is this true? If I uninstall the noscramble and apply the hmo superpatch, will mfs_ftp and tytools still work correctly? In other words, does the noscramble built in the superpatch handle ann stuff the noscramble standalone patch does?

Also, I am running 4.01b-02-240, and I see some have found a problem with this and empty 'now playing' screens. Is this happenning to alot or is it a network glitch causing this artifact?

And lastly, does the bufferhack patch get in the way of this hmo patch?

[SledgeHammer]

Hello,
One of my tivos (running 4.01b-02-240) has an invisible now-playing. sometimes it shows up, but usually it doesn't or it takes a long time. I can view the now-playing from the other tivo (running 4.01b-01-240) and even watch shows across the network. I used the most recent patch files.

opps. Saw this has been posted before but I thought the FINAL version was supposed to fix this.

e257d2323bf513a30d82f8be442be1d2 /tvbin/tivoapp.tmp

This (I think) is my orriginal file that was put on by a tivo update (not from am image)

I also reset my hub to account for the network traffic (only thing on it is laptop, and the two tivos. turned the xbox and everything else off). It still takes a while for the now showing to appear.

My suggestion would be to run 4.01b-01-240 on all three since you dont see the no playing problem and I dont either (my box is 4.01b-01-240 too).

[SledgeHammer]

ok, 3 quick hmo questions:

I see that the patch does the same thing for descrambling that the noscramble patch does. Is this true? If I uninstall the noscramble and apply the hmo superpatch, will mfs_ftp and tytools still work correctly? In other words, does the noscramble built in the superpatch handle ann stuff the noscramble standalone patch does?

Also, I am running 4.01b-02-240, and I see some have found a problem with this and empty 'now playing' screens. Is this happenning to alot or is it a network glitch causing this artifact?

And lastly, does the bufferhack patch get in the way of this hmo patch?

Part of the HMO patch is turning scrambling/encryption off on everything. You dont need the seperate no scramble patch.

[Haderak]

Johnnydeath: I have the same issue and it is with that same version of tivoapp. I think its something with that version, which was pointed out elsewhere is possibly not a production release but an internal build. The md5sum is:

e257d2323bf513a30d82f8be442be1d2 /tvbin/tivoapp

I haven't been able to test other versions of 4.0.1b as I am still working on getting other images. So like Sledge suggests, maybe find a new image to use, at least that is what I am trying to do.

[philhu]

Johnnydeath: I have the same issue and it is with that same version of tivoapp. I think its something with that version, which was pointed out elsewhere is possibly not a production release but an internal build. The md5sum is:

e257d2323bf513a30d82f8be442be1d2 /tvbin/tivoapp

I haven't been able to test other versions of 4.0.1b as I am still working on getting other images. So like Sledge suggests, maybe find a new image to use, at least that is what I am trying to do.


4.01b-02-240 is *NOT* an internal build. I just rcvd it on 2 sa s2 tivos a few nights ago! It is what is being sent down now. If anything, the 4.01b-2003 or whatever, which does not follow naming conventions, is an internal build.

[malfunct]

I haven't been able to test other versions of 4.0.1b as I am still working on getting other images. So like Sledge suggests, maybe find a new image to use, at least that is what I am trying to do.

The other thing you could do is use the methods that have been explained here a few times and find the new offsets (it won't be easy but its not impossible) and post a new superpatch that can detect the different version and apply the right offsets based on that.

[SledgeHammer]

4.01b-02-240 is *NOT* an internal build. I just rcvd it on 2 sa s2 tivos a few nights ago! It is what is being sent down now. If anything, the 4.01b-2003 or whatever, which does not follow naming conventions, is an internal build.

Thats what we said... or meant to say :)

[SledgeHammer]

The other thing you could do is use the methods that have been explained here a few times and find the new offsets (it won't be easy but its not impossible) and post a new superpatch that can detect the different version and apply the right offsets based on that.

The scripts I posted for 4.01b-02 and 4.01b-2003 work just fine. There is nothing wrong with the offsets, but there seems to be the now playing bug with one or both of these versions.

I also posted a script for the 4.01b-01 version (that version doesn't seem to have that bug).

[Haderak]

Yeah what sledge said. I meant to say that the 4.0.1b-2003-xxx is probably an internal build, and that is where I am seeing the now showing problem....

[NutKase]

The scripts I posted for 4.01b-02 and 4.01b-2003 work just fine.

I confirm. 4.0.1b-02 works fine and no 'Now Playing' problems.

NutKase

[UPDATE] It 'fails during processing' after retreiving data.

More testing... info to follow.

[philhu]

I did some testing about usb 2/transfer speeds, etc. SEe my post in Newbies.

But, while I was at it, I also experienced the 'Now Playing' bug in 01 *and* 02
when I have usb 2.0 drivers loaded and they are sending alot of traffic on the lan.

It caused the nics to hang eventually. But while stressing the network, I saw the now playing bug. In usb 2 mode, it runs the nic at 1050 kB/sec or more.

With std standalone sleeper drivers, which run the nics at abot 450kB/sec, problems were not observed.

I think the usb 2.0 drivers cause too much data for the slow tivo processor to handle, hanging the card, but also causing processor interrupt code problems.

Anyone think this might be the case?

If so, what I might try, if I can get my dev environment right, is to force the usb 2.0 driver to stall a millisecond or two after each transfer. Attempting to slow it down to the 800 kB/sec range

[NutKase]

I will try this when I get home tonight (it may have already tried it for me).

New input.

I'm getting the "Failed during processing" error on 4.0.1b-02 with your HMO superpatch. I don't think it's 100% yet.


NutKase

[philhu]

New input.

I'm getting the "Failed during processing" error on 4.0.1b-02 with your HMO superpatch. I don't think it's 100% yet.

NutKase

You said it worked fine 2 posts up! What changed?


I just put in the patch

I'd try a callout, but I typo'd the usb 2 drivers stuff and I need to pull my drive to get network working again :(

phil

[NutKase]

You said it worked fine 2 posts up! What changed?


I just put in the patch

I'd try a callout, but I typo'd the usb 2 drivers stuff and I need to pull my drive to get network working again :(

phil

Well duh... I started getting the same errors again. You can always go back to your original tivoapp like I did.


NutKase

[Haderak]

So with the Superpatch I have now tested versions

4.0.1b-01-02-240
4.0.1b-2003-xxx
4.0.1b-01-02-xxx

The 4.0.1b-01 version of the patch worked on my 4.0.1-01 image. On every single version I have used the superpatch on I have gotten the "Now Playing" bug. This is without any other hacks applied to tivoapp and without any extra things running like TivoWebPlus or such.

I have an HDVR2 and using the Linksys USB200M network adapter. Not sure how to narrow down the problem, as its only with the HMO patch. If anyone has suggestions I can do to figure out where the problem is exactly I am all ears...

[SledgeHammer]

Are you still installing the USB2 drivers? That seems to be the cause of the problem. Seems the USB2 speeds are too much for HMO to handle. Other threads on the forum say people see the now playing bug with USB2 drivers, but then reverting back to the USB1 drivers clears up the problem.

Other then that, my 4.0.1b-01 version doesn't seem to have it...

[Haderak]

I am not installing the USB2 drivers. This is only with the HMO Superpatch, nothing else. I am useing a Linksys USB200M. I went to CompUSA and picked up a Netgear FA120 to see if that makes any difference. I will know later tonight...

[SledgeHammer]

I am not installing the USB2 drivers. This is only with the HMO Superpatch, nothing else. I am useing a Linksys USB200M. I went to CompUSA and picked up a Netgear FA120 to see if that makes any difference. I will know later tonight...

I dunno then... "it works on my machine" :) ... how you are testing it? just one machine? two machines? javahmo, tivodesktop, etc?

I tested mine on a single 4.01b-01 box with TivoDesktop.

Is there something weird on your network?

[Haderak]

No my network is plain. I am using JavaHMO (but have also used TivoDesktop). I can get all that fine. The HMO patch does work :)

The network is a 10 foot crossover cable from my Tivo directly into my computer. No hub/switch or anything. Static IP assignment on both links. Same result whether the network cable is connected or not.

[SledgeHammer]

No my network is plain. I am using JavaHMO (but have also used TivoDesktop). I can get all that fine. The HMO patch does work :)

The network is a 10 foot crossover cable from my Tivo directly into my computer. No hub/switch or anything. Static IP assignment on both links. Same result whether the network cable is connected or not.

Well, perhaps JavaHMO is giving bad data or something of that sort?

[philhu]

I posted in series 2 support about some of this.

What usb network nics are everyone using?

I now use the dub-e100 and it seems much more stable that the linksys, which uses the pegasus.o driver (Which I think is not as stable a driver, based upon onther posts I've read).

[SledgeHammer]

I posted in series 2 support about some of this.

What usb network nics are everyone using?

I now use the dub-e100 and it seems much more stable that the linksys, which uses the pegasus.o driver (Which I think is not as stable a driver, based upon onther posts I've read).

I'm using the stock "standalone" drivers that sleeper installs.

[NutKase]

Not sure why we've got 2 threads going... I guess this one is more for 4.0.1b.

Anyway, here's a link to my post's in the other. I put HMO superpatch on my 4.0.1b-02 machine and it's failing again. I did have one successful one I think but now I don't know.

Tclient log showing"failed during processing" problems (http://www.dealdatabase.com/forum/showthread.php?p=176841#post176841)

Key related somehow...

NutKase

[SledgeHammer]

My guess is that there is a missing function patch somewhere for that routine that verifies the key (which is faked). The original HMO superpatch was for DTivos (which usually use FixSub) so this was probably ignored.

Just a guess ... :)

[philhu]

My guess is that there is a missing function patch somewhere for that routine that verifies the key (which is faked). The original HMO superpatch was for DTivos (which usually use FixSub) so this was probably ignored.

Just a guess ... :)

I bet you are right. Either tclient needs a patch or something is missing in tivoapp.

Remember, noscramble2 patches do not suffer from this problem.....

adh posted the fix for 4.0 in S2 Development. It only selectively kills the blowfish encryption. Someone needs to port it to 4.01b

He shows the old code and the new code. The old, with different offsets, does exist in the patch, so it might be easy to get the new code in a patch.

[NutKase]

I bet you are right. Either tclient needs a patch or something is missing in tivoapp.

Remember, noscramble2 patches do not suffer from this problem.....

adh posted the fix for 4.0 in S2 Development. It only selectively kills the blowfish encryption. Someone needs to port it to 4.01b

He shows the old code and the new code. The old, with different offsets, does exist in the patch, so it might be easy to get the new code in a patch.

Hey. I'll look into that. I'm working nights for a few days so it may be the weekend.

NutKase

[philhu]

hey nutkase-
rc3105 posted the fix, but I am having problems converting the address from hex to decimal.

They don't line up

Can you take a look and see my post in the other group and the patch there?

Phil

[SledgeHammer]

hey nutkase-
rc3105 posted the fix, but I am having problems converting the address from hex to decimal.

They don't line up

Can you take a look and see my post in the other group and the patch there?

Phil

I responded to your post there.

[NutKase]

I responded to your post there.

Oh, a race? You win. :) Really, I have nothing to prove and very little time...

Don't take that the wrong way, I've been up for 17hrs working nights already.

Maybe on my next click we'll be all done. :)

...if I can find that other thread again.

NutKase

[philhu]

Ok, I guess no one has responded.

I'll go post at the other thread about this...

[DocTauri]

I have an HDVR2 running 4.0.1-01-2-140. I've been out of the game for a while, just read last night that HMO has been opened up to us. I have a few questions though:

1: I understand that the SuperPatch does a lot of things, but what are the minimum patches needed for MRV/M&P? I'm assuming the HMO patch, encryption patch, and MRV name, anything else REQUIRED to make HMO work?

2: Are the required patches truly patches, or something that only runs at runtime (i.e. kmem statements from init.rc rather than patches to tivoapp)? I ask because it seems the HMO patch is a true binary modification, but in my reading, it seems the unencrypt patch may be a kmem thing.

3: I'm a legit subscriber, so don't care to run any of the fixsub type stuff, in fact, I don't have a problem with it phoning home after the update, other than raising eyebrows, is there any reason I SHOULDN'T have it call home?

4: My 3 HDVR2's are currently running the above software, but not hacked (no monte, telnet, tivoweb, etc.). Would it work to simply replace my tivoapp with a patched one, or does one need telnet/custom script access in order to achieve HMO?

5: Finally (and I'm sure the answer is no), but is there any central repository where I can find 4.01b-02-240?

Thanks a lot!
Doc

And I forgot to ask, I don't have any drives larger than 120GB, but does running the 4.x kernel on a S2 DTivo allow you to overcome the 137 GB limit?

[SledgeHammer]

I have an HDVR2 running 4.0.1-01-2-140. I've been out of the game for a while, just read last night that HMO has been opened up to us. I have a few questions though:

1: I understand that the SuperPatch does a lot of things, but what are the minimum patches needed for MRV/M&P? I'm assuming the HMO patch, encryption patch, and MRV name, anything else REQUIRED to make HMO work?

2: Are the required patches truly patches, or something that only runs at runtime (i.e. kmem statements from init.rc rather than patches to tivoapp)? I ask because it seems the HMO patch is a true binary modification, but in my reading, it seems the unencrypt patch may be a kmem thing.

3: I'm a legit subscriber, so don't care to run any of the fixsub type stuff, in fact, I don't have a problem with it phoning home after the update, other than raising eyebrows, is there any reason I SHOULDN'T have it call home?

4: My 3 HDVR2's are currently running the above software, but not hacked (no monte, telnet, tivoweb, etc.). Would it work to simply replace my tivoapp with a patched one, or does one need telnet/custom script access in order to achieve HMO?

5: Finally (and I'm sure the answer is no), but is there any central repository where I can find 4.01b-02-240?

Thanks a lot!
Doc

And I forgot to ask, I don't have any drives larger than 120GB, but does running the 4.x kernel on a S2 DTivo allow you to overcome the 137 GB limit?

1) All you need is the HMO patch and mrv name. The encryption patch is built into the HMO patch.

2) The HMO superpatch is a patch... you run it once and it physically modifies a binary on your harddrive. There are many ways to do the encryption patch. One of which is a byte patch and another of which is kmem.

3) If you install any version of 4.x on your DTivo, you should use fixsub (and thus loose the power to order PPVs from your remote) because you are not allowed to run this software on a DTivo and allowing it to phone home will break a lot of stuff on both sides and might cause you to get in a wee bit of trouble.

4) If you are running 4.x on your HDVR2 and allowing it to phone home, I am surprised you have not gotten a letter or phone call about running unauthorized software on your tivo. Setting the MRV name is machine specific, you can not copy anything there, you would need bash access. Also, if you want to make any changes to the file system, you would need to monte or otherwise hack the system.

5) No, distributing images is illegal. But apperently there are some people doing it on eMule/eDonkey.

[DocTauri]

Thanks for the info. That's what I figured on the images (and is where I got mine). I do have a comment and a couple of questions though:

3) If you install any version of 4.x on your DTivo, you should use fixsub (and thus loose the power to order PPVs from your remote) because you are not allowed to run this software on a DTivo and allowing it to phone home will break a lot of stuff on both sides and might cause you to get in a wee bit of trouble.
What things would this (4.x and phoning home) break? To be honest, I've seen no problems (or complaints from the mothership).

4) If you are running 4.x on your HDVR2 and allowing it to phone home, I am surprised you have not gotten a letter or phone call about running unauthorized software on your tivo. Setting the MRV name is machine specific, you can not copy anything there, you would need bash access. Also, if you want to make any changes to the file system, you would need to monte or otherwise hack the system.
Actually, I've been running 4.0 on one box, allowing it to phone home, for about a year now, waiting for them to call so that I can rant. Haven't heard anything yet. Has anyone actually been "talked to", or is this speculation?

Where is the machine name stored?

Also, any idea on the drive size limitation?

Thanks again!
Doc

[SledgeHammer]

Thanks for the info. That's what I figured on the images (and is where I got mine). I do have a comment and a couple of questions though:


What things would this (4.x and phoning home) break? To be honest, I've seen no problems (or complaints from the mothership).


Actually, I've been running 4.0 on one box, allowing it to phone home, for about a year now, waiting for them to call so that I can rant. Haven't heard anything yet. Has anyone actually been "talked to", or is this speculation?

Where is the machine name stored?

Also, any idea on the drive size limitation?

Thanks again!
Doc

There was always some speculation that your account would be flagged or that you might download something incompatible or confuse Tivos servers. I guess that has been proved false.

The mrv name is stored in the MFS database and is used to encrypt the host name certificate. There is no way to "copy" the certificate since the script uses the crypto chip on the motherboard. So the keys are going to be unique to each machine.

Only the HD-DTivo comes stock with an LBA48 kernel, so every thing else is going to have the 137GB limit out of the box.

[DocTauri]

1) Good
2) Now I understand
3) Damn!

Thanks for the clarifications and your hard work! I'll be playing with this tonight (although the wife probably hates you now ;) )

Doc

[blueman2]

Image filename: 40g-s2-4.0.1b.mfs
Image version according to Tivo: 4.0.1b.2003.12.02-1731-01-2-240
...

Haderak,

Were you able to get this image working? I think that is the version I found on ED2K (file name Tivo_40g-s2-4.0.1b HDVR2.rar, image inside that file is called 40g-s2-4.0.1b.mfs).

You mentioned earlier that maybe that eDonkey file was not good. Did it end up working for you?

[Haderak]

I found a different image. 4.0.1b-01-2-120. While its not the lastest (4.0.1b-02-2-xxx) is, its close enough and probably a better bet then the -2003 version.

[gtrogue]

I seem to remeber reading something about this somewhere but I can't seem to find it now...

If you install 4.x on a DTivo and use Sleeper's ISO do you need to block the DTivo's network traffic from the internet to keep it from "calling" in? Or does a hack on Sleeper's ISO prevent the thing from calling in?

[blueman2]

According to Tip#1 of this thread, yes, you need to block your box IP address from communicating outside your firewall. I think this is still true.

http://www.dealdatabase.com/forum/showthread.php?t=29020

[NutKase]

The point is that he did say...

Actually, I've been running 4.0 on one box, allowing it to phone home, for about a year now, waiting for them to call so that I can rant. Haven't heard anything yet. Has anyone actually been "talked to", or is this speculation?

So maybe TiVo isn't as 'against' 4.0 on DTivo as was thought. Of course, maybe they just 'missed' him :).


NutKase

[joevv]

[QUOTE=SledgeHammer]Haderak,

run the script as follows:

1) remount the partition as read/write with:

mount -o remount,rw /

2) give the script execute permission with:

chmod 755 superpatch401b.tcl

3) execute it with:

superpatch401b.tcl

After giving the script execute permission I get "no such file or directory"
Can someone please help



(none):/tvbin$ mount -o remount,rw /
(none):/tvbin$ superpatch401.tcl
bash: /tvbin/superpatch401.tcl: Permission denied
(none):/tvbin$ chmod 755 superpatch401.tcl
(none):/tvbin$ superpatch401.tcl
bash: ./superpatch401.tcl: No such file or directory

[SledgeHammer]

After giving the script execute permission I get "no such file or directory"
Can someone please help



(none):/tvbin$ mount -o remount,rw /
(none):/tvbin$ superpatch401.tcl
bash: /tvbin/superpatch401.tcl: Permission denied
(none):/tvbin$ chmod 755 superpatch401.tcl
(none):/tvbin$ superpatch401.tcl
bash: ./superpatch401.tcl: No such file or directory

are you sure thats what the file is called on your disk and that its in the tvbin directory? there has never been a version named "superpatch401.tcl"... the released version is "superpatch401b-FINAL.tcl".

[gtrogue]

According to Tip#1 of this thread, yes, you need to block your box IP address from communicating outside your firewall. I think this is still true.

http://www.dealdatabase.com/forum/showthread.php?t=29020

That's the one I was thinking about. Being that it is a 9 month old thread I didn't know if it was still the case.

[NutKase]

(none):/tvbin$ mount -o remount,rw /
(none):/tvbin$ superpatch401.tcl
bash: /tvbin/superpatch401.tcl: Permission denied
(none):/tvbin$ chmod 755 superpatch401.tcl
(none):/tvbin$ superpatch401.tcl
bash: ./superpatch401.tcl: No such file or directory

Did you open the file with Notepad or any other non unix-aware editor?

NutKase

[blueman2]

That's the one I was thinking about. Being that it is a 9 month old thread I didn't know if it was still the case.

I am not sure it is still the case either; I just wanted to pass along the thread to you.

BTW, you a Ga Tech grad? Nice logo...

[gtrogue]

BTW, you a Ga Tech grad? Nice logo...
Yes I am. Thanks.

[joevv]

Did you open the file with Notepad or any other non unix-aware editor?

NutKase
No, I did not open the file but I did rename it in windowsxp .

[NutKase]

No, I did not open the file but I did rename it in windowsxp .

OK, is the tivoapp file you're trying to patch still named 'tivoapp'?

If not, it won't work without editing the superpatch. I suggest just ensuring that the tivoapp is named tivoapp...


NutKase

[joevv]

are you sure thats what the file is called on your disk and that its in the tvbin directory? there has never been a version named "superpatch401.tcl"... the released version is "superpatch401b-FINAL.tcl".
Yes the file is in the tvbin dir and I renamed it in windowsxp from "superpatch401b-FINAL.tcl" to "superpatch401.tcl"
Would that mess it up?
Also I have a HDVR2 running version 4.0.1-01-2-140. Is that the right patch for my setup?

[joevv]

OK, is the tivoapp file you're trying to patch still named 'tivoapp'?

If not, it won't work without editing the superpatch. I suggest just ensuring that the tivoapp is named tivoapp...


NutKase
I made two copies of tivoapp. 1. tivoapp.bak 2. tivoapp.orig. The original tivoapp is still there.

[NutKase]

I made two copies of tivoapp. 1. tivoapp.bak 2. tivoapp.orig. The original tivoapp is still there.

You have to patch tivoapp (named tivoapp) while it's in another directory.

so cp your tivoapp to /hack or somewhere and put the superpatch there too. Then run it.

You need to be MUCH more explanatory in your posts so we don't have to go back and forth with little short ones pulling the info out.


NutKase

[NutKase]

Yes the file is in the tvbin dir and I renamed it in windowsxp from "superpatch401b-FINAL.tcl" to "superpatch401.tcl"
Would that mess it up?
Also I have a HDVR2 running version 4.0.1-01-2-140. Is that the right patch for my setup?

Yeah, that's the right patch but as I just said you can't patch it in /tvbin.


NutKase

[joevv]

You have to patch tivoapp (named tivoapp) while it's in another directory.

so cp your tivoapp to /hack or somewhere and put the superpatch there too. Then run it.

You need to be MUCH more explanatory in your posts so we don't have to go back and forth with little short ones pulling the info out.


NutKase

(none):/$ mount -o remount,rw /
(none):/$ cd /var/hack
(none):/var/hack$ chmod 755 superpatch401b-FINAL.tcl
(none):/var/hack$ superpatch401b-FINAL.tcl
bash: ./superpatch401b-FINAL.tcl: No such file or directory
(none):/var/hack$ ls
51killer_nonag.tcl log tivoapp
SetupComplete.tcl setmrvname401b-FINAL.tcl tivoapp.bak
etc superpatch401b-FINAL.tcl
(none):/var/hack$

Still not working for me. I've done everything like you said. I FTP the files to the tivo usind FlashFXP, then I run windows Hyperterminal to issue the commands.
What am I doing wrong?
If I run the file before I chmod 755 it it get this:
(none):/var/hack$ superpatch401b-FINAL.tcl
bash: ./superpatch401b-FINAL.tcl: Permission denied
(none):/var/hack$
Once I chmod 755 the file then I get : "No such file or directory"

[jonnydeath]

try:
dos2unix superpatch401b-FINAL.tcl
./superpatch401b-FINAL.tcl

ftping from windows garbles to ASCII and you need to put it back. if you open it in joe, you'll see lots of M's all over the place. This should fix it.

[joevv]

try:
dos2unix superpatch401b-FINAL.tcl
./superpatch401b-FINAL.tcl

ftping from windows garbles to ASCII and you need to put it back. if you open it in joe, you'll see lots of M's all over the place. This should fix it.

Progress!! thanks for the tip jonny. After I FTP the file using red hat linux it finally runs. Now I get this:
(none):/var/hack$ chmod 755 superpatch401b-FINAL.tcl
(none):/var/hack$ superpatch401b-FINAL.tcl
At offset 12581952, expected 0x8c820004 but got 0x00c93021
Aborting...
(none):/var/hack$

By what I read I think this means my tivoapp has hack codes in it...next step would be to get a virgin tivoapp. Can anyone help me with that?

[philhu]

You DID make a backup before you started patching didn't you?

If not, you will need to get one from eDonkey or their equivalents. They post them regularly. It is a 16+meg file, so emailing it to you is not a reasonable solution.

Make sure you get the correct one for your exact version.

There are 3 versions or 4.01b out there.

[joevv]

You DID make a backup before you started patching didn't you?

If not, you will need to get one from eDonkey or their equivalents. They post them regularly. It is a 16+meg file, so emailing it to you is not a reasonable solution.

Make sure you get the correct one for your exact version.

There are 3 versions or 4.01b out there.
I made a backup but it was already patched when I got it so I don't have the original. I have ver. 4.0.1-01-2-140.

[philhu]

My reply stands.

You'll need to go to edonkey, overnet, etc and look for a virgin tivoapp.

4.01b -01 will be tough to find, most now have 4.01b-02

Or you could use a hex editor to remove the 4 bytes that show a different value and put back the original values.

[NutKase]

My reply stands.

You'll need to go to edonkey, overnet, etc and look for a virgin tivoapp.

4.01b -01 will be tough to find, most now have 4.01b-02

Or you could use a hex editor to remove the 4 bytes that show a different value and put back the original values.

He didn't say he had any b version, he said 4.0.1-01, but like you said it will be easier to patch the file he has back to original.

I'm researching it now.


NutKase

[NutKase]

My research confirms that you have a 4.0.1 version of tivoapp. I have a copy and my orginal unpatched version shows 0x00c93021 at offset 12581952 just like yours.

You're using a 4.0.1b superpatch. You should be using the 4.0.1 superpatch that can be found [EDIT] below.


NutKase

[Edit] On second thought, I don't think it's been ported to 4.0.1 (without b).

[NutKase]

Yes the file is in the tvbin dir and I renamed it in windowsxp from "superpatch401b-FINAL.tcl" to "superpatch401.tcl"
Would that mess it up?
Also I have a HDVR2 running version 4.0.1-01-2-140. Is that the right patch for my setup?

No, as I reread your posts, I don't think you have the right patch. There are more than 100 (I stopped counting at 100) differences between the tivoapp binary for 4.0.1 and 4.0.1b

I suspect that this post (http://www.dealdatabase.com/forum/showpost.php?p=176719&postcount=86) contains a typo on the 4.0.1-01 version working with a 4.0.1b-01 superpatch.

I'll try to update the patch for 4.0.1, if I have the time, just to burn in what I learned here (http://www.dealdatabase.com/forum/showthread.php?t=36719).

[EDIT]
I've ported the patch to 4.0.1 and posted it here (http://www.dealdatabase.com/forum/showthread.php?t=36943). I couldn't test it in a tivo running 4.0.1 but it patched my 4.0.1 binary fine and is ready for testing.


NutKase

[blueman2]

I have been able to get copies of 4.01b-01 and 4.0ab-2003 and was about to start the hack process on my HDVR2 (will be using USB2.0 mode with FA120). Are the 'failed during processing' and 'now showing' bugs resolved for these versions? Does it seem pretty stable?

[Haderak]

On my HDVR2 with no other hacks and the FA120 I consistently get the Now Showing bug on -01 and -2003 with the HMO Superpatch. I can do everything else fine, but no matter when I apply the HMO Superpatch I get the Now Showing problem.

I have been able to get copies of 4.01b-01 and 4.0ab-2003 and was about to start the hack process on my HDVR2 (will be using USB2.0 mode with FA120). Are the 'failed during processing' and 'now showing' bugs resolved for these versions? Does it seem pretty stable?

[mhartman]

Are you keeping your network connection? I was getting the now showing bug when I had the USB 2.0 drivers installed. I would get the bug when I lost my connection.

Mike

[NutKase]

SledgeHammer,

I accidently posted this to the 'Files' thread and it was deleted. Your 4.0.1b-01 patch referenced here (http://www.dealdatabase.com/forum/showpost.php?p=175124&postcount=2) appears to be in error.

The array locations are for 4.0.1-01.

Also, I've, hex and md5sum, compared tivoapps, 4.0.1b-01, 4.0.1b-02, abd 4.0.1b.2003 and they are exact matches and so wouldn't need a different patch.

Thanks for you work.

As you can tell I'm still having some fun sorting out all the versions vs type tivo's :)


NutKase

[usa11usa]

Hi, I've done all the step that are needed to get the HMO to install I get no errors and everything says it is ok. I reboot my tivo and look at the system info. it tells me HMO is inactive. what am I doing worng. I have a HDVR2 from Dirctv. software ver says 4.0-01-2-240. can some one help :confused:

[NutKase]

Hi, I've done all the step that are needed to get the HMO to install I get no errors and everything says it is ok. I reboot my tivo and look at the system info. it tells me HMO is inactive. what am I doing worng. I have a HDVR2 from Dirctv. software ver says 4.0-01-2-240. can some one help :confused:

Yes. Go to the developers thread (http://www.dealdatabase.com/forum/forumdisplay.php?f=51). Apply superpatch-4all.

Also, apply the set_mrv_name.tcl, updated by alldeadhomiez which is linked there.

Then post in the superpatch-4all support thread (http://www.dealdatabase.com/forum/showthread.php?t=37197), answering the questions in post #2, about your success or problems.

We'll be glad to help.


NutKase

[jjsmd]

Hi.

I sucessfully got the superpatch for HMO working , but every time I reboot the tivo it looses the name I assigned it in the set_mrv_name.tcl.

I put the following in the rc.sysinit.author file but it still has to be put in manually every time I reboot the Dtiov.

mount -o remount,rw /
chmod 755 set_mrv_name.tcl
set_mrv_name.tcl TIVO2


is there anything I can do to have the following run automatically every time I reboot? Thanks

[NutKase]

Hi.

I sucessfully got the superpatch for HMO working , but every time I reboot the tivo it looses the name I assigned it in the set_mrv_name.tcl.

I put the following in the rc.sysinit.author file but it still has to be put in manually every time I reboot the Dtiov.

mount -o remount,rw /
chmod 755 set_mrv_name.tcl
set_mrv_name.tcl TIVO2


is there anything I can do to have the following run automatically every time I reboot? Thanks

Which superpatch did you install?


NutKase

[jjsmd]

I used

superpatch-4-all-NutKase-0.6.1.tcl


when I run set mrv from a telnet sessionit works ok, it just looses the info if I
reboot.

[NutKase]

I used

superpatch-4-all-NutKase-0.6.1.tcl


when I run set mrv from a telnet sessionit works ok, it just looses the info if I
reboot.

I thought so but didn't want to assume.

I'm not sure why people can dig this old thread up but not be able to find the clearly labeled superpatch-4all support thread. I linked to it above over a month ago.

I guess you didn't even read that post?

Your question has been answered in the superpatch-4all support thread linked above.


NutKase