My phone recently became dead out of nowhere, I was using it like everyday, social media apps, outlook, whatever. The screen simply became frozen and I hard reset the device using the volume and power button trick. It restarted like nothing happened and after 15 or 20 minutes it became frozen again, only that after this, hard reset didn't work anymore and it never turned on again. I sent it to sony repair and they denied my warranty saying that my phone had some scratches on the body. My phone is barely a paper wheight since then. I decided to try recovering and all the stuff, I was pretty acquainted with old sony phones and did a lot of flashing back in the days, but I can find no much discussion about the XA1 Ultra. I'm struggling with a lot of errors in the flashing process, I believe that the device is not being recognized by my computer so if anyone can give me some advices on how to procedure here.
I've already faced this issues below:
1- No loader found. After some searches, I already found that some new sony phones don't need loader in the process of flashing, but yet flashtool insists in asking for it.
2- Flashing process gets stuck in "Reading device information". I'm aware that flashtool doesn't officially recognizes the XA1 Ultra (G3226), but I found some people commenting that they were able to flash this model after some patching, which I've already did unsucessfully.
3- Device disconnect from flashmode about 30s after process begin, usually in conjunction with the "Reading device information" issue. I don't know nothing about this yet.
I've tried run this process in 3 different pcs (win 7 and win 10) and I get the same issues in all of them. Don't know how to procede anymore and I'm really annoyed with a dead phone right now. If someone could help with any of these topics I'll be very grateful.
1: what's your flashtool version
2: I had to add my g3223 to the flash tool list to flash things
3: reading device information usually means something happened. I just kept closing flash and re opening till it worked. Also opening with admin rights is a must
I'm using flashtool latest version. I'm also always running it with admin permissions. I'm now stuck in this situation, the flashtool gives an error after a while trying to read device information. When my phone LED turns from green to red, i also hear a sound notification from windows saying that some device has been disconnected. I think that from this point I can't make progress with flashing because my phone keeps disconnecting from flashmode.
Try a different cord, try a different port. Don't use USB 3.0 ports. Reinstall the drivers under you root flashtool folder. Something is prevent from flashtool reading your driver information
lonewolfbtown said:
Try a different cord, try a different port. Don't use USB 3.0 ports. Reinstall the drivers under you root flashtool folder. Something is prevent from flashtool reading your driver information
Click to expand...
Click to collapse
Otherwise,I think it’s your hardware fault regarding ram/storage
Related
Hi - more questions, but this time its a problem I'm having. Before flashing the latest O2 UK firmware I want to decrypt my current Orange France 2.3.2 firmware in case I need to go back to it. However, I'm assuming that I need to connect with SEUS once (and possibly update whatever they have) so I can then find the current firmware files in the SEUS folders on my PC.
Anyway, the long and short of it is that when I am told to hold the back button while connecting the phone, NOTHING HAPPENS. I've tried loads of times, tried reinstalling SEUS, nothing. Some drivers started to install, and all seems OK there - no yellow triangles in device manager. Also installed PC Companion (automatically offered when I connected the phone with it turned on). It installed drivers then too. All fine. I tried using a different USB cable too - no luck.
Any clues ?? Searched Sony Ericsson site and it is bare of useful info. Did a search here too but no luck either.
Thanks in advance.
and you followed the instruction as they say:
1. switch off the phone
2. wait for 30 seconds or so (pref. remove the battery and insert it)
3. hold the back button
4. insert usb..
it should detect the phone no matter what. i hope there is some juice in battery...
I've heard that SEUS and PCC now are able to detect rooted phones and don't let you reinstall stock software. It needs the stock build.prop
Thanks for the replies. I have been pulling my hair out on this. I realised that it is to do with my SECM USB Flash drivers being faulty or something.
I tried to use PC Companion and it got to the same bit where SEUS crashes - right when it wants to get in to flash mode on the phone. It hangs the computer up.
I have googled like crazy and have seen reports of others PCs hanging at the same place. BUT, I can't find a way to repair or reinstall the USB Flash drivers - I've reinstalled SEUS and PC Companion plenty of times, with my anti-virus off. And tried to get in to flash mode with the anti virus off.
Problem I think I had is that a lightning storm stopped my first installation of PC Companion - I think it may have screwed something.
Any ideas how to fix the usb flash drivers ???
Have you tried de-installing SEUS and PCC, then in device manager search for and remove the USB Drivers for SEMC.. then reboot.. then re-install SEUS..
??
im_iceman said:
Have you tried de-installing SEUS and PCC, then in device manager search for and remove the USB Drivers for SEMC.. then reboot.. then re-install SEUS..
??
Click to expand...
Click to collapse
Thanks - tried that but no luck unfortunately. Couldn't even see anything in Device Manager to do with SEMC, SEUS or Sony Ericsson - was looking under USB Controllers. When I did a full search I did find plenty of traces of the drivers GGSEMC (Gordons Gate Flash USB drivers) in both system32 folder and in the Sony Ericsson folder left over after uninstalling SEUS. Didn't want to just delete the ones in system folders.
you could try doing the "update driver" operation - my driver was called Sony Ericsson seechri (or something like that!).... see if you can repair..
Perhaps you could try on ur friends pc. Just to confirm that seus is the problem.
SOLVED (sort of)
Thanks for the advice.
OK - I tried on another machine (why didn't I do that 6 hours earlier ). Works fine on Win7 64 bit. Maybe the drivers didn't get installed properly on Win XP ?? Going to have a go rolling back to an earlier restore point on the XP machine to see if I can get it working.
Anyway, SOLVED. Thanks
Can I get some help guys? My phone got bricked after I stupidly installed Chainfire3D, the phone is in a boot loop state for now.
My phone's firmware version is 6.1.A.2.55 and I have an unlocked bootloader, my CWM was gone after flashing 6.1.A.2.55 before but my phone is unlocked and it's USB Debugging is turned ON before I bricked it.
After 2 days of researching, here's what I've got (and tried):
My phone's vibrator is not functioning so I don't know how many times my phone vibrate when I hold Power + Volume Up.
My phone's USB port is faulty, it charges but it can't be recognized on a computer then I found a guide here on the forum about cleaning the USB port using a toothpick, and I think it's working fine now.
I am using Windows 8.1 Pro 64-bit and I found out that there are issues regarding the ADB drivers, I tried some solutions I found online but my phone is still not detected.
I installed a bootable Windows 7 SP1 64-bit on a external HDD and tried to use Flashtool there. I installed the Fastboot, Flash Mode, Xperia Acro S drivers from C:\Flashtool\drivers and still my phone is not detected.
I tried to install Flashtool again from my girlfriend's computer, Windows 7 64-bit, my phone is detected in Flash Mode but can't stay there for long, it will exit Flash Mode then goes to charging, unlike in Fastboot wherein it stays there.
Tried installing Flashtool again from my mom's computer and borrowed her USB cable, it stays in Flash Mode then I tried to flash LT26w_1265-3909_6.1.A.2.55_GENERIC-user_CUST_1266-3278_R4G from there, but it stops with an error Error processing loader.sin, again I did some research about it and then I tried flashing it again, but this time Flashtool didn't gave me an error but it stops at Checking header right after Processing loader.sin
I also tried to flash only the kernel.sin on Fastboot mode but the Flashtool crashed.
Again, from my mom's computer, I installed Sony PC Companion, it was detected as Xperia Acro HD but my mom's computer don't have internet so I wasn't able to try to repair from there.
I also have another question, could it be that my USB port is not functioning? Are there any other methods to make my USB function again aside from bringing it to a service center?
0x013666f said:
Can I get some help guys? My phone got bricked after I stupidly installed Chainfire3D, the phone is in a boot loop state for now.
My phone's firmware version is 6.1.A.2.55 and I have an unlocked bootloader, my CWM was gone after flashing 6.1.A.2.55 before but my phone is unlocked and it's USB Debugging is turned ON before I bricked it.
After 2 days of researching, here's what I've got (and tried):
My phone's vibrator is not functioning so I don't know how many times my phone vibrate when I hold Power + Volume Up.
My phone's USB port is faulty, it charges but it can't be recognized on a computer then I found a guide here on the forum about cleaning the USB port using a toothpick, and I think it's working fine now.
I am using Windows 8.1 Pro 64-bit and I found out that there are issues regarding the ADB drivers, I tried some solutions I found online but my phone is still not detected.
I installed a bootable Windows 7 SP1 64-bit on a external HDD and tried to use Flashtool there. I installed the Fastboot, Flash Mode, Xperia Acro S drivers from C:\Flashtool\drivers and still my phone is not detected.
I tried to install Flashtool again from my girlfriend's computer, Windows 7 64-bit, my phone is detected in Flash Mode but can't stay there for long, it will exit Flash Mode then goes to charging, unlike in Fastboot wherein it stays there.
Tried installing Flashtool again from my mom's computer and borrowed her USB cable, it stays in Flash Mode then I tried to flash LT26w_1265-3909_6.1.A.2.55_GENERIC-user_CUST_1266-3278_R4G from there, but it stops with an error Error processing loader.sin, again I did some research about it and then I tried flashing it again, but this time Flashtool didn't gave me an error but it stops at Checking header right after Processing loader.sin
I also tried to flash only the kernel.sin on Fastboot mode but the Flashtool crashed.
Again, from my mom's computer, I installed Sony PC Companion, it was detected as Xperia Acro HD but my mom's computer don't have internet so I wasn't able to try to repair from there.
I also have another question, could it be that my USB port is not functioning? Are there any other methods to make my USB function again aside from bringing it to a service center?
Click to expand...
Click to collapse
Instead of trying to install rom, try installing cwm, then if cwm is installed and working, you can use that to flash zip through sideload from pc.
Mufrad said:
Instead of trying to install rom, try installing cwm, then if cwm is installed and working, you can use that to flash zip through sideload from pc.
Click to expand...
Click to collapse
Okay sir I will try your suggestion, thanks. Can I install CWM using an SD card?
By the way, I brought my phone at the Sony Service Center here, they told me that they can not repair my phone since their computer couldn't detect it and the phone's problem is the motherboard. My phone has dents on it, so I'm pretty sure that they used it as a reason. And also, they told me that my phone was rooted. I was so frustrated because I know that my phone's problem is the USB since the phone charges and goes into bootloop after installing Chainfire3D.
I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance.
#edit
i also took my phone apart to disconnect the morthermboard and reset the chips without letting the battery die, didnt work. Then i let the battery die but still no luck. I also tried from linux after following tutorial to install adb corectly but it wont see my phone.(it can see it in usb devices)
Hello friends!
New registered user here but have already read tons of threads regarding G3 troubleshooting. Anyway, have decided to post this problem and if a similar situation has already been posted (and solved), please provide link.
For some strange reason, my G3 have decided to stay in the LG logo (I understand that this is the so-called boot-loop). This happened when the phone suddenly restarted while watching a YT vid and the battery still at 30%++. The phone just keeps on restarting until such a time that it never got pass the LG logo.
Here are the things that I have already tried to no avail:
1. Enter Hard Reset page via hardware keys (Power + Vol Up buttons). Have chosen "Yes" to hard reset device but alas, it never got pass the LG logo.
2. Downloaded PC suite, KDZ flashtool, and LGUP. Installed all three software. Connected G3 to PC and entered download mode (Vol Down while inserting USB cable). Unfortunately, unable to fully use either of the three software since the PC cannot detect G3.
Number 2 is quite strange since I have downloaded and installed all G3 drivers. This I know since a friend of mine who owns a working G3 unit was detected by the computer and can sync with the PC suite.
For some strange reason, everytime I connect my broken G3 to the computer, it is not detected by the PC and was not even listed in the device manager.
Any help and advise would be highly appreciated
I already downloaded all necessary tools (KDZ, LGUP, and flashtool) to flash the ROM but I need the PC to see the G3 unit to be able to do so.
By the way, before the bootloop scenario: the debugging (or is it developer?) options are disabled and I'm not sure if the bootloader is locked or unlocked.
I hope all this info is of any use.
Thanks a lot in advance
Have you tried simpler solutions first? Like, trying another USB ? Or another USB port from your pc? This maybe hardware related rather than software. You should try that before anything else. (Maybe you did?)
neyvermore said:
Have you tried simpler solutions first? Like, trying another USB ? Or another USB port from your pc? This maybe hardware related rather than software. You should try that before anything else. (Maybe you did?)
Click to expand...
Click to collapse
Thanks for the reply. Yup, have done those. Tried a different cable, different USB port, and borrowed a working G3 unit. The good G3 unit was detected by the PC but when I connect my broken G3 (same cable and same USB port), the PC does not detect it (not even listed in device manager).
Because of this hurdle, I couldn't flash with LGUP (it states no handset was connected). The KDZ flashtool basically says the same message.
By the way, my debugging options are disabled before this whole problem started. Could that be a reason why the PC won't detect the unit?
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.