PDA

View Full Version : HMO superpatch



CapablePerson66
06-02-2004, 10:05 PM
Attached is the HMO superpatch for users running v4.0 on their HDVR2s. It enables all HMO/MRV functions (and then some)!

Specifically, it:

enables Music and Photos
enables Multiroom Viewing (MRV)
decrypts all HMO/MRV network traffic
disables the daily nag screen when your box hasn't connected to the service for more than 30 days
decrypts all future records (as provided by other patches on this forum)
other various stuff


There are two patches, and ideally each needs to be run only once. The superpatch.tcl script patches your tivoapp binary. For directions on how to apply this sort of patch, please refer to other posts in this forum. After applying the patch, reboot your TiVo.

Once your system is up and running again, think of a name you want to call your TiVo. This is what other TiVos on your network will see in their Now Showing list. Give the name as an argument to the set_mrv_name.tcl script. This is necessary because the superpatch overrides all the normal TiVo certificate controls, which is where the network name usually comes from. You should only need to run this once, unless you've deleted your previous fake certificate.

This patch is specifically targeted at v4.0 users, and I will not be providing similar patches for other versions. This is to prevent the possiblity of theft of service by SA S2 owners (who are running on other versions). I strongly discrourage anyone from porting the superpatch to other TiVo versions.

I may also be releasing applications that take advantage of the decrypted HMO/MRV network layer (think: pulling recordings directly from your TiVo to your PC using TiVo's own MRV protocol).

Anyhow, this is what many people have been waiting for, so enjoy!

mrblack51
06-03-2004, 12:14 AM
rules related to this script, until otherwise changed:

don't talk about ways to downgrade your SA to 4.0
don't talk about ways to port it to 4.0.1b+
subject will be closed if HMO ever comes out for the DTiVos

do not use this for service theft. if you are an SA owner, pay for HMO, its the right thing to do. we do not condone service theft.

JJBliss
06-03-2004, 12:26 AM
To follow up on mrblack51's comments.

The following will put you in a very bad light:

If you ask, hint at, beg or discuss methods to downgrade your SA to 4.0, you will be warned, then banned for a period of time, until you learn how to follow directions.

If you talk about ways to port it to 4.0.1b+ you will be warned, then banned for a period of time, until you learn how to follow directions.

This entire thread will be deleted if HMO ever comes out for the DTiVos

do not use this for service theft. if you are an SA owner, pay for HMO, its the right thing to do. we do not condone service theft.

The logic behind this is:

Since only DTivo users can relatively easily keep their units at 4.0, this tivoapp patch and script is really only usefull for them.

Since DTivo users cannot purchase the HMO or MRV option from DTV directly, this cannot cost DTV any money or revenue, since it is not a service that is for sale by them.

Since SA2 users cannot keep their units downgraded at 4.0 indefinitely, this hack is not for them, as new versions of the OS will be downloaded via the nightly call, which they have no choice but to do in order to get the guide data.

If you have any questions, feel free to ask them, but remember that the decision and commentary from the moderators and administrators of this forum are final.

Enjoy

JJBliss

alldeadhomiez
06-03-2004, 02:21 PM
The original poster mentioned that porting this to other versions was discouraged. Since this posting is made available to 4.0, thus freeing D-Tivo users to apply and use it, what would be the direct harm in making this work for 3.1.1b/3.1.1c for D-Tivo users?

The 3.x series has no HMO code whatsoever, so there's nothing there to patch.

Since this is a development forum, please post non-technical questions such as this in the support or newbie forums. Here is a thread (http://www.dealdatabase.com/forum/showthread.php?t=35244) started for that very purpose.

ret
06-07-2004, 04:07 AM
Does anyone have a break down of what each line in the script is targeting/patching.. -Thanks

mrblack51
06-07-2004, 11:24 AM
Does anyone have a break down of what each line in the script is targeting/patching.. -Thanks

each line? well, the script is just a generic patching script. as for each patch location, if you look at the locations, some are contiguous, some are spaced. in general, many these patches bypass a function and force the return value to 0 or 1 depending on what is needed.

ret
06-07-2004, 04:13 PM
What I was getting at was if anyone could break down the patch.. This part does this.. This part does this... I already have most of the patchs this patch provides. I only want a segment of it, for example I'm already not scrambling my recordings, It seems that this script is doing this as well but in a different location. I was wondering if anyone had commented patch providing information on what each location change is doing.. -thanks

mrblack51
06-07-2004, 10:30 PM
What I was getting at was if anyone could break down the patch.. This part does this.. This part does this... I already have most of the patchs this patch provides. I only want a segment of it, for example I'm already not scrambling my recordings, It seems that this script is doing this as well but in a different location. I was wondering if anyone had commented patch providing information on what each location change is doing.. -thanks

actually, the NoCSO patch is in the identical location. the only difference is different ways to get the same result (move $v0, $0 <=> add $v0, $0, $0 for example). have you decoded the purpose of any of the other patches? which specific segment are you reffering to?

lenroc
06-09-2004, 06:16 AM
Do the rules here change at all now that HMO is (or will soon be) free for all SA S2 users?

http://news.com.com/TiVo+cuts+prices+on+services/2100-1041_3-5229146.html

I guess the "Free Trial" of HMO won't be ending ;)

Juppers
06-09-2004, 02:09 PM
While it is becoming free for SA users, there is no guarantee that if and when 4.0 is released to Directivos, that it will be free there. The rules should apply for any platform or software version where there is a purchase requirement to enable the functionality.


Do the rules here change at all now that HMO is (or will soon be) free for all SA S2 users?

http://news.com.com/TiVo+cuts+prices+on+services/2100-1041_3-5229146.html

I guess the "Free Trial" of HMO won't be ending ;)

MuscleNerd
06-09-2004, 05:03 PM
I don't know if the patch offers anything that "real" HMO doesn't, though
Part of what the patch does is keep the MRV and HMO traffic unencrypted, which can be *very* useful for those developing 3rd party apps to interface via those protocols.

littlerm
06-09-2004, 05:54 PM
So now that HMO is included with standard subscriptions could I backup my SAS2 Tivo and restore it on my HDVR2 drive and have HMO without using the SuperPatch? I may give it a try tonight.

MuscleNerd
06-09-2004, 06:19 PM
No, that won't work.

MuscleNerd
06-11-2004, 10:36 AM
Because of the way the superpatch disables encryption and the use of hostname certificates, only machines with the superpatch applied can talk to each other.

alldeadhomiez
06-11-2004, 03:15 PM
do not use this for service theft. if you are an SA owner, pay for HMO, its the right thing to do. we do not condone service theft.

The logic behind this is:

Since only DTivo users can relatively easily keep their units at 4.0, this tivoapp patch and script is really only usefull for them.

Since DTivo users cannot purchase the HMO or MRV option from DTV directly, this cannot cost DTV any money or revenue, since it is not a service that is for sale by them.

As alluded to earlier, the HMO service is no longer being sold to any users running 4.x software, so discussion of HMO patches on 4.0.1* is now permissible as it will not give TiVo a financial incentive to bother us.

Reminder: this thead is in the development section and should only contain technical posts, announcements/info, and such. If you have non-technical questions or other comments, they belong in one of the HMO support threads.

rc3105
07-18-2004, 07:35 PM
Okay so has anyone figured out a way to enable HMO on SA2 ???
the patch at the start of this thread does

what are you trying to ask? :confused:

philhu
07-19-2004, 05:11 PM
the patch at the start of this thread does

what are you trying to ask? :confused:

Actually, the way this thread reads is that it will NOT work on an SA2 since the SA2 keeps taking system/os updates.

So, will this work on an SA2? And either way, why would you do it, instead of just allowing Tivo to turn on HMO and using Sleeper's iso disk and the unscramble patch?

alldeadhomiez
07-19-2004, 05:32 PM
Actually, the way this thread reads is that it will NOT work on an SA2 since the SA2 keeps taking system/os updates.

So, will this work on an SA2? And either way, why would you do it, instead of just allowing Tivo to turn on HMO and using Sleeper's iso disk and the unscramble patch?

If you pull down guide data from the official TiVo servers, this will not work (without a few modifications).

If you run a software version other than 4.0, it will not work. If you make daily calls to TiVo, you will not be running 4.0 for long.

Otherwise, you should be in good shape.

I still don't understand the obsession with porting this patch to other software versions. If you have an SA, run 4.0.1b and use the free HMO that comes with your sub. If you have a DTiVo or live outside the USA, run 4.0 and use the superpatch.

aristoBrat
07-19-2004, 05:57 PM
I still don't understand the obsession with porting this patch to other software versions. If you have an SA, run 4.0.1b and use the free HMO that comes with your sub. If you have a DTiVo or live outside the USA, run 4.0 and use the superpatch.
For me, it's the assumption that little things have changed since 4.0 (for the better). For example, 4.0.1b doesn't report my DTiVo as a "COMCAST" box. What else might have changed?

Anyhow, I'm content with 4.0 on my DTiVo, but I don't think I'd say NO to a 4.0.1b superpatch. :D

ronnythunder
07-19-2004, 06:30 PM
I still don't understand the obsession with porting this patch to other software versions.well, some folks have both sas2 and directivo, and want to share shows between them. that requires the superpatch or variation thereof on both machines.

ronny

MuscleNerd
07-21-2004, 01:22 AM
I still don't understand the obsession with porting this patch to other software versions.
For at least some, it provides the ability to transfer shows between your TiVo and PC/Mac using the native MRV protocol (because of the decrypted network layer).

tivomaster
07-21-2004, 08:39 AM
For at least some, it provides the ability to transfer shows between your TiVo and PC/Mac using the native MRV protocol (because of the decrypted network layer).

Interesting...
Is there a development project already afoot to decode the MRV protocol? I have seen 0 discussions on the subject. I have been debating buying a second HDVR2 for just that purpose but don't have the extra 100-200 dollars to feed the ebay demon right now. If there is already a development project in place I would be happy to assist.

Where is the meeting place and what is the secret handshake?

MuscleNerd
07-21-2004, 11:47 AM
Interesting...
Is there a development project already afoot to decode the MRV protocol?
All of its secrets lie in the IDL files (i.e. /tvlib/idl/*tvbin). The IDL files describe all of the state transitions (of many things, not just MRV). And the IDL format is very regular once you stare at it long enough (it's even somewhat self-describing).

tivomaster
07-21-2004, 01:21 PM
All of its secrets lie in the IDL files (i.e. /tvlib/idl/*tvbin). The IDL files describe all of the state transitions (of many things, not just MRV). And the IDL format is very regular once you stare at it long enough (it's even somewhat self-describing).

Ok, so what I am hearing is that there is no unified development effort afoot right now. I will start looking at the IDL stuff...

alldeadhomiez
07-27-2004, 02:08 AM
If you pull down guide data from the official TiVo servers, this will not work (without a few modifications).


# kill blowfish globally (original superpatch)
#ff9730: 8c820004 8cab0000 -> 03e00008 00000000
#ff9ce4: 8c820048 8cab0000 -> 03e00008 00000000

# kill blowfish selectively (new)
ff9724: 3c1c0f06 279c504c -> 03e00008 00000000
ff9cd8: 3c1c0f06 279c4a98 -> 03e00008 00000000
8d3f00: 033cc821 8f394aac -> 3c190100 27399ce4
8d22f0: 033cc821 8f396124 -> 3c190100 27399730
ffa3ec: 033cc821 8f396124 -> 3c190100 27399730
ffa444: 033cc821 8f396124 -> 3c190100 27399730
8d223c: 033cc821 8f396124 -> 3c190100 27399730

MuscleNerd
07-27-2004, 06:55 PM
Ok, so what I am hearing is that there is no unified development effort afoot right now. I will start looking at the IDL stuff...
drnull has started a technical discussion about the IDL structures at alt org.

philhu
08-03-2004, 01:10 AM
# kill blowfish globally (original superpatch)
#ff9730: 8c820004 8cab0000 -> 03e00008 00000000
#ff9ce4: 8c820048 8cab0000 -> 03e00008 00000000

# kill blowfish selectively (new)
ff9724: 3c1c0f06 279c504c -> 03e00008 00000000
ff9cd8: 3c1c0f06 279c4a98 -> 03e00008 00000000
8d3f00: 033cc821 8f394aac -> 3c190100 27399ce4
8d22f0: 033cc821 8f396124 -> 3c190100 27399730
ffa3ec: 033cc821 8f396124 -> 3c190100 27399730
ffa444: 033cc821 8f396124 -> 3c190100 27399730
8d223c: 033cc821 8f396124 -> 3c190100 27399730

Hey

I was looking through patches for this.

Will these changes you've shown here which kills the key stuff selectively, will it fix the current SA S2 problem of 'Failed while loading series' when you d/l from tivo directly for guide data?

alldeadhomiez
08-03-2004, 01:22 AM
Hey

I was looking through patches for this.

Will these changes you've shown here which kills the key stuff selectively, will it fix the current SA S2 problem of 'Failed while loading series' when you d/l from tivo directly for guide data?

It did for me. Since this is a patch against 4.0 it will need to be ported to whatever version you are running.

MuscleNerd
08-05-2004, 03:58 PM
Just a heads up for set_mrv_name.tcl...

If you want to include spaces in the name you give your TiVo, use this kind of syntax:


set_mrv_name.tcl "{foo bar}"

(Those are curly braces in there....but they won't appear in the final name that TIVo uses)

NutKase
08-07-2004, 12:19 AM
It did for me. Since this is a patch against 4.0 it will need to be ported to whatever version you are running.

The script is ported to 4.0.1b-02 here (http://www.dealdatabase.com/forum/showthread.php?t=36719) and you can thank ADH and rc3105 for their expertise and the 'others that did the heavy lifting' for the updated HMO superpatch script.

This works, so far, for 4.0.1b-02 SA S2 Tivo's by preventing the "Failed during processing" errors... and may work for other tivos with the 4.0.1b-02 software version.

NutKase

alldeadhomiez
08-07-2004, 05:39 PM
Here is the version of set_mrv_name.tcl I am running. Changes:

- detects 4.0 and uses the NAMETABLE-2 key prefix for 4.0, TIVOVID_2 key prefix for anything else

- clears NAMETABLE, TIVOVID, and MRV keys from /State/Keyring, but leaves others intact (it is probably not a good idea to clobber keys needed to load the guide on an SA)

- works with hostnames which contain spaces

my0gr81
08-20-2004, 02:41 PM
Attached is the HMO superpatch for users running v4.0 on their HDVR2s. It enables all HMO/MRV functions (and then some)!

Specifically, it:

other various stuff




Can you elaborate on this. I looked at the offsets and tried to cross reference with Sleeper's thread on tivoapp patches, and there are some offsets that don't appear either here or there.

I searced for those offsets and didn't find a referrence to them. I don't hve those exact numbers handy right now or I would include them in.

Thanks

my0gr81
09-02-2004, 06:31 PM
Attached is the HMO superpatch for users running v4.0 on their HDVR2s. It enables all HMO/MRV functions (and then some)!

Specifically, it:

enables Music and Photos
enables Multiroom Viewing (MRV)
decrypts all HMO/MRV network traffic
disables the daily nag screen when your box hasn't connected to the service for more than 30 days
decrypts all future records (as provided by other patches on this forum)
other various stuff


There are two patches, and ideally each needs to be run only once. The superpatch.tcl script patches your tivoapp binary. For directions on how to apply this sort of patch, please refer to other posts in this forum. After applying the patch, reboot your TiVo.

Once your system is up and running again, think of a name you want to call your TiVo. This is what other TiVos on your network will see in their Now Showing list. Give the name as an argument to the set_mrv_name.tcl script. This is necessary because the superpatch overrides all the normal TiVo certificate controls, which is where the network name usually comes from. You should only need to run this once, unless you've deleted your previous fake certificate.

This patch is specifically targeted at v4.0 users, and I will not be providing similar patches for other versions. This is to prevent the possiblity of theft of service by SA S2 owners (who are running on other versions). I strongly discrourage anyone from porting the superpatch to other TiVo versions.

I may also be releasing applications that take advantage of the decrypted HMO/MRV network layer (think: pulling recordings directly from your TiVo to your PC using TiVo's own MRV protocol).

Anyhow, this is what many people have been waiting for, so enjoy!

OK, since there is now a new version of tivoapp 5.x, is it kosher/halal to talk about porting this to that version?

Mods: feel free to delete if you find this inappropriate. Since this is a dev thread and not a support thread, I think we can talk about the possibilities, challenges and potential effects of doing it without actually publishing the actual patches, offsets etc.

mrblack51
09-03-2004, 01:49 PM
OK, since there is now a new version of tivoapp 5.x, is it kosher/halal to talk about porting this to that version?

Mods: feel free to delete if you find this inappropriate. Since this is a dev thread and not a support thread, I think we can talk about the possibilities, challenges and potential effects of doing it without actually publishing the actual patches, offsets etc.

http://www.dealdatabase.com/forum/showpost.php?p=182404&postcount=3

the problem lies with the fact that tivoPlus is directly tied to hmo in 5.x. tivoPlus is not free, but hmo is free with tivoplus. tivo basic does not include hmo. as such, bypassing tivoplus would be service theft at this point.

my0gr81
09-03-2004, 02:05 PM
http://www.dealdatabase.com/forum/showpost.php?p=182404&postcount=3

... hmo in 5.x. tivoPlus is not free, but hmo is free with tivoplus. tivo basic does not include hmo. ...

Kind of a "reverse catch 22". My head is spinning just thinking about it. :confused:

What happens when TIVO finaly backports all the new software to the current SA S2 units or is it even worth the development efforst? :eek:

alldeadhomiez
09-03-2004, 02:19 PM
What happens when TIVO finaly backports all the new software to the current SA S2 units or is it even worth the development efforst? :eek:

They tend not to bother. :(

Remember that the "superpatch" is made up of a number of different changes to the binary. What are you trying to do with it? If you just want to rig your subbed 5.x box so that it can talk to your superpatched 4.x boxes, you don't need to bypass service authorization.

my0gr81
09-03-2004, 02:36 PM
- MRV between a SA S2.5 and a SA S2 that has been patched.

This is not to condone service theft as that is illegal, immoral and just plain wrong. There are instances where there is a need to get your own guide data instead of the TIVO supplied guide data, UK, AU, CA is one example of this I understand, that the new software lets you do that as long you have a subscription. The only issue with that is, once a month (or whatever) you connect to the mothership to get the new keys, but it also wipes out your current data at the same time and you have to rebuild and re-index.

I know, with time, we will find ways to work around most of these issues. I understand that we want to remain legit, and ensure that TIVO has a steady revenue stream so that they keep coming up with new services and products. Let's keep sleeping dogs lie for now.

rc3105
09-03-2004, 02:46 PM
you're mixing apples & oranges


the superpatch allows for mrv on boxes where mrv isn't an option (dtivo) and unencrypted transfers between legit boxes


custom guide data & use outside tivo serviced areas is a WHOLE 'nother discussion


buying a 2.5 unit specifically for use outside subscribable areas is definatly a dark grey area and we really don't want to discuss that here