so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
I have been trying to root my Samsung Intercept from Virgin Mobile now for a couple of days.
For the record, I am doing this under Linux, I have access to a Windows Machine but it's not mine so I do this purely under Linux.
Here are the steps I took and what happened...
Followed the tutorial on using ADB under linux to root the phone.
I pushed the kernel I wanted to flash to the correct folder, /DATA/LOCAL/TMP and then also uploaded a recovery to the same folder.
I then attempted to ./KERNEL and after it ran it displayed some weird txt in the bottom, nothing that looked good and from what I can remember the txt sad something about the partition, and it just didn't look like a good root.
I then restarted the phone, the FIRST samsung logo shows up with their website address underneath it and it stays there forever! Well at least for 5-10mins and then it goes to a black screen, it does nothing from their, I've left it run overnight on that screen and no go.
NOW, the only thing I can think of to fix my phone. I can still access download mode, and I can still get into the default recovery.. note that I don't have a custom recovery installed, because with the Intercept you need to install a kernel before the recovery.. so I never got that far because my kernel install messed up.
Anyway I tried using the recovery to wipe all data, and also wipe partition cache, still nothing good or different has come from this.
Really hoping someone can point me in the right direction.. I downloaded a STOCK VM kernel that I found on the SDX forums but it just says that the file isn't verified or doesn't match up.. something like that. Either way I have found no good UPDATE.ZIP to help bring my phone back.
I have also tried using the SWUPGRADE method on my friends Windows XP SP3 computer and it just won't recognized my phone. I tried everything, picking new USB ports in the back, I tried unplugging and plugging the USB in and out at different times. All Windows tells me is that "The usb device is not recognized" so I don't know where to go with this.
I really hope someone can help, I only had the phone for 4-5 days and I don't think I have my receipt anymore, hopefully I can find it cause this isn't looking very good.
I'd perfer a way to fix this on Linux but I can use Windows if I have to.
Hopefully someone knows the answer.. I saw a guy on SDX who had the same problem but no one had a fix for him...
I bricked a brand new verizon galaxy tab! It isn't even mine. it's my brothers and he's going to be pissed if i can't fix it
here is what i did:
i rooted it using z4root from this post: http://forum.xda-developers.com/showthread.php?t=833953
no problems.
then i downloaded sgs kernel flasher from the market and flashed this file http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.zImage
which i got from this post: http://forum.xda-developers.com/showthread.php?t=941781
it auto re-booted when done and is now stuck on samsung logo forever! **** me! i can't reboot into recovery, but i can reboot into download mode.
only problem is i have an old mac ibook running osx 10.4 which is too old for hemidall and too mac for odin. for christs sake i can't even get bootcamp or parallels to work on that old of a mac so i can run windows and thus odin.
what can i do? i'd really like to fix this without having to ask my brother to use his newer mac that should let me run hemidall, cause if i bricked his tab he ain't gonna want me touching his computer.
any suggestions? pleeeeeeease
Get rid of your ****ty mac and get a windows based PC/laptop instead obviously, then flash using odin etc.
Also use the search function, there is an endless amount of topics on this exact issue so no need to create a new one just because you are scared your bro is gunna kick your arse.
Oh btw, your device isnt "bricked", I wish people would not use that term so loosely.
You're gonna have to beg, borrow, buy, or otherwise get yourself a machine that'll run Heimdall... don't think there's any other way around it...
Once you do that, do this: http://forum.xda-developers.com/showthread.php?t=967175
crisis averted
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
tkirkable said:
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
Click to expand...
Click to collapse
Good to hear you solved the problem. Just out of curiosity what happened when you tried to run Heimdall on your mac? Theoretically the universal binaries I redistribute should run on 10.4+ with any processors architecture supported by OS X (i.e. x86, AMD64 and PPC).
Heimdall requires osx 10.5?
Apparently. That's what it says when i try to open the .pkg file. it says this package type requires osx 10.5 I can run it in windows 7 though. I had to three times yesterday cause i kept soft bricking my device if that's the right way to put it. read read read. i must be missing something. I had clockworkmod recovery and ext. 4 for a second but then froze on the samsung logo at reboot again. had to heimdall my way back and lost it all. back to the drawing board
recently went to linux mint 16 os. something ive found is i cant get any samsung drivers to work. ive tried using wine as well but i get an error message about halfway through installation. any advice? im looking to re root and probably flash the leak (im on 4.3) ive been looking around in the linus forums for quite a while and no success so i figured maybe an android dev site would have some advice. thanks
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.