xperia x10 unlock error why?

[khoykhoy20]

RUNNING v 1.1203/01.14/UNI
CARD SERIAL 00080120
USBFLASH DRIVER VERSION 02.02.00.05
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:110000000000

credits consumption for full signature unlock:
S1 v1 xx credits ( OFFLINE )
S1 v2 xx credits ( OFFLINE )
S1 OPEN 05 credits ( OFFLINE FOR AID 004 PHONES)
A1 phones 05 credits
A2 phones 05 credits
S1 v2 alternative bypass unlock 02 credits
S1 v2 alternative bypass repair 05 credits
W100,W150 codes 05 credits

current setool2 version: 1.1203
SERVER CREDITS LEFT/USED: 10/20
CARD COUNTERS: FLASH 933, UNLOCK 276
Elapsed: 4 secs.
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:110000000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...

RUNNING S1_EROM VER "R8A031"

EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001

FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"

PHONE IMEI : 35949603871762
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1238-3759_R2C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB511TMDL7
Elapsed: 9 secs.
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:110100000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...

RUNNING S1_EROM VER "R8A031"

EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001

FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"

PHONE IMEI : 35949603871762
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1238-3759_R2C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB511TMDL7
Elapsed: 5 secs.
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:110100000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...

RUNNING S1_EROM VER "R8A031"

EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001

FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"

PHONE IMEI : 35949603871762
Unlock FAILED
Elapsed: 7 secs.

[xxxman]

here is your answer genius user .

MAKE SURE YOU HAVE ANDROID 2.1 FIRMWARE ..

[khoykhoy20]

firmware is 2.3.3

help me for error

setool not support?

[ARS.Rehman]

install 2.1 and do unlock again !

[khoykhoy20]

RUNNING v 1.1203/01.14/UNI
CARD SERIAL 00080120
USBFLASH DRIVER VERSION 02.02.00.05
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:111000000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...

RUNNING S1_EROM VER "R8A031"

EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001

FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"

PHONE IMEI : 35949603871762
Unlock FAILED
Elapsed: 6 secs.
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:111000000000

credits consumption for full signature unlock:
S1 v1 xx credits ( OFFLINE )
S1 v2 xx credits ( OFFLINE )
S1 OPEN 05 credits ( OFFLINE FOR AID 004 PHONES)
A1 phones 05 credits
A2 phones 05 credits
S1 v2 alternative bypass unlock 02 credits
S1 v2 alternative bypass repair 05 credits
W100,W150 codes 05 credits

current setool2 version: 1.1203
SERVER CREDITS LEFT/USED: 10/20
CARD COUNTERS: FLASH 935, UNLOCK 278
Elapsed: 4 secs.
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:111000000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...

RUNNING S1_EROM VER "R8A031"

EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001

FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"

PHONE IMEI : 35949603871762
Unlock FAILED
Elapsed: 7 secs.

[khoykhoy20]

plzzzzzzzzzzzz now 2.1

[ct3im]

Are you using correct ADB drivers from setools software? uninstall and reinstall.

[DOUHAL]

I tink your configuration Setting not Correct

------------------ FAQ HOW TO WORCK WITH SEMC PDA PHONES -------------

q:
which s1 android based phones i can unlock using alternative security bypass ?

a:
you can use that method for
x10i,x10i,s0-o1b, e10,e15,e16,u20 phones.
lt15,mt15,r800 and other msm8255-based phones require very simple testpoint to perform alternative security bypass.
x10i,x10i,s0-o1b, e10,e15,e16,u20 phones can also use testpoint method (complex, but powerful ) for unlock/repair

q:
how to unlock s1 android based phones, based on msm7227,qsd8250 using alternative security bypass without testpoint ?

a:
Here is procedure.

1.
make sure you have firmware with android 2.x, NOT 1.6.
firmware 2.3 is NOT supported, downgrade to 2.1.
flash required firmware, if needed.



2.
power on phone without sim card, go to menu->settings->applications->development, enable "usb debugging"
connect phone to PC, install drivers from setool2 distr ( drivers\ADB_Drivers)

hint:
i suggest to import DisableADBNumbering.reg (DisableADBNumbering.zip) , however that is not required.

3.
select proper phone model.
select USB as interface
on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset
press unlock

when prompted, detach phone, turn it on fully, connect it again.
( or you can leave phone on cable, then power it on manually )

when program tells "warming up...", manually power on phone fully, cause it will automatically enter charging mode.

after you see "GETTING ROOT ACCESS ..." DO NOT TOUCH PHONE until procedure complete.

DO NOT DETACH PHONE FROM CABLE AFTER PROCEDURE STARTED, YOU CAN KILL YOUR PHONE.
DO NOT REMOVE BATTERY FROM PHONE AFTER PROCEDURE STARTED, YOU CAN KILL YOUR PHONE.
SUCH KILLED PHONES CAN BE REPAIRED WITH RESURRECTION CABLES.


possible problems:

you getting "err: 00000005","err: 00000002" during process.

solution:
disable antivirus, especially if you using "koshmarsky antivirus", i recommend Doctor Web
do NOT run setool2 from restricted accounts.
do NOT run setool2 from read-only media.

problem:
it can happen ( very unlikely, though ) that ADB server will not recognize phone after reboot

solution:
IF phone not detecting automatically and on status bar you can see "waiting for phone...", again - only in that case - disconnect phone from usb and connect it again, procedure should continue.

if not, well, repeat from start.


q:
how to unlock s1 android based phones, based on msm7227,qsd8250, using alternative security bypass using testpoint?

a:
Here is procedure.

FIRMWARE VERSION DOES NOT MATTER, WHEN USING TESTPOINT METHOD

1.
prepare for testpoint operation.
check testpoints location for your phone model in dist\docs\s1_qualcomm_uart_cables or use GPG cable set
open testpoints for access
if you do not have GPG cable set, get some needle with wire, connect it to phone gnd ( battery minus ) or to usb cable shield, etc.

2.
select proper phone model.
select COM as interface.
on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset, use testpoint (gnd type)
fill login/password and check if account valid.

press unlock

when prompted, execute steps in EXACT order:

1 remove cable from phone,
2 remove battery from phone,
3 attach testpoint ( turn on switch on cable set )
4 insert cable to phone, HOLDING TESTPOINT ( cable set switch in "on" position )
5 press "ready"
6 when prompted detach testpoint
7 press "ready"
8 install drivers from dist\drivers\USBFlash_driver\ ( if asked )


phone will be unlocked.

q:
how to unlock s1 android based phones, based on qsd8x55, using alternative security bypass using testpoint?

a:
Here is procedure.

1.
prepare for testpoint operation.
check testpoint location for your phone model in dist\docs\
open testpoint for access
get some needle with wire, connect it to phone gnd ( battery minus ) or to usb cable shield, etc.

2.
select proper phone model.
select USB as interface.
on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset
fill login/password and check if account valid.

press unlock

when prompted, execute steps in EXACT order:

remove cable from phone,
remove battery from phone,
attach testpoint
press "ready"
insert cable to phone, HOLDING TESTPOINT
install drivers from dist\drivers\USBFlash_driver\
make sure that driver for qhusb_dload ( device, which will appear after successful testpoint ) is installed from dist\drivers\usbflash_drivers and named "ZEUS Flash Device".
Install driver manually, if testpoint driver named otherwise.
when prompted detach testpoint
press "ready"

REGARDS!