Author Topic: unlock s1 android based phones  (Read 1705 times)

sundar

  • Administrator
  • Hero Member
  • *****
  • Posts: 15188
  • Karma: +10/-0
    • View Profile
    • http://www.srimeenakshimobiles.com
unlock s1 android based phones
« on: December 24, 2011, 12:41:18 PM »
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, ONLY RIFF JTAG WILL HELP
DO NOT REMOVE BATTERY FROM PHONE AFTER PROCEDURE STARTED, YOU CAN KILL YOUR PHONE, ONLY RIFF JTAG WILL HELP


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.
Always TAG your threads

  • Download all the schematics here Direct download
  • Stay connected with SMMobiles on

Srimeenakshimobiles

unlock s1 android based phones
« on: December 24, 2011, 12:41:18 PM »