when i get to the command window part of the sony ericsson unlocking bootloader site and type in the phrase it just says wsaiting for device
Install correct drivers easiest way u found is download gordan gate drivers and run it
Swyped from my Xperia Play via Tapatalk
I Read your thread of "Namaste Guide to Arc Rooting" etc and I Started following the procedure of Rooting my LT15i without unlocking the bootloader.
But the moment i connected my Arc in flash mode, It started installing the drivers of "S1 Boot Download" but then it didnt succesfully install them. It also failed to download the drivers via Windows Update.
Could you please provide me the drivers or the Link to them? Or a workaround (if any)
Thank You!
I'm Sorry For Double Posting but 32 Views and not a single Reply!
Isn't there any solution to this?
Same here mate
install pc companion..then conect your device..pc companion auto install all driver on your pc..
If your using Win 7 it seems to be a bit stupid concerning the MTP driver i had to reinstall PC companion several times befor it would install the MTP driver properly.
on My XP machine it seems to do it on its own when i connect the phone pretty fast. Win 7 alot slower and half the time it fails to install
There are all drivers what you need
This package includes Fastboot, Flashmode and ADB Drivers for all XPERIA devices
It's from Flashtool
If you have win7 64 bits or win vista 64 bits and you follow the official SE guide (so you have donwloaded Android SDK + modified inf file from SE site), you have to use the inf file I've posted here instead of SE one.
If you are following lollylost100 guide, you'll find needed packages here
anyone can give me arc usb driver for win7 x64..most of the link doesnt work..pls help..need the driver to unlock bootloader..thanks
download flashtool in it there are quite a few drivers
founded the driver..thanks
I have an Xperia Play that I got off eBay (I know, I know, personal project - I do have another working one). Reported issue was that it wouldn't boot, but after messing with it, I found that it would 1/10 times if I pull the battery for a few seconds before trying. I was even able to flash a stock firmware again. However, the majority of the time, it won't boot into OS, fastboot, OR flash mode.
Here's why: QHSUSB_DLOAD
From my research, this basically means the bootloader is corrupt or somehow otherwise malfunctioning. When connected to a computer, it resolves to "Qualcomm HS-USB QDLoader 9008 (COM3)" or whatever COM port it lands on, and it does this in fastboot and flash mode. Except for those rare instances where it acts like a normal phone.
I've spent most of the past couple of days digging around in forums, Google, and the Wayback Machine, trying to find a solution. Unfortunately, beyond trying a different computer and reinstalling drivers (both of which I have), the only solutions given are to use Omnius or s1tool/s2tool. They both seem to require payment for unlocking phones, which I don't need, but as far as I can tell should work fine for repairing the s1 boot, which I think is what I need to do. I've been following different guides that all say to remove the battery, connect the test points, and plug in the USB, but I can't get Omnius or the s-tools to work.
Is there any hope for this device? Can anyone who has gone through this before offer some suggestions? Alternatively, is there maybe a way I can just deal with the problem while still being able to use the phone without needing to pull the battery a bunch of times? The Xperia Play is still a great portable gaming system, so I'm hoping we'll be able to figure something out, as I know many other people are starting to acquire these from eBay and try to get them working, and may also run into this issue.
#metoo
I'm also having the same issue.
found this thread [Q] [Hardbricked]Xperia Play lifeless
CamillaHinchcliffe said:
Here's my problem, I wanted to flash a new ROM into my R800a but when I plugged it into my computer it detected the phone as a device called "Qualcomm HS-USB QDloader 9008" and now it does not turn on anymore .
Searching around Google I found that it doesn't turn on because the "SEMCboot" or "Trim Area" is damaged, but I've no idea how to fix that on my own.
Click to expand...
Click to collapse
And this one [How-to] Repair Damaged Bootloader + Trim Area [Red Led][Unknown Device]
Alejandrissimo said:
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
THIS PROCESS IS FREE
anyway if you want me to buy a Dr. Peper just
Click to expand...
Click to collapse
And finally, I found this thread in the Xperia SP forum [Guide]Zeus Flash Or qhsusb_dload Solved!!!!!
Almas008 said:
Thanks to mr @the_laser!!!!
Now those who have their phones in qhsusb or zeus flash device can revive their xperia sp to life back....!!!!!
Download attachement and run s1tool and click flash...
select attached sin file set and folow instructions....
Click to expand...
Click to collapse
And also this thread S1 boot download driver.
Some of these fixes and threads are old/outdated, so I dont know what will work Ive already started to use some of the tips last night. I have found out that my phone does get detected as "Qualcomm HS-USB QDloader 9008" but that's as far as Ive gotten. Please read the threads and tell me what you find out, or try that works
I've already been through those threads, and several more like them. The immediate answer is to contact Alejandrissimo, but they've been MIA for years now. I shot them an email the other day, but I don't expect to hear back.
Things I've tried:
Xperia Companion (PC Companion) - doesn't recognize device
SEUS (Sony Ericsson Updater Service) - discontinued, can't connect to servers
S1tool testpoint method - doesn't recognize that a device is connected
Omnius - doesn't recognize that a device is connected
Flashing stock the one time I could get it to boot into flashmode
It looks like this method stands a good chance of working, but it requires an "APPSW .sin_file_set" file, which I haven't been able to acquire for the Xperia Play. From Googling around, it seems that's the blob file that gets downloaded when you get an OTA update or when using XperiFirm (which no longer gives Xperia Play as an option), but all I can find are recompiled *.ftf files. Those files do contain a bunch of *.sin files, but comparing the contents to what you find in a *.sin_file_set file, is too different; the latter has a different folder structure and a bunch of XML files that provide information to the phone. I'm not sure exactly just how necessary that structure is and I couldn't find a guide on recreating a *.sin_file_set file, just how to decrypt one to convert to FTF.
If you click that link to the tutorial for that process, you can download a *.sin_file_set for a different model of phone to see what it should look like.
Of course now I just stumbled on a guide to convert FTF back... I will have to try that.
EDIT: Okay, I grabbed the s1tool from that link and disabled my antivirus before using it. Did the testpoint procedure as described, and got this error:
llbug: [] open error: "The system cannot find the path specified"
Click to expand...
Click to collapse
That might be because the bootloader is still locked. If I can get it to let me into fastboot, I may be able to change that.
EDIT 2: Got it into fastboot, verified the bootloader is locked. Ran the unlock command, but it failed. Tried doing it through s1boot and got the same error as before. Guessing there isn't anything else I can do at this point.
EDIT 3: Forgot to mention the process I tried before was with an FTF, since I discovered S1tool will use those after all (I used the version from that website I linked to). I still need to recompile a sin_file_set version and try that. In the meantime, I did actually receive a response back from Alejandrissimo, so we'll see where that goes and I'll report back.
Hey guys,
i've got a problem with my Z5 Premium and I hope you can help me.
I just got it repaired (flex cable broke) and I wanted to give it a try unlocking the bootloader and later rooting it. Unfortunately it fails already at the first point.
My model is a regular Z5 Premium E6853. I am currently on version 32.4.A.1.5 / R1E.
Everytime I try to unlock my bootloader, it says "FAILED (remote: Command did not succeed)".
I'm starting to run out of ideas and I really want that bootloader unlocked.
Things I checked before:
I octuple-checked the IMEI and the unlock code. I also quadruple-checked my IMEI (phone box, settings, phone pad and service menu)
I did reinstall all drivers and I did install the fastboot drivers using the unsigned drivers (tried with the google drivers too)
I did try to use different USB cables (unfortunately the original one is broken, but I tried it with another Sony cable and some brand-new aftermarket cables)
I did enable OEM unlocking, ADB debugging and untrusted sources in the settings
I did check my bootloader version: it's 0.5
I did check that my bootloader is unlockable. The service menu says "Bootloader unlock allowed: Yes"
Are there any other things I need to do? Like having a valid sim card in the phone (not that I havent tried)?
I hope you guys can help me.
Best regards
Lyrex