[TUTORIAL] Sony Ericsson Xperia Arc bootloader unlocking


Senior Member
Jun 19, 2009
Quick tutorial for unlocking new Xperia devices. Although there is one on the SE developer website, this thread can be used for users to discuss their problems during unlocking etc.

Warning! This procedure will wipe the /data partition of your phone.

1. Download:
-fastboot package: http://www.multiupload.com/BMJ24IL6XY
-32/64bit drivers: http://www.multiupload.com/0XZV1LXRVA
2. Go to: http://unlockbootloader.sonyericsson.com/instructions
3. At the bottom click 'Continue' and enter your IMEI (type *#06# to find out), name and email address
4. You should now receive your unique unlock key
5. Extract fastboot.rar and open fastboot folder
6. Hold SHIFT and right click on the background of the folder
7. Select 'Open command window here'
8. Connect your phone in fastboot mode (turn phone off, hold menu button and plug in USB Cable)
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
10. If a value is returned, it means the phone is correctly connected
11. Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key provided in step 4.
12. You're device should now be bootloader unlocked

If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
Last edited:


Senior Member
Jun 19, 2009
IMEIs are not registered for specific operators. Only part is the start which is used for SEUS detection. Branded devices will be able to receive their key, just won't be able to go into fastboot. I need someone to debrand their phone and check if fastboot is enabled after debranding.
  • Like
Reactions: Mooozer and Step666


Retired Forum Moderator
Jan 13, 2009
I can't quite bring myself believe that SE don't keep a record of which handsets are sold to whom and what network they're locked to.
Obviously, they're not cross-referencing against those records when issuing the unlocking keys but I'm sure they know.

Thank you for the drivers, I think they've done it...
Here's what it said on the command prompt:
C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce getvar version

version: 0.3
finished. total time: 0.001s

C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce oem unlock 0x[my key]
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
OKAY [  4.170s]
finished. total time: 4.170s

C:\Users\[username]\Desktop\SE Unlock\fastboot>
  • Like
Reactions: t_adams
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone