S5230 unlock error !!! [ANSWERED] - GSM-Forum

zapped · 03-02-2010, 20:55

connect phone
detecting. . .
found! phone mode : #NORMAL#
model : GT-S5230
imei no. : 357952-03-32xxxx-1
fw version : S5230BBIG
unique id : 55190000378283
patience, BOOTmode sequence activating. . .
[!] NANO-DBG.UART.Error* receive[] missing A5_resp

The_Gorr · 03-03-2010, 01:30

check if phone code is activated, if yes, desable it
also try to reinstall drivers, it's possible they cause this error

br

<= The_Gorr =>

Amir-SkillZ · 03-03-2010, 06:22

Hello,

Reading Simlock Codes Should install broadcom2 drivers
When BootMode Sequence Try to be Engaged if it fails ...Such error will come
Retry Should Work Fine..
I saw encounter this error but was Ok in second TRY

zapped · 03-03-2010, 10:36

thanks for the answers... will try again next time i get this model! I tried a few times and I made sure the drivers were downloaded from nanobox support and installed but I was always getting that error... maybe resetting the phone was going to fix this but the customer did not want to lose the info on the phone so I had to use another tool to unlock it.

Amir-SkillZ · 03-04-2010, 06:11

No the Problem ONly was
When phone changes it Mode to bootloader for its final Step for unlocking through server
Due to some communication timing prob etc it fails phone gets ON
and u will recieve such error as above...
here i personally tested today ...got same issue for first time...secondly gets OK
http://forum.gsmhosting.com/vbb/show...5&postcount=42

03-02-2010, 20:55	#1 (permalink)
zapped No Life Poster Join Date: Feb 2003 Location: here Posts: 958 Member: 20953 Status: Offline Thanks Meter: 94	S5230 unlock error !!! [ANSWERED] connect phone detecting. . . found! phone mode : #NORMAL# model : GT-S5230 imei no. : 357952-03-32xxxx-1 fw version : S5230BBIG unique id : 55190000378283 patience, BOOTmode sequence activating. . . [!] NANO-DBG.UART.Error* receive[] missing A5_resp

03-04-2010, 06:11	#5 (permalink)
Amir-SkillZ No Life Poster Join Date: Nov 2004 Location: Capetown Posts: 6,709 Member: 91045 Status: Offline Thanks Meter: 8,696	No the Problem ONly was When phone changes it Mode to bootloader for its final Step for unlocking through server Due to some communication timing prob etc it fails phone gets ON and u will recieve such error as above... here i personally tested today ...got same issue for first time...secondly gets OK http://forum.gsmhosting.com/vbb/show...5&postcount=42 Last edited by Amir-SkillZ; 03-04-2010 at 06:18.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
vodafone sagem 231 unlock error[ANSWERED]	anam120	Basic Micro-Box Software Support (SAMSUNG, HUAWEI, etc...)	11	01-02-2011 13:50
S5230 Unlocking ERROR	equinoks	Easy-Unlocker	5	10-01-2010 21:05
samsung s5230 again error [ANSWERED]	lusomaco	PolarBox 3	10	03-22-2010 18:05
Error lg tu720 unlock error[ANSWERED]	baooshe2	Basic Micro-Box Software Support (SAMSUNG, HUAWEI, etc...)	3	03-02-2010 23:59
s5230 unlock error	cejer	UST Pro II	2	08-21-2009 18:44

03-03-2010, 01:30	#2 (permalink)
The_Gorr No Life Poster Join Date: May 2005 Location: Tunisia Age: 46 Posts: 14,198 Member: 145648 Status: Offline Sonork: 100.100487 The_Gorr Thanks Meter: 23,034	check if phone code is activated, if yes, desable it also try to reinstall drivers, it's possible they cause this error br <= The_Gorr =>

03-03-2010, 06:22	#3 (permalink)
Amir-SkillZ No Life Poster Join Date: Nov 2004 Location: Capetown Posts: 6,709 Member: 91045 Status: Offline Thanks Meter: 8,696	Hello, Reading Simlock Codes Should install broadcom2 drivers When BootMode Sequence Try to be Engaged if it fails ...Such error will come Retry Should Work Fine.. I saw encounter this error but was Ok in second TRY

03-03-2010, 10:36	#4 (permalink)
zapped No Life Poster Join Date: Feb 2003 Location: here Posts: 958 Member: 20953 Status: Offline Thanks Meter: 94	thanks for the answers... will try again next time i get this model! I tried a few times and I made sure the drivers were downloaded from nanobox support and installed but I was always getting that error... maybe resetting the phone was going to fix this but the customer did not want to lose the info on the phone so I had to use another tool to unlock it.