The method of updating is now listed here:
http://www.satelliteguys.us/threads/291053-First-Aid-Serial-Update-via-Internal-TTL-Header
Bob
http://www.satelliteguys.us/threads/291053-First-Aid-Serial-Update-via-Internal-TTL-Header
Bob
Hi Babadem. Seems like we are both in the same boat -- mine worked fine for 18 hours or so after the firmware upgrade...and yes, I also tried to upload my user .udf files. However, when I did that, it didn't look as if it loaded correctly (first time that's happened since I've been using the microHD ALI editor), so I just reloaded the default back onto it. But mine didn't stop working right away. It worked without a hitch the rest of the evening and the next day...even scanned several sats. After I blindscanned 127W, the screen froze and the cycling started. Most of the time, all it shows is the boot logo before cycling off and on again. About 5% of the time, it would show an info screen for Guatemala 27 at the bottom, but no picture and no access at all to anything...I have to unplug it, and when I plug it back up, the endless cycle continues.
I've ordered the converter, but it seems like the 3.3v is coming to me instead of the 5vLet me know when you get yours working again
![]()
If the STB operated normally for a few hours then started power cycling without any additional file loads, it is not related to the firmware loading or loading a corrupt channel list. Have you tried disconnecting the coax cable from the SAT IN port to see if power cycling stops?
Did you load a channel list or only the firmware update? Was the STB Factory Reset and power cycled after loading the firmware?
I don't mean to hijack the thread, but my problem was exactly the same as tekjunkie02 describes. Mine happened after the 8/29 update, and not instantly. I did, however, try to load my own channel list with the microHD ALI Editor, as I have done for weeks...noticed a strange problem where it listed my satellites as 1/25, 2/25, 3/25 (etc.), so immediately reflashed with the factory default. I power cycled each time. Worked as normal for half a day or so, then suddenly went into the continuous cycle. I had disconnected the coax and reconnected. Even disconnected the entire STB for a whole day to see if the problem was still there...and it is. OK, sorry for hijacking, but thought my comment could be useful here tooBack to tekjunkie02...
I just got my cable today, and I am sad to report the exact same issue.... the recycling continues. The computer shows that it downloaded the new firmware, but the cycling continues. I'll try to try some other things when I have a little more time, but preliminary results seem to indicate this is not a fix for the machine.![]()
I used Windows XP Pro, and yes I downloaded from Prolific web site. COM port 5 was Identified in the device manager of Win XP as belonging to Prolific USB Serial or something of that nature.What version of Windows are you using? Did you download the drivers from the Prolific web site? After installing them, I'd do a reboot. Did you double-check what Com port shows up for this device? Most issues like this almost always involve the selection of the wrong com port. Did you get any indication it was connected and downloaded the software?
I'd also disconnect my pc from the internet (turn off wireless, or disconnect any ethernet cable), shut down all but the editor program, and turn OFF any firewall AND your anti-virus software for during the flash.
Post the auction for the exact device you purchased, so we can avoid that one right now until we know for sure.
P.S. I also wouldn't trust the color of the wires coming from your board. Verify what each one is. Hopefully the header on the board is labeled.
I'd also disconnect my pc from the internet (turn off wireless, or disconnect any ethernet cable), shut down all but the editor program, and turn OFF any firewall AND your anti-virus software for during the flash.
One question. If conecting the MicroHD to the PC via the USB to Serial Cable, powers up the receiver, why do we need to plug in the power supply into the MicroHD when flashing the unit?
What if you go through all the same steps, EXCEPT just push a different .udf file to your receiver? Maybe one of the ones posted by another user?
Here's some to choose from: http://www.satelliteguys.us/threads/291275-Share-or-Download-User-Data-Base-Files-udf
What if you go through all the same steps, EXCEPT just push a different .udf file to your receiver? Maybe one of the ones posted by another user?
Here's some to choose from: http://www.satelliteguys.us/threads/291275-Share-or-Download-User-Data-Base-Files-udf
In my case no "UDF" files involved yet. I just trying to install the latest firmware so that the receiver can stop continuously rebooting.
That was the case with me. I will account for that when I tried the update next.That may be true, however just the firmware push didn't work. Since in some cases people mentioned that the rebooting came after they played with their .udf file, perhaps a corrupted .udf file caused the reboots. It therefore follows that maybe a good .udf file will stop the reboots..