Cruiser 2.20b Problem - GSM-Forum

isaackenny · 01-27-2005, 12:39

Few weird problem on Cruiser 2.20b when booting certain type K700 attempt to unlock RSA but CANT , while trying to boot with Cruiser 1.00 there is no problem n no need to unlock RSA see the picture below

seanhong · 01-27-2005, 14:35

i got some similar problem.
K500i i try to unlock 4 locks so i try it out with Cruiser then i was able to unlock the RSA.
then the same phone i unlock it using SETool 'direct unlock' after that when i connect back to Cruiser i was failed.
when reach 'must unlock RSA first' then i press unlock RSA its writen 'invalid response'.

is it the 2.20b bugs or wat????

BR

muppet · 01-27-2005, 16:38

Quote:

Originally Posted by isaackenny

Few weird problem on Cruiser 2.20b when booting certain type K700 attempt to unlock RSA but CANT , while trying to boot with Cruiser 1.00 there is no problem n no need to unlock RSA see the picture below

Have you tried unticking "Analyse Configuration" ?

isaackenny · 01-27-2005, 16:55

original configuration ..

gbrooks3 · 01-27-2005, 17:05

@isaackenny

I notice in the first picture you select K700c from the list of phone but in the second picture you use autodetect. Maybe this is nothing to do with it but its the only thing i can think of.

isaackenny · 01-27-2005, 17:27

i select K700c because the Cruiser 1.00 unable to defined the TAC so the phone unknown if using auto detect

isaackenny · 01-27-2005, 17:32

the problem is on all my K700 i had around 50 pcs IMEI start from 354010-00-XXXXXX Orange customised K700 any only worked on Cruise 1.00 but not worked in 2.20b

01-27-2005, 12:39	#1 (permalink)
isaackenny Freak Poster Join Date: Feb 2002 Location: singapore Age: 46 Posts: 404 Member: 9194 Status: Offline Thanks Meter: 3	Cruiser 2.20b Problem Few weird problem on Cruiser 2.20b when booting certain type K700 attempt to unlock RSA but CANT , while trying to boot with Cruiser 1.00 there is no problem n no need to unlock RSA see the picture below Last edited by isaackenny; 02-25-2008 at 11:42.

01-27-2005, 14:35	#2 (permalink)
seanhong Insane Poster Join Date: Jul 2004 Age: 45 Posts: 72 Member: 71845 Status: Offline Thanks Meter: 0	i got some similar problem. K500i i try to unlock 4 locks so i try it out with Cruiser then i was able to unlock the RSA. then the same phone i unlock it using SETool 'direct unlock' after that when i connect back to Cruiser i was failed. when reach 'must unlock RSA first' then i press unlock RSA its writen 'invalid response'. is it the 2.20b bugs or wat???? BR

01-27-2005, 16:55	#4 (permalink)
isaackenny Freak Poster Join Date: Feb 2002 Location: singapore Age: 46 Posts: 404 Member: 9194 Status: Offline Thanks Meter: 3	original configuration ..

01-27-2005, 17:05	#5 (permalink)
gbrooks3 No Life Poster Join Date: Jul 2004 Location: 0xBA, 0xBE Age: 38 Posts: 690 Member: 73743 Status: Offline Thanks Meter: 2	@isaackenny I notice in the first picture you select K700c from the list of phone but in the second picture you use autodetect. Maybe this is nothing to do with it but its the only thing i can think of.

01-27-2005, 17:27	#6 (permalink)
isaackenny Freak Poster Join Date: Feb 2002 Location: singapore Age: 46 Posts: 404 Member: 9194 Status: Offline Thanks Meter: 3	i select K700c because the Cruiser 1.00 unable to defined the TAC so the phone unknown if using auto detect

01-27-2005, 17:32	#7 (permalink)
isaackenny Freak Poster Join Date: Feb 2002 Location: singapore Age: 46 Posts: 404 Member: 9194 Status: Offline Thanks Meter: 3	the problem is on all my K700 i had around 50 pcs IMEI start from 354010-00-XXXXXX Orange customised K700 any only worked on Cruise 1.00 but not worked in 2.20b