Separate names with a comma.
Discussion in 'TiVo Underground' started by rbautch, Jul 21, 2005.
Not true. Just run the slicer to go to 6.3e. It worked fine for me on my Zippered HR10-250.
Thanks. BTW, do you recommend I re-do the hacks (encryption, 30-second, etc.) BEFORE I reboot?
No. It's best to run the enhancement script on it after it reboots.
OK, it's rebooting now. Slicer went fine. I just hope I didn't lose bash. I remember losing bash on another such unit months back. Had to serial in to do anything.
It rebooted, and as feared, I lost all bash access. Tried to serial in and now THAT won't even connect! I've tried all the various baud rates with TeraTermPro. Any suggestions?
If I could at least get serial bash I can manually run tweak and upload rbautch's files into the same directory as tweak.
Just zipper again, you'll be all set.
But can I do that without losing all my recordings and stuff?
What's really irritating me more than anything else now is that going to 6.3e is supposed to stop all these damn reboots. In the three hours since I Sliced to 6.3e, this thing has rebooted 7 times, messing up several recordings!
I'd assume so. Doesn't it ask if there are recordings you want to keep? You can easily rehack the box without hurting any recordings, as long as you don't reimage, and the existing recordings are not scrambled and you don't disturb the diskconfig key.
I think you're right. It's been so long since I last zippered a drive, that I easily forget.
Either I'm getting old or I got too involved in my HR20-700 DVRs.
No not really. They are actually decent boxes once you get used to them.
I'm one of those who still uses both. I still have multiple HR10-250s working and don't intend to dismiss them outright.
Interesting...I used The Slicer to go to 6.3e. The script ran and gave me a response that it was successful in loading the 6.3e slices. However, the information screen on the HR10-250 says my software is version 6.3a. Also, I jusrt rezippered the drive successfully, and when running Zipper then tweak, both mentioned during their running that I have "version 6.3a". If Slicer says it was successful in loading the 6.3e slices, why is it I'm being told I'm still at 6.3a?
Edited to add that my SwSystem in MFS shows this:
I noticed this IS different from what it was before I Sliced to 6.3e.
It looks like everything says you are still running 6.3a. The slicer checks to see if the slices are loaded in MFS, which they are, and then runs installSw.itcl to install the new software on your alternate partition. It looks like that never happened.
Well, that sucks. I wonder why Slicer ended up telling me it successfully installed 6.3e.
I did notice, FWIW, that following the Slicer install and responses, when my unit rebooted, the message on the screen said "updating new software," or something like that. I wouldn't think it would do that if it remained at the same version, but I can be wrong.
It sure seems like you still have "A"
6.3a-01-2-357 tyDb 53870 11/01/07 17:31 796
6.3e-01-2-357 tyDb 1139775 11/01/07 17:31 780
ACTIVE tyDb 53870 11/01/07 17:31 796
If you had a "pending restart" message in system info or phone it might have "upgraded" itself BACK to A. I had that happen a while back. In fact, each time I sliced the next day it went BACK to the previous version. There was a patch for that somewhere on DDB which worked for me.
Edit: Found it - //www.d-e-a-l-d-a-t-a-b-a-s-e.com/forum/showpost.php?p=271411&postcount=1149 (obviously remove the dashes)
I just may leave it at 6.3a and see if it still suffers from these constant reboots. If it does, then I'll try to fiddle with it again. I wish there was a way to remove the 6.3a software and leave 6.3e as the only one to work with. But that'd be too easy, wouldn't it?
If it said "installing the service update" then it should have installed the new software.
One would think, but I believe incog is right, as he pointed to what was "active" in my setup. But as I said, I'll monitor it and see if the reboots continue. I've programmed some recordings tonight on CBS, which seems to be the common denominator in these weird reboots.
I wonder if you can slice again since 6.3e is still on the alternate partition?
Edited to correct version to 6.3e