Following the instructions on unlocking my Xperia Arc S:
instructions as provided by SonyEricsson, I succeeded in unlocking my Xperia Arc S:
First check the version:
./fastboot-linux -i 0x0fce getvar version
finished. total time: 0.001s
This is the correct version as the SonyEricsson website said.
And then following the instructions in the URL above, I got my unlock key, which is specific to each handset.
Next download the “fastboot-linux”, or whatever it is renamed as, just search here:
Continue to follow the instruction from SE website, eg, specifying in the fastboot-linux commandline (XXXXXXXX below is the unlock key):
./fastboot-linux -i 0x0fce oem unlock XXXXXXXX
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
(bootloader) Erasing block 0x00001900
(bootloader) Erasing block 0x00001a00
(bootloader) Erasing block 0x00001b00
(bootloader) Erasing block 0x00001c00
(bootloader) Erasing block 0x00001d00
(bootloader) Erasing block 0x00001e00
(bootloader) Erasing block 0x00001f00
OKAY [ 4.629s]
finished. total time: 4.629s
CAVEAT: Not told to us in the website, is that everything on your phone is wipe out. So my contact list, all my installed and downloaded Android program, all disappeared. If it is a purchased item from Android Market, it is always possible to re-download from “My Apps” (Android Market -> Settings), which is supposedly to list all your previously purchased items from Android Market. But if it is free, then it is not listed, and you have to search and download it again.
PS: Whether unlocking the SIM is the same as unlocking the bootloader, I am not sure, more info here:
But essentially unlocking bootloader allow you to flash a new kernel image on it, which subsequently will boot up Android OS, and also implied customizing Android OS to whatever you want to do.
But unlocking the SIM is to free up the link that tied the baseband processor to communicate with a fixed telecom operator (which does not apply to phones from my country – Singapore).
CAVEAT: Not sure why, but I just discovered that the nand partitioning seemed to be missing the “recovery” and “boot” partition:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00020000 "system"
mtd1: 00600000 00020000 "appslog"
mtd2: 06580000 00020000 "cache"
mtd3: 1a400000 00020000 "userdata"
# cat /proc/partitions
major minor #blocks name
7 0 35375 loop0
31 0 409600 mtdblock0
31 1 6144 mtdblock1
31 2 103936 mtdblock2
31 3 430080 mtdblock3
179 0 7772160 mmcblk0
179 1 7768064 mmcblk0p1
254 0 35374 dm-0
Well if you compare this image with other Android NAND partitioning like this:
This is definitely quite different, and so all the different instructions on how to reflash new copy of the boot.img to the NAND really puzzle me: