[Xperia Arc Q&A, Help & Troubleshooting] scholbert:
... still some bootloader unlock questions.

Hi,

i try to get some enhanced information about unlocking bootloader with the s1tool from here:

http://xdaforums.com/showthread.php?t=1551494

To be sure that i won't cause a brick i did a little research, if it is safe to use this method on my device.

Some details:

The label on my Xperia Pro says it is built in 12W11 and service menu tells me that 1241-3656 R9B031 S1 bootloader is installed.

After reading many forum entries about the date codes and EROM versions it is still very confusing.

Some say devices after 12W14 are definitely affected other say there could be 12W11 as well...

Some reported bricks with 1241-3656 R9B031 others told they made it even with this version.

So i started s1tool and used the identify function first.

Then pressed the back button and attached my device to the host (detecting as QHUSB_DLOAD).

Everything looks just fine:

17.12.2012 16:54:12 Welcome to S1 tool.
17.12.2012 16:54:12 That is small and crippled subset of SETOOL2 service tool.
17.12.2012 16:54:16
17.12.2012 16:54:16 TO CONNECT NEXT PHONES
17.12.2012 16:54:16 X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
17.12.2012 16:54:16 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
17.12.2012 16:54:16 PRESS AND HOLD "BACK" BUTTON...
17.12.2012 16:54:16
17.12.2012 16:54:16 ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
17.12.2012 16:54:16 PRESS AND HOLD "Volume Down" BUTTON...
17.12.2012 16:54:16
17.12.2012 16:54:16 PLEASE ATTACH TURNED OFF PHONE NOW
17.12.2012 16:54:16
17.12.2012 16:54:30
17.12.2012 16:54:30 RUNNING S1_EROM VER "R9B031"
17.12.2012 16:54:30 SOFTWARE AID: 0001
17.12.2012 16:54:30 LOADER AID: 0001
17.12.2012 16:54:32 FLASH ID: "0098/00B3"
17.12.2012 16:54:32 LOADER VERSION: "R4A069"
17.12.2012 16:54:32
17.12.2012 16:54:32 MODEL (from GDFS): MK16i
17.12.2012 16:54:32 SOFTWARE VERSION: 1243-7775_4.1.B.0.587
17.12.2012 16:54:32 CUSTOM VERSION: 1249-6015_R2I
17.12.2012 16:54:32 FILESYSTEM VERSION: WORLD-i_4.1.B.0.587
17.12.2012 16:54:32 SERIAL NO: xxxxxxxxxx
17.12.2012 16:54:32
17.12.2012 16:54:32 SEMC SIMLOCK CERTIFICATE
17.12.2012 16:54:32 Elapsed:16 secs.
17.12.2012 16:55:34 PROCEDURE STOPPED BY USER

Anyway i am still confused because some reported that they bricked their device... so tried to find some answers.

This time i read many threads all over the setool forum and found a statement from the_laser.

There was a guy who asked if it would be safe to unlock and if it would work.

His answer:

So i did it again, started the identify process within setool and connected my device with the testpoint attached to ground.

I did not press the back button this time

The device got detected as zeus device and I got no error while connected, but the phone got not detected this way.

Do i need to release the testpoint after the first detection is finished?

Normally the identify process does only work with the back key pressed... confused.

How could i make sure that my phone could be unlocked or if it will be bricked during this process because it is one of the "new security" phones?

I would really appreciate any comment on this.

Please help to get some light on this issue!

EDIT:

If you got no idea what i'm talking about, it would be helpful to get some general info.

Please Xperia Pro users who successfully unlocked with the s1tool:

- Type *#*#7378423#*#*

- Under Service info -> Software info -> S1 Boot Version; Post the version number, e.g. 1241-3656 R9B031

- Take out your battery and post your manufacturing date from the device sticker, e.g. 12W11

Best regards,

scholbert