I recently acquired an SGP312 from ebay and the seller upgraded it to 5.0.2 without anyone asking for it (it was supposed to be NIB now who knows).
I have not unlocked the bootloader but I did confirm it is locked and can be unlocked.
I'm trying to connect it to my PC so I can get it rooted but I'm running into issues with the device being recognized.
I installed the Android SDK USB drivers & copied over android_winusb.inf and fastboot appears to be working fine. Windowns (7) Device Manager, Flashtool, and the Sony flash tool (Emma) all see the tab.
However, none of the other connection modes appear to work.
Flash mode will initially connect with Flashtool but the the device disconnects:
31/037/2015 23:37:03 - INFO - Device connected in flash mode
31/038/2015 23:38:04 - INFO - Device disconnected
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Device Manager shows an Other Devices with SGP312. I tried doing the Update Driver Software option with the drivers from the Sony developer site or the Android SDK drivers but no go.
I then boot up normally and connect either with or without ADB turned on and get the same Device Manager and driver results and PC Companion won't see the phone, either.
kadiir said:
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Download this package of drivers and install properly (Tick Flashmode, Fastboot, Common Drivers Lagan, Xperia Tablet Z drivers).
Sorry, I forgot to mention I ran the flash tool driver utility in the flashtool\drivers directory and chose the first 2 options and the XTZ-specific option but I'll give that a shot and report back.
While I did see a driver I missed I have little change in results other than MTP in non-USB debugging mode attempted to install a driver and failed:
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device
The system cannot find the file specified.
That reminds me that when I try to manually install the driver while in usb debugging mode it has the same message but with USB Composite Device where it says MTP USB Device.
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
kadiir said:
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
Click to expand...
Click to collapse
Seems to be this is an issue, because flashtool driver packages installed fine for me on WinXP/7/8.
Also pc-companion usually installs everything that is necessary for its fuctional, so must be OS problem.
Yep, that was it. Man, I should've checked that first. Sorry for the waste of time.
Quick question - do you know which ADB Interface I install from the SDK drivers? Is it ADB Interface or ADB Composite Interface? Or do I do 2 passes and install both?
Never mind - did some googling and got my answer. Thanks!
Related
I've got an Xperia U (st25i) unbranded firmware 6.0.B.3.184, but my Windows 7 x64 doesn't show adb device at all, I have a working mtp device (that looks like it cannot be disabled). Same device works fine in adb on linux, even passing the usb device to a vmware machine with linux.
I've tried with Xperia_P_Xperia_U_Xperia_sola_drivers.zip and install PC Companion, but the adb devices still does not show, if I force add the adb interface from inf, windows 7 says it cannot start, there is same problem on windows 7 x86. Windows xp x86 instead automatically installs mtd devices but prompts for the adb device drivers, so I can give him the drivers. Any clue?
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Rapier07 said:
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Click to expand...
Click to collapse
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
sherpya said:
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
Click to expand...
Click to collapse
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
gazhead said:
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
Click to expand...
Click to collapse
The only driver windows automatically install is the mtd (that doesn't need internet because is in win), I don't have the device VID_0FCE&PID_5171&MI_01 but only VID_0FCE&PID_5171
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
I had a similar problem with my XS, I get around it by enabling 'install PC companion' in connectivity settings under 'xperia'. Then when you plug the phone in, on your phone select install. It should then appear both as an MTP device the PCC installation, just cancel that latter.
I've used the wrong thread title, it should be x64 not x86, I've just verified that windows 7 32bit downloads and installs the adb driver, I had similar problem with gt7500 on windows xp 64bit, http://forum.xda-developers.com/showthread.php?t=1434319
I've solved modifying the inf file, I think I cannot change inf on windows 7 x64 because the driver becomes unsigned. Perhaps gt7500 works fine on windows 7
Heh... You stiill refuse to listen.
Install drivers provided with flashtool. Just doit and report back
mt27i
tested with internet disconnected and drivers pack in flashtool-0.9.1.0-windows.exe, same thing, windows shows only mtp device
check this out:
http://forum.xda-developers.com/showthread.php?t=1554632
more drivers:
http://www.mediafire.com/?2fxtdec2fxacux1
sherpya said:
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
Click to expand...
Click to collapse
eeh.. its GOOGLE Android default tools. adb fastboot etc its all Android getit?
Request
thebrainkafka said:
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Click to expand...
Click to collapse
Tell Me how Please....:crying:
I just solved this issue for my Xperia S.
Here are the steps:
1. Install driver on flashtool (I also install the pc companion)
1. On device manager, open the MTP device, and select reinstall device driver
2. Choose install the driver manually and list the compatible driver
3. It would only show one "USB Composite Device" for this device and install it
4. After the driver installed, the adb device just shows up!
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
Hi there,
I got a really nasty problem here: when I connect my Sony Xperia T to my home computer, the ADB driver will be installed properly. When I connect the same phone to my work computer, Windows just doesn't want to accept the drivers. The following things are equal:
- USB debugging is always on on the phone
- Both computer are running Windows 7 64bit
- On both computers I am pointing the Windows driver installation at the same folder with drivers downloaded from Sony.
The thing that is different is the device ID that Windows reports in the Details dialogue from Device manager:
On the home PC it is:
USB\VID_0FCE&PID_5182&REV_0228&MI_01
USB\VID_0FCE&PID_5182&MI_01
On the other PC where things go wrong it is:
USB\VID_0FCE&PID_5182&REV_0228
USB\VID_0FCE&PID_5182
So it seems Windows is not recognizing the phone as a composite device (MI is it multiplexing identifier?). I double checked that USB debugging is always on and also rebooted Windows.
What could could be causing this strange problem?
Android version is 4.1.2 (original Sony firmware).
Thanks
Tom
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
This is exactly what I did! Downloaded the adb driver from Sony's website. Installed them on one computer - works. Transferred exactly this driver package to the second computer with a USB Stick.
On the second computer, Windows does not find a matching driver for the same phone in the same driver package.
The reason apparently is that the phone reports a slightly different USB id when connected to the second computer (missing the MI at the end of the ID, see my original post).
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.