6300 spansion ver 6.01 - GSM-Forum

CHAGUA · 04-12-2008, 20:23

i have this phone that i cant reset fbus counters cuase the state of the phone is fbus 10 from 10 and keyboard is 0 of 3 so the application doesnt let me rest cause its says counters are not to the limit and the problem is that when i try to unlock the keyboard response is byte 07 so what can i do try to fix this bug

thks

br
chaguaceda

MishkaGSM · 04-13-2008, 21:52

12th Mar 2008, 09:16 #4 SEMEN
No Life Poster

Join Date: Aug 2006
Age: 22
Posts: 600
Member: 333494
Status: Offline

my frend use serch button its problem postet many times
This byte response (07) you get only on phones from Telcel Mexico where entering codes is disabled.
More responses details:
08 - wrong code entered (in our case because of wrong TP cannot patch corectly flash on the fly)
0C - no more tries left (wrong counter at max. value)
55 - communication error (usualy when connect TP in wrong location

next time try to use serch button

ronandaly · 04-14-2008, 08:53

Quote:

Originally Posted by CHAGUA

i have this phone that i cant reset fbus counters cuase the state of the phone is fbus 10 from 10 and keyboard is 0 of 3 so the application doesnt let me rest cause its says counters are not to the limit and the problem is that when i try to unlock the keyboard response is byte 07 so what can i do try to fix this bug

thks

br
chaguaceda

Possibly your SP area is corrupted - if you posted your log then maybe you will get the correct solution to your problem.

Quote:

Originally Posted by MishkaGSM

12th Mar 2008, 09:16 #4 SEMEN
No Life Poster

Join Date: Aug 2006
Age: 22
Posts: 600
Member: 333494
Status: Offline

my frend use serch button its problem postet many times
This byte response (07) you get only on phones from Telcel Mexico where entering codes is disabled.
More responses details:
08 - wrong code entered (in our case because of wrong TP cannot patch corectly flash on the fly)
0C - no more tries left (wrong counter at max. value)
55 - communication error (usualy when connect TP in wrong location

next time try to use serch button

Better you get your facts right before you give lectures about using the search button. If you searched for Byte 07 you will find that not only does it appear on Telecel phones but also any phone with a corrupt SP area.

BR

Ronan

CHAGUA · 04-14-2008, 16:50

first of all i know what response byte 07 is but this phone is from movistar and its locked to a lot of carriers

2nd this is not somthing that is posted before if it was it i didnt ask

3rd my sp area is not corrupted

Connecting to BB5 Box ...
Searching for phone ...
Phone found on FBUS interface
Reading phone info ...
Type: RM-217
Version: V_06.01_16-01-08_RM-217_(c)_Nokia.
IMEI: 354827014538159
SP LOCK status:
Config Key: 3340309996332460
Block 1: CLOSED Type 5 Data: 33403F
Block 2: CLOSED Type 5 Data: 70403F
Block 3: CLOSED Type 5 Data: 70604F
Block 4: CLOSED Type 5 Data: 71030F
Block 5: CLOSED Type 5 Data: 71402F
Block 6: CLOSED Type 5 Data: 72207F
Block 7: CLOSED Type 5 Data: 73002F
Block 8: CLOSED Type 5 Data: 73212F
Block 9: CLOSED Type 5 Data: 74000F
Block 10: CLOSED Type 5 Data: 74807F
Block 11: CLOSED Type 5 Data: 21407F
Block 12: CLOSED Type 5 Data: 21402F
Block 13: CLOSED Type 5 Data: 71606F
Keyboard wrong codes counter: 0 wrong tries from max. 3 tries
Cable wrong codes counter: 10 wrong tries from max. 10 tries
Checking if model/version is supported for unlock ...
This model/version IS SUPPORTED for FBUS counter reset.
This model/version IS SUPPORTED for UNLOCK.

after unlock attempt

Connecting to BB5 Box ...
Searching for phone ...
Phone found on FBUS interface
Reading phone info ...
Type: RM-217
Version: V_06.01_16-01-08_RM-217_(c)_Nokia.
IMEI: 354827014538159
SP LOCK status:
Config Key: 3340309996332460
Block 1: CLOSED Type 5 Data: 33403F
Block 2: CLOSED Type 5 Data: 70403F
Block 3: CLOSED Type 5 Data: 70604F
Block 4: CLOSED Type 5 Data: 71030F
Block 5: CLOSED Type 5 Data: 71402F
Block 6: CLOSED Type 5 Data: 72207F
Block 7: CLOSED Type 5 Data: 73002F
Block 8: CLOSED Type 5 Data: 73212F
Block 9: CLOSED Type 5 Data: 74000F
Block 10: CLOSED Type 5 Data: 74807F
Block 11: CLOSED Type 5 Data: 21407F
Block 12: CLOSED Type 5 Data: 21402F
Block 13: CLOSED Type 5 Data: 71606F
Keyboard wrong codes counter: 0 wrong tries from max. 3 tries
Cable wrong codes counter: 10 wrong tries from max. 10 tries
Set Full Factory Defaults ...
Reset phone ...
Full Factory Defaults set OK
Skip autobackup of PM 308
Autobackup file:
RM-217_354827014538159_Locked_Keycnt_0_Fbuscnt_10__V_ 06.01_16-01-08_RM-217_(c)_Nokia..bin
already exist
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: 07
Try number (Keyboard): 2
Sending SP code: #pw+012345678901234+7#
Response byte: 07
Try number (Keyboard): 3
Sending SP code: #pw+012345678901234+7#
Response byte: 07
Unlock using keyboard codes fail.
Reading again SP Locks ...
SP LOCK status:
Config Key: 3340309996332460
Block 1: CLOSED Type 5 Data: 33403F
Block 2: CLOSED Type 5 Data: 70403F
Block 3: CLOSED Type 5 Data: 70604F
Block 4: CLOSED Type 5 Data: 71030F
Block 5: CLOSED Type 5 Data: 71402F
Block 6: CLOSED Type 5 Data: 72207F
Block 7: CLOSED Type 5 Data: 73002F
Block 8: CLOSED Type 5 Data: 73212F
Block 9: CLOSED Type 5 Data: 74000F
Block 10: CLOSED Type 5 Data: 74807F
Block 11: CLOSED Type 5 Data: 21407F
Block 12: CLOSED Type 5 Data: 21402F
Block 13: CLOSED Type 5 Data: 71606F
Keyboard wrong codes counter: 0 wrong tries from max. 3 tries
Cable wrong codes counter: 10 wrong tries from max. 10 tries
Unlock fail. Please try again.

trying to reset counters

Connecting to BB5 Box ...
Searching for phone ...
Phone found on FBUS interface
Reading phone info ...
Type: RM-217
Version: V_06.01_16-01-08_RM-217_(c)_Nokia.
IMEI: 354827014538159
SP LOCK status:
Config Key: 3340309996332460
Block 1: CLOSED Type 5 Data: 33403F
Block 2: CLOSED Type 5 Data: 70403F
Block 3: CLOSED Type 5 Data: 70604F
Block 4: CLOSED Type 5 Data: 71030F
Block 5: CLOSED Type 5 Data: 71402F
Block 6: CLOSED Type 5 Data: 72207F
Block 7: CLOSED Type 5 Data: 73002F
Block 8: CLOSED Type 5 Data: 73212F
Block 9: CLOSED Type 5 Data: 74000F
Block 10: CLOSED Type 5 Data: 74807F
Block 11: CLOSED Type 5 Data: 21407F
Block 12: CLOSED Type 5 Data: 21402F
Block 13: CLOSED Type 5 Data: 71606F
Keyboard wrong codes counter: 0 wrong tries from max. 3 tries
Cable wrong codes counter: 10 wrong tries from max. 10 tries
Counters lower than maximum limit. No need reset counters

so as you can see im not doing nothings wrong dont try to know to much cause youll never finish to learn in this life so supporters what about this case

thks

ronandaly · 04-14-2008, 20:29

If you are so sure that your phone is fine and that the software has a bug then try version 0.3.1 which was the first version to support 0/3 & 10/10 unlocking. You will have to downgrade the phone to do so. If you still get error 07 then it proves your phone has a corrupt SP area. There was no need to be rude when asking for help. Just because you don't like the suggestions doesn't mean you are right. I said that POSSIBLY your SP area was corrupted. Please read before you get up on your high horse. By the way how did your phone get in this condition?

CHAGUA · 04-14-2008, 20:49

Quote:

Originally Posted by ronandaly

If you are so sure that your phone is fine and that the software has a bug then try version 0.3.1 which was the first version to support 0/3 & 10/10 unlocking. You will have to downgrade the phone to do so. If you still get error 07 then it proves your phone has a corrupt SP area. There was no need to be rude when asking for help. Just because you don't like the suggestions doesn't mean you are right. I said that POSSIBLY your SP area was corrupted. Please read before you get up on your high horse. By the way how did your phone get in this condition?

thks for the suggestions its just that the suggestion doesnt comes to the case im no rude and i dont want to start fighting here now for leting you know and also for other forum members the nokias

6300
5300
6131
comes with the keypad unlock desable

also the nokias 5300 6300 6131 from claro guatemala that also locked to other carriers comes with keypad unlock desabble to

BUT with unlock via fbus capable

so what should i do thats the question

what about the phones that comes with keypad unlock desabble but with fbus trys to 10 what we all should do to face this problem

thks to all

04-12-2008, 20:23	#1 (permalink)
CHAGUA No Life Poster Join Date: Mar 2006 Location: UNLOCKER SINCE 2003 Age: 42 Posts: 601 Member: 249497 Status: Offline Thanks Meter: 180	6300 spansion ver 6.01 i have this phone that i cant reset fbus counters cuase the state of the phone is fbus 10 from 10 and keyboard is 0 of 3 so the application doesnt let me rest cause its says counters are not to the limit and the problem is that when i try to unlock the keyboard response is byte 07 so what can i do try to fix this bug thks br chaguaceda

04-14-2008, 16:50	#4 (permalink)
CHAGUA No Life Poster Join Date: Mar 2006 Location: UNLOCKER SINCE 2003 Age: 42 Posts: 601 Member: 249497 Status: Offline Thanks Meter: 180	lets clarify sonthing first of all i know what response byte 07 is but this phone is from movistar and its locked to a lot of carriers 2nd this is not somthing that is posted before if it was it i didnt ask 3rd my sp area is not corrupted Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-217 Version: V_06.01_16-01-08_RM-217_(c)_Nokia. IMEI: 354827014538159 SP LOCK status: Config Key: 3340309996332460 Block 1: CLOSED Type 5 Data: 33403F Block 2: CLOSED Type 5 Data: 70403F Block 3: CLOSED Type 5 Data: 70604F Block 4: CLOSED Type 5 Data: 71030F Block 5: CLOSED Type 5 Data: 71402F Block 6: CLOSED Type 5 Data: 72207F Block 7: CLOSED Type 5 Data: 73002F Block 8: CLOSED Type 5 Data: 73212F Block 9: CLOSED Type 5 Data: 74000F Block 10: CLOSED Type 5 Data: 74807F Block 11: CLOSED Type 5 Data: 21407F Block 12: CLOSED Type 5 Data: 21402F Block 13: CLOSED Type 5 Data: 71606F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Checking if model/version is supported for unlock ... This model/version IS SUPPORTED for FBUS counter reset. This model/version IS SUPPORTED for UNLOCK. after unlock attempt Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-217 Version: V_06.01_16-01-08_RM-217_(c)_Nokia. IMEI: 354827014538159 SP LOCK status: Config Key: 3340309996332460 Block 1: CLOSED Type 5 Data: 33403F Block 2: CLOSED Type 5 Data: 70403F Block 3: CLOSED Type 5 Data: 70604F Block 4: CLOSED Type 5 Data: 71030F Block 5: CLOSED Type 5 Data: 71402F Block 6: CLOSED Type 5 Data: 72207F Block 7: CLOSED Type 5 Data: 73002F Block 8: CLOSED Type 5 Data: 73212F Block 9: CLOSED Type 5 Data: 74000F Block 10: CLOSED Type 5 Data: 74807F Block 11: CLOSED Type 5 Data: 21407F Block 12: CLOSED Type 5 Data: 21402F Block 13: CLOSED Type 5 Data: 71606F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Set Full Factory Defaults ... Reset phone ... Full Factory Defaults set OK Skip autobackup of PM 308 Autobackup file: RM-217_354827014538159_Locked_Keycnt_0_Fbuscnt_10__V_ 06.01_16-01-08_RM-217_(c)_Nokia..bin already exist 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: 07 Try number (Keyboard): 2 Sending SP code: #pw+012345678901234+7# Response byte: 07 Try number (Keyboard): 3 Sending SP code: #pw+012345678901234+7# Response byte: 07 Unlock using keyboard codes fail. Reading again SP Locks ... SP LOCK status: Config Key: 3340309996332460 Block 1: CLOSED Type 5 Data: 33403F Block 2: CLOSED Type 5 Data: 70403F Block 3: CLOSED Type 5 Data: 70604F Block 4: CLOSED Type 5 Data: 71030F Block 5: CLOSED Type 5 Data: 71402F Block 6: CLOSED Type 5 Data: 72207F Block 7: CLOSED Type 5 Data: 73002F Block 8: CLOSED Type 5 Data: 73212F Block 9: CLOSED Type 5 Data: 74000F Block 10: CLOSED Type 5 Data: 74807F Block 11: CLOSED Type 5 Data: 21407F Block 12: CLOSED Type 5 Data: 21402F Block 13: CLOSED Type 5 Data: 71606F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Unlock fail. Please try again. trying to reset counters Connecting to BB5 Box ... Searching for phone ... Phone found on FBUS interface Reading phone info ... Type: RM-217 Version: V_06.01_16-01-08_RM-217_(c)_Nokia. IMEI: 354827014538159 SP LOCK status: Config Key: 3340309996332460 Block 1: CLOSED Type 5 Data: 33403F Block 2: CLOSED Type 5 Data: 70403F Block 3: CLOSED Type 5 Data: 70604F Block 4: CLOSED Type 5 Data: 71030F Block 5: CLOSED Type 5 Data: 71402F Block 6: CLOSED Type 5 Data: 72207F Block 7: CLOSED Type 5 Data: 73002F Block 8: CLOSED Type 5 Data: 73212F Block 9: CLOSED Type 5 Data: 74000F Block 10: CLOSED Type 5 Data: 74807F Block 11: CLOSED Type 5 Data: 21407F Block 12: CLOSED Type 5 Data: 21402F Block 13: CLOSED Type 5 Data: 71606F Keyboard wrong codes counter: 0 wrong tries from max. 3 tries Cable wrong codes counter: 10 wrong tries from max. 10 tries Counters lower than maximum limit. No need reset counters so as you can see im not doing nothings wrong dont try to know to much cause youll never finish to learn in this life so supporters what about this case thks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
i need arabic ppm for 6120c ver.6.01	F@RUK S	Nokia Base Band 5 ( BB-5 )	5	05-16-2009 11:04
++--///6300 ver 6.01 Successfully Unlocked\\\--++	.::BHATTI::.	BB5 No TP By Jafsupport	4	12-15-2008 18:05
6300 Spansion VER 5.00 unlocked Successfully	.::BHATTI::.	UID - Box	0	01-31-2008 13:34
Rh 19 Ver 6.01 Nokia 3100	tnsupplies	Nokia Digital Core Technology 4 ( DCT-4 )	5	07-21-2005 22:38
Rh 19 Ver 6.01 Nokia 3100 FULL PAK	hd96	Nokia Digital Core Technology 4 ( DCT-4 )	3	07-21-2005 16:14

04-13-2008, 21:52	#2 (permalink)
MishkaGSM Junior Member Join Date: Apr 2008 Posts: 12 Member: 743572 Status: Offline Sonork: Marlboro Thanks Meter: 4	12th Mar 2008, 09:16 #4 SEMEN No Life Poster Join Date: Aug 2006 Age: 22 Posts: 600 Member: 333494 Status: Offline my frend use serch button its problem postet many times This byte response (07) you get only on phones from Telcel Mexico where entering codes is disabled. More responses details: 08 - wrong code entered (in our case because of wrong TP cannot patch corectly flash on the fly) 0C - no more tries left (wrong counter at max. value) 55 - communication error (usualy when connect TP in wrong location next time try to use serch button

04-14-2008, 20:29	#5 (permalink)
ronandaly Registered User Join Date: Feb 2006 Location: Ireland / Belarus Posts: 885 Member: 234917 Status: Offline Thanks Meter: 160	If you are so sure that your phone is fine and that the software has a bug then try version 0.3.1 which was the first version to support 0/3 & 10/10 unlocking. You will have to downgrade the phone to do so. If you still get error 07 then it proves your phone has a corrupt SP area. There was no need to be rude when asking for help. Just because you don't like the suggestions doesn't mean you are right. I said that POSSIBLY your SP area was corrupted. Please read before you get up on your high horse. By the way how did your phone get in this condition?