damd
New Member
Posts: 1
|
Post by damd on Oct 23, 2012 21:49:54 GMT 7
I got a fix from Thecus support and it worked for me. Use the attached file, unzip it to a fat32 usb stick along with www.thecus.com/Downloads/N5200_N5200PRO_FW_2.00.16.bin2009/03/12 16:37 33,626,632 N5200_N5200PRO_FW_2.00.16.bin MD5(N5200_N5200PRO_FW_2.00.16.bin)= 77b3f124c8753866d3017085568df312 Plug it in the the 5200 and boot up. The Orange busy light should soon light up. This will stay lit for 1-2 mins, the unit will then bleep and the light will go out, remove the usb stick. Flashing will then continue and after another 4-5 minutes the nas should reboot. I'd just like to say that this worked for me with my N5200 (non-Pro) for downgrading from .17! Thanks a thousand times!
|
|
|
Post by howarddavidp on Jan 19, 2013 12:41:07 GMT 7
My downgrade was flawless, watched it on my monitor as it did it's thing David
|
|
|
Post by anosis on Jan 26, 2016 19:59:27 GMT 7
Hello all,
Sorry to dig up such old post, but I have attempted to follow the instructions it this post and cannot downgrade from 3.00.04.5 at all.
Some history and info...
I re-inherited my old N5200 (non-PRO) version from a friend who no longer had a need for it. There were no disks in it so to start off I purchased two 2TB HGST server drives. I was able to successful configure RAID-1 (mirror) in ZFS. I then managed to create user accounts for ACL and make a shared folder, however every attempt I make to assign a user profile to a shared folder is met with the refusal to take the change.
Then I did some research on the firmware currently installed and found out that it was a very short lived beta version, however once installed difficult to downgrade. Then I came across this post and I downloaded the factory_test.sh scrip and placed the recommended BIN on a 8GB FAT32 formated usb stick (i did the full format, not quick).
The stick is plugged into the front USB, the same port that would be used for USB backup, and initially when the NAS powers up I see the stick LED flashing, however the NAS soon shows BOOTING and by that time I know it didn't execute the script.
Can anyone give me some input on what else I could try to revert back to an older and more stable V2 firmware? Is there maybe a way to disguise a V2 firmware BIN as an upgrade to V3 so that the internal firmware upgrade can be used?
Thank you.
|
|
|
Post by cobalt60 on Aug 26, 2016 23:58:54 GMT 7
Did you ever get any reply on this? Because I am stuck at exactly the same situation. Maybe and 8GB is too big?
|
|