My iHub Overview:

What exactly will these steps do for me if everything works out?

1. You will be able to get the new v1.4 update on to your virgin iHub.
2. You will be able to get the new v1.4 update on to your v82.0 (bricked) iHub.
3. This will fix IP Config menu from not showing up after loading previous working files.
4. You will be able to get TV back, once the iHub settings are corrected and updated, the receiver will take care of itself.

So, have you been up for endless hours/days trying to figure out why your iHub is bricked and trying to get it back to life? Or even simply just trying to get your receiver to show up IP Config in the menu? Does your iHub fail to load the current v1.4 update? Then keep reading.....

I could not seem to find a NO-BS fix, all the "fix it this way guides" were way to vague for me and didn't cover the bases I needed covered, after asking for help and getting nothing, I decided to test a little myself. The results will have you up and running with v1.4 and a debricked iHub in no time at all if you are lucky.

This is basically the exact steps I took to get the iHub back to life and upload 1.4 from the dreaded v82.0, this is also going to fix the receiver not detecting the iHub as well. - Follow the below steps EXACTLY as I have typed them, if you RUN in to a problem at all during any of the steps, please post the problem. Keep in mind the files that I have included are for SonicView 360 Elite ONLY, you will have to download the premier/8000 files yourself if thats the STB in question.

Preliminary Check:

This will work as long as you have a router, and as long as you have a working iHub (one that lights up on back), and as long as when you plug the iHub in and press Search, and at least some sort of iHub info shows up, if it does, then this is what you will need to do.

Exactly as I have done it below, I was able to bring two iHub/IP Config menu back to life fairly easily. This is all based on me using a linksys router with default gateway of 192.168.1.1 - majority of routers have the same gateway ip.

But just something to check before you get started with the steps. Make sure you are directly plugged in to the first port on your router (with your computer in 1st port) and modem connection or dsl in the one furthest to left. Go to Start>Run>CMD>ipconfig

Make sure your Local IP is 192.168.1.100 and default gateway of 192.168.1.1, if not then I am not sure these steps would apply to you as well.

Make sure you have done:
Factory Default file from USB to receiver
Sys Clean file from USB to receiver
Hard reboot (back switch)
Load 206 Bin (for elite receivers only)
Hard reboot (back switch)

Steps to take:

1. Connect iHub to receiver

2. Leave Power on, on the receiver, but turn power off from the front panel (so that the time is displayed)

3. Connect ethernet cord to iHub, then directly in to ethernet port on computer, this part is where it is tricky and you might have to wait until you see "limited or no connectivity"

4. Open up the WIZ program, click search until it displays the fields with some sort of info. Once it does, your in luck! No BS!!!! Now you need to skip around a little for this next step.

4 1/2. Make sure Static is checked, you should now see the fields able to change settings. Make your settings exact to mine.

Local IP: 192.168.1.101 Port: 1920
Subnet: 255.255.255.0
Gateway: 192.168.1.1

Operation Mode: Mixed

Make sure USE DNS is checked!!!

DNS SERVER IP: 208.67.222.222
Domain Name: WWW.SVFTAIKS.COM

Now click on Setting, if it gives you an error after clicking, click setting again until it takes. Once it does, close the WIZ program and follow on to next step.

5. Now that you can see the iHub current info and the settings, now what you want to do is check on the back of your router, this part is crucial... Make absolute certain that your PC is plugged in to the first outgoing port on the router. And now unplug iHub from back of computer, plug it in to the 2nd outgoing port on the router (the ip that the router assigns to this port should be 192.168.1.101 by default.)

6. Open up WIZ program again, and click on Search until it finds your iHub, notice that the settings should read what I typed above? If it does then continue on, if not, then go back and retry until it does!! So now that it says the settings that we want it too, we still see the v82.0 right? Lets get rid of that now.

7. Go to Start>Run>CMD>ipconfig

Now type: ping 192.168.1.101 (if you get a series of replies, we will be able to load 1.4 with no problems at all!) Thats right, you can click thanks!!

8. Now bring the WIZ program back up, and I want you to click on Upload tab, you should be able to at this point, make sure you have extracted the 1.4 bin to your desktop. and then choose that file. You should instantly notice it start uploading with little bars with pretty much no hanging at all.

9. Once it says Completed, close WIZ, then reopen it, notice a new version?

10. Thats it, that should be the solid fix that everyone has been looking for, and no need to use rom 1, its a waste of time when you can just do it this way with 0% problems.

Additional steps to load bin 209 (for elite users only). You should see Network device connect! after rebooting receiver with iHub plugged in.

Then just put bin 209 on USB stick, upload, reboot, and you should be good to setup all your settings as before - Also, you will now be able to see your IP Config menu again and able to change settings at will.

Let me know if you guys run in to snags, this should seriously be the best fix that you guys can get for the iHub not communicating with the receiver/not taking the files/v82 error.

This is a COMPLETE fix. Not just a band-aid, if you are needing files for 360 Premier, you will need to obtain them from the downloads section.

Attached Files

SonicView iHub Fix Pack.zip (8.79 MB, 243 views)

__________________


Please don't PM me with fta related questions, they will no longer be answered.

this is a pretty elaborate fix thats relatively easy to follow but i get to the part of hooking the ethernet up from the ihub to my computer direct with the receiver power off and instead of getting limited to no connectivity, my net icon flashes on and off about every 3 seconds saying its disconnected. when the ihub itself flashes the green light (every 3 seconds) it causes the net to receive some sorta momentary signal and tries to connect but it never stays on long enough to do anything. it acts like its trying to find a working signal but like i said, it only lasts a split second then says disconnected. i think im giving up on the ihub fix and just waiting it out until theres a stand alone n3 bin fix :( stupid cheap (expensive) ihub that doesnt work...

Yes I agree with you this ihub is not very user friendly, I myself dont have one just yet,,, but Ive been reading about every ones issues,,just give Sonicview a lil more time and they will get the bugs figured out!!!

__________________

I too had to go thru this posting and re-boot my i-hub. Great and easy to follow instructions. I had a different gateway due to a different router.Other than that it was a sure fix for losing the signal and cleaning up the problem.

__________________

I have followed this procedure several times and the IPCONFIG is not in my receiver menu. What can I do. SonicView 360 elite.

Thanks

What is the bin file number you put in your receiver?When you open wiznet tool What does it show in the top left corner in the version box?

Click on the link below.If you don't think you fix your problem yourself.

http://www.ftaprofessionals.tv/usefu...-try-help.html

__________________