no good. copied to usb, ejected, opened wosqi command line window, copied above command, and here's what it did:
Originally Posted by John Steffes
C:\Users\Administrator\Documents\Palm>"C:/Program Files/Palm, Inc/novacom.exe" -
d f97f160e838599353dea7caa45c5695447f97b38 -t open tty://
root@TMcPre2sHPPre:/# ipkg install -force-overwrite /media/internal/Provisioner
ipkg install -force-overwrite /media/internal/Provisioner
Begin installation of provisioner
Installing provisioner (1.0.0-28) to root...
root@TMcPre2sHPPre:/# novacomd socket was closed prematurely
novacom: unexpected EOF from server
the 'closed' line above occurred after waiting 10 mins then disc. the phone from the computer.
i rebooted, opened the phone app, but no change with the updater options. they both say provisioning svc not avail.
things i'm now wondering:
- did i not install it right...was it done when it returned to root prompt after configuring or not??
- does it need something else, an external file to refer to that i didn't copy over from the sprint tar?
- is my meta sprint franken dr. config preventing it somehow? one of the confusing things about my franken install is that my device info (and i assume its token values too) still say Verizon and Pre2 model number. i've read those values needed to match the sprint comm board, but the conversion instructions say token values aren't needed any longer so i never worried about it.
are the token values of consideration any longer? does the OP also need to check if their phone has its own, or the comm board's identity and token values?
of course the goal here is to test if this provisioning ipk will communicate to sprint at all with an active phone, then the OP may have something to aim for with their partially active phone.