6.2, Failed while preparing data.

[mateom199]

I've had my (upgraded from 4.01b via slices, hacked) 6.2 HDVR2 running for about 2 months now, and its been phoning home via wireless net connection just fine, until this week. I noticed that the call home earlier this week failed, so I tried running it again a few times, and each time it connect, downloads data, but fails during the final "preparing data" stage. I'm assuming it has something to do with tivo wanting to force a 6.2 upgrade on my box, but its already been upgraded and I have the upgradesoftware=false set in my bootpage, but I'm not positive.

The following is from my tclient log:

May 28 19:01:43 (none) tcphonehome[284]: Log file rotation complete.
May 28 19:01:43 (none) comm[284]: NewSoftware: getting SwSystem name
May 28 19:01:43 (none) comm[284]: NewSoftware: SwSystem 6.2-01-2-121 is already active.
May 28 19:01:43 (none) tcphonehome[284]: Setting callActive to 0
May 28 19:01:43 (none) tcphonehome[284]: setCallStatus called with: Failed state 0
May 28 19:01:43 (none) tcphonehome[284]: LastCallAttempt at 1117306781
May 28 19:01:43 (none) tcphonehome[284]: setting call status to: Failed
May 28 19:01:44 (none) comm[284]: UpdateStatus: Failed phase=0 code=18
May 28 19:01:44 (none) comm[284]: Skipping DataSets cleanup
May 28 19:01:45 (none) DialRequestChore[284]: End nChore=5

Any idea on how to remedy this? Or should I just run fakecall and ignore it?

Thanks

Edit: I am getting the error with a tivoapp patched with NK's superpatch-67all , and also when i replace it with a virgin tivoapp.

[Gunnyman]

how many times do people have to say
"if your unit is hacked, DON'T let it make a daily call?"
/smacks head against a wall....

[mateom199]

In all seriousness, what is the harm? Has anyone had anything bad happen because of calling in with a hacked box, or is it just that bad things could happen, so don't do it?

For the 2 months I've had 6.2, I've let it call in because 6.2 is a valid software version for a dtivo. When I had 4.01b I did not let it call in. Up until two weeks ago it was working fine, no problems. I guess I just don't see what the problem is, but if others have had problems I will stop.

And if your reasoning is that tivo and directv will come down hard on hackers, do you honestly believe a handful of boxes calling in with altered software (assuming they even do a check to see if its been altered) is going to bring forth the wrath of tivo/directv?

[Thinkdiff]

to beat a dead (or maybe not as dead as we thought) horse...

DO NOT LET YOUR HACKED TIVO CALL IN
DO NOT LET YOUR HACKED TIVO CALL IN
DO NOT LET YOUR HACKED TIVO CALL IN

Get the idea?

[Thinkdiff]

In all seriousness, what is the harm? Has anyone had anything bad happen because of calling in with a hacked box, or is it just that bad things could happen, so don't do it?

For the 2 months I've had 6.2, I've let it call in because 6.2 is a valid software version for a dtivo. When I had 4.01b I did not let it call in. Up until two weeks ago it was working fine, no problems. I guess I just don't see what the problem is, but if others have had problems I will stop.

And if your reasoning is that tivo and directv will come down hard on hackers, do you honestly believe a handful of boxes calling in with altered software (assuming they even do a check to see if its been altered) is going to bring forth the wrath of tivo/directv?

The general feeling of the regulars on the forum believe that by calling into TiVo, their servers expect a certain, EXACT set of software to be on the client. If they run a tivoapp check, it would be completely different. Also, with MRV active, your tivo is requesting MRV keys from TiVo that you shouldn't have as a DTiVo.. that can cause even more problems.

And in the end, there is absolutely NO reason to call DTV/TiVo, so you are wasting time and bandwidth.

[mateom199]

Ok, I'll take the advice of the "regulars" but still, even if DTV/Tivo check tivoapps or what have you and realize I'm running a hacked system, what are they going to do? So far in two months they have either a) not realized I'm using a hacked box, or b) realized it but have done nothing. Yes, my previously posted problem is probably due to the fact I'm using a hacked box, but I doubt DTV/Tivo did anything on purpose, its more likely an unintended side affect. It doesn't seem like calling in is as harmful as its being touted as.

Is DTV/Tivo going to cancel my service? With a DTV monthly fee of a little over $100, I doubt it. Also, if they actually threatened, "Oh wow, gee I bought this Tivo off of ebay, I had no idea what it was doing." End of story.

I'll block the daily call, but I still don't buy into the hype. Oh well.

[Thinkdiff]

Ok, I'll take the advice of the "regulars" but still, even if DTV/Tivo check tivoapps or what have you and realize I'm running a hacked system, what are they going to do? So far in two months they have either a) not realized I'm using a hacked box, or b) realized it but have done nothing. Yes, my previously posted problem is probably due to the fact I'm using a hacked box, but I doubt DTV/Tivo did anything on purpose, its more likely an unintended side affect. It doesn't seem like calling in is as harmful as its being touted as.

Is DTV/Tivo going to cancel my service? With a DTV monthly fee of a little over $100, I doubt it. Also, if they actually threatened, "Oh wow, gee I bought this Tivo off of ebay, I had no idea what it was doing." End of story.

I'll block the daily call, but I still don't buy into the hype. Oh well.

I don't think it's so much DTV finding out it's hacked.. it's not wasting time on tivo's server and possibily causing problems by calling in with nonstandard software on the tivo (hacked 6.2 would be considered nonstandard, imo). I, too, don't think anything would or does really happen, but it is the feeling of the community to not find out if something could happen. Better safe then sorry, right?

Besides all that, like I said before. there really isn't a point to calling in.

[fixn278]

Ok, I'll take the advice of the "regulars" but still, even if DTV/Tivo check tivoapps or what have you and realize I'm running a hacked system, what are they going to do? So far in two months they have either a) not realized I'm using a hacked box, or b) realized it but have done nothing. Yes, my previously posted problem is probably due to the fact I'm using a hacked box, but I doubt DTV/Tivo did anything on purpose, its more likely an unintended side affect. It doesn't seem like calling in is as harmful as its being touted as.

Is DTV/Tivo going to cancel my service? With a DTV monthly fee of a little over $100, I doubt it. Also, if they actually threatened, "Oh wow, gee I bought this Tivo off of ebay, I had no idea what it was doing." End of story.

I'll block the daily call, but I still don't buy into the hype. Oh well.

Tivo has been tolerant about Tivo hacking in the past. They do enough to provent hacking to satisfy DTV and the media, but they don't spend their time closing holes/exploits, which they could. Every time someone with a hacked box dials in, it is another opportunity to give them grief and potentially convince them they need to do more to close these exploits. So the real answer is, why tick them off and take the risk? You could potentially spoil it for everyone.

There is no good reason to dial-in and every reason to avoid it.

[rbautch]

If you haven't already, download fakecall.tcl, which is attached to this post (http://www.dealdatabase.com/forum/showpost.php?p=222876&postcount=1) and ftp it to /bin or /busybox. Then put a line in you rc.sysinit.author to run it. This will make your Tivo think it's made a successful daily call.

[PlainBill]

If you haven't already, download fakecall.tcl, which is attached to this post (http://www.dealdatabase.com/forum/showpost.php?p=222876&postcount=1) and ftp it to /bin or /busybox. Then put a line in you rc.sysinit.author to run it. This will make your Tivo think it's made a successful daily call.
Which brings to mind a question that's been bothering me. fakecall.tcl sets some timers so the nag never occurs, but does not actually block the call, nor the timer which starts the call. Is there any reason we don't have a "do_not_call.tcl" script, or some other hack to actually block the call?

PlainBill

[The Only Druid]

Also, with MRV active, your tivo is requesting MRV keys from TiVo that you shouldn't have as a DTiVo.. that can cause even more problems.
Specifically, the problem is this: if you don't call home after using the Superpatch, your system will run fine in perpetuity. If you do call home, your system will download MRV keys which expire every 180 days (I think its 180 days...anyone know if its a diff. number?). The problem is, your system has no way to get new valid keys, which means you'd have to manually renew your keys (I presume using Superpatch? I'm not sure if that's even viable...running superpatch again...or whether that would actually do this) in 6 months.

[mateom199]

Specifically, the problem is this: if you don't call home after using the Superpatch, your system will run fine in perpetuity. If you do call home, your system will download MRV keys which expire every 180 days (I think its 180 days...anyone know if its a diff. number?). The problem is, your system has no way to get new valid keys, which means you'd have to manually renew your keys (I presume using Superpatch? I'm not sure if that's even viable...running superpatch again...or whether that would actually do this) in 6 months.


Ah, very good point. Thanks.

[mateom199]

As a side note, I never order PPV, but if I did, would my box still phone DTV with the purchase? I have debug_board set to true, so the tivo daily call would be routed through the net, but what about the DTV PPV call, is that treated seperately. I've blocked any outgoing connections on my tivo, so it can no longer phone home, but has anyone had experience ordering PPV with a setup like this.

Yea, I know I could just order something and try itmyself...but I'm cheap!

[Thinkdiff]

As a side note, I never order PPV, but if I did, would my box still phone DTV with the purchase? I have debug_board set to true, so the tivo daily call would be routed through the net, but what about the DTV PPV call, is that treated seperately. I've blocked any outgoing connections on my tivo, so it can no longer phone home, but has anyone had experience ordering PPV with a setup like this.

Yea, I know I could just order something and try itmyself...but I'm cheap!

Order PPV online. It's better and easier that way, imo. Better because ALL your boxes will have access, not only the one you ordered on.

[DTimVo_S2]

Specifically, the problem is this: if you don't call home after using the Superpatch, your system will run fine in perpetuity. If you do call home, your system will download MRV keys which expire every 180 days (I think its 180 days...anyone know if its a diff. number?). The problem is, your system has no way to get new valid keys, which means you'd have to manually renew your keys (I presume using Superpatch? I'm not sure if that's even viable...running superpatch again...or whether that would actually do this) in 6 months.

The keys are indeed valid for 180 days, and no, running the superpatch again will not renew the keys, as far as I can tell. It is worth not letting your unit call in just to avoid the eventual breakage of the hacks. And to avoid the angry posts from the forum elders... :D

Maybe a future version of the superpatch can disable the modem to avoid these problems... just a thought.

[rpl]

and each time it connect, downloads data, but fails during the final "preparing data" stage. I'm assuming it has something to do with tivo wanting to force a 6.2 upgrade on my box, but its already been upgraded and I have the upgradesoftware=false set in my bootpage, but I'm not positive.I'm not so sure it has to do with wanting to force an upgrade. I have an SA unit that I need it calling home to get guide data and its doing the same thing, connecting and then failing when it tries to process the data. I just let my box update to the latest version for SA units (7.1) yesterday and now I have this problem. It currently has two days of guide data and the call home fails to process any more downloads. The Tivo is currently unhacked. I'm going to try a clear and delete everything and see if that flushes out the problem in the database.

[mateom199]

The keys are indeed valid for 180 days, and no, running the superpatch again will not renew the keys, as far as I can tell. It is worth not letting your unit call in just to avoid the eventual breakage of the hacks. And to avoid the angry posts from the forum elders... :D

Maybe a future version of the superpatch can disable the modem to avoid these problems... just a thought.

I guess I'm gonna have to do a clean install with a virgin 6.2 image before November 15th, 2005...

I'm now a believer of never letting your hacked box phone home :)

..unless of course theres someway to reset the mrv/musicphoto certs without doing a clean install

[psxboy]

I'm not so sure it has to do with wanting to force an upgrade. I have an SA unit that I need it calling home to get guide data and its doing the same thing, connecting and then failing when it tries to process the data. I just let my box update to the latest version for SA units (7.1) yesterday and now I have this problem. It currently has two days of guide data and the call home fails to process any more downloads. The Tivo is currently unhacked. I'm going to try a clear and delete everything and see if that flushes out the problem in the database.

Look at your Otclient log to see where it's failing. I was having a similar problem before I upgraded to 7.1b (from 4.0.1b). In my case, the 7.1b install had been sitting in MFS for over a month & I guess it "timed out" & got deleted by the normal db maintainence. The next time the Tivo called in, it tried to download the 7.1b upgrade again, but since I was using the ADD/DROP keyring patch I no longer had the correct SW key to decrypt the swsystem slice. Anyway, the Tivo said it "Failed while preparing data" or something like that, but the Otclient log revealed it was the swsystem slice that was the culprit. Once I re-loaded the 7.1b software manually (I had previously decrypted the swsystem slice and had all of the other slices saved) the problem went away & it was happily downloading guide data again.

Regarding the MRV keys in 6.2... if you use the "setmrvname" script for 6.2, it will generate a valid MRV certificate for you. If the certificate does expire (which I doubt... I'm thinking it doesn't expire at all) you can just re-run the setmrvname script again to get a new, valid cert. No calls home, no re-running the superpatch script, etc.

-psxboy

[rpl]

In my case, the 7.1b install had been sitting in MFS for over a month & I guess it "timed out"
Tivo said it "Failed while preparing data" or something like that, but the Otclient log revealed it was the swsystem slice that was the culprit. Once I re-loaded the 7.1b software manually
I had let my tivo do the nightly reboot for the past month also.

Thanks for the tip psx.

[HuMan321]

My system never called home after hacking and I notice far down in the system information screen it says some info about the issueing of tickets
Ticket
issued Friday June,3rd 2005
days valid 180
service level 1 A
sl 1 expiration Wednesday November 30,2005
service level 2
sl2 expiration Wednesday November 30,2005
service level 3 A
behavior setidentsring default
current expiration date 13118

Can anyone tell me more about this or flip me a link. The last thing I want is a surprise in November
Thanks

[HuMan321]

My system never called home after hacking and I notice far down in the system information screen it says some info about the issueing of tickets
Ticket
issued Friday June,3rd 2005
days valid 180
service level 1 A
sl 1 expiration Wednesday November 30,2005
service level 2
sl2 expiration Wednesday November 30,2005
service level 3 A
behavior setidentsring default
current expiration date 13118

Can anyone tell me more about this or flip me a link. The last thing I want is a surprise in November
Thanks

Update
This message cleared up after I did a clear and delete all. The only dates now are from 1969 and I can't see any expiration