|
|
 |
|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
| |||||||
| Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source | Today's Posts | Search |
 |
| | LinkBack | Thread Tools | Display Modes |
02-15-2008, 11:22
| #1 (permalink) |
| Crazy Poster  Join Date: Mar 2005 Age: 47
Posts: 49
Member: 122256 Status: Offline Thanks Meter: 2 | why is this happend? ------ Operation: READ PHONE INFO Date: 15-02-2008 Time: 11:24:39 ------- Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-170 Version: V_2.26.01_04-07-06_RM-170_(c)_Nokia. IMEI: 351***xx SP LOCK status: Config Key: 2261000000000000 Block 1: CLOSED Type 5 Data: 22610F Block 2: CLOSED Type 5 Data: 22610F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 0 wrong tries from max. 10 tries Checking if model/version is supported for unlock ... This model/version IS SUPPORTED for unlock. ------ Operation: READ PM 308 Date: 15-02-2008 Time: 11:24:49 ------- Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-170 Version: V_2.26.01_04-07-06_RM-170_(c)_Nokia. IMEI: 351*** Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 0 wrong tries from max. 10 tries Reading PM Field 308 Subfield 1 with length 8192 bytes Saving to file: RM-170_351***_Locked_Keycnt_0_Fbuscnt_0__V_2.26.01_04-07-06_RM-170_(c)_Nokia.__15_02_2008__11_25_02.bin Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-170 Version: V_2.26.01_04-07-06_RM-170_(c)_Nokia. IMEI: 351*** SP LOCK status: Config Key: 2261000000000000 Block 1: CLOSED Type 5 Data: 22610F Block 2: CLOSED Type 5 Data: 22610F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 0 wrong tries from max. 10 tries Create autobackup of PM 308 Reading PM Field 308 Subfield 1 with length 8192 bytes Saving autobackup to file: RM-170_351***xx_Locked_Keycnt_0_Fbuscnt_0__V_2.26.01_ 04-07-06_RM-170_(c)_Nokia..bin Checking if model/version is supported for unlock ... Please connect testpoints Testpoints connected OK Keep Testpoints connected until unlock finish! Unlocking phone ... Try unlocking using keyboard codes ... Try number (Keyboard): 1 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Keyboard): 2 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Keyboard): 3 Sending SP code: #pw+012345678901234+7# Response byte: 08 Unlock using keyboard codes fail. Try unlocking using cable codes ... Try number (Cable): 1 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 2 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 3 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 4 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 5 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 6 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 7 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 8 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 9 Sending SP code: #pw+012345678901234+7# Response byte: 08 Try number (Cable): 10 Sending SP code: #pw+012345678901234+7# Response byte: 08 Unlock using cable codes fail. Reading again SP Locks ... SP LOCK status: Config Key: 2261000000000000 Block 1: CLOSED Type 5 Data: 22610F Block 2: CLOSED Type 5 Data: 22610F Keyboard wrong codes counter: 3 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Unlock fail. Please try again. ------ Operation: WRITE PM 308 Date: 15-02-2008 Time: 11:41:11 ------- Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-170 Version: V_2.26.01_04-07-06_RM-170_(c)_Nokia. IMEI: 351***xx Keyboard wrong codes counter: 3 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Writting PM Field 308 Subfield 1 with length 8192 bytes Reset phone ... PM Field 308 Subfield 1 written OK ------ Operation: READ PHONE INFO Date: 15-02-2008 Time: 11:41:29 ------- Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-170 Version: V_2.26.01_04-07-06_RM-170_(c)_Nokia. IMEI: 351****** SP LOCK status: Config Key: 2261000000000000 Block 1: CLOSED Type 5 Data: 22610F Block 2: CLOSED Type 5 Data: 22610F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 0 wrong tries from max. 10 tries Checking if model/version is supported for unlock ... Model/version NOT supported for unlock. Please upgrade or downgrade! |
 |
|
02-15-2008, 11:44
| #3 (permalink) |
| Crazy Poster Join Date: Mar 2005 Age: 47
Posts: 49
Member: 122256 Status: Offline Thanks Meter: 2 | but first time software version supported, second time software not supported, and is the same phone.... info phone supported unlock unlock failed write pm308 info phone not supported |
| |
|
02-15-2008, 12:05
| #4 (permalink) |
| Crazy Poster Join Date: Feb 2006
Posts: 54
Member: 228551 Status: Offline Thanks Meter: 3 | Make sure you select chip type properly, I think you selected wrong chip type on first read, not all chip types and versions can be done, some chip types can be done with newer versions and some cannot be done with new versions. Check this, and if not the case, then check points on PCB etc, clean down with brush and fluid - Usually solves my problems. br, Danny. |
| |
|
02-15-2008, 12:12
| #6 (permalink) | |
| Crazy Poster Join Date: Mar 2005 Age: 47
Posts: 49
Member: 122256 Status: Offline Thanks Meter: 2 | Quote:
no chip seloction for this model E50 RM-170 please read my first post again is the log of one single phone first unlock attempt say phone supported, unlock failed then write pm308 backup and tried again to unlock and box say pnone not supported why? | |
| |
|
02-15-2008, 15:07
| #8 (permalink) |
| Product Manager  Join Date: Sep 2007
Posts: 886
Member: 588059 Status: Offline Thanks Meter: 47 | @decebal: You have some problems with your box. Mainly this happens if: 1. Your box have USB communication problems with PC (check your USB cable, HUB port - if used, your PC USB port power, other FTDI drivers installed on your PC, ...) 2. Smartcard inside box have dirty contacts. Open your box and move/clean smartcard and smartcard connector contacts. 3. Your box firmware is not written correctly, try to make update firmware again |
| |
|
02-15-2008, 16:27
| #9 (permalink) | |
| Crazy Poster Join Date: Mar 2005 Age: 47
Posts: 49
Member: 122256 Status: Offline Thanks Meter: 2 | Quote:
thank you for reply i will do all things you indicated usb power too low is probably my problem here i made the unlock using another tool(customer was not pacient) so i can't tell wich problem i had, if i face the problem again i will inform you i hope that it won't be the case | |
| |
|
| Bookmarks |
| |
Similar Threads | ||||
| thread | Thread Starter | Forum | Replies | Last Post |
| why is this removed from API? | Sigma | Genie Universal | 12 | 08-07-2008 21:50 |
| Why is this happening with support area...... | sokolibrahimi | FuriousGold | 1 | 04-14-2008 14:05 |
| Why is this error? | Indyss | Universalbox | 4 | 06-27-2007 16:17 |
| why is this erorr in Z300 ??? | cellularman | NSPRO | 0 | 12-22-2005 16:44 |
|
|
Linear Mode
