I am rooting my friends phone using the proper thread, following all the directions, did this on my previous Fascinate, however I get into download mode, but Odin does not recognize it and does nothing....?
make sure you have the samsung drivers installed...
Everything is installed including the drivers, its saying the device is not being recognized even though the drivers are on my computer..
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
droidstyle said:
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
Click to expand...
Click to collapse
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
CC268 said:
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
Click to expand...
Click to collapse
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
droidstyle said:
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
Click to expand...
Click to collapse
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
CC268 said:
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
Click to expand...
Click to collapse
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
droidstyle said:
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I will try this tonight when I get over to my buddies apartment, thanks
I couldn't get it installed...the directions on actually getting the driver installed are not good...there are a lot of steps that I can't do on my computer such as go to manage in computer and then devices tab...there is no devices tab?!?!
CC268 said:
I couldn't get it installed. It just said windows has already found the appropriate driver. I dont understand how it could be so hard to find a dang driver for this phone...
Click to expand...
Click to collapse
it wont automatically install...you have to click on the device in device manager and go to update driver, then manually push the google driver. After successful install it should say android device in DM.
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
CC268 said:
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
Click to expand...
Click to collapse
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
droidstyle said:
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
Click to expand...
Click to collapse
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
CC268 said:
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
Click to expand...
Click to collapse
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
droidstyle said:
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
Click to expand...
Click to collapse
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
CC268 said:
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
Click to expand...
Click to collapse
here is adb root method if it helps:
To Root
(credit p3droid/Mines_01 from ec09)
***Requires ADB***
1. Download this: http://www.multiupload.com/HXKQY717LY
md5: 113a9158535ddefa802eb2dc187f236d
2. unpack to wherever adb folder is
(if adb is universal unpack wherever)
3. cd folder with unpackaged files
4. adb push su /data/local
5. adb push Superuser.apk /data/local
6. adb shell
7. mount -o remount,rw -t rfs /dev/block/stl19/system
8. cat /data/local/su > /system/xbin/su
9. chmod 6755 /system/xbin/su
10. cat /data/local/Superuser.apk > /system/app/Superuser.apk
11. chmod 755 /system/app/Superuser.apk
12. reboot
Related
I had adb set up before I flashed the stock kernel using HTC sync, but now it doesn't seem to want to work. How can I get HTC sync to work again so that I'm able to use adb once more?
abctilly said:
I had adb set up before I flashed the stock kernel using HTC sync, but now it doesn't seem to want to work. How can I get HTC sync to work again so that I'm able to use adb once more?
Click to expand...
Click to collapse
try reinstalling the driver or if you haven't done so installing lol
http://www.multiupload.com/2OFYWZFCCR
if anything try another usb slot. I noticed one of my usb slot shows like the SD and phone but then it won't be detected on ADB whereas my other usb slot does.
Teo032 said:
try reinstalling the driver or if you haven't done so installing lol
http://www.multiupload.com/2OFYWZFCCR
if anything try another usb slot. I noticed one of my usb slot shows like the SD and phone but then it won't be detected on ADB whereas my other usb slot does.
Click to expand...
Click to collapse
I've tried installing the drivers before, but it just doesn't open anything when I click on the zip file. I'll try my other 3 ports
Edit: Wow... the usb slot furthest away from me actually worked... can't believe I didn't try it yet lol. Thanks!
abctilly said:
I've tried installing the drivers before, but it just doesn't open anything when I click on the zip file. I'll try my other 3 ports
Edit: Wow... the usb slot furthest away from me actually worked... can't believe I didn't try it yet lol. Thanks!
Click to expand...
Click to collapse
the link i posted isn't the manual zip file. I posted the exe file that would automatically install the drivers in for plug and play use. But if your usb slow works then you have the drivers. I would suggest using USBdeview and uninstalling everything that has like HTC in it because it sounds like your other usb slots have a bad install when you connected your phone. It takes awhile for the drivers to install when you connect your phone.
Please take the time to read this:I flashed and installed SkyRaider a couple days ago and I noticed when I connected to my PC that my PC started recognizing it as HTC Phone (or something of the like). This apparently really screwed up my drivers on my computer because I installed iKReaM and now I can't even get into disk drive mode...it doesn't ask what connection type I want anymore and my computer just says "USB Device Not Recognized". I tried uninstalling the HTC Driver Installer but that didn't do anything either. This is not good as I ran into the same problem when trying to root my friends Samsung Fascinate and never go the problem fixed. Anyways...my phone worked perfect before and SkyRaider evidently messed it up pretty good...to say I am pissed is an understatement. If you need any more info please let me know.
Please link me to the newest HTC Drivers as well, it would be much appreciated.
If no one can help I will have to do a clean install of windows 7, which is not an enjoyable experience
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Stratejaket said:
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Click to expand...
Click to collapse
I can't get into recovery anymore using usb mode, computer doesn't recognize the device so no way to use it...and I would use the Wifi app instead of using a usb cable? I see what you mean by easy but I don't wanna avoid the problem...I have a brand new $1600 Alienware so I would like to have it fixed lol...if need be I may just have to do a clean install
I know this isn't your actual problem but just for the record, AirDroid lets you control your phone and push files to it with a web browser and wifi for free.
(I tried linking it but I guess I haven't made enough posts to include links yet, easy to find by searching the Market tho)
You might check under Settings/ Connect to PC to make sure the Ask Me option is turned on.
Sent from my ADR6400L using Tapatalk
When you plug your phone into your computer does the phone start to charge?
If so restart the computer and plug the phone into a different usb port. Check device manager and see if you have it listed in your usb devices, or you have an ! over a usb. Most of the time this ends up being an issue with the computer it is being hooked to, not the phone. The computer isn't launching the driver correctly to show the phone that it is connected to a computer, and not just a wall outlet.
Even when I've had this issue, which is random I have still been able to use recovery usb to manage it. Make sure when your in recovery you mount the sdcard before enabling the usb.
Happy Holidays Everyone!!!
Phone:
Tmobile T959 aka Samsung Vibrant
It is on stock Froyo 2.2
It has the 3E recovery.
I tried on 2 computers but I can NOT connect via USB it gives me USB malfunction error. The phone does charge. I can put it into download mode vie the 3 finger trick. When you connect it does give you the option to click the green Android icon Connect to USB. So it is talking to the computer, the usb is not totally dead.
Problem:
I need to root this phone. I can not use 1 click or anything else because I think there is a problem with the USB port. I can get files onto the phone via wifi or using the external sd card.
I tried using the update.zip file BUT because I am on the 3E recovery it will say signature failed. I can not run the install.bat to get it back to 2E recovery. I can not use ODIN because the Windows will not detect the phone properly.
What workaround can I use to root this phone? How would I use terminal on the phone?
HOW WOULD YOU ROOT THE PHONE IF YOUR USB PORT WAS "broken"?
THANKS for helping!
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
TheAndroidGod said:
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
Click to expand...
Click to collapse
It's out of warranty
I think there may be a way to do it via terminal emulator on the phone.
If this is possible, can someone please post how to do it.
anyone with a work around?
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
droiduzr2 said:
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
Click to expand...
Click to collapse
Try to install phone drivers for the computer i had to do that for my phone.
maikzen said:
Try to install phone drivers for the computer i had to do that for my phone.
Click to expand...
Click to collapse
I did all of that.
I think something is wrong with the phone's OS that is effecting the usb port.
How do I root this phone WITHOUT the USB port?
There has to be a way!
Can you determinate VID&PID of phone?
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
droiduzr2 said:
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
Click to expand...
Click to collapse
Is there not a device forum where you might could get some better information? My thinking is, a lot of the people (or most of the people) who may know some workarounds can probably help, but they don't check this section very often or at all.
Even if there's not a section for that model, I'm thinking there's probably one quite similar. Also a lot of times, a big portion of the userbase of one phone, will migrate to the same model when they upgrade.
Just throwing out some ideas in case that's helpful. My only advice on the problem itself is that I would look further into the driver issue. I've helped several people with very similar issues that we finally were able to correct.
Have you tried to ADB the device just to pull the serial? With USB debugging enabled. Have you installed the SDK and tried the naked drivers? There's some things to pursue possibly so you can have more information for the person who helps you get things straightened out.
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
Hello all I recently received a bricked prime from a noob who did not know what they were doing. I tried the method Option 1A from the following thread http://forum.xda-developers.com/showthread.php?t=1514088. As I am unable to boot. Here is what happens and what I have tried.
The tablet turns on and goes straight into recovery, I attempted to run the adb commands from the above thread to no avail, because adb can not detect the device, I have installed the naked drivers for the device on my windows machine with no luck either, windows says Unknown Device, unable to start.
There are no additional roms on the sd card to attempt to install one, I am not sure how to place a rom onto the tablet in recovery or through the pc.
Thanks for any help in advance
mastherser said:
Hello all I recently received a bricked prime from a noob who did not know what they were doing. I tried the method Option 1A from the following thread http://forum.xda-developers.com/showthread.php?t=1514088. As I am unable to boot. Here is what happens and what I have tried.
The tablet turns on and goes straight into recovery, I attempted to run the adb commands from the above thread to no avail, because adb can not detect the device, I have installed the naked drivers for the device on my windows machine with no luck either, windows says Unknown Device, unable to start.
There are no additional roms on the sd card to attempt to install one, I am not sure how to place a rom onto the tablet in recovery or through the pc.
Thanks for any help in advance
Click to expand...
Click to collapse
Sometimes windows saying Unknown Device and you can't install naked drivers is a faulty cable. It will still charge but give the symptoms you describe.
Try borrowing a cable or get a cheap one off eBay to eliminate cable.
flumpster said:
Sometimes windows saying Unknown Device and you can't install naked drivers is a faulty cable. It will still charge but give the symptoms you describe.
Try borrowing a cable or get a cheap one off eBay to eliminate cable.
Click to expand...
Click to collapse
Thanks bro, now that you mention this cable is a little beat up, I will go purchase another one and post back.
flumpster said:
Sometimes windows saying Unknown Device and you can't install naked drivers is a faulty cable. It will still charge but give the symptoms you describe.
Try borrowing a cable or get a cheap one off eBay to eliminate cable.
Click to expand...
Click to collapse
You were right the cable did do the trick, windows recognizes it as "transformer" begins to install something, and when I check in device manager, it shows up as Transformer, but it has an error 28 no driver installed, it asked me to update, I tried to manually update to the naked adb interface driver and it gives me error code 10 device cannot start.
Fixed thanks again for the help.
Sent from my Transformer Prime TF201 using XDA Premium HD app