possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?
i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.
Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.
Related
I've searched all over the posts and google and have yet to find a solution. I am a MAC user and trying to restore fascinate. I am stuck at Samsung screen. I can get into Clockwork Mod Voodoo.
When i did my last backup I never enabled USB Debugging. I can not ./adb into device, nor can I use ODIN on friends PC. (No Device) Same result with Heimdal "Failed to detect Device" I would just like to get back to stock. Is there a step by step guide to recover similar to ODIN get you back to stock but for a MAC. Or since i never enabled Debug mode I should just use my warranty?
When you tried Odin, did you have the battery out and put the phone in download mode?
Kevin Gossett said:
When you tried Odin, did you have the battery out and put the phone in download mode?
Click to expand...
Click to collapse
Yes, I did see the Yellow triangle Droid character w/ shovel
So, battery out and in download mode, Odin doesn't recognize? Hm
Kevin Gossett said:
So, battery out and in download mode, Odin doesn't recognize? Hm
Click to expand...
Click to collapse
I feel because I never enabled debug mode originally.
Does it recognize the phone at all? Maybe the drivers need to be updated
Sent from my SCH-I500 using XDA App
Morning, I'm attempting to resolve the same issue. I have the "Yellow Shovel" Andy but I can't get Odin to recognize the device.
The device was fine and Odin was working last night, however I do believe I did something ridiculous last night. I tried flashing my phone with a Nexus S rom and succeeded. HOWEVER, the only buttons that are recognized are the "Home" and "Menu" soft keys.
I can boot into the 2.3 Nexus S rom but I can't get the hardware to recognize anymore.
UPDATE: I managed to get the USB to recognize. I'm not completely sure how, it just started recognizing it after fidgeting with the cable. I'm not flashing it back to stock using ODIN and the following post.
http://forum.xda-developers.com/showthread.php?t=867648
UPDATE: The link above worked. I recommend using the stock USB cable that comes with the phone. Now that it's back.. I'm curious to know what I would have to change for 2.3 to work.. hm..
Kevin Gossett said:
Does it recognize the phone at all? Maybe the drivers need to be updated
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Come to think of it I did update the drivers on my friends PC but there was an error installing drivers. He had a Windows XP 32bit device (Did install the 32bit drivers X86) Im going to try my other buddies PC he has Vista should that make a difference?
Soft Brick fixed
rolo12010 said:
Come to think of it I did update the drivers on my friends PC but there was an error installing drivers. He had a Windows XP 32bit device (Did install the 32bit drivers X86) Im going to try my other buddies PC he has Vista should that make a difference?
Click to expand...
Click to collapse
UPDATE: My buddy brought over his PC and got it restored! looking good now. We just updated the samsung drivers. restarted the machine. And it worked. Will update w/ the file he used. Thanks for the help and feedback.
Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.
Hello Guys...GretoVerno here fellow Samsung Galaxy S Vibrant Owner...
I have this phone and everytime i connect it to usb i Get the Message
"USB Device Not Recognized" error message...I have installed all the drivers i could possible find on the internet and the error still pops up...i ahve tried using the phone in USB Debugging mode to no avail what so ever...
Someone Please help if there's a genius out there...I really love this phone
Uninstall the Samsung drivers off your computer. Then reinstall make sure that have the correct version windows 32 bit or 64 bit for the correct operating format. Make sure you give admin rights to it. you can find these drivers in the Noob bible by S15274N in the Gen section. I am assuming there is not a problem with your phone. If you have a friend, check it on their computer, that's an easy way to rule out phone issues. That should resolve what ever problem you have.
There ia another way to check, that is have a friend with odin (or you) and see if Odin recognizes, if it does, then you got it solved or at the very least Odin back to stock and reinstall a new rom, this will solve all these issues as well.
Hope you get it, good luck
Had an issue with my brother in laws comp not recognizing his vibrant. Took an hour or two to get his phone recognized. I think we ended up using the drivers from pdanet instead of the official danny drivers. First try getting your phone to work on another comp. Will help narrow down the issue by 50%
Sent from my SGH-T959 using XDA App
Windows cannot recognize my vibrant!
Hopefully someone can help me out as I am having the
same problem with my computer not recognizing my phone.
The thing is that I am already running Froyo stock 2.2
and at the time I was able to update it to 2.2 my
computer recognized my phone without a problem. I have
been reading the forums for a while now and the only
time anyone had this problem was when they first bought
the phone when it was released but here is my problem.
After updating Kies mini and installing the official
Samsung drivers from the Samsung website I plug in the
phone and i get the error that windows does not
recognize the device. I have tried this on Windows Xp
and Windows 7 on 2 different laptops and got the same
error everytime. So what I did was while on Windows Xp I
uninstalled the unknown driver and I kept plugging and
unplugging the phone and uninstalling the unknown driver
until I got my computer to finally recognize my phone.
Once my computer recognized my phone I Then started
downloading the recent update, when the download was
done as soon as my phone went into download mode my
computer kicked out my phone and gave me the error that
windows does not recognize the device and at that time
Kies mini gave me the emergency recovery notice which I
didnt have to use because the phone booted fine without
fail.
You should also know that prior to the recent
update from tmobile for minor bug fixes I tried to root
my vibrant using the superoneclick root program. Upon
doing this after fighting with my vibrant and my laptop
to communicate with each other my computer recognized
the phone and I attempted to root. Then I got the
looping message and at that time windows did not
recognize my device which then messed up my modem and I
had to do a system restore. So after weeks of fustration
trying to root and now not able to downlaod the recent
update I am now asking for your help as XDA has been
there for us all. I have tried samsung drivers, kies mini
drivers and pdanet drivers and get the same windows
doesn't recognize my device everytime. Does anyone have
any ideas as what I can do to get my computer to
recognize my phone as I can not do anything until my
computer and my vibrant get along. Your help is greatly
appreciated XDA thanks for all that you do!
do you guys have Samsung kies installd??
Sent from my SGH-T959 using XDA App
I do and its been updated for the new update for thee recent bug fixes.
can you try a different USB chord?
Sent from my SGH-T959 using XDA App
You know that's the only thing that I haven't tried should I pick one up from T-Mobile or were should I get one?
I am getting the same error and i tried a buddy's cord and it still did the same thing. Not really sure what happened. My phone was working fine just a few days ago. I am wondering if it has anything to do with the large amount of Windows Updates that just happened.
Try uninstalling your drivers and install these. I had the same problem and then I used this and it has worked on every computer. Heck even worked when I hooked up my SGS2
http://www.multiupload.com/FUL878MTJH
I had the same issue. It is a phone problem and I had to get a warranty replacement. No combo of cables or drivers would fix mine.
Well after uninstalling and reinstalling, trying new drivers, restarting countless number of times, troubleshooting through the device manager, I had the genius idea to restart my phone in a last ditch effort before i gave up and it worked.
Now i feel somewhat like a dodo. Rule #1 - Restart
GretoVerno said:
Hello Guys...GretoVerno here fellow Samsung Galaxy S Vibrant Owner...
I have this phone and everytime i connect it to usb i Get the Message
"USB Device Not Recognized" error message...I have installed all the drivers i could possible find on the internet and the error still pops up...i ahve tried using the phone in USB Debugging mode to no avail what so ever...
Someone Please help if there's a genius out there...I really love this phone
Click to expand...
Click to collapse
Have you rebooted since you installed the drivers?
Well I tried those drivers from that link you provided and no dice. Im going to pick up a new usb cord from Tmobile tomorrow and see if that might be the problem. I can always use a 2nd cord for charging I guess.
djrysk said:
Well I tried those drivers from that link you provided and no dice. Im going to pick up a new usb cord from Tmobile tomorrow and see if that might be the problem. I can always use a 2nd cord for charging I guess.
Click to expand...
Click to collapse
That would be the logical next step.. just to verify, you have restarted the phone and computer since installing the drivers right? If you have then its most likely the cord. Its weird these cords seem to have been giving me problems more than any previously owned ones ie regular usb or even my amp cord which I step on and rip out the amp more than i'd like to admit
Sent from my SGH-T959 using XDA Premium App
Makes sure that when you uninstall your drivers to restart your PC then reinstall and give a shot. Of course, also make sure you are using the right 64x or 86x driver.
madguitarist63 said:
Try uninstalling your drivers and install these. I had the same problem and then I used this and it has worked on every computer. Heck even worked when I hooked up my SGS2
http://www.multiupload.com/FUL878MTJH
Click to expand...
Click to collapse
omg thank you! I was having the same problem! /me bows to madguitarist63 :victory:
Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?
I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?
Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..
Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.