QUOTE(cunyalen @ 1-4-07, 7:28pm)

Why do you emphasize PRIMARY (i.e. ROOT )XML? Do you mean that if we don't factory reset it, it may request an xml file other than Primary? Is so, won't it request FW?
The only Vonage XML who's GPP_K value remains constant is the PRIMARY XML file. An adapter fresh out of the box should be asking for its PRIMARY XML file, but in the event it's not, a factory reset will ensure that it does.
QUOTE(cunyalen @ 1-4-07, 7:28pm)

In the unlock guide for 3.1.7+, the first step is "STEP 1: Factory Reset the adapter:". The only thing we do with that is remove the dns server. Actually, this could be done with IVR like in step 3. So, if we don't factory reset, we can still proceed our unlock process by feeding the xml file and it'll request FW, then feed the plain txt file to set user and admin password. It's not like in step 1 "If not, you’re pretty much “stuck” at this point and need to find a working Vonage USER Password."
Right?
Correct. The 3.1.7+ unlock guide was written back when USED PAP2's connected to the internet could still be unlocked. Those PAP2's needed to be FACTORY RESET to ensure that they'd request their PRIMARY (i.e. ROOT) XML file.
QUOTE(cunyalen @ 1-4-07, 7:28pm)

If we don't do the factory reset, we can still open the web interface, but we can't access because we don't have the password for user. Right? But it won't stop us from unlocking it.
There may not necessarily be a USER password defined on a virgin PAP2 v1 (Vonage), so you may in fact be able to access USER mode of the web interface.
QUOTE(cunyalen @ 1-4-07, 7:28pm)

The reason why I'm asking this is because I see a post on broadbandreport as follows
So, if we don't factory reset it, we'll be able to feed FW again and again.
Interesting theory, but I'm skeptical about its outcome. The last BRAND NEW PAP2v1 3.1.9 I unlocked took several "rounds" to complete. This was a PAP2 I had purchased due to numerous posters in this thread claiming that the unlock process was no longer working. (It was also what led me to come up with the CROSSOVER CABLE method). Anyway, I didn't have my HTTP directory structure setup correctly for several "rounds," but my TFTP structure was in place. Each time the adapter loaded the XML file,
it made an HTTP request to load the firmware but failed. After each failure, I would FACTORY RESET the adapter and start all over. This happened 2 or 3 times,
with each time HTTP requesting a firmware file, until I finally had my directory structure setup correctly. Thereafter the adapter loaded firmware (SPA2K 2.0.9), after which I finished the unlock process, extracted the GPP_K, and finally loaded true PAP2 3.1.6 firmware onto the adapter. Since this PAP2 was purchased for testing purposes only (and was anyway going to return when done), after it was unlocked, I FACTORY RESET it and connected it to the internet just to see what would happen. The adapter loaded its PRIMARY XML FILE from Vonage
but DID NOT attempt a firmware upgrade to 3.1.9 even though it was now loaded w/ 3.1.6! Thus, this adapter had made multiple HTTP attempts to automatically load in firmware until it finally succeeded in loading a firmware file. Thereafter, it no longer attempted any
automatic firmware upgrades with Vonage's XML files, even when communicating directly w/ Vonage's servers.
Diggler