Post by arcaneshark on Nov 5, 2007 20:17:23 GMT 7
-----WARNING-------
These steps are a rough outline of the steps I performed myself. They are not definative and may compromise your setup.
I will attempt a better step by step when I get time.
However, if some of the more active members of this forum would like to check/correct/rip to pieces my information please feel free. However, I have posted this as a rough guide to those out there happy to play, but not sure where to start.
If anyone knows of a simpler, or better detailed, solution please let me know. If forum admins wish to remove this due to "safety" please do.
Regards
---------------------------------------------------------------------------------
For those that really do want the features resolved in the 2.00.03 release, but need to add modules, I found a temporary solution. Sorry these instructions are not step by step, but I'm sure you should be able to work around it.
First, if your SSH and SYS User modules are not installed, you can use the firmware patcher from www.mostlyharmless.org/thecus/Thecus_N5200_sshd_0.6.zip
modify the version file to 2.00.03 so that it will patch this firmware, but not increase the number preventing future firmware upgrades. Recompile the patcher as detailed in the readme file and install like a full firmware.
This SSH only seems to be usable per session. If the Thecus is rebooted, you will need to repatch your firmware. I believe this is because the service is not set to start on reboot, and repatching finishes by starting the service for you.
(Feel free to correct my comments/steps/statements if I am wrong)
This will then give you SSH access to the box.
Download a previous functional firmware version.
Using des -d -k 2006N5200 firmwarefilename outputtarfilename to decrypt the firmware
Then untar the output file to a usable location to provide the unpacked firmware source files.
I believe my next step was to manually install the IMGDUP module to provide writable access to the cloopfs structure.
To perform this I manually performed the steps detailed on the wiki sites module development section.
i.e
extract the imgdup package
Copy the contents of the IMGDUP folder to /raid/data/tmp/module
then from /raid/data/tmp/module/Shell run the
install.sh
and then run the
enable.sh -off
(I think it is off. The option is the opposite of what you want to do
?)
This should then give you access to the /cloopfs structure.
change to the /cloopfs structure and rename the www_v1.rom file and then copy the www_v1.rom from the extracted firmware to this folder.
After a reboot, the old web system should be active. You can then install and enable any module you like.
When you are happy with your module configuration.
Log back in over ssh and rename the functional www_v1.rom file to something else and rename the original (broken module management) www_v1.rom back to www_v1.rom.
After a reboot you should have your modules installed and working correctly and have access to the working NFS etc of the latest firmware.
These steps are a rough outline of the steps I performed myself. They are not definative and may compromise your setup.
I will attempt a better step by step when I get time.
However, if some of the more active members of this forum would like to check/correct/rip to pieces my information please feel free. However, I have posted this as a rough guide to those out there happy to play, but not sure where to start.
If anyone knows of a simpler, or better detailed, solution please let me know. If forum admins wish to remove this due to "safety" please do.
Regards
---------------------------------------------------------------------------------
For those that really do want the features resolved in the 2.00.03 release, but need to add modules, I found a temporary solution. Sorry these instructions are not step by step, but I'm sure you should be able to work around it.
First, if your SSH and SYS User modules are not installed, you can use the firmware patcher from www.mostlyharmless.org/thecus/Thecus_N5200_sshd_0.6.zip
modify the version file to 2.00.03 so that it will patch this firmware, but not increase the number preventing future firmware upgrades. Recompile the patcher as detailed in the readme file and install like a full firmware.
This SSH only seems to be usable per session. If the Thecus is rebooted, you will need to repatch your firmware. I believe this is because the service is not set to start on reboot, and repatching finishes by starting the service for you.
(Feel free to correct my comments/steps/statements if I am wrong)
This will then give you SSH access to the box.
Download a previous functional firmware version.
Using des -d -k 2006N5200 firmwarefilename outputtarfilename to decrypt the firmware
Then untar the output file to a usable location to provide the unpacked firmware source files.
I believe my next step was to manually install the IMGDUP module to provide writable access to the cloopfs structure.
To perform this I manually performed the steps detailed on the wiki sites module development section.
i.e
extract the imgdup package
Copy the contents of the IMGDUP folder to /raid/data/tmp/module
then from /raid/data/tmp/module/Shell run the
install.sh
and then run the
enable.sh -off
(I think it is off. The option is the opposite of what you want to do
?)This should then give you access to the /cloopfs structure.
change to the /cloopfs structure and rename the www_v1.rom file and then copy the www_v1.rom from the extracted firmware to this folder.
After a reboot, the old web system should be active. You can then install and enable any module you like.
When you are happy with your module configuration.
Log back in over ssh and rename the functional www_v1.rom file to something else and rename the original (broken module management) www_v1.rom back to www_v1.rom.
After a reboot you should have your modules installed and working correctly and have access to the working NFS etc of the latest firmware.
