PC Companion and Win 8.1 - Sony Xperia T, TL, TX, V

I found it very frustrating to update my Xperia T to the recent 4.3 release. PC Companion will still backup your phone nicely. I could see that there was an update, but PCC would tell me that it needed to be used in a previous version of Windows like Win 7 (?). Now this is incredibly stupid, but as we all know, there is always another way. I reinstalled and also chose other USB ports; no go. So I searched for answers and saw references to Compatibility mode - no matter what mode I chose however it made no difference. References to a recent MS fix had no relevence - it was already installed and not making any difference here. So I installed Java and also installed SEUS. I was able to get that going but it only showed recent various Sony products but not my T - argh! So after a few hours of of frustration I was no further ahead. Then I saw somewhere a suggestion for adjusting Compatibility Mode for SEUS - bingo that was the ticket. So the short version: Using Win 8.1 PC Companion is not going to allow the Update function to work, but SEUS will work, after switching it's compatibility mode to Win 7. Hope this helps.

Related

[Q] unable to get kies working on w7 64, tried everything how can I flash firmware?

Hi all,
I am unable to get Kies to recognise my galaxy s (when in Kies mode) or windows for that matter. I've tried installing the samsung usb drivers etc using the latest version of kies, still doesn't work.
What options do I have now in terms of firmware flashing? (I'm not installing 32bit xp just to flash my phone)
Cheers
if you search the forums you will find your answer, which will be along the line sof using Odin, very easy to use, so good luck and enjoy.
win7-64bit and kies connection semi-working method
I've tried almost all methods mentioned on different forums...but since i'm unwilling to mess to much around i've opted for this way:
using latest kies 1.5.3. 80something... on win7 64 bit..
remove the lockpattern from the phone if yo uhave it enabled
install kies...remove the kies autostart option and the kies trayagent
do the repair drivers and reboot
ones the bios screen is done..have the phone unlocked and connect to pc/laptop
wait and wait some more after login to windows..
one most occasions windows will finally tell you it have a new device ready for you...then open kies and life is good.. at least until like in my case the laptop goes into powersave mode and the connections are broken and I have to do the reboot step again
the firmware update from jf__ something to jm__ something was a hassle...but after a few attempts to run it the darn thing finally worked..
hope this helps
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
ardll said:
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
Click to expand...
Click to collapse
i am with win7 x64, fine here
using odin to flash rom is dam easy job.
Kies updated to _82 today.
the _82 update fixed closing the firmware updater for me that was in the last 2 builds on win7 x64 , it promptly closes having not used up more than 33mb ram when I click cancel or close after checking for new firmware, previously it billowed up to over 1300mb use and really flawed my system until it, kies and the connection manager were terminated fully.
http://www.samsung.de/de/support/detail.aspx?aguid=47e29085-4dff-4b5c-b8ab-dd9b9c8b70f8&dl=software
try the new PC Studio software for SGS
download link and detailed info on SGS wiki, click my link

Problem making pc to recognize phone.

Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!

9001 wont update through kies

Just bought this galaxy 9001 phone, and installed kies.
Kies says there is an update for the phone, so sure i want to update.
Kies download firmware fine, but the phone dosnt update , now 3 try waited for 1 hour now, and the update meter is still 0 %.
The phone shows " Downloading do not turn off target " .
Well anybody , am i missing anything here.
My latest wave 8500 updated fine trough kies.
ps. did af total reinstall after disposing my old wave phone.
please help.
Try to reinstall the drivers in kies.
There is a option connection problem.
Try another usb port.
Try another cable.
If you got the option, try anther pc/laptop
Sent from my GT-I9001 using XDA App
Same thing happened to me the first time ever i tried to update through kies, i can suggest the same thing suggested by outbrood: try using another usb port or another pc.
Sent from my GT-I9001 using XDA App
I had exactly the same.. stop using Kies and go for Odin!
ok Tried on my wifes pc today, and the same thing happens. i can see kies is downloading, and preparing, the phone turns on with a little green guy, and now stock at 0%. the pc isn´t frozen, and taskman tells my both kies and firmware update is running.
How long does it normaly take to update the phone. im at over 1 h. now and nothing had happend.
About odin, is future update through kies still possible.
Remember my old wave phone, after manualy update , kies then complaind about not been able to update to my phone, cause wrong firm installed.
Yes but what does it care? Kies is known as a bad flashing tool. Odin is much better.. If you are using Win7 x64 you can forget using Kies properly. I suggest you just backup your numbers using kies and then start using Odin.
Odin is much better. Kies bricks phones.
sent from my Nexus S
picorama said:
ok Tried on my wifes pc today, and the same thing happens. i can see kies is downloading, and preparing, the phone turns on with a little green guy, and now stock at 0%. the pc isn´t frozen, and taskman tells my both kies and firmware update is running.
How long does it normaly take to update the phone. im at over 1 h. now and nothing had happend.
About odin, is future update through kies still possible.
Remember my old wave phone, after manualy update , kies then complaind about not been able to update to my phone, cause wrong firm installed.
Click to expand...
Click to collapse
When I first updated my phone through Kies it took about 15-20 minutes, if you want to update your phone using Stock Rom (that is the ROM you're trying to update throgh kies - you have to take note of the number and letters before updates) i advice you too to use Odin.
Ok ill give odin a go.
Does odin clear all settings and apps installed, like MultiLoader did when flashing my wave.
I know about falshing the right firmware, it was a ***** to get my hands on Danish firm to the old wave, hope i more luck finding the latest in danish for the Galaxy.
Right now im very very happy that i flushed that sammy wave the galaxy is so much faster and fun to use.
thanks for replying. Odin it is.
A friend just managed to update his SGS+ via Kies after 12 or something hours of failed attempts (he did try everything from drivers to USB port and cable)
The official update stopped mid-download at a random percentage every time.
His PC was running Win7 x64 and on his final attempt he used another computer with Win XP that did the trick.
The good thing after this adventure of his was that all the apps, messages and settings were kept.
wonder if a virtual xp inside win7 32bit , would do the job.
picorama said:
wonder if a virtual xp inside win7 32bit , would do the job.
Click to expand...
Click to collapse
Quite risky in my opinion, as USB has to be connected through virtualization layers. This might work without any issues but could cause severe problems as well.
I personally tried to connect with KIES from a Win XP vm running on Win7 x64 natively (with vmware Workstation) and it did not work properly.
Tried it several times and with various boots and settings.
But I may have been too impatient, on my netbook KIES also needed several attempts to get connected to the phone.
In the end, I flashed with Odin, that worked right at the first attempt.
If you have Windows 7 on 32 bits you can update via Kies.I updated my phone without any problems when I was using stock ROM.I now just use it for backup.
Windows 7 32 bit never faced this type of problem but yups my friend bricked his phone while updating through kies so be careful also

New phone, can't update. Driver issue

I'm sure this is been written about several times, but I just bought a new Z3 compact and have attempted to update the firmware through the Sony PC companion app. When it is prepared and it tries to turn off your phone and install the S1 drivers, it is unable to do so. I have manually downloaded the Z3 compact drivers and pointed device manager to them but they will still not install. Google search hasn't helped anything although I've seen references to fast boot drivers. Is this what I want? I assumed I needed the USB drivers and I've only grabbed the ones from Sony directly. I'm not interested in modding the phone at this point, just installing the stock updates.
For what it's worth Sony PC companion can recognize my phone when I attach the USB when the phone is powered on it's the update process where it stalls out.
Thank you in advance for any thoughts.

Can't connect Nexus 6 via USB

Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Lyper said:
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Click to expand...
Click to collapse
Delete all your android drivers, and try this:
http://forum.xda-developers.com/showthread.php?t=2588979
I removed 4 adb drivers and many samsung ones, installed with administrator settings the linked content, then it tried to install the nexus 6 via the default windows updated. Seemed to work, get the sound for connection, but no option to transfer my stuff. I tried uninstalling the drivers and re-installing, still nothing.
http://puu.sh/jVt0q/57fb6bf8d3.png
No more ideas?
Lyper said:
No more ideas?
Click to expand...
Click to collapse
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
prdog1 said:
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
Click to expand...
Click to collapse
Yeah well I did that multiple times, which didn't work. I really don't feel like reformatting, ho boy, but I really gotta get this going. Thanks for the suggestion!
Try switching ports.
Sent from my Nexus 6 using Tapatalk
I tried switching ports.
Ok so the list of things I tried : Manually removing any drivers that had to do with android/usb phone, I reinstalled the drivers for my motherboard, I fixed every system inconsistency with ccleaner, removed android studio. I had also manually removed any prior detection fo the nexus 6 in the device manager. It will once again pop up the "driver install" from windows, complete, but be impossible to manually update via device manager as it doesn't recognize my device.
I'm also using the default cable from my nexus 6, and tried others. Is there anything else to do? Otherwise reformatting tonight. Thanks everyone for the support.
Hello, sorry to keep bumping this thread. I just reformat... and the problem still persists. I have no clue what to do anymore, I literally tried everything I could possibly think of.
Anyone got any ideas? To state again, I'm running windows 10 x64.
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Nevermind, I did a total complete reformat now, still doesn't work. I'm literally out of ideas now.
Should I contact my motherboard manufacturer (MSI) ?
not sure what to tell you, but definitely samsung drivers and motorola drivers do not play well together very often
Lyper said:
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Click to expand...
Click to collapse
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
prdog1 said:
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
Click to expand...
Click to collapse
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Lyper said:
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Click to expand...
Click to collapse
Have you tried a Windows update since the original boot. On my son's AZUS the touchpad driver was bad. It had changed driver to a Generic. Deleted that driver and ran Windows update and it found the new driver. Worth a shot. Hard to tell what to do. I couldn't see any differences after the Win 10 upgrade. Didn't even effect my dual boot Linux. My friend just lost lost the drive sync to his Linux setup.
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Lyper said:
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Click to expand...
Click to collapse
Can you tell where can I find the media pack for windows 10?
Thanks.

Categories

Resources