RT31P2/WRT54GP2 Alternate Unlock - Long Method
This is the Long Method unlock instructions which involve extra tasks like loading an encrypted xml file w/o using internet provisioning.
Please Note: This is an advanced unlock process. meister_sd's original methods in Post 4/Post 5 or the Guides in Post 10 may be easier.
Pre-Unlock Setup:
RT31P2 - See Post #2 (Link)
WRT54GP2 - See Post #3 (Link)
STEP 0 : Factory Reset the adapter (Optional):
1) This step probably isn't necessary unless you had a number of problems with your adapter or your adapter has already been on the internet. You could probably skip it unless you have further issues during the unlock process.
2) There are two methods of reset if you need to use it:
- Hold the reset button on the back for 5 seconds (Some say 30 seconds)
- In the Web Interface at 192.168.15.1, reset to factory defaults under the administration tab.
STEP 1: Setup the HTTP/TFTP/DNS/DHCP servers to load encrypted xml file and firmware:
1) See Server Setup Post #8 (Link)
STEP 2: Prepare your local file structure:
Encrypted XML:
1) In your TFTP ROOT directory (or directories if running multiple TFTP servers), copy your adapter's ENCRYPTED config file to that directory as spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
To download it: >>http://httpconfig.vonage.net/spa000000000000.xml (where 000000000000 is the MAC ADDRESS)
2.0.9 Unlocking Firmware:
2) In your HTTP ROOT directory (typically htdocs for Apache, docs for IPlanet/Netscape, wwwroot for IIS), create sub-directory: +000000000000 (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
3) Rename Unlocking Firmware 2.0.9 filename:
RT31P2: RT31P2_v1.17.02_000_combin_code.bin to "RT31P2_v1.30.01_000_VM_3.1.06_LI_combin_code.bin"
WRT54GP2: wrt54gp2_v1.27.02_209_combin_code.bin to "wrt54gp2_v1.30.01_000_VM_3.1.06_LI_combin_code.bin"
4) Copy the modified unlocking v2.0.9 firmware to the HTTP-ROOT/+000000000000/ directory (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
5) Double check to make sure that the renaming of the modified 2.0.9 unlocking firmware filename was completed.
STEP 3: Start the UNLOCK PROCESS (i.e. load the unlocking 2.0.9 firmware into your RT31P2/WRT54GP2):
1) Disconnect the ethernet cable from the PC running the HTTP/TFTP/DNS servers
2) Disconnect the POWER cable from the RT31P2/WRT54GP2
3) Reconnect the standard ethernet cable between the WRTGP2 WAN port and the PC ethernet port. (I don't think you'll need a crossover cable.)
4) Make sure the PC is powered up and that the DNS, TFTP and HTTP servers are running
5) Power on the RT31P2/WRT54GP2
6) If all goes well, your TFTP server's log will show the RT31P2/WRT54GP2 grabbing the encrypted file.
7) Shortly thereafter, the HTTP server's log should show the RT31P2/WRT54GP2 grabbing the modified SPA2000 v2.0.9 firmware file.
Once the RT31P2/WRT54GP2 has loaded the 2.0.9 Unlocking Firmware, you may want to double check that the firmware is updated by checking the web interface.
9) You should now be ready to proceed with re-opening the Voice Section of the Web Interface
STEP 4: Setup Dummy XML file in TFTP Folder to (Re-)Open WEB access:
1) Create a TEXT FILE called spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2) as follows:
CODE
<flat-profile>
<Restricted_Access_Domains ua="na"></Restricted_Access_Domains>
<Enable_Web_Server ua="na">Yes</Enable_Web_Server>
<Web_Server_Port ua="na">80</Web_Server_Port>
<Enable_Web_Admin_Access ua="na">Yes</Enable_Web_Admin_Access>
<Admin_Passwd ua="na"></Admin_Passwd>
<User_Password ua="na"></User_Password>
<Protect_IVR_FactoryReset ua="na">No</Protect_IVR_FactoryReset>
</flat-profile>
2) Copy the new dummy spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2) file to your TFTP ROOT directory (or directories if running multiple TFTP servers)
3) Make sure the encrypted xml config file is REMOVED from your TFTP root. You only want the dummy file now.
4) Reconnect the standard ethernet cable between the RT31P2/WRT54GP2 WAN port and the PC ethernet port. (I don't think you'll need a crossover cable.)
5) Make sure all your servers are still started and then power cycle the RT31P2/WRT54GP2.
6) Check your TFTP Server's log to see when the file has been grabbed
If the TFTP Server's log shows a FILE NOT FOUND error message, and if the file attempting to be grabbed was requested from an obscurely named sub-directory (i.e. /a12BcdeFgH/spa000000000000.xml), create that sub-directory (a12BcdeFgH) underneath the TFTP Root and move (or copy) the spa000000000000.xml file to that sub-directory. Then re-Power Cycle the RT31P2/WRT54GP2 and re-check the TFTP Server's log.
7) You should now have access to the Voice_adminPage.htm of your adapter.
RT31P2/WRT54GP2 Voice Web Interface: >>http://192.168.15.1/Voice_adminPage.htm
At this point, you don't want to make any changes in the Voice Tab as the modified RT31P2/WRT54GP2 firmware is unstable.
Note: The unlocking 2.0.9 firmware allows PLAIN TEXT config files to be loaded and processed. That is why this unlock "trick" works.
STEP 5: Obtain the FACTORY FRESH GPP_K key (recommended)
Why do I need the GPP_K value? (Linked Post for Details)
1) On the Provision page in the Voice section of your Web Interface copy down the Vonage GPP_K value. This is NOT the value you need, but it may be worth writing down in a text file for future reference.
RT31P2/WRT54GP2 Voice Web Interface: >>http://192.168.15.1/Voice_adminPage.htm
2) In STEP 3, the encrypted Vonage Config File got loaded into the adapter. This caused the adapter's FACTORY FRESH GPP_K value to be overwritten w/ one supplied by Vonage.
3) With the adapter disconnected from the internet and loaded with the 2.0.9 unlocking firmware, FACTORY RESET THE ADAPTER (Using Web Interface if possible). This will cause the FACTORY FRESH GPP_K value to be re-loaded, but it will also re-lock the adapter. Before FACTORY RESETTING the adapter though, delete your Vonage Encrypted spa000000000000.xml file from your TFTP ROOT! Otherwise, upon performing a FACTORY RESET, your adapter will request and process this file, a file which DISABLES THE ADAPTER'S WEB INTERACE! dry.gif
4) Repeat STEP 1 (Setup Servers) and STEP 4 (Load Dummy XML file) to Re-Open your Web Interface. (Step 1 and Step 4 ONLY)
5) After the adapter has been re-unlocked, extract the GPP_K value and save it!
6) Copy down the GPP_K value into a text file and save. This GPP_K should be the Factory Fresh value.
How do you tell the difference beween the FACTORY FRESH GPP_K value and a Vonage assigned one? (Link)
7) To verify that this is the Factory Fresh value, use VuckFonage to download and decrypt the XML file.
How do I use VuckFonage? (Link)
STEP 6: Upgrade to a Stable Firmware:
1) Go to the Firmware Update page of the Web Interface
2) Update to the Latest Stable Firmware
RT31P2 Stable Firmware: (Latest Firmware Link)
WRT54GP2 Stable Firmware: (Latest Firmware Link)
3) After the firmware update, you should still have access to the Voice Admin page.
4) You should now be able to disable provisioning and remove the Vonage DNS entries as this is a stable firmware.
This is the Long Method unlock instructions which involve extra tasks like loading an encrypted xml file w/o using internet provisioning.
Please Note: This is an advanced unlock process. meister_sd's original methods in Post 4/Post 5 or the Guides in Post 10 may be easier.
Pre-Unlock Setup:
RT31P2 - See Post #2 (Link)
WRT54GP2 - See Post #3 (Link)
STEP 0 : Factory Reset the adapter (Optional):
1) This step probably isn't necessary unless you had a number of problems with your adapter or your adapter has already been on the internet. You could probably skip it unless you have further issues during the unlock process.
2) There are two methods of reset if you need to use it:
- Hold the reset button on the back for 5 seconds (Some say 30 seconds)
- In the Web Interface at 192.168.15.1, reset to factory defaults under the administration tab.
STEP 1: Setup the HTTP/TFTP/DNS/DHCP servers to load encrypted xml file and firmware:
1) See Server Setup Post #8 (Link)
STEP 2: Prepare your local file structure:
Encrypted XML:
1) In your TFTP ROOT directory (or directories if running multiple TFTP servers), copy your adapter's ENCRYPTED config file to that directory as spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
To download it: >>http://httpconfig.vonage.net/spa000000000000.xml (where 000000000000 is the MAC ADDRESS)
2.0.9 Unlocking Firmware:
2) In your HTTP ROOT directory (typically htdocs for Apache, docs for IPlanet/Netscape, wwwroot for IIS), create sub-directory: +000000000000 (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
3) Rename Unlocking Firmware 2.0.9 filename:
RT31P2: RT31P2_v1.17.02_000_combin_code.bin to "RT31P2_v1.30.01_000_VM_3.1.06_LI_combin_code.bin"
WRT54GP2: wrt54gp2_v1.27.02_209_combin_code.bin to "wrt54gp2_v1.30.01_000_VM_3.1.06_LI_combin_code.bin"
4) Copy the modified unlocking v2.0.9 firmware to the HTTP-ROOT/+000000000000/ directory (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2)
5) Double check to make sure that the renaming of the modified 2.0.9 unlocking firmware filename was completed.
STEP 3: Start the UNLOCK PROCESS (i.e. load the unlocking 2.0.9 firmware into your RT31P2/WRT54GP2):
1) Disconnect the ethernet cable from the PC running the HTTP/TFTP/DNS servers
2) Disconnect the POWER cable from the RT31P2/WRT54GP2
3) Reconnect the standard ethernet cable between the WRTGP2 WAN port and the PC ethernet port. (I don't think you'll need a crossover cable.)
4) Make sure the PC is powered up and that the DNS, TFTP and HTTP servers are running
5) Power on the RT31P2/WRT54GP2
6) If all goes well, your TFTP server's log will show the RT31P2/WRT54GP2 grabbing the encrypted file.
7) Shortly thereafter, the HTTP server's log should show the RT31P2/WRT54GP2 grabbing the modified SPA2000 v2.0.9 firmware file.
Once the RT31P2/WRT54GP2 has loaded the 2.0.9 Unlocking Firmware, you may want to double check that the firmware is updated by checking the web interface. 9) You should now be ready to proceed with re-opening the Voice Section of the Web Interface
STEP 4: Setup Dummy XML file in TFTP Folder to (Re-)Open WEB access:
1) Create a TEXT FILE called spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2) as follows:
CODE
<flat-profile>
<Restricted_Access_Domains ua="na"></Restricted_Access_Domains>
<Enable_Web_Server ua="na">Yes</Enable_Web_Server>
<Web_Server_Port ua="na">80</Web_Server_Port>
<Enable_Web_Admin_Access ua="na">Yes</Enable_Web_Admin_Access>
<Admin_Passwd ua="na"></Admin_Passwd>
<User_Password ua="na"></User_Password>
<Protect_IVR_FactoryReset ua="na">No</Protect_IVR_FactoryReset>
</flat-profile>
2) Copy the new dummy spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your RT31P2/WRT54GP2) file to your TFTP ROOT directory (or directories if running multiple TFTP servers)
3) Make sure the encrypted xml config file is REMOVED from your TFTP root. You only want the dummy file now.
4) Reconnect the standard ethernet cable between the RT31P2/WRT54GP2 WAN port and the PC ethernet port. (I don't think you'll need a crossover cable.)
5) Make sure all your servers are still started and then power cycle the RT31P2/WRT54GP2.
6) Check your TFTP Server's log to see when the file has been grabbed
If the TFTP Server's log shows a FILE NOT FOUND error message, and if the file attempting to be grabbed was requested from an obscurely named sub-directory (i.e. /a12BcdeFgH/spa000000000000.xml), create that sub-directory (a12BcdeFgH) underneath the TFTP Root and move (or copy) the spa000000000000.xml file to that sub-directory. Then re-Power Cycle the RT31P2/WRT54GP2 and re-check the TFTP Server's log.
7) You should now have access to the Voice_adminPage.htm of your adapter.
RT31P2/WRT54GP2 Voice Web Interface: >>http://192.168.15.1/Voice_adminPage.htm
At this point, you don't want to make any changes in the Voice Tab as the modified RT31P2/WRT54GP2 firmware is unstable. Note: The unlocking 2.0.9 firmware allows PLAIN TEXT config files to be loaded and processed. That is why this unlock "trick" works.
STEP 5: Obtain the FACTORY FRESH GPP_K key (recommended)
Why do I need the GPP_K value? (Linked Post for Details)
1) On the Provision page in the Voice section of your Web Interface copy down the Vonage GPP_K value. This is NOT the value you need, but it may be worth writing down in a text file for future reference.
RT31P2/WRT54GP2 Voice Web Interface: >>http://192.168.15.1/Voice_adminPage.htm
2) In STEP 3, the encrypted Vonage Config File got loaded into the adapter. This caused the adapter's FACTORY FRESH GPP_K value to be overwritten w/ one supplied by Vonage.
3) With the adapter disconnected from the internet and loaded with the 2.0.9 unlocking firmware, FACTORY RESET THE ADAPTER (Using Web Interface if possible). This will cause the FACTORY FRESH GPP_K value to be re-loaded, but it will also re-lock the adapter. Before FACTORY RESETTING the adapter though, delete your Vonage Encrypted spa000000000000.xml file from your TFTP ROOT! Otherwise, upon performing a FACTORY RESET, your adapter will request and process this file, a file which DISABLES THE ADAPTER'S WEB INTERACE! dry.gif
4) Repeat STEP 1 (Setup Servers) and STEP 4 (Load Dummy XML file) to Re-Open your Web Interface. (Step 1 and Step 4 ONLY)
5) After the adapter has been re-unlocked, extract the GPP_K value and save it!
6) Copy down the GPP_K value into a text file and save. This GPP_K should be the Factory Fresh value.
How do you tell the difference beween the FACTORY FRESH GPP_K value and a Vonage assigned one? (Link)
7) To verify that this is the Factory Fresh value, use VuckFonage to download and decrypt the XML file.
How do I use VuckFonage? (Link)
STEP 6: Upgrade to a Stable Firmware:
1) Go to the Firmware Update page of the Web Interface
2) Update to the Latest Stable Firmware
RT31P2 Stable Firmware: (Latest Firmware Link)
WRT54GP2 Stable Firmware: (Latest Firmware Link)
3) After the firmware update, you should still have access to the Voice Admin page.
4) You should now be able to disable provisioning and remove the Vonage DNS entries as this is a stable firmware.
