hi there
recently re-instaleld windows, now with flashtool installed when attempting to drop an ftf onto the flashtool window I just get a no entry icon
the flashtool window does say
error drivers need to be installed for connected device
you can find them in the drivers folder
I have run that exe in there, ticket the tx and flashtool, fastboot drivers all installed fine it seems
but no luck
also when I use pc companion to install MTP i get an error:
operation failed with 0x8007047F
the specified program is not a windows or ms-dos program
I am running win7 x64 Pro N (which is no media player.. could this be the issue..?)
any ideas?
driving me potty
I have a Xperia T
currently with
siyah kernel and
7.0.A.3.195
stock rom
CWM
any help much appreciated
basically am just trying to get timin8r's rooted JB rom on to the phone following the steps here: forum.xda-developers.com/showthread.php?t=2026918
xda-nat said:
hi there
recently re-instaleld windows, now with flashtool installed when attempting to drop an ftf onto the flashtool window I just get a no entry icon
the flashtool window does say
error drivers need to be installed for connected device
you can find them in the drivers folder
I have run that exe in there, ticket the tx and flashtool, fastboot drivers all installed fine it seems
but no luck
also when I use pc companion to install MTP i get an error:
operation failed with 0x8007047F
the specified program is not a windows or ms-dos program
I am running win7 x64 Pro N (which is no media player.. could this be the issue..?)
any ideas?
driving me potty
I have a Xperia T
currently with
siyah kernel and
7.0.A.3.195
stock rom
CWM
any help much appreciated
basically am just trying to get timin8r's rooted JB rom on to the phone following the steps here: forum.xda-developers.com/showthread.php?t=2026918
Click to expand...
Click to collapse
try turning it off and connecting it into flashmode and hold the volume down maybe it will install drivers.
mcsqwizzys98 said:
try turning it off and connecting it into flashmode and hold the volume down maybe it will install drivers.
Click to expand...
Click to collapse
thanks for the reply.
seems it was media player, installed that and MTP started working..
although still no luck with the ftf but installed the kernel.zip via CWM as there was a second one in Timin8rs post
just finished and all appears fine....
Related
hello there guys!
i recently bought my xperia sp and got the .245 official update from pc companion!
now i followed doomlord's and jackaros' guide on rooting the .245 but i have some issues..
so..using the flashtool i can flash both the .257 an the .245 kernels provided successfully!
but when i turn on debuging mode and unknown surces and connect the phone to the pc windows' utility cant find any drivers! even i install manually the google's usb drivers from sdk tools my phone will be recognised as Android Composite ADB Interface..but if i dont it gets recognised as c5303(with a yellow exclamation mark)(the debug mode is always on!)
also tried rebooting pc and phone..drivers update..still nothing..the command adb devices show up an empty list and the rooting toolkit stucks on *daemon started successfully*
any suggestions?
thanks in advance!
Same thing happened with me, but i think this is more Flashtool + Windows issue with .245 firmware then USB problem. Just because i did flashing using SUS, PC companion and Flashtool Linux client.
Ze Tolas said:
Same thing happened with me, but i think this is more Flashtool + Windows issue with .245 firmware then USB problem. Just because i did flashing using SUS, PC companion and Flashtool Linux client.
Click to expand...
Click to collapse
but my problem isn't with flashtool..its with the toolkit and the adb not recognising my phone..
pap96 said:
but my problem isn't with flashtool..its with the toolkit and the adb not recognising my phone..
Click to expand...
Click to collapse
For real, i not tried adb with Windows, just with Linux in my office. I gonna try later. But idk how can connect with SUS, and not with Flashtool/ ADB.
hi there i modified the android_winusb.inf trying to root my xperia z1 and to be recognized as adb device but it doesnot work
i think that i am missing something itried it with z and works perfectly but with z1 ithink its PIDS and VIDS are different
so can you upload me the adb and usb debugging drivers
i searched all over the net but canot find it please help
Does it recognize your phone?
Try Koush universal adb driver it fix it for me.
http://koush.com/post/universal-adb-driver
Sent from my C6916 using Tapatalk 2
15 seconds ADB Installer
http://forum.xda-developers.com/showthread.php?t=2588979
constantinexx said:
hi there i modified the android_winusb.inf trying to root my xperia z1 and to be recognized as adb device but it doesnot work
i think that i am missing something itried it with z and works perfectly but with z1 ithink its PIDS and VIDS are different
so can you upload me the adb and usb debugging drivers
i searched all over the net but canot find it please help
Click to expand...
Click to collapse
I have deleted your duplicate Q&A thread.
Installing Sony's PC Companion will automatically install ADB drivers.
Just download it from the Sony site and install it, then just connect your phone (while it is on) and the drivers should be installed.
Also FlashTool will also install the proper drivers.
Just remember to reboot your PC after install.
And only have 1 program using ADB open at 1 time.
Meaning that if PC Companion is running, it will interfere with flashtool working. They both connect via ADB and only ONE can be connected.
I hope it helps
Toledo_JAB said:
I have deleted your duplicate Q&A thread.
Installing Sony's PC Companion will automatically install ADB drivers.
Just download it from the Sony site and install it, then just connect your phone (while it is on) and the drivers should be installed.
Also FlashTool will also install the proper drivers.
Just remember to reboot your PC after install.
And only have 1 program using ADB open at 1 time.
Meaning that if PC Companion is running, it will interfere with flashtool working. They both connect via ADB and only ONE can be connected.
I hope it helps
Click to expand...
Click to collapse
i already had installed flashtool drivers and pccompanion but the problem is that i have a 64 bit windows 7
?? so please help again
constantinexx said:
i already had installed flashtool drivers and pccompanion but the problem is that i have a 64 bit windows 7
?? so please help again
Click to expand...
Click to collapse
just to cover the basics is USB Debugging is checked on the device?
And neither PC Companion or flashtools see the device?
Make sure there are no entries for sony in the usb section of the device manager in windows.
If you find some just right click and uninstall
I just found this [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1
I have same problem like you
Pc Recognize my phone and I can flash ftf file using flashtool but when i try to unlock bl it failed.
Sent from my C6903 using xda app-developers app
iam stuck here
iwant to root z1 android 4.3 and back up the TA sector so if i want to backup TA's i must be rooted and i have to unlock bootloader then the TA will be erased ..
how to root then the v root not working cause its not detecting the xperia as adb composite device , windows is detecting it as xperia z1
and the adb composite device driver for windows 7 64bit canot be found so what the hell iam going to do ..
no one have adb drivers for xperia z1 on 64bit
USB\VID_0FCE&PID_519E
here is my device pids&vids
That's why is better have 2 PC in house, 1 32bit and another in 64bit. Still 32bit the best.
I got the message from pc siad missing adbwinapi.dll
what is that?
let me fix my problemfirst
download the missing dll and turnoff your antivirus
here is the adb dll: http://download.dll-files.com/47a6ee3f186b2c2f5057028906bac0c6/adbwinapi.zip?0WLmVAVFeW
constantinexx said:
iam stuck here
iwant to root z1 android 4.3 and back up the TA sector so if i want to backup TA's i must be rooted and i have to unlock bootloader then the TA will be erased ..
how to root then the v root not working cause its not detecting the xperia as adb composite device , windows is detecting it as xperia z1
and the adb composite device driver for windows 7 64bit canot be found so what the hell iam going to do ..
Click to expand...
Click to collapse
i did this yesterday.
downgrade to 534 via flashtool with firmware from here. you can do this without unlocking your bootloader. ta partition will be intact. data will be gone however...
then use kingoroot to root your phone (or whatever you like) and backup your ta-partition. for this you need working adb drivers...
i did the trick with this tool. i've installed the tool, the tool has installed the right adb drivers and then i've removed it. working on win 7 64 bit ultimate
after that you can use this procedure to get a rooted 4.3 firmware.
worked fine for me
really thanks for your reply ill try it today
you are really genius you saved ma day
ive been looking for this **** 3 days and the pdanet saved my ass tanks alot
Only use a usb 2.0 port!
ONLY USE A USB 2.0 PORT - Then start Sony PC Companion and connect your phone just for anyone who like me has just stumbled upon this thread in an attempt to get ADB installed, I just found this to work.
Okay,
This is my friends phone and since i've done it i feel responsible,whatever.
The story goes,the xperia was on stock 4.2.2 i believe and we decided to flash 4.4 on it. So we downloaded the zip etc.
Now i've done the research and i think we shouldve first installed 4.3 then 4.4,i also think we shouldve flashed the kernel via flashtool first.
Anyway,now when i boot it vibrates and only shows the sony logo. I cant get into recovery.
We did manage to get into download mode with flashtool. But it disconnects (Do i need fastboot drivers,adb?)
Your input would be very appreciated!
Thanks in advance
You can hopefully use Flashtool to flash an appropriate stock FTF file to get the phone back to normal working order. There is a thread in here somewhere that links the latest version of Flashtool.
After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. Go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia V? or T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** Win8.1 will not allow these drivers to install. At all. Win8 will allow but you must disable Driver Signature Enforcement first. I dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again.
Wow thank you so much! I've tried all of the above but on windows 8.1 laptop. But I got ahold of a windows 7 one and it did the job perfectly. Thanks!
Sent from my GT-I9505 using xda app-developers app
Thanks
LaZiODROID said:
You can hopefully use Flashtool to flash an appropriate stock FTF file to get the phone back to normal working order. There is a thread in here somewhere that links the latest version of Flashtool.
After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. Go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia V? or T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** Win8.1 will not allow these drivers to install. At all. Win8 will allow but you must disable Driver Signature Enforcement first. I dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again.
Click to expand...
Click to collapse
Thanks, I also have same problem, Thanks again
Hey XDA.
For long i have been trying to get a custom ROM for my android, but to be able to do that, i need to unlock bootloarders for my device.
I have been trying for a couple of months now, and everytime i try, i hope that it will work this time... but i always end up quitting, because i always encounter some problem, i cant seem to resovle.
I was wondering if anyone would like to help me through, step by step, until it actually works.
This is what i have tried
- I have entered the system configurator, and it says yes to that my device can be unlocked.
- I have enabled all the developer options descirbed everywhere
- I have downloaded the Android SDK, with the google USB drivers.
- I have gotten my unlock-code from Sony
But everytime i try to follow the steps from Sony, I get an error when coming to install the drivers.
The tutorial says, that when i plug the usb-cable to my computer, i would be prompted to install some drivers... I dont, it automaticly installs something called "S1Boot Fastboot".
Then i enter my device-manager, finds the device, and updates drivers manually from my computer.
But when i point to the downloaded drivers, i get this error:
Windows found a driver-software for your device, but encountered an error while trying to install it.
Windows ADB Interface
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with.
The files i have downloaded are all those Sony told me to download, from the official distributors... I got no idea how to solve this issue!!
Can anybody please help to fix this issue, or guide me through another way that works?
I have given up trying...
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
electrash said:
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
Click to expand...
Click to collapse
I agree with this. I just did it the other day.
I'm using a Win 8.1 laptop and it was driving me mad. I followed the information regarding changing some of my start up settings on the laptop and flashtool installation of drivers worked. Follow this. http://forum.xda-developers.com/showthread.php?t=1913245&page=6
In my case i had Flashtool installed, but when i went to install the drivers for my z1 , the windows installer would always fail. After using the information on that page I Linked, it worked straight away!
Good luck .
Thanks alot!
Thank you very much guys, that was just what i missed!
Glad you finally got it!
Sent from my C6903 using XDA Free mobile app
Hey guys,
long story short: I flashed my device and now my pc wont recognise the usb-connection between my phone and computer. The hardware-manager describes as if the phone cant tell the computer that it is a z3 compact.
Errormessage: Unknown USB-device (Cannot get the device description)
*something like that*
what I did to troubleshoot:
- reflash the device with firmeware: A.1.264 (without this strange script)
- reflash the device with the concept preview (without this strange script)
- installed PC Companion from Sony
- Linux cant see the phone, but can flash it
- USB-Debugging wont work as well
Nothing worked for me so far. Anyone an idea what to do?
thanks in advance
Nummer35 said:
Hey guys,
long story short: I flashed my device and now my pc wont recognise the usb-connection between my phone and computer. The hardware-manager describes as if the phone cant tell the computer that it is a z3 compact.
Errormessage: Unknown USB-device (Cannot get the device description)
*something like that*
what I did to troubleshoot:
- reflash the device with firmeware: A.1.264 (without this strange script)
- reflash the device with the concept preview (without this strange script)
- installed PC Companion from Sony
- Linux cant see the phone, but can flash it
- USB-Debugging wont work as well
Nothing worked for me so far. Anyone an idea what to do?
thanks in advance
Click to expand...
Click to collapse
I tried a fresh install of windows 10 and flashed the official 6.0.1 update fia .zip
NOTHING HELPED any ideas?
Nummer35 said:
NOTHING HELPED any ideas?
Click to expand...
Click to collapse
Some roms come with the usb functions disabled, removed as bloatware. So it's possible the first rom you tried didn't have the usb functions installed.
Do you have the correct drivers
Presumably flashtool can see your phone and it's still charging, so I'm sure the hardware is ok.
Did you try a repair with PC companion?
Do you have a different usb lead you can try?
Didgesteve said:
Some roms come with the usb functions disabled, removed as bloatware. So it's possible the first rom you tried didn't have the usb functions installed.
Do you have the correct drivers
Presumably flashtool can see your phone and it's still charging, so I'm sure the hardware is ok.
Did you try a repair with PC companion?
Do you have a different usb lead you can try?
Click to expand...
Click to collapse
Hey,
thanks for your answere. I found a "solution" to connect the phone via fastboot to the pc and with this I could do a complete reset with the PCC. When the phone is booted however I get the same error message over and over again: Cant get a device description!
Maybe you can look up the specific driver which is used in the device-manager so I can force windows to use this one?
Nummer35 said:
Hey,
thanks for your answere. I found a "solution" to connect the phone via fastboot to the pc and with this I could do a complete reset with the PCC. When the phone is booted however I get the same error message over and over again: Cant get a device description!
Maybe you can look up the specific driver which is used in the device-manager so I can force windows to use this one?
Click to expand...
Click to collapse
Did you install the ADB drivers that come with flashtool? Look in the install folder for a folder called 'drivers' run the exe in there and tik the fist two and then Z3c.
Yep, all three unsigned drivers.