Screwed and need help

[Sincere0219]

well I did the monte auto iso. Tried to get some direction but was told to search so I searched some more read and did what I thought was correct from some thread followed it to the t and didnt work. messed up the hd so did a restore w/ same monte auto iso but seems my back up I made is corrupted because I got failed along the way. I downloaded the u5-151-hacked.mfs image and want to make sure before I continue. Do I burn that image to cd, boot from that cd, and follow hindales, section 8, to restore that image back to my otivo. In need of real assistance now willing to pay if need be or give an extra P4 that I got w/ new room receiver. I have a HDVR2

[pkpss]

I'll take the P4, ;)

If you have the mfs, just boot into linux (Johnny Death's or mfstools). Then, assuming you use the same setup as Cobelli's or a lot of the guides floating around, mount the FAT32 drive (which should have the hacked image or any image floating around that is a backup). Next command is,

mfsrestore -s127 -xzpi /mnt/c/*.mfs /de/hdc

You probably know the commands for mfsrestore as well. HTH.

[Sincere0219]

deal. How do I get the image I downloaded from my xp machine to my fat32 drive (its a another hd). Do I burn the image to cd and some how boot into linux transfer to my fat 32 from cd??? if your on line my yahoo is Sincere02199

[pkpss]

You can do that, or if you don't want to waste a CD, just have the XP HDD and the FAT32 HDD going. Boot into XP and just transfer the file over. You could easily burn the file to CD, mount, then copy as well.

[NutKase]

You've got to be kidding. If you're giving away a p4 I'll help you monte AND unscramble for your house. Maybe even tell you about extracting for your sailboat.

All joking aside, all this information is here.

Here's some more searching advice.

DON'T search.

Print out at least 3 sticky'd threads with monte and BASH in the title.

Read them 4 times, with no alcohol involved, and you'll be far more advanced and ready to tackle anything ;)

NutKase

[Sincere0219]

I have done nothing but reading. I was up till 430a last nigh woke up and have bee reading. This is what I tried without success to do a restore w/ dt2.3.1b.mfs. I burned the dt2.3.1b.mfs to cd and another cd with mfstools right. Then I shut down my xp machine put my OTIVO as Secondary master, my blank 20gb fat32 hd as Primary master and cd rom as primary 2nd. Then I did these exact steps:

http://generationtivo.com/index.php?type=monte&page=restore&pTitle=Monte:%20Restore&pColor=O

once I got to step 9 I typed in mfsrestore then hit enter because restore my original drive in returns I got the usage: mfsrestore [options} Adrive Bdrive and all the different options and brought me back to that "mount/c" (whatever it was cant remember) I then typed in the zpi (because the Otivo is 40gb) /mnt/c/dt2-3.1b.mfs (because thats the name of the files I have burned on cd or is that the problem) /dev/hdc and I get

sh: zpi: command not found
I did a ls and got
disk2/ (in blue)
I am dead serious where I will give a P4 to help get me up and running fully!!! I should be back on line around 5p est my yahoo is Sincere02199

[Sincere0219]

or am I suppose to convert the dt2.3.1b.mfs to dt2.3.1b.bak some how??? Really lost

[pkpss]

Since you have the files on CD.

mount /dev/hdb /cdrom
mount /dev/hda1 /mnt/c

cp /cdrom/directory/whereever/file/is/dt2-3.1b.mfs /mnt/c

mfsrestore -zpi /mnt/c/dt2-3.1b.mfs /dev/hdc

[NutKase]

Originally posted by Sincere0219
or am I suppose to convert the dt2.3.1b.mfs to dt2.3.1b.bak some how??? Really lost

They're the same thing. One of the guide writers named his differently that's all.

You're getting lost in the /path/to/your/files/ commands.

pkpss is trying to simplify this by having you copy files you need to /mnt/c

That's fine but I don't clutter up my C root directory with all those files. I just make a directory on my C fat32 drive called cdrom.

Then all those mount cdrom commands can be ignored and you're always typing get or copy such and such a file from

/mnt/c/cdrom/whateverfilename.extension

You're taking every thing VERY literally and that's good.

Your mistake with ''file not found" was that you just typed 'xpi' when what Cobelli had intended was that you just leave out the 'x' in the 'xzpi' of the original command - this is fun isn't it?

Also, if you have a sailboat I'll hand hold your through all this and come pick it up, or even pay the postage for you to send your tivo to me and I'll trade it back for the boat - still poking fun ;)

NutKase

[Sincere0219]

make sure I understand correctly before I proceed
Otivo=Secondary master (hdc)
blank fat32 hd= Primary master (hda1)
Cdrom= Primary slave (hdb)

1.Boot w/ mfstools
2.mount /dev/hdb /cdrom ENTER
3.mount /dev/hda1 /mnt/c ENTER
?4.(do I also mount the Otivo? here or dont mount it at all)
5.mkdir /cdrom/xxx.mfs ENTER
6.insert image xxx.mfs cd ENTER
7. cp /cdrom/xxx.mfs /mnt/c/cdrom ENTER and wait for prompt (which means copy from cd the xxx.mfs file to /mnt/c/cdrom directory which is my fat32)
8. then mfsrestore -zpi /mnt/c/cdrom/xxx.mfs /dev/hdc ENTER(which means to restore the image I have in my fat32/cdrom/xxx.mfs directory to /dev/hdc which is my Otivo.

9. Presto I can drink and use the sleeper auto iso till I can get another hd I can play with

Is this correct please edit where needed. Also I remember i did type zpi not xpi and got that error mssg. Sailboat pick it up huh? sorry all I can think now is mount, bash, monte blah blah blah lol. I am in FL

[pkpss]

You won't need 2 or 4.

After you you insert your CD with the image on it (after booting with mfstools and taking it out).

4. mount /dev/hdb /cdrom

5. cp /cdrom /xxx.mfs /mnt/c/cdrom

and your mfsrestore command at 8 is correct.

[rpl]

If you you read Mr. Blacks S2 hacking thread the very first post you will see that in many cases the backup image just will not fit on the original 40 gig HD. I ran into the same thing. Some 40 Gig HD's are just a smidgen larger and it will fit. My advice go ahead and pick up one of these inexpensive 120 Gig HD deals. Besides why spend so much time on this only to have to do it again later when you run out of room?

Are you having problems just copying over your backup image to your FAT32 C directory? Just boot up your FAT32 computer, put your CD into the CDROM and copy the file over. Then:
Reboot with the MFSTools linux disk.
mount /dev/hda1 /mnt/c
mfsrestore -s 127 -xzbpi /mnt/c/hackedbackup.bak /dev/hdc

If you try to use a 40 gig HD just leave out the x and -s 127 switches from mfsrestore.

When you put this restored hacked U5 image in your Tivo you will also have to do a clear and restore all or run the 51killer script. I would recommend doing the clear and restore, it will take about an hour. Then do the guided setup and your initial call in to get local numbers.

At this point go ahead and make your own backup. This way you will have the initial call done and your Tivo serial number on the HD so you don't have the error 51, then go ahead and play with Sleepers ISO. Skip the backup and restore parts. I think he tells us in the readme to only use the backup and restore with an original image.
Good luck, when are we going sailing?

[Sleeper]

I know that he's getting alot of help here. Here are my suggestions.

1) Get a good working NON-HACKED image of 3.1.1b that has been made with dd from an unhacked drive. I have one but I don't really have the resources (bandwidth) to send it to him. dd that image to your original 40 Gig drive. Boot with it, clear and delete everything - get unit running.

2) Get a LARGER hard drive.

3) Run the tivoscripts.

Just my opinion.

Sleeper

[NutKase]

Originally posted by rpl
Not to disagree with Nutcase but in your case I think you should just take that backup U5 image you burned to a CD and copy it to your FAT32 C directory.

I think you misunderstood me. I do exactly what you're doing, make a directory on the fat32 C drive and put everything including the mfstools cd's contents into that directory.

That way, just as you said, you don't have to mount anything but /dev/hda1 to get at all your files. Your advice was right on.

NutKase

[rpl]

You were right I have all these files moved over to my FAT32 drive so i don't have to go back to the CDROM. But I see that Sincere is having problems with Linux and just getting his backup copied over to his FAT32 drive so I was hopefully getting him to use DOS or Windows or whatever GUI he is more comfortable with to copy the files over to hda. SincereOtivo=Secondary master (hdc)
blank fat32 hd= Primary master (hda1)
Cdrom= Primary slave (hdb)

1.Boot w/ mfstools
2.mount /dev/hdb /cdrom ENTER
3.mount /dev/hda1 /mnt/c ENTER
?4.(do I also mount the Otivo? here or dont mount it at all)
5.mkdir /cdrom/xxx.mfs ENTER
6.insert image xxx.mfs cd ENTER

Since he mounted the CDROM in step 2 isn't he going to have to umount it in order to do step 6. Sorry way to many steps to just copy a file over. But I now see what you want at step 5a copy over his mfstools files to his new directory /mnt/c/cdrom. Then at steps 6/7 finally getting to copy his backup file over. I was just letting him run MFSTools from his CD but get his backup file into his system.

hmm I just noticed that he is trying to use a blank HD for hda.

[NutKase]

Originally posted by rpl
You were right I have all these files moved over to my FAT32 drive so i don't have to go back to the CDROM.

This exactly what I recommend. He should use windows or dos and put all his files on the fat32 drive and blow off all this mounting that's confusing him.

Originally posted by rpl
Since he mounted the CDROM in step 2 isn't he going to have to umount it in order to do step 6.

Step 6? Steps 5 and 6 are wrong useless and won't do anything.

The only steps I see that are correct are 1 and 2. The rest just show that Sincere hasn't learned what's going on yet.

Originally posted by rpl
But I now see what you want at step 5a copy over his mfstools files to his new directory /mnt/c/cdrom.

I never said any of that and don't put words in for me.

NutKase

[Sincere0219]

well I successfully got my image restored to my Otivo! :D Basically I took both of your excellent advice made some sense out of it wrote it down read it to myself to make sure it made sense and actually did it. My major problem was I only had a blank 20gb fat32 hd, so I did I believe what nutkase suggested mkdir /cdrom, cp image to that directory then -zpi to otivo I believe thats was from pkpss (whats that short for?)

mount /dev/hdb /cdrom
mount /dev/hda1 /mnt/c
(I added here mkdir /cdrom)
cp /cdrom/directory/whereever/file/is/dt2-3.1b.mfs /mnt/c(/cdrom I believe I put here cant find the paper I wrote it on)

mfsrestore -zpi /mnt/c/dt2-3.1b.mfs /dev/hdc(/cdrom I believe I put here cant find the paper I wrote it on)

but all I know it worked. Somebody emailed me someinstructions about some dap, i think, and some subfix dont remember but deleted it because had no clue what he was saying and you guys didng say to do it nor saw a thread on it.

THANKS FOR ALL THE HELP! now I am comprehending how this works. Whenever I can afford will buy a bigger hd will do and usb network card. Question though is it possible to buy like a 120gb hardrive make 2 partionions one 100gb for TIVO and the other 20gb fat32 windows xp so if anything can just plug the hd in to computer and restore for example by just transfering image from one partiontion to the other from windows xp until I get a network card?

[NutKase]

Originally posted by Sincere0219
well I successfully got my image restored to my Otivo! :D Basically I took both of your excellent advice made some sense out of it wrote it down read it to myself to make sure it made sense and actually did it. My major problem was I only had a blank 20gb fat32 hd, so I did I believe what nutkase suggested mkdir /cdrom, cp image to that directory then -zpi to otivo I believe thats was from pkpss (whats that short for?)

Congratulations.

NutKase

[Sincere0219]

sleeper this is not a flame or anything rude so please dont take out of context or directed at you. It seems that this is the 1st site where people automatically assume that newbs havent read, tried or searched and tell newbs consistently to search or read some more becoming upset at the newbie. For example I did nothing but read before I even registered for 3 days and really didnt understand a thing until Nut and pkpss came along gave me a headstart and took because of there approach. It seems that at some of the things I read people just lash out immediately not considering the fact that some newbs probably never even heard of linux. For example at one point I wanted to see if I could transfer a fixsub file with out a serial connection http://www.dealdatabase.com/forum/showthread.php?s=&threadid=29849&highlight=Sincere0219
it was just for my general knowledge how to transfer files I did search before I posted read some threads but did not comprehend. My advice is to in the "Newbie" section to do stickies explaining certain things that us newbies might not know such as what a bash prompt is and what it will look like ex bash in hyperterminal looks different if you boot up. Some of the guides dont even explain it newbies are just getting your cd and hitting enter enter enter even though it does give some explanation but how many people will actually study it. Maybe someone should work on the Newbie, in plain english not ok copy files by cp /var/hack explain cp means copy and /var/hack is what its copying to make it easier so no one "wastes the time and resource of others". Some people are not as bright as others on here, nor learn like others and really wont comprehend w/o a little help no matter how much they read. Its like giving somebody a book to learn French say read it over and over and over till you learn it dont ask questions because the answer is in the book. Again not flaming or anything if you want to ban me or whatever its fine just thought I would speak my mind because of some threads I read and the rudeness. At least make the Newbie thread flame free. Ok done anyone need visine or a beer? :D

[Sincere0219]

thanks Nut for all your help and pkpss. also when you guys started typing stuff out that werent in other many a threads I read it started making sense

[Sincere0219]

sleeper I just seen that the commands dictionary is under the howto section under DirecTiVo Hacking as unix commands thought it was linux? I would put that in the newbie section that would have been a great deal of help if I could have found earlier

[Sleeper]

Originally posted by Sincere0219
[B]For example I did nothing but read before I even registered for 3 days and really didnt understand a thing until Nut and pkpss came along gave me a headstart and took because of there approach.

Yes, the information is not organized and there is much HOWTO and not enough WHYTO. However, searching will help.

FYI, I read for two weeks straight before hacking my tivo. When it did not work I figured it out on my own.

Look, I realize that everyone's interest and potential for learning computer technology is different. Some of my best friends and family have difficulty just turning one on. That's why I wrote the scripts. I never thought that I would have to explain the difference between making a bootable CD from an ISO and burning a file (ISO) to a CD.

When someone uses the tivoscripts, I expect them to read at least the first couple of posts in the thread. There is important information there about how to minimize your failure rate and report a problem. I feel confident that had you read the thread a little more carefully and posted the required information to report a problem, that you would not have had nearly as much difficulty.

[Ideasite]

I have been in the same boat as Sincere. This site is a massive amount of information.

I finally figured out that Sleeper had a CD-ROM image file - Sleeper.iso. It completely automated the process but it displayed what each step was doing.

I learned more by using that ISO that I had from all the reading I had done. (Yes I actually did read. Alot.)

The drive also worked. Thanks Sleeper!

[pkpss]

I haven't really been in other threads cause I'm still new to this like you are. I just understand enough of this stuff to actually be making a post. Congrats though, you'll start seeing it. ;)