I have an ATT X10, and i can no longer root it...after updating via Sues Anyway...2.1 update 1, bb 54, build 435. I have installed ADB and i get the error, " ADB didn't ACK, starting on port 5037*. Checked all drivers, everything is fine...even uninstalled ADB and tried reinstalling still the same...superoneclick, i get the same error..FAILED By the way debugging is enabled, unknown sources also! X10 drivers installed and gordons gate for flashtool. I've tried it all, and i cant figure it out! I don't want to go to the extent of clean installing windows 7 again..hope not. Can it be rooted manually like the first root was ha?!?! Please help and thank you much!
Flashtool also says searching adb device please plug in etc...it is...same thing again. Only option i have there is to flash, all other options are greyed out! I don't get it!
Did you lose all and any kind of access through ADB, you can't do anything through a USB cable?
Did you try to have an ADB access from other PCs and failed, too?
Related
I tried to root my Samsung Vibrant using the One-Click Root method but when I get to the part where the phone is supposed to reboot into Recovery Mode, nothing happens. Then, I checked Device Manger to see if there were any problems with the drivers and it said that Windows failed to initialize the Samsung Android Composite ADB Interface driver. How do I fix this?
I have Windows XP 32-bit.
I googled fixes for this for a while but nothing I found worked. Any help would be appreciated.
Does Kies is running without any problems and you can connect your phone?
If No, pls install Kies and be sure that you have an access to your phone.
If it is working: pls close Kies - also in the Systray. Not that the 2 different application makes trouble
I can connect my phone to Kies without any problems but it still won't work even after I uninstalled Kies
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
_SpAiK_ said:
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
Click to expand...
Click to collapse
Does it not recognise it at all or will just not mount?
I can mount it, but if I type "adb devices" in cmd it returns a blank list. I've switched of my firewall and antivirus, but it does not resolve anything. I've seen that when running adb, it loads two instances of adb.exe and then kills one, also when trying to root with SuperOneClick it loads and maintains two instances.
I've had trouble with it most of the day but seem to have sorted it now, but it does show with adb devices for me so not sure.
Once you update to 2.1, you need to update the drivers.
The easiest way is to install Sony Ericsson's PC Companion (and update): http://www.sonyericsson.com/cws/support/softwaredownloads/detailed/pccompanion/xperiax10
I was wondering about this too. Sony Ericsson Update Service would detect the phone in flash mode, but not ADB or SuperOneClick. Once I installed PC Companion, it was fine.
Check your Device Manager. I'd bet you have a yellow exclamation mark.
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.
Hello,
it's almost 2-3 hours that i'm stuck with instaling drivers on pc for my Prestigio Multipad PMP5097CPRO.
I wanna root it, but I need first to install drivers propery to debug via USB.
Root with "ICS Root Unlocker"
I used that guide sendspace.com/file/4dwex1
tried with different versions of Rockusb, but still the same. (unable to install drivers)
I even tried different usb cable/port/ and pc, but no work (win7 64bit)
ADB driver don't work too. I've read this thread but find nothing similar http://forum.xda-developers.com/showthread.php?t=1796067 or this http://forum.xda-developers.com/showthread.php?t=1957790
Any idea
thanks
4Cvetko4 said:
Hello,
it's almost 2-3 hours that i'm stuck with instaling drivers on pc for my Prestigio Multipad PMP5097CPRO.
I wanna root it, but I need first to install drivers propery to debug via USB.
Root with "ICS Root Unlocker"
I used that guide sendspace.com/file/4dwex1
tried with different versions of Rockusb, but still the same. (unable to install drivers)
I even tried different usb cable/port/ and pc, but no work (win7 64bit)
ADB driver don't work too. I've read this thread but find nothing similar http://forum.xda-developers.com/showthread.php?t=1796067 or this http://forum.xda-developers.com/showthread.php?t=1957790
Any idea
thanks
Click to expand...
Click to collapse
Go to www.snappea.com and install it on your PC, with phone disconnected from PC. Once snap pea installs it will pop up a message asking you to turn on USB debugging on phone then it will ask you to connect to pc, Snap pea should be able to install a generic ADB driver that will work for what you need.
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.