Develop Bugs

[Q] Problems with SEUS

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 t connect the watch to a computer

hi folks,
first time it happend to me with an adroid device, so i guess i ve missed something
i can t connect the watch to my computer on iwich i have no prob with all my other android device ans sony z2 & z3
in the device manage i keep having a yellow triangle warning, i ve re installed sony companion, changed nothing, and if i activate adb debut, it s not seing by the pc
i ve also tried different pc, and cables, so waving the white flag and asking for help!!!!!
thxx for your time
best regards

nocomp said:
hi folks,
first time it happend to me with an adroid device, so i guess i ve missed something
i can t connect the watch to my computer on iwich i have no prob with all my other android device ans sony z2 & z3
in the device manage i keep having a yellow triangle warning, i ve re installed sony companion, changed nothing, and if i activate adb debut, it s not seing by the pc
i ve also tried different pc, and cables, so waving the white flag and asking for help!!!!!
thxx for your time
best regards
Click to expand...
Click to collapse
Yep, I have the same issue. Its not being detected at all. I've troubleshooted this on linux. No udev events are emitted when the device is plugged in and on. A mass storage device is detected when I switch the device off though. I'm on 5.0.2.

Hi, I had this very problem and found that that you have to switch the watch off then attach the mini us to the watch only, then hold the power button of the watch (don't let go) and eventually the watch screen will come on with an attach usb picture, now plug the main usb end into the PC and it should be recognised by Sony PC companion. I forgot to mention that the PC companion program should be started before plugging it in. Good luck Grant.

hi grant, thxx a lot for your message
i tried that before and no luck :/

Help, Bricked xperia s is not detecting by PC

Hi guys, I bricked my xperia s by flashing wrong kernel few months ago. I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=1849170
But my phone is not getting detected by PC. I am using Windows 7. I had install fasboot, flashmode and xperia s drivers from flashtool folder but no luck connecting the phone to pc.
The red LED appears while charging. after somtime it goes off and sony logo appears. but still pc doesnt recognise my phone.
do i need to install adb drivers as well??
and if anyone can send a link to right drivers for xperia s, it will be helpfull. thanks

How to unbrick Xperia S lt26i [already tried what other links in the forum say]

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)

Dead XA1 Ultra (G3226) - Brazil

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