Factory Reset - No boot when Network is plugged in, without network, boots ok

#1

Hi,

I did a complete factory reset. In doing this, the device hangs at the WE Live Hub loading screen, however, when I disconnect the network cable, reboot the device, the device boots up pretty quick. When I plug the network cable back in, the device reboots, and hangs the loading screen. An item to note, I did downgrade the firmware, and update the firmware. I also tried using the reset button on the device.

Any one got any idea’s on how to resolve this?

Thank you in advance!

#2

Hi,
I Have same issue. Did you fix it the problem?

#3

Kind of,

It has something to do with DNS, if you put in a bogus DNS server, it will come up. From a traffic capture, it looks like it tried to register itself to a url that is no longer valid.

That’s about as far as I have gotten. It seems to query http://www.wd.com/wdtvlivehub, and looking specifically for a SRV (WDTVLiveHub.wd.com:445 0 0) records for WDTVLiveHub. It never finds these.

It does hit up wd2go.com, and appears to be looking for something else as well, (which goes to AWS)

If anyone has any ideas how to get past this, that would be great.

For kicks, I did open up a ticket with WD support, however I expect them to close it without doing much.

My guess is, this is an unexpected bug, which I hope they have a workaround for, or a quick fix.

#4

Hi,

I have an update. With my network port unplugged, what I had to do, was download the original firmware from the firmware rollback site: https://support.wdc.com/knowledgebase/answer.aspx?h=p2&ID=5860&lang=en&p=412 (version 2.02.16), install this firmware, do a factory reset. I plugged in the network cable, and everything came up. Rebooted twice, just to make sure it came up correct. Upgraded the firmware to the latest, version 3.12.13, and the issue went away.

Looking at the traffic capture, all the online queries went away. My guess is the factory reset at version 3.12.13 corrupts something on the device.

#5

Just sharing my experience.
I have same issue with my wdtvhub, it boots only with unplugged network or when in my lan internet was disabled.
So workaround for me was:

  1. Unplug network and boot as normal.
  2. Rollback to 2.08.13 and do factory reset. After this i was able boot with plugged network.
  3. Update to 3.12.13.
    Cancel any registrations, experience and etc.
    And don’t do factory reset.

This is working solution, if anyone interested, maybe there is sense to findout which service cause this, and maybe there is only disabling this service in settings is enough (i mean disable it with unplugged network, without reflash device).

Also looks like my another wdtvhub is still working fine as dlna nas. Maybe this because this issue becomes not so long time ago and first hub all this time was working without turning off.

#6

Sadly the same as happened to me with my WDTVLIVEHUB. I was just about to put it on ebay to sell so i cleared out the HDD of the goodies and reset it and now with the ethernet or wifi stick plugged in it crashes the system.

I’ve tried to follow the directions of Anton and icemantechno but alas the oldest firmware that the box will take is 3.0.28 and that does not fix the networking issue. Either the box does not see the firmware on the USB stick(2.08.13 and a couple below that) or it says it is not compatible(2.02.16 and a couple above that).

If I manually give it network numbers including DNS it works but that’s a PITA to common folk.

Thoughts?

#7

what i did was go into the zip file and rename the file wdtvlivehub.ver from 2.08.13 to 3.08.13
the first number has to be higher, i changed the number to 3, flashed that, without the ethernet cable in…then once it finished flashing and i booted in to main screen, i went into system, then reset it.
when i rebooted, i plugged in the ethernet cable…bingo it worked, then after that i flashed the last firmware 3.12.13 and reset then reboot, works good as new.

1 Like
#8

That worked fender62! Had to rename 2.08.13 to 4.08.13 as 3.x.x was already on it.

I’m curious that you would want me to reset after installing 3.12.13. Isn’t resetting the cause of the problem?

#9

i think the cause maybe if you do a sudden shutdown, pull the power while it’s on, the idea of a reset after flashing is to tell the system or flush the system, mmm like a clean up i suppose, worked for me.

#10

Hello all.
Try Automatic Firmware check to off.
I had the same problem and after a firmware reset it persisted but the above cured it.