Related
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
I just got a captivate and i tried to put the phone in download mode to flash a new rom...no luck i tried the two and three button method...no luck. I also tried putting the phone in dl mode by using a command prompt...is there someone out there than can help a noob?
May need to give us some more specifics. I have only been able to get into download mode using the adb method. It may take you some time to get the drivers and everything communicating properly. Google and forum search are your friend.
1) Install the Android SDK.
http://developer.android.com/sdk/index.html
Not sure if it's required, but I also have the android adb driver installed.
http://developer.android.com/sdk/win-usb.html
2) Install the Samsung USB driver. Usually found at the link below, but they took the downloads down for some reason. (Is Samsung about to release an update?)
http://www.samsung.com/us/support/downloads/SGH-I897ZKAATT
3) Enable USB debugging on phone and plug it in.
4) Navigate to your ../android-sdk-windows/tools/ directory in a command prompt.
5) Type "adb devices" without quotes and press enter. Should see your device listed.
6) Type "adb reboot download" without quotes. Good to go.
Try this... turn your phone off... turn on ODIN in PC... while holding BOTH volume buttons plug in the USB... you should be in download mode
My suggestion is to wait. Do a couple checks before you BRICK your phone. Check this thread for info, http://forum.xda-developers.com/showthread.php?t=784147
There is a wave of phones out now that have 2 or 3 button modes disabled, broken, or something, but they don't work and have caused hard bricks. Most have had to return their phones.
when i try to search for sdk through the command prompt thats in windows it keep saying it not recognized as a internal or external command...now what?
chevy454 said:
when i try to search for sdk through the command prompt thats in windows it keep saying it not recognized as a internal or external command...now what?
Click to expand...
Click to collapse
If you are brave enough to try, then here.
Download the SDK from google. Once done, you can upzip it and buried in there is a folder called Tools. I usually take that folder and copy it to the root of my C: on my pc. So it's, C:\tools.
Plug in your phone, make sure USB debugging is on. Open a cmd windows and cd C:\tools
Now in your command window you should be able to use ADB. adb reboot recovery, adb reboot download, adb shell, etc.
Again, I would verify 100% that my button method for recovery and download work before you start modding. If you soft brick your phone, and your buttons don't work, you are screwed. If buttons work you can recover from a soft brick. I have soft bricked my phone numerous times, I have never been able to get ADB to work, I ALWAYS have to use the buttons to get into download mode.
Can I put the phone in recovery mode using clockworkmod? It doess have to be download mode NOT recovery mode right?
Recovery mode is for installing update.zip files and wiping user data. Download mode is for flashing roms using Odin.
Moved to Q&A as this is not a development question.
chevy454 said:
I just got a captivate and i tried to put the phone in download mode to flash a new rom...no luck i tried the two and three button method...no luck. I also tried putting the phone in dl mode by using a command prompt...is there someone out there than can help a noob?
Click to expand...
Click to collapse
if you are rooted then you can do the latter.
Have you gotten ADB to work?
The latest OTA updates fixes the issue with 3 button combos
Once you install the update, reboot, then try to get into recovery or download modes. Should be fine after the update
i just got my phone back after cracking the screen but i still cant get adb to work and i cant install clockworkmod because it will not let me connect to the server
Odin Flash fail. Bricked my SGS , getting phone-!-pc. Can get into Download mode, ODIN /Windows/kies will not recognize it. reinstalled kies multiple times, still wont work/recognise. Objective is to go back to stock which is I9000DTJP5. ideas? device is consistently shown to "USB device unrecognizable"
SOLVED.
if any others have this issue, see if you can get windows to recognise your phone in download mode as a Modem. Windows 7 recognised my Galaxy S in download mode as a CDMA modem and odin worked a charmed afterwards
did you click "install drivers" in ODIN
there's an option for that? which version of odin would that be in?
lol sorry, my mistake.
i meant to say in KIES, there is an option to re-install drivers.
if that does not work, try downloading the drivers found here somewhere, forgot where though sorry.
also, try rebooting into download mode with the USB connected using ADB
how would i use ADB? sorry but ive always been lost concerning that bit
Also, using kies two and the install drivers gave me some korean writing... 0_o
download ADB from some where ( i recomend just the ADB not the whole suite, it can be found here somewhere, im bout to have dinner so will have a look after )
after you grab that, tell me and i will help you from there
basically, you navigate to the ADB folder, for example. if its on C drive in georges download folder you go into CMD and go.
cd C:/ <<< to get to the C drive, ( or what ever drive its stored on )
then cd C:/users/george/downloads/
then you would go, adb reboot download
EDIT: not sure why you got korean writing lol.
it should say something along the lines of " you cannot use other KIES widgets when you are about to install drivers" or something like that.
ok , i got ADB, got it semi working , the ADB i mean but the downside is that even in download mode, ADB cant recognize my device
Hey guys,
For some reason, my Windows 7 32bit laptop is not recognizing the Galaxy tab at all when in download mode. I have installed kies (which incidentally also doesn't recognize the tab), and installed the individual drivers, but cannot get my computer to even see the Tab.
When the Tab is in normal mode (debugging turned off), I can mount the Tab as a drive and it has no problems.
Has anybody else run into this issue? The Tab is not showing up in the device manager at all. I do have root, and my end desire is to connect with Heimdall, and continue to get the error message "Failed to detect compatible device."
Any help would be greatly appreciated.
Seth
Download and install drivers for your tab. Samsung website should have them, if not they shouldn't be too hard to find.
drivers
Hi,
Already tried that. Kies doesn't recognize the device at all (with USB debugging active and not active both), and the Device Manager doesn't show anything either. When I plug the tab in, it recognizes that it is connected, but mounting the SD card as a drive doesn't do anything either.
The worst part about it is that I'm not sure that I can even revert to stock without being able to get Heimdall working. I've searched a ton, and it seems to be the key to just about everything. Any other ideas?
Seth
have you tried to install the drivers that come with Heimdall? I've had to force install those a couple times to get my Tab recognized in download mode.
Heimdall drivers
pvtjoker42,
Can you explain a little about what you mean? I am running Heimdall 1.1.1 have done the following:
1. Browse from the main folder to the "Drivers" folder and run zadig as an Administrator.
2. Click on "Options" and select "List all devices"
3. Click on the dropdown menu and search for anything that might be related to Samsung Galaxy Tab or Android of which there are none.
Is there a different way to force the install of the Heimdall drivers that I'm unaware of?
Thanks for your help,
Seth
when you drop down the list of devices what all is listed? I've had it show up as just a serial device before, with no mention of samsung/tab/galaxy etc..
Devices
Cisco VT Camera II (Interface 0)
Cisco Microphone (VT Camera II) (Interface 2)
USB Receiver (Interface 0)
USB Receiver (Interface 1)
USB-Serial Controller D
Fingerprint Sensor
Optical Drive Controller
TOSHIBA Web Camera (Interface 0)
USB Multimedia Audio Device (Interface 0)
USB Multimedia Audio Device (Interface 3)
Those same entries can be found in Device Manager>Universal Serial Bus controllers even on first boot if the Tab is not connected. Even after connecting the Tab, this list does not change.
Thanks again for your help!
Seth
have you tried uninstalling everything related to the tab? Kies, the specific drivers etc, then trying the Heimdall drivers?
So all the devices listed above are there when the Tab isn't even plugged in? Odd.. I would have suggested trying it for the USB-Serial Controller D, but if it's there without the Tab plugged in it sound like a different system device.
Don't suppose you have access to a different pc to try it on? see if it even notices the Tab being plugged in and tries to install drivers..
Yeah, I have other computers to try. Tried plugging it in yesterday to a different computer (same brand and model) with no change. Computer didn't recognize the device at all and/or try to install drivers.
Usually when an unknown device is plugged into a computer, the computer registers that it's there - the Device Manager shows an "Unknown Device" somewhere in the list, but this isn't the case with this device. Not sure what happened, but it appears as though I goofed up the USB somehow in the rooting process or the port itself went bad.
I'll try other computers and write back.
Thanks again,
Seth
I've tried three different computers with the same outcome. They do not register the device at all, and I cannot mount the SD card to the computer. I'm definitely at a bit of a loss at this point. Without USB, I'm not sure how else to make this happen. Ideas?
Seth
Just to double check with hemidall ur opening the drivers folder and running zadig.exe in there going to options>list all devices
Yes, that is correct. I'm opening the Heimdall 1.1.1 folder, opening the drivers folder, and running zadig. Nothing pops up at all and nothing shows up in the device manager.
I cannot mount the SD card to my computer, but the Tab recognizes it when I plug it into the computer's USB port. That's as far as I can get, however, as the computer does not see the Tab at all.
Have you tried 'fix permisions' in recovery mode - usually under the advanced option?
Sent from my GT-P1000 using XDA App
There is no "Fix permissions" in this recovery mode. Tried to fix permissions from cwr (which only went through 2 lines), but it doesn't seem to make any difference. Still force closes Gallery when I try to mount the SD card. Also force closes gallery when I try to open gallery.
This is very strange. It continues to tell me that there is an update available. I might go ahead and take it to see if it takes me back to stock. I would be okay with this as long as I had USB connectivity again and could root.
Any other thoughts?
Seth
P.S. Tried to take the update, but it gets about 1/3 of the way through the install and fails.
Any other ideas on how to flash without Heimdall?
Seth, what about trying Odin3 and its drivers?
Sent from my GT-P1000 using XDA App
I'll look around and find Odin3 and give it a shot. I'm concerned that because my computer doesn't recognize it as a connected USB device, that no program will see it either. That said, it's worth the shot and I appreciate the suggestion.
Do you know whether I can use the same files for Odin that I would use with Heimdall? Do they need to be packaged differently?
Thanks in advance,
Seth
If you have GSM based tab you can try flashing Team Overcome's Kratos ROM (I had no issues with download mode following their excellent ROM flashing instruction here http://p1000.teamovercome.net/?page_id=64 ) which involves download mode + using Odin, which displayed that it's connected to a tab through a serial port emulation. At least you can confirm if your tab's download mode is working. I'm using Win 7 Home Premium 64 btw.
I downloaded Odin 3, but without knowing if I am able to flash a package designed for Heimdall, I'm not sure what Odin 3 would tell me. Thoughts? Can I use Odin3 to transfer one of the Heimdall-specific ROMs to the Tab?
I had this same problem some weeks back. I had to use the drivers that came with Heimdall, and most importantly, in order to get it to recognize in download mode, I had to install them while in download mode and plugged in.
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
bump
Did you solved it? I have the same problem
Sunaj1 said:
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
Click to expand...
Click to collapse
because flashing twrp.... phone doesnt have to be in download mode..
you turn on phone plug usb. then install minmal adb
copy twrp file into adb folder/ keep pressed SHIFT KEY on empty space in minimal adb.. then right click mouse
then select start command prompt here.
then send command you should see a message on phone .. turn on screen. select ok. then again send command
the twrp files both one in sd card and in minimal adb and the command should be named the same for twrp. example twrp.v.1.1.3 the command has to be the same .. just edit command or both or rename twrp the twrp file.