Related
Hey, so I was trying to enable non-market apps through ADB. Everything was going good until I typed in "adb reboot" and then stupidly unplugged the cable.
Now the phone doesn't do anything, can't boot Android, only the recovery menu. It just shows the intro movie and then shuts down. I've tried deleting user data and clearing cache from recovery which doesn't help.
I do have a NANDROID backup for it, both on the phone and on my PC (which was made with Clockworkmod Recovery). But the problem is that I don't have the update.zip for Clockwork on the /sdcard, it's in /titaniumbackup. How can I put the update.zip on the /sdcard of a bricked Captivate?
when you boot in recovery, does ur computer recognize the device if connected with usb? If so you can use adb to relocate files, droid explorer may even work.
Oh thanks, I had no idea ADB would work in recovery, gonna try that and get back to you.
As you can see I'm still new to Android. Dumped iPhone 3G for Captivate. But I'm learning!
So Droid Explorer won't install because it doesn't like 64bit Windows.
ADB can connect, but I can't put any file on the device (I've tried the "adb push" command) or gain root, says permission denied. Please help!
EDIT: Never mind, by some miracle of God it all worked out and let me adb push all I needed, I'm in Clockwork Recovery and my phone is gonna be OK.
i have droid explorer running on my intel, windows 7 ultim 64x rig. works.
you just have to make sure you dl the 64 bit version of the program. Here's a link:
http://de.codeplex.com/releases/49896/download/139717
you also need .net framework 3.5 sp1 at least. I installed the newest one and it works regardless.
im glad you managed to unbrick your device. Kudos.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
hello and pardon by the English because I am translating.
I have a HTC S and I wanted one 2 days ago I put a ROM nandroip and everything but I realized and I wipe the entire phone erasing all the ROM and everything I had.
the problem is I can not install a ROM on my phone now because every time I try from windows CMD when you start the installation makes me daemon not running, and sends me error: device not found.
I've tried with another tutorial that you have with the application all in one kit but also not let me access this sd every time I try to enter telling me insert disk into drive E: \.
I can do?
I think it may be by the drivers of PC but not sure I instadao have 5 or 6 drivers and nothing.
an administrator's name is called android MYHTC ADB and other android or something.
I am desperate thank you very much took 2 days doing everything.
thank you very much.
my windows is XP.
Ok, Sorry but im having difficult understanding everything you say, But i think i got the basics.
I would suggest you re download the drivers, Remove HTC Sync if you have it. Move all of your ADB files in to 1 folder so its easier to navigate to when using ADB.
Can you boot the phone into recovery ? I assume you have CWM as you say you installed a nandroid ? If so, Use ADB whilst in recovery, USB Debugging is always enabled when in recovery so you should have no issues finding your device from there.
If all goes well and you find the device, You can then PUSH and INSTALL files / roms from there
Keep us posted
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
UPDATE :
Use flashtool drivers to install adb/fastboot/flashboot drivers. This is the most simplest and easiest method I have come across lately.
Simply download flashtool
http://www.flashtool.net/index.php
Go to folder where you have downloaded it. Usually C:/flashtool/drivers.
Select the drivers for your particular device. I use universal for all three types of drivers. It is helpful to boot into fastboot/Flashtool before installing the drivers but not necessarily.
Good Luck
Reserved
This is great Hnk1 thanks a bunch
joel113- said:
This is great Hnk1 thanks a bunch
Click to expand...
Click to collapse
I am glad I could be of help
Good work
Hnk1 said:
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
Click to expand...
Click to collapse
:good: Good work
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
ReSkid said:
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
Click to expand...
Click to collapse
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
you can use ADB Wireless
https://play.google.com/store/apps/details?id=com.sherdle.adbwireless&hl=en
Hnk1 said:
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
Click to expand...
Click to collapse
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
ReSkid said:
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
Click to expand...
Click to collapse
I am here for anything that I can help you with. It's great that your problem is fixed now !
AATrooperz said:
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
Click to expand...
Click to collapse
For a second when I looked at your images, I was just baffled. THOSE MANY UNKNOWN DEVICES! That can't be right you know.
There must be only ONE unknown device that ought to be installed as mentioned above in my post.
Do you see these devices when you connect your phone to your PC or those unknown devices are already there?
Have you tried windows update to fix it?
Tell me more about why you see so many devices.
If suppose, they are already there, just see which device comes up when you connect your phone and try installing drivers for that particular device.
Also, i suggest just go for add a new device and then select hard disk and then install drivers which are attached. I hope that fixes your problem.
REMEMBER your device must be connected when you are trying to install the drivers
right.i'm gonna give it a try,wish me luck. thanks!
I still need your help!!
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Hnk1 said:
I am glad I could be of help
Click to expand...
Click to collapse
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
Hi
well first thing you need to understand is there are three drivers you need to install to make everything work including fastboot , flashboot, and Xperia L storage and SD card.
To install each type of drivers, you must have the phone in that particular state. To install normal drivers (for mass storage and PC companion), if suppose not detected automatically, you need to turn on your phone and then unlock it. Then see if drivers are found or not!
If the windows give you the error like undetectable device attached, go to my computers and then properties and the device manager and look for any device with an exclamation mark (yellow).
click on it and then select update drivers and use drivers that have been attached in the first post. (Remember to extract the attachment in a folder)
Then click on select drivers from hard drive (click manual installation of drivers )
and locate the folder where you have extracted drivers. This will install drivers!
if you want drivers for flashmode/fastboot, turn off phone and boot into flashmode and then install drivers as I mentioned above.
I'm quite certain they wouldn't trouble you at all. If you still need help, do not hesitate to ask !
Good luck
P.S: You will need to enable developers option and select USB debugging to root your device. I hope you are doing that right !
Joel16 said:
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
Click to expand...
Click to collapse
Thank you so much ! I only check my notifications so I really appreciate it
uremytoy said:
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
Click to expand...
Click to collapse
Actually why don't you have a look at what the OP said,
"Thankyou so much, I only check my notifications so I really appreciate it"
I know what I'm doing here, if you don't have anything nice to say about it then DON'T say anything
Thanks..but still need you
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
FPThatea said:
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
Click to expand...
Click to collapse
you must boot your phone in fast boot mode. turn off your phone and hold down volume down when you connect it to the PC!
Use flashtool to flash ftf file. you'll need to place ftf file in C:/flashtool/firmwares
then select the right file for xperia L and just flash ftf.
in flash tool , select flash n then fastboot and then I'll ask you to put your phone in fast boot (use method mentioned above)
good luck !
I have tried all your methods
but I keep getting this error message "An error occurred during the installation of the device"
I am using windows xp sp3
please help
I just got my Nexus 5. Unlock bootloader, flash CWM, and rooted it with SuperSU..
Apparently it can work with fastboot, however when I try to use windows explorer to browse the files, it does not work correctly.
Example, from the phone's es explorer i can see my TiBu files in its folder, but in windows there is nothing there..
I cannot copy files into my phone, windows will prompt me the device stopped working.
Is it something to do with the drivers? I tried on a completely new laptop and just tried to let Windows do its own driver installing but its still the same..