Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Im Hoping someone out thier can Help me. I have a Evo 4G and tried using Revolutionary to S-Off. Unfortunatly I Get stuck on "Waiting for Device..." I made sure phone connects to cpu with charge only and Debugging on, Three Different usb cords, Disabled Firewalls, Downloaded Revolutionary several Times, Used one other cpu, and removed battery and still Nothing all with the same Result of "Waiting for Device..." Im at a dead end. Can anyone help?
Try to download "PDAnet" from Google for windows. It will automatically install those drivers you required... this app solved my problem in my nexus s.
Accidentally sent from my Nexus S using XDA Premium App
melvinchng said:
Try to download "PDAnet" from Google for windows. It will automatically install those drivers you required... this app solved my problem in my nexus s.
Accidentally sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Just tried using the pdanet and drivers connected, but still Nothing and still get stuck on "Waiting for Device..." I also tried other usb ports and still nothing.
Okay I have search XDA and LG AND google search for this problem and have not found any solution to what I'm going through. Here's a little background on my phone
T-Mobile G2x rooted with the ROM HellFire Phoenix V2.1
Before today I was able to mount my SD card to my computer with no problem seeing I've had the phone since it came out. Today my computer showed it was installing the drivers but gave me a message "device drive was not successfully installed...usb composite device failed. Now I have used different usb ports and different usb cables and my computer is STILL giving me the same message!
I have even uninstalled the drivers and reinstalled them and still coming up with the same issue. I even restarted my computer after each and I keep coming to the same issue. Can someone please give me a solution to this frustrating problem? It would be greatly appreciated!
Same exact issue except on 2.2
I think you mean HFP, hfs is only up to 1.7
Sent from my LG-P999 using XDA
What about USB debugging is it checked? try the opposite of what it is with a reboot, also link where the drivers are being downloaded from.
Sent from my LG-P999 using xda premium
mt3g said:
What about USB debugging is it checked? try the opposite of what it is with a reboot, also link where the drivers are being downloaded from.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah I made sure USB debugging is indeed checked, and when you say try the opposite meaning what? uncheck debugging...reboot then check it again?
The drivers are being downloaded from the LG Mobile Support tool program that downloads and installs the latest drivers. Which can be found here http://www.lg.com/us/support/mobile-devices/phone-support
I even posted on the LG forum as well, got a response from an employee who told me basically what I had been doing, uninstalling , restart the computer, reinstall, restart again and then connect my device and STILL the same message. I have no idea why its doing this, its never done this before unless there was a new Windows update or something but there hasn't been. Oh and my Windows is Vista by the way in case anyone was wondering.
I used B2CAppSetup.exe From LG. I was having the exact same issue, this solved it. I uploaded it here: http://www.mediafire.com/?e2vnaw5a0ljljj4
EDIT: Vista or Seven - make sure you right-click the .exe and Run As Administrator.
I had the same issue with HFS so I just started taking the card out of my phone and putting it directly into the computer.
I had this issue a while back after re-installing the drivers. Plug the phone in and the little systray icon would tell me the usb composite device failed.
What worked was going to the device manager and installing drivers from there, but instead of browsing to the drivers as I tried many times the solution was letting Windows choose. It popped up with two choices the generic usb composite device and the LG phone. Picked the phone and I was good to go.
Hope this helps someone and if it does please hit the thanks button.
TorrentzRock said:
I used B2CAppSetup.exe From LG. I was having the exact same issue, this solved it. I uploaded it here: http://www.mediafire.com/?e2vnaw5a0ljljj4
EDIT: Vista or Seven - make sure you right-click the .exe and Run As Administrator.
Click to expand...
Click to collapse
Thats the exact program I have been using and I still have the same issue, I'm thinking of just going back to another ROM since it seems to be an issue with HFP then I'm glad to hear I'm not the only one with this issue.
On the stock ROMs you had to set it for USB file sharing only and then actually enable file sharing once it's plugged in. I can't try anything but a stock ROM (running BB 3/2012) at the moment.
Not sure if HF is the same way.....
Antivirus
Once I had driver issues because of an overzealous Antivirus. Try uninstalling the drivers, restart, disable the antivirus, and reinstall.
I have a question for you guys, I tried restoring to a previous Hellfire ROM i backed up thinking that would work and it didn't.
So what happens if I can't get this to work? Without me being able to access my external/internal SD cards I can't load a new ROM or anything even if i wanted to unroot the phone and get another one from T-Mobile I can't or can I?
Is there any other way to restore back to factory settings without connecting to my PC? This is highly frustrating and i have NO idea why my phone and PC aren't working together like they did before in the past.
Did you run as administrator?
Sent from my SGH-T989 using xda premium
Yes i have done everything. Run as administrator, restarting my computer after every uninstall and re-install of the drivers, made sure USB debugging was checked, even restored a previous ROM i saved thru clockwork-mod and when i connect the phone through the USB to my computer i keep getting the USB composite device failed.
Nothing seems to work, so I'm thinking of just accepting that its not going to work and save up and get a new phone eventually which sucks cause since rooting the G2x I love it more than when it was stocked.
quest4fire said:
Did you run as administrator?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Sometimes switching cables help. Once i used a blackberry micro hdmi cable and had problems until i switched to a LG cable. Also running Win 7 in win xp mode helps.
Sent from my SGH-T989 using xda premium
quest4fire said:
Sometimes switching cables help. Once i used a blackberry micro hdmi cable and had problems until i switched to a LG cable. Also running Win 7 in win xp mode helps.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Tried that already still doesn't work and I'm on a Vista computer don't have access to Win 7 so suggesting that won't help at all.
Sent from my LG-P999 using XDA
Ok mshoney6, Here is your solution: (you can thank me later)
After much digging and searching, searching, searching I found this driver and I uploaded it for you. Get it HERE: http://www.mediafire.com/?ahc3iklqmoa0gnc
First, go to your control panel > add/remove programs > and uninstall ANYTHING LG! This includes the Mobile Support Tool.
Second, make sure your phone and USB cable are not connected to your pc.
Now, right-click the file you downloaded above and "Run As Administrator".
DONE! Connect your phone to the PC and Viola!
I have a galaxy s2 4g i9210t. I had kies installed and Odin worked fine for all my other phones and read this phone fine when in recovery mode or normal mode, but when I boot it into download mode Odin doesn't detect it and I get an error say failed to Install Samsung USB Cdc device driver. So my first instinct was to reinstall kies, that failed so I tried just installing the drivers on their own, that also failed. I then tried it all on another computer, that failed. I've also tried 5 different cables all of which work for my other phones. Can anyone help?
Sent from my GT-I9210T using xda premium
First you have to manage to install drivers...
Until you can not install drivers successfully it will not detect your device..
Are you using window 7?
Because it automatically detects and installs drivers.
we all should be polite enough to press thanks for anyone who helped US.
shivam1688 said:
First you have to manage to install drivers...
Until you can not install drivers successfully it will not detect your device..
Are you using window 7?
Because it automatically detects and installs drivers.
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Yeah windows 7
Sent from my GT-I9210T using xda premium
Try to start Odin in Compatibility Mode!
As in just right click properties compatibility?
Sent from my GT-I9210T using xda premium
No go on compatibility mode. I don't think it's a problem with Odin reading it I think it's a problem with windows installing the drivers as I get the failed to installs driver error every time.
Sent from my GT-I9210T using xda premium
maybe you can change another usb. i also experienced odin problem before. after i changed another usb the problem was gone...
sorry for my english...
rainbow9 said:
maybe you can change another usb. i also experienced odin problem before. after i changed another usb the problem was gone...
sorry for my english...
Click to expand...
Click to collapse
Tried that
Sent from my GT-I9210T using xda premium
download mode
You need to get your phones USB system drivers installed or it is not going to find your phone no matter how many cables you use. You need to get the drivers that are there off and get a good clean install done. Find the right drivers "Samsung" windows for your flavor OS and install them on the computer. It should work fine then.
- txpigkiller -
Well it's stock at the moment so I'm using kies for the drivers or the driver pack. But I'm trying more clean installs now.
Sent from my GT-I9210T using xda premium
Wow. So uninstalled kies again restarted, reinstalled. Now whenever I plug my phone in whilst in download mode it blue screens my.computer after 3 mins of trying to installs the driver. Wtf
Sent from my GT-I9210T using xda premium
Fedelrick said:
Wow. So uninstalled kies again restarted, reinstalled. Now whenever I plug my phone in whilst in download mode it blue screens my.computer after 3 mins of trying to installs the driver. Wtf
Sent from my GT-I9210T using xda premium
Click to expand...
Click to collapse
Do you have acces to another pc My pc would never work with odin. I had to use my wife. I never figured out what the issues was but try different pc if possible.
I'll try another PC today, the problem is I only have access to an old one but I'll try
Sent from my GT-I9210T using xda premium
No go. I even tried to do it on a friends PC who just flashed his s2 perfectly and it still says failed to installs driver. (at least it didn't blue screen his PC!!)... This has made me think that it may be an issue with the phone itself
Sent from my GT-I9210T using xda premium
I had my phone in download mode and tried it in 2 USB Ports. That's the errors I get. I then restarted it into normal mode and you can see all the drivers installing fine. Also when turned off my computer says that the device has malfunctioned??
Sent from my GT-I9210T using xda premium
Why odin never detect my ace+ in any mode???
hi, i'm new to this forum and i'm realy want to root my ace+ but odin never detect it. What should i do? and i'm still just a junior high school student and know nothing about all this i just wanna get my phone rooted! so please explain it specificly i promise that i would thank anyone that explain me. oh, one more thing, i'm from indonesia and i'm not good in english
Fedelrick said:
I had my phone in download mode and tried it in 2 USB Ports. That's the errors I get. I then restarted it into normal mode and you can see all the drivers installing fine. Also when turned off my computer says that the device has malfunctioned??
Sent from my GT-I9210T using xda premium
Click to expand...
Click to collapse
UNINSTALL KIES completely. Don't reinstall it! Use this DRIVERS.
Happy flashing
I got the same problem yesterday. I want to flash a CustomROM but Odin will not find my Galaxy S3. I had no Kies installed and had try every USB-Port I had, nothing work. Anyone has a idea for me to get Odin working for my S3?
Merith said:
I got the same problem yesterday. I want to flash a CustomROM but Odin will not find my Galaxy S3. I had no Kies installed and had try every USB-Port I had, nothing work. Anyone has a idea for me to get Odin working for my S3?
Click to expand...
Click to collapse
Which Windows / ODIN version?
Odin 3.09 with Windows 8.1 Update 1. USB driver are correct because I can access the memory of my S3. Only Odin won't worum.
Sent from my GT-I9300 using XDA Free mobile app
Okay, so this is a new one to me, I installed TWRP Recovery after formatting System, Boot, Recovery, and Modem. I successfully reinstalled everything using a combo of fastboot and TWRP, but now my device is acting, well, weird. My system loads, but only after I open the bootloader and choose the "Normal Startup" option. Everytime I power down, it shuts off and loads into fastboot. I then need to open the bootloader and choose the above stated option to load my OS. What the heck, all I want to do is be able to UPDATE so I can participate in the JB Soak Test...has anyone come across this issue? Need some Dev Love right about now, I'm relatively new to this.
Reflash stock FXZ.
mrvek said:
Reflash stock FXZ.
Click to expand...
Click to collapse
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
galacticservant said:
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yeah, I just installed a driver cleaner. Then I disabled the auto driver updater that windows has. Next I'll reinstall Moto device Manager and RSD Lite. The one driver that does not install is the Moto Networking Interface, which I believe is the culprit here if I'm not mistaken.
Sent from my XT897 using xda app-developers app
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas?
Sent from my XT897 using xda app-developers app
galacticservant said:
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas? I even progressively went through and installed every version of RSD all the way back to version 5.7.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Sorry for the double post
Sent from my XT897 using xda app-developers app
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
kabaldan said:
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
Click to expand...
Click to collapse
I will definitely try that...thanks
Sent from my XT897 using xda app-developers app
mrvek said:
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
Click to expand...
Click to collapse
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
galacticservant said:
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
mrvek said:
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
Click to expand...
Click to collapse
Hind sight.....
Sent from my XT897 using xda app-developers app
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
galacticservant said:
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
(I followed the .xml script contained in the SBF and manually erased and flashed my entire system. Forgot the above referenced line though and my system was locked going to sticky-bit factory fastboot. There is a command line "moto-fastboot oem fb_mode_set" which I believe RSD uses to make the device reboot into fastboot after partitioning and such (.mbn?). Anyway, I'm still learning so cut me some slack. Everybody has to start somewhere, right?
Sent from my XT897 using xda premium