Shows still scrambled after applying CSO Patch

[NoCalME]

I've killhdinitrd'd my SD-DVR80 with a 3.1.1c kernel from the LBA 48 PTV Upgrade CD. I'm running software version 3.1.1e.

I have telnet, FTP, and extraction working. The last step was to disable encryption using Alphawolf's patch, i.e. echo -ne "\x3C\x02...". I followed the directions for backing up tivoapp in the thread-- triple checking my typing before hitting ENTER after each command.

Since I'm running software version 3.1.1e, I typed in:
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=6500332

The result was:
4+0 records in
4+0 records out

I then typed:
mount -o remount,ro /
reboot

After reboot, I recorded a show for 15 min. When I run ciphercheck.tcl, it tells me the show is still scrambled??? Any ideas what is wrong?

[WRabbit8]

I've killhdinitrd'd my SD-DVR80 with a 3.1.1c kernel from the LBA 48 PTV Upgrade CD. I'm running software version 3.1.1e.
[..clip..]
reboot
After reboot, I run ciphercheck.tcl, it tells me my recordings are still scrambled??? Any ideas what is wrong?
The NoCSO patch only disables scrabbling for new recordings you make. If you want to unscramble your current recording, you will have to go through a somewhat tedious process. It does work - I have done it twice myself. See this thread for the gory details:
http://www.dealdatabase.com/forum/showthread.php?t=39207

-WR

[NoCalME]

The show I ran ciphercheck.tcl on was a newly recorded program after applying the patch and rebooting. My previous post did not specifically point this out, so I have edited it to say so. The one 15 min. recording is the only show I have on the hard drive.

[PlainBill]

I can say that the only answer is that you made a mistake somehow. I have used Alphawolf's procedure several times, including on 3.1.1e. The only time it failed, the problem was between the keyboard and the chair. :o

The only obvious place for confusion is the character preceding dd is not a lower case L or an upper case i, but the pipeline symbol |

Alternatively, use a hex editor to make this change.

PlainBill

[AlphaWolf]

Try making sure that ciphercheck.tcl is able to execute mfs_export. If you don't have mfs_export and/or the script can't find it, it will misreport the crypto status. It'll probably say that the CSO isn't set but the show is encrypted, which in reality can't happen unless you really screw something up.

[eastwind]

Try making sure that ciphercheck.tcl is able to execute mfs_export. If you don't have mfs_export and/or the script can't find it, it will misreport the crypto status. It'll probably say that the CSO isn't set but the show is encrypted, which in reality can't happen unless you really screw something up.
I've done that before. Can't say for sure how, but I remember it was when I was unscrambling my (pre-hacked) recordings in place.
But then I've done a lot of things that I'd never seen reported before. Like booting from hda3 with hda7 mounted and hda4 as my root (as far as bootpage knew). Just happened that I dd'd my hda7 to hda4 and didn't edit the /etc/fstab to make it mount the right partitions.

ew

[NoCalME]

I'm positive the show is in fact encrypted as Vsplit will not process the file. The error message Vsplit spits out typically means the encryption has not been disabled according to searches on the topic.

So it appears that I messed up something during the hacking process--not hard to believe. Oh well, nothing worthwhile ever comes easy right.

[eastwind]

I'm positive the show is in fact encrypted as Vsplit will not process the file. The error message Vsplit spits out typically means the encryption has not been disabled according to searches on the topic.

So it appears that I messed up something during the hacking process--not hard to believe. Oh well, nothing worthwhile ever comes easy right.
You don't by any chance have the unscramble tools in you path do you?

ew

[NoCalME]

No I don't.

I've decided it's easier to start from scratch then to figure out how to fix what is wrong--if that's even possible. Hopefully the second time around will get me to home plate instead of being stranded at 3rd.

[PlainBill]

No I don't.

I've decided it's easier to start from scratch then to figure out how to fix what is wrong--if that's even possible. Hopefully the second time around will get me to home plate instead of being stranded at 3rd.
It depends on what you mean by 'starting from scratch'. If everything is working, EXCEPT disabling encrytion, simply restore your original copy of tivoapp and try again. As I mentioned above, try using a hex editor; it gives you confidence you are editing the correct values. Then, of course, make sure you copy the edited file back to the TiVo, not the original like I did.

PlainBill

[NoCalME]

I'm up and running with the noCSO patch working this time:)

Apparently whatever mistake I made on attempt #1 was not repeated this go-around. Thanks to all that replied to my post.