Separate names with a comma.
Discussion in 'TiVo Series3 HDTV DVRs' started by bkdtv, Oct 19, 2007.
I got 1TB EURX in my Roamio Plus.
Guess it varies. My Pro had the "S" version, as did my Premiere XL.
I replaced a bad hard drive in my TiVo Series 3 unit last night from a TiVo file I found on the internet, and it's working great other than the fact that whenever I enter the Media Access Key into the iOS apps, it tells me that it's an invalid MAK.
We need more info, what you did, what you are trying to do, what happened?
You said you replaced the drive, did you use an image from another Tivo? If you did, you need to have run Clear & Delete Everything, or it will not record or get service.
Since that file was not made from your S3, it probably still thinks it's supposed to be in a TiVo with a different TiVo Service Number.
Did you have to run Guided Setup?
Sorry for not replying right away.
Almost a day after I did a "Clear & Delete Everything", the iOS apps started working. I forced a firmware upgrade between that time, so that was probably the problem.
I don't know the deal with the Media Access Key now. I have OSX Mavericks which doesn't work with TiVo Desktop (at this time). I do have a Windows computer I can install TiVo Desktop on and see if the Key works, but I haven't done so yet.
The TiVo gets the MAK from the TiVo, Inc. servers when it connects to get program guide info and set the clock and get updates and account status and all of that, and it has to report it's TiVo Service Number to get account status, and when it does so, the TSN has to show as being on your account for it to get the MAK associated with your account.
F'rinstance, an S3 I recently acquired would still have a different MAK, the one for the previous owner's account, if I hadn't contacted TiVo and had that set moved to my account.
Did you do a clear and delete everything? If not that would be the first thing I try...
EDIT: Nevermind, I see you did that and it seems to have cleared things up - congratulations!
Question - I have a S3 HDXL, on it's 4th drive (just got it from WD after RMA on my last of the 2 I got from DVR_dude). How long does the C&DE take after reimaging with WinMFS?
I used the image posted by Unitron (TCD658000) and all seems to be going along OK so far. Tried this with the last drive I RMA'd and it kept going for days with no end. Anyone have the same experience?
You need to be making your own backup images after you get everything set the way you want it.
If, after about 4 hours, it's still on the "Clearing and deleting everything" screen, pull the power cord plug, let it sit for 10 minutes, and plug it back in.
You already ran wdidle3.exe to make sure Intellipark is disabled, right?
What size and model were the drives you got from DVR_dude?
OK, noted on the backup images once I get it everything back to normal. Still going but it's only about 2 hours at this point.
Did not run wdidle3.exe....
The drives I got from DVR_dude are WD 20EURS-73SPKY0, 2.0TB
One more curveball here, I am doing this all on a Macbook Pro with Windows Vista, via VMware Fusion and a USB SATA adapter
UPDATE: It finished with C&DE and I am into the guided setup. So far so good....
Okay, if it's a recently manufactured WD20EURS then Intellipark is probably not enabled, but without connecting it directly to a SATA controller you can't use wdidle3 anyway.
UPDATE: I'm through CD&E and guided setup, just need someone at Time Warner to pair my card with the S3. Basic channels work without that.
Read something (can't verify if true or not) that Intellipark comes disabled by default with the WD drives. The manufacture date on the replacement from WD is October 2013.
One last thing is that I replaced all but three of the capacitors on the PS, working fine for now. The PS I have is one of the newer ones, the three caps in question are 16V/2200UF (mounted in a triangle formation under an aluminum L-shaped heatsink?). Anyone have the Mouser part numbers for those? Or can anyone recommend an equivalent replacement from another source? The ones I received were not skinny enough, need to be taller and smaller diameter.
Once I get my card paired, backup image time for the next drive replacement adventure....
Unitron - Thanks for the help!
If those 3 caps don't need replacing now, they probably will eventually.
Where did you get the replacements that are too short and fat?
Agreed, it's not if but rather when those 3 will fail. When I first looked at the PS as a possible issue there was only one that was domed. I just need to figure out the right P/N's for the 16V/2200uF caps.
I ordered all of the caps from Mouser, including the ones that are too short/fat. They are the right size capacitance wise but no way they will fit in that space physically. Panasonic low ESR.
See if you can search for the Panasonic part number in this post assuming this is the HD power supply that you have and verify that the dimensions match what you need.
What Panasonic part number did you order from Mouser?
My PS is a newer version, less stuff on the board than what you'd find in a TCD652160 (bought one for parts to try the PS with my TCD658000). The caps are located under an upside-down L shaped heat sink with what looks to be some FET's screwed to it. They are tall and skinny compared to all others.
Can you measure the current capacitor in mm as the EEU-FR1C222 is the taller/thinner version of that capacitor (12.5mm x 22mm)? There is another version that's shorter and wider (EEU-FR1C1222S - 16mm x 20mm).
Going to open the box up again and measure those last three caps.
Just as I thought everything was OK again, I am getting Green Screen of Death, seems to be looping. This drive is brand new, anyone think it's one of the last three caps I didn't change?
Here's what I have done so far:
-New RMA replacement drive from WD (WD20EURS), no wdidle as I'm doing this from a Mac w/USB to SATA using WinMFS (Vista, running WinMFS as Admin).
-Used image provided by Unitron, no issues imaging with WinMFS, answered yes to utilizing extra space.
-Did C&DE, then went through guided setup. Could not get Time Warner on the phone so waited until now to do it. After C&DE guided setup went fine and normal TV channels were working OK. Let it run since that time, now looping Green Screen of Death. Brand new WD drive, manufacture date 10/2013.
What gives? Any ideas?
When you do a copy or restore, do not accept the offer to expand.
Check the drive with
Then expand the drive with
If you copy from another drive with WinMFS, the source drive is the one "selected", and after the copy is finished, you'll have to select the target drive before clicking on
Then, when you run
it'll already be the drive selected.
When you restore from a file, you tell it to which drive to write the image, but I don't know if that counts as having "selected" it according to WinMFS's internal logic, so perhaps that has something to do with the need to do the expansion separately.
The green screen may be the TiVo straightening out the disparity between the TiVo Service Number that's burned into a chip on the motherboard and the different TSN that got copied from the hard drive from which the image was made, which will be the TSN of the TiVo out of which the drive from which the image was made was taken.
Did you see anything about Error 51? (Which is what they call that TSN mismatch)
Eventually it should get itself straightened out.
Unlikely power supply problems have anything to do with GSOD, and unlikely Intellipark is a problem, as if it's rebooting and going back into the GSOD, that means the motherboard is communicating with the drive enough to detect the problem that triggers the GSOD.
I don't know which version of the 658 software was on the TiVo from which that image was made, because I got it from someone else and just renamed it to put the 658 in the file name.
I didn't actually have a 658 to try it on.
I tried it in a 652 and it booted it and displayed the THX logo splash screen and I figured that was a pretty good indication that it would work in an actual 658.
If it's not a new enough version of the TiVo software (I think it needs to be at least 11.0h), then it might not be able to handle all 2TB, so maybe you should restore again without expanding, see if you can get it to boot and straighten out the TSN mismatch, and all that good stuff, and then let it update to 11.0m when it calls in, and only then pull it back out and run