Testing challenge code 03 error on uid
 

any idea why most of the time i get this error on n95's with uid:

"Testing challenge code 03" and it hangs here,

after about 50 tries it works but it takes too long to do.

testpoints are ok.

br

log:

Server: [70.85.181.2], port: [35555]
Will use server 70.85.181.2 to port 35555
BB5 box connected, awaiting commands.
Request box ID.
************************************************** ************************************
BOX INFO: ID: 0b75, VERSION: beef, HW_REV: cb, SW_REV: 01
************************************************** ************************************
Connecting server...Server conected.
Requesting data...Got page, exiting!
Got auth: [48ae36be407a1ee52936a33cdcd4b2b35ba1dfc467f9310075 4b5570fc0ca32a00], ssid: [118885064825933]
Incoming auth_req len: 33
48 ae 36 be 40 7a 1e e5 29 36 a3 3c dc d4 b2 b3 5b a1 df c4 67 f9 31 00 75 4b 55 70 fc 0c a3 2a 00
Requested Secret
**SECRET_ANSWER:
0b75beef76dbc90b3e657180c48aaf2360641047671d203431 b561c266ac51853acf3f1f15
Connecting server...Server conected.
Requesting data...Got page, exiting!
Got unlock block: [0a6cd2f72683384a19fdcf47fe6fe9a82c79f216308c995753 e022fde264fcc5b707d56f57e14de61e1f45e3a57b9caf92fc 09e9266ebbb964b301e371f45eec60f730e8a134d9331f14fc 1edad7871a6adbbce3f63b5470b12a4d89969215645a27c1f1 ea18e5a304b0c355f5c0ded3097ebd318acefe7afdb6bbb20e 45b08600]
Sending UNLOCK string(128 bytes)
unl_log: 01
unl_log: 02
unl_log: 30
unl_log: 03
unl_log: 33
Please press '#pw+369765105835521+1#' on phone keypad NOW!
Testing challenge code 03
Testing challenge code 02
Incomplete challenge - code missing. Box will try again in about 20 seconds
Box ready to retry!
unl_log: 04
unl_log: 03
unl_log: 33
Please press '#pw+789943302799997+1#' on phone keypad NOW!
Testing challenge code 03

then it hangs.

br

bro your problem is dont have good connection on rap or on gnd
read this and post result
http:///vbb/showpo...6&postcount=41

still the same and most of the time the phone re-starts for no reason?

br

another n95 and the same.

anyone know the problem??

br

fixed now...........