Premier/Elite with 422 and 418

Clean out your receiver folks.

0. Disconnect hub and sat cables
1. Factory default and hard boot
2. Run system clean file 3 times with hard boot between each
3. Load current factory bin hard boot
4. Load new file 2 times hard boot between each
5. Re-connect sats adjust all settings and scan then power down
6. Re-connect hub and fire up on channel 340

I had pic within 2 minutes and this is the most stable my Premier has been in 2 months!

Post back if it works for you please!

It did not work for me my 5e is dark its been DARK please help me put the ligths back on.

Hey old german it's great to see you buddy,,

maybe this could help you,,

here a link I found that could get you back,,

https://preferredbypete.com/sonicview-discussions/24492-sv-binary-format-file-update-read.html

good luck

The new files have shorted out the old 5e hubs. Try and reload the old file and get back the ip config and then re-load the new one. It still may not work. I think they are looking at the resolution to the problem still.

Hey dells did you read this link that found and I posted yesterday it right above your reply and let me know if that help you guys???

here it is again,
https://preferredbypete.com/sonicview-discussions/24492-sv-binary-format-file-update-read.html

old german said:

It did not work for me my 5e is dark its been DARK please help me put the ligths back on.

Click to expand...

I been reading alot and it seem that these new files SV put out had fried the I hud on some people, and is ok on others,

here a few thing you could try to get it back

(1)--C/P
the ihub is blinking your I-hub is fine

BIN 422 has removed the IP Config Screen is all

Please run Wiznet and click search can you see the Ips and to the top left Ver 2.3?

The new Bins released yesterday are able to update the I-hub now via the Rs232.

Just wish there was more info on this before they released the files or added the changes that were incorperated.

(2)-- C/P
G back to BIN 514 and reboot, the I-hub lights should come back.
If not, turn off receiver from the rear fpor 10 minutes.
Turn it on again and check for lights.

Please Load BIN 420 again and reboot see if I-hub lights come back
If not turn off recceiver 10 minutes with rear Swith
Then turn it back on and check for lights and report back please.

(3)-- C/P

From what I have been reading, most ppl load the bins like normal, that is what I did with my SV 360 Elite and I am fine.
We tried same thing we did with my buddy's SV 8000 and he lost Ihub Lights as well.
WE waited 10 minutes loaded BIN 514 brought I hub lights are back.
Everything pointing to a buggy BIN 515.
Some ppl have little to no problems but they are few and in between.
I think it may be a good idea to ask SV 8000 to just hang tight and wait for a new Bin.
A few ppl may have already lost their I-hubs for good.
Not worth taking the chance I don't believe.

I hope this could help you guys

That is exactly how I loaded mine and I have a 5E and now it is working fine. The secret is not to rush it, just let the stb do its thing and it will come up in due time.

hotrod11 said:

That is exactly how I loaded mine and I have a 5E and now it is working fine. The secret is not to rush it, just let the stb do its thing and it will come up in due time.

Click to expand...

"Sweet hotrod11"!! Thanks for the tip,, Now see if we could get "old german" back up and testing..

Followed Dells instructions.

Used V0119P to Clean.
Used Factory File dated Jan. 26, 2010.
Then loaded 422P.

First time failed... waited about 40 minutes and got nothing. Also screwed up the first time and connected the iHub as a part of step 6 (instead of waiting for another hard boot).

This time I did it correct, and did steps 6 and 7 separately. Can not remember if I did a hard reboot after the factory file...on the third try I will be sure to follow all instructions fully and completely.

Nothing showing after 10 minutes... I will try again. As a side note the iHub appears to operating just fine, lit up and network adaptor connection message appears after step 7.

Cheers,
Fitch

Repeated for the third time.

Only change is that this time I used the Factory File from Nov. 21, 2009.

Now just waiting patiently. Will post if successful.

Cheers,
Fitch

fitch1 said:

Repeated for the third time.

Only change is that this time I used the Factory File from Nov. 21, 2009.

Now just waiting patiently. Will post if successful.

Cheers,
Fitch

Click to expand...

Thanks fitch1 for all your trying and reporting back your testing,,

Still nothing.

Confirmed on Wiznet that the iHub is now at version 2.3.

Nothing seems to be blocking the iHub communication... so I will try downgrading to 420 see if I get a picture back... then repeat post ones steps.

Cheers,
Fitch

Alright so I finally got it to work, by attempting to follow Buttmann302's "SV Bin Update Read Before Loading File How 2" (tried to link it but my count is only at 3... need 15 to have links) instructions. Here is what I was able to do from the 17 points outlined in the Step by Step.

1. Use the (usb pendrive) and install the file (syscleanfile) the one that correspond to the model receiver you have.(hard boot). - Used 119P again - completed
2. Install by USB file (263p) or (230e) depends what model you have. [p=premier e=elite] - updated to 263P
3. Go to IP Config. and verify the (serial #) from ihub, if is correct just leave that alone. if is incorrect and need to change please add to serial number all (0) and apply. (verify 2 times to make sure changes have been made). - have a wm iHub and it did not look like my serial number so I zeroed it and applied 3 separate times to ensure it took
4. Using your PC, open Wiznet and install file (1.9) to ihub. - Tried this but my iHub would not go from 2.3 to any of the earlier bins that I had, so I left it at 2.3
5. Install one more time using the usb bin (syscleanfile) to receiver. - did this
6. Turn off your receiver from the back and remove your ihub. - did this
7. Connect the null cable from the port (rs232) - tried this but I only ha ve computers with USB ports, have a few USB to Serial connectors laying about... tried one, it installed on the computer correctly but would not work to upload to the receiver on any of the ports that were available to select
8. Open loader at your PC (2.01) and upload file (264p) o (231e) depending on your receiver model, start the process with receiver still off from the back - because of USB to Serial adaptor problems I loaded 264P via the USB pen drive with the iHub disconnected
9. When is ready then turn on the back switch and it will start loading the file. - N/A as explained in point 7 above
10. Just make sure (dn01) shows on the display, if not repeat process. - N/A as explained in point 7 above
11. Wait few mins until is done ( DO NOT INTERRUPT). - N/A as explained in point 7 above
12. Wait for the receiver to flash the file, when you see the time on the display flashing is done.. - N/A as explained in point 7 above
13. Remove the NULL Cable and connect the ihub to receiver. - Reconnected the iHub
14. Using the usb upload file (411) depends on the receiver model you have - Loaded 422P using USB
15. Check for any channels that are mostly up like 105 for sample and turn to that channel, when on that channel (hard boot) receiver from the back switch and wait to see message (network adapter connected) wait for few mins until you get video. - Went to 300 then Hardboot
16. If you get to see tv then we are good until now. - Saw TV within a minute
17. If not verify if server is up or down - N/A as I saw TV


SUMMARY - to get it to work if it didn't from Dells Instructions in Post 1 - for a 360 Premier
Load System Clean File - 119P - Hard Reboot
Load 263P - Hard Reboot
Zero all Serial Numbers - (I may have done a Hard Reboot here - can't remember for sure but I would just to be safe)
Load System Clean File 119P - Hard Reboot
Load 264P - Hard Reboot
Load 422P - Hard Reboot
Put on Channel 300 and in came the picture.

This is the second time that I had to zero all the serial numbers to get an update to work, I believe that I had to do it to get 420P (might have been 418P - I can't remember for sure... but it was within the last few months) to work as well. This could be a critical step for those having problems... just my opinion.

Hope this helps anyone having problems.

Cheers,
Fitch

"BIG WOW"!! "Fitch"

Thanks For Your Hard Work, I Hope This Could Help Others Out,,

B hunter

The other thing I've been doing also for WM hubs only is forcing the connect in a similar fashion.
Load 263 yes with WM hub. Don't worry about numbers
0 out the fields and apply
Reboot and load 422 (This forces the Fail TO Get Serial From Server error)
Reboot again and you should get the network connect and the FTGSFS error
Let it sit on one channel for 2 hours it should roll in. It forces the hub to reconnect with server and recreate a serial number. I have done this several times and it works well.

dells said:

The other thing I've been doing also for WM hubs only is forcing the connect in a similar fashion.
Load 263 yes with WM hub. Don't worry about numbers
0 out the fields and apply
Reboot and load 422 (This forces the Fail TO Get Serial From Server error)
Reboot again and you should get the network connect and the FTGSFS error
Let it sit on one channel for 2 hours it should roll in. It forces the hub to reconnect with server and recreate a serial number. I have done this several times and it works well.

Click to expand...

"dells" here another WOW!!

This Is Great "old german" Put a 911 out for his system and You Guys Gave Up The 411,,
This Is PreferredByPete.com Members At It Best!!



B hunter

At the end of the day.......here's the deal, SV needs help. I have been battling connection problems for months. I loaded the NFPS trial today and what do you know..............rolled in 30 seconds and not a freeze or disconnect since. SV better clean it up they now have File/hub issues, FRIED ihubs from their newest files, and people with faulty connections with their server. FINALLY JUSTICE! I KNOW WHAT I'M DOING WITH MY SETUP, IT'S SV THAT DOESN'T!