Quote:
Originally Posted by TMAC1122  trying to unlock xperia X10i with setool but showing error, please help..
RUNNING v 1.1436/01.15/UNI
CARD SERIAL 00184482
USBFLASH DRIVER VERSION 03.02.00.00
SIGNED MODE (USING SERVER)
ALTERNATIVE SECURITY BYPASS ENABLED
CFG:110010000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...
\\.\EPIUSB1
\\?\USB#VID_0FCE&PID_ADDE#5&1c975dd7&0 &3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
RUNNING S1_EROM VER "R8A013"
EROM_AID : 0001
LOADER_AID : 0001
SW_AID : 0001
CUST_AID : 0001
SIM_LOCK_AID : 0001
[ llcomm: 00010000,00080000 ]
DEVICE ID: 9CA68DA9116B87A38D6BED62408D637AB441A527
FLASH ID: "002C/00B3"
LOADER VERSION: R4A024
PHONE IMEI : 359419031*****
Checking for signature ...
signature found, skipping calculation
REMOVE SIM CARD FROM PHONE
FULLY POWER ON PHONE
ENABLE "USB DEBUGGING" IN PHONE:
MENU,SETTINGS,APPLICATIONS,DEVELOPMENT
INSTALL ADB DRIVERS IF NEEDED
MAKE SURE PHONE HAVE ANDROID 2.x FIRMWARE
WARMING UP ...
GETTING ROOT ACCESS ...
Access violation at address 0055E647 in module 'Setool2g.exe'. Read of address 00000000
Unlock FAILED
Elapsed: 54 seconds |
Here is procedure.
1.
make sure you have firmware with android 2.x, NOT 1.6.
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.
-------------------------------
------------------------------