Mine will boot to s1boot fast boot for a couple seconds and then becomes a SEMC HSUSB device. i then don't have the option to install the driver in device manager.
Mine will boot to s1boot fast boot for a couple seconds and then becomes a SEMC HSUSB device. i then don't have the option to install the driver in device manager.
@Doomlord: Did you maybe have any other drivers/SDK previously installed that would work for the Xperia S fastboot?
the correct drivers are already provided...
search online on how to manually install drivers in windows...
Yup, same steps I followed, that's how I unlocked my Arc too. Just that the Xperia S won't stay in fastboot.
I am too having the same issue with LT26i tried pressing the volume up and plugging the usb cable, the PC identifies s1boot device but then the phone goes into the normal state (orange light) and it gets installed as usb storage device.
I have tried different drivers, none work including Google driver, Google driver with modified USB configuration, SE2Tool and PdaNet drivers.
I would appreciate any guidance...
One step further, I installed the latest Omnius SE Tool. Set my windows 7 64bit device installation settings to NEVER INSTALL DRIVER FROM WINDOWS UPDATE. The device was identified as Android ADB, I updated the driver by selecting it manually from a bundle I downloaded from the internet some time ago "fastboot_with_Android_USB_file" which includes fastboot and "usb_driver".
what os are people using?
I have tried on two separate Win7 x64 machines.
Shouldn't matter but just wondering.
I'm on Win7 x64.
I think I'll fire up an XP VM and try on there.
EDIT: SUCCESS!!! Once I tried it on an XP VM that I have, it worked like a charm. All 3 PCs where the instructions failed were Win7 x64 PCs.
One step further, I installed the latest Omnius SE Tool. Set my windows 7 64bit device installation settings to NEVER INSTALL DRIVER FROM WINDOWS UPDATE. The device was identified as Android ADB, I updated the driver by selecting it manually from a bundle I downloaded from the internet some time ago "fastboot_with_Android_USB_file" which includes fastboot and "usb_driver".
Running Fastboot.exe devices gives me the id, however, running getvar gives me an error as below. Trying to unlock the bootloader gives me as well an error, provided below.
D:\Android\SE Arc\fastboot_with_Android_USB_file\fastboot>fastboot -i 0x0fce get
var version
getvar:version FAILED (command write failed (Unknown error))
finished. total time: 0.613s
D:\Android\SE Arc\fastboot_with_Android_USB_file\fastboot>fastboot.exe -i 0x0fce
oem unlock 0x.....
...
FAILED (command write failed (Unknown error))
finished. total time: 0.732s
Tried flashing the system image, failed:
D:\Android\SE Arc\fastboot_with_Android_USB_file\fastboot>fastboot flash system
system_xps_prerooted_63fw.img
sending 'system' (420244 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
Nice to hear that Was it a straight forward process??
Also, have you tried to root it with Zergrush?
First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
yea I guess it's pointless locking back the BOOTLOADER but I think with the unofficial way, they know or they have registered the serial key or IMEI which you won't be able to update it to ICS via SEUS or PcCompaninon. Either way like you said, we can use the FTF files to update it to ICS. and I saw when the run ICS on Arc S and Play, I saw that they had to unlock the bootloader to install alpha ICS and it was mentioned there that you might face lotta troubles when you update it to the official ICS, so I'm gonna wait till it gets official ICS cause it'll be out very soon like end of the March.