Inconsistent results with hack attempts

[srs]

I have two S2 DTiVos. I have several 120gb maxtor drives. The twinbrothers ftp site is on my server, so I have all the tools. I have a couple of fully hacked S1 DTiVos.

I don't think I'm stupid. (others may disagree)

I have tried both the U5hacked image method and the monte method. Both work ......... ONCE.

I also tried the howto on hostfreedom.com/tivo with the same results.

Clear and Delete works to fix the 51 error and I go thru the initial guided setup. After rebooting, I NEVER EVER EVER get back to a running TiVo. If I reimage, it boots.

WTF?

This is on both S2's, with 4 different drives both 40 and 120gb.

Also, the 51killer.tcl script.... well, the OS tells me it doesn't exist. I can cat it, I can chmod it, I just can't run it.

Again, WTF?

So far I have spent (wasted?) over 15 hours fighting these damn things.

thanks.
Steve

[mrblack51]

try doing a tivosh ./51killer.tcl

[TheWickedPriest]

I think we'll need more details of what you did and what the results were.

As for running the script, it has to have the executable bit set, and it has to be in the path, or else you have to specify the path explicitly; e.g., "./51killer.tcl". This applies to all executables and scripts. When telling bash to run a program, it only looks in the directories specified by the "PATH" environment variable; it does not check the current directory, unless "." happens to be in the PATH.

[srs]

I tried chmod +x 51killer.tcl, then ./51killer.tcl

Thats how i run any other script. On this one, the os simply responds that it can't find ./51killer.tcl

As for what I did:

I downloaded the u5-151-hacked.mfs file and put it on a cdrom. Booted from mfstools floppy with cd on hdb, 120gb empty drive on hdc. mounted the cd on /mnt/cdrom and typed:

mfsrestore -s 127 -zbpi /mnt/cdrom/u5-151-hacked.mfs /dev/hdc

It did its thing and reported sucess. mounted the drive in the s2 with the jumper on CS. (only drive). booted ok, and made me run thru the guided setup. good numbers on the birds, but failed to recognize them in the next screen (apparently something odd going on at DirecTV, see tivocommunity discussions), told it I would fix it later and went on. Ran Clear and Delete everything since I can't make 51killer work. It rebooted and cleared. ran thru guided setup again, same deal. rebooted and got

"Welcome, Powering up" and nothing else.

Lather, rinse, repeat with the jumper set to Master with the exact same results.

suggestions?

[srs]

So i moved on:

I printed rev0.12 of cobelli's howto. (very well written) I followed each step exactly up to section four.

At this point I could care less about ethernet or anything other than just recorded a show, so I hook it to the dish. Run guided setup as above, same issues.

SAME EXACT FAILURE.

(@#*&$(@#&*$)!@#*(&#@$(*&!

this was on a different s2.

[JJBliss]

make sure 51killer has been transfered properly, and has no "^M" characters at the end of every line.

If was transfered as ascii, or wasn't saved as unix, that might happen

[SR712]

There is a DOS2UNIX.zip (that has DOS2UNIX.EXE) available in one of the stickys that can be run on your windows box to convert windows corrupted files to a unix friendly format.

[TheWickedPriest]

Thats how i run any other script. On this one, the os simply responds that it can't find ./51killer.tcl

In that case, it probably means that it can't find the interpreter. On the first line of the script, you'll see something like "#!/tvbin/tivosh". /tvbin/tivosh is the path to the interpreter used to run the script; if this line is messed up, the script won't run. As JJBliss and SR712 have said, that could happen if the line gets a stray '^M' added.

As for your main problem, I still have no advice, sorry. In my case, I never even had to deal with error 51. The one real problem I had was that I couldn't get a U5 kernel to work with a 3.1.0 root; I ended up using a monte system booting with U5 kernel + root, and from there, switching to my original 3.1.0 setup with hacked kernel etc.

mfsrestore -s 127 -zbpi /mnt/cdrom/u5-151-hacked.mfs /dev/hdc

You probably ought to include an 'x' in the options since you're restoring to a larger drive, though I think it should work without it. And I'd leave out the 'b'. Oh, and add "-v 127" for good measure.

[DealDataLOVER]

I don't know if this will help but the 51killer.tcl has been fixed on the tivostuff.com website to UNIX. (my ftp wouldn't send it so I had to use another. I used cuteftp) I also used the hacked u5 and got the 51 error, but it was easily fixed thanks to this site.
-----------------------------------------------------------------------------
send to the tivo to Var/Hack folder (then use bash or telent)

<Type to set file permission>

cd /var/hack
chmod 777 51killer.tcl

<Type to execute>

cd /var/hack
./51killer.tcl

Type yes and hit enter

make sure it worked (it will tell you)

then type restart and hit enter, and 51 is gone :)
---------------------------------------------------------------

Cheers!

[cobelli]

Sorry you are having problems :(
As far as the time using my guide, there is a bug with the bootpage stuff. When you rewrite the bootpage, you have to use the same number as was originally reported. This should have been fixed a while ago, but I've been having server problems. I'll have rev 0.13 up today.

To try and troubleshoot your problem, I have a few questions:
What happens if you don't hook the box to the satellite? Can you keep rebooting?

If not, what happens if you don't clear and delete? Can you keep rebotting?

Can you pull one of the hard drives and look at the logs? Anything interesting in there?

Hopefully some of this will lead to your problem.
BTW, thanks for the compliment :)

Good luck!
- Cobelli

[srs]

I printed the 0.13 version of cobelli's HowTo and followed the instructions precisely.

It worked! Well mostly, I did find one small typo in step 20. The name of the backup file is not the same as the name used in the earlier step.

I did not have any luck with the ethernet part. On the TiVo website, one of the FAQs lists the Microsoft MN-110 USB->ethernet adapter as one that works, but it does not work with the pegasus.o or ax8817x.o drivers. I have no idea what chip it is. Anyone know?

51killer.tcl works after I downloaded a new copy from the site mentioned in this thread.

Thanks!
Steve

[srs]

I got a Linksys USB100TX. I now have the ethernet part working too!

Thanks for the guide and for the suggestions!