Related
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.
Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?
I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.
Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?
Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????
Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.
Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.
When my phone is just sitting in bootloader, it is not recognized by adb devices.
You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.
gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.
Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore
Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly
Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?
Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.
Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.
Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
Hi, I was going to setup adb on my froyo MT4G, but I didn't...now I am trying to setup fastboot and ADB on my computer, but I can't figure it out. It seems like guides are written for android 2.2 when it comes to the MT4G and ADB. I have cm7 on my phone, so how do I setup ADB for it? I am trying to find it, but I don't know enough to know what would work, have tried certain guides, but once I get to a point where there is a disclaimer I tend to shy away since, I am not sure what guide I should be following for my weird situation and trying to setup adb for it..Please, thank you.
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Hmmm might be awhile before I can try this but I will
jbrew78 said:
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
Honestly, I think your long term fix is ubuntu. A lot of people don't want to hear that, but it's easier than you think. You can run a dual boot, or set up a virtual machine on your current computer. You can download vmware here:
http://www.vmware.com/products/player/
And ubuntu here:
http://www.ubuntu.com/desktop/get-ubuntu/download
Then install adb, fastboot, etc. and never have any driver issues again. Problem solved.
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Thank you. I am downloading the sdk files right now, I wish I had a computer so I could read more about developing and stuff...right now I just have to use my GFs when im over here, but I have to avoid things once I start getting interested otherwise I will be sucked into an abyss of knowledge for hours, and snap out of it, and then have to figure out why she is mad at me, hahhaha... so I have a generic question though... is fastboot basically like terminal? And you can get into it from hboot right? Don't need to have your computer connected to it or anything right?
foxdl99 said:
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Click to expand...
Click to collapse
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
foxdl99 said:
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
Click to expand...
Click to collapse
Wait so I have to connect my phone to my computer to use fastboot cmds on my phone?
So if I have fastboot setup, and I am walking around with my phone in my pocket and I pull it out and check xda and see a new splash screen I want. I can reboot into bootloader, and then enter fastboot and type some kind of command like.. fastboot splash3 google.img and that will work? Or your saying I have to have it plugged into the computer?...because if that is the case then whats the difference between ADB and fastboot?
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
I have root explorer... hmm I guess I have been missing what fastboot is all about... well maybe ill just get it all setup and play with it to figure it out.. thanks for your help I'm going to sleep for now.
foxdl99 said:
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
i downloaded toolkit and unlocked my phone , rooted it i installed chainfire 3d and now its stuck on the nexus logo
i tried to unroot it but when i connect it and open the toolkit it says that there is no adb connection so what the **** is that ?? so i relocked it and tried to root it again but its still telling me that there is no adb connection so i found out that i can fix this by going to settings/devloper/the check the bugging usb but the problem is i cant boot in this ****ty device :S
and i installed the nexus driver on pc
but really i dont know what should i do :S:S
i swear that i will never root my nexus again
please big help
Re: help again :S
If you do not know what ADB is then you really have no business rooting any android device.
ADB stands for android debugging bridge. You need to install this on your PC before f##%%*g about with your device. Google how to install Android SDK (which includes ADB). There are plenty of threads on XDA.
And the thread title should be something more descriptive than 'help again' in order that someone who actually respects this forum by searching first will find threads with the same issue.
killall said:
If you do not know what ADB is then you really have no business rooting any android device.
ADB stands for android debugging bridge. You need to install this on your PC before f##%%*g about with your device. Google how to install Android SDK (which includes ADB). There are plenty of threads on XDA.
Click to expand...
Click to collapse
hey my friend i did what u told about the SDK but when i open toolkit its says "daemon not running. starting it now on port 5037" then it says " ADB server didnt ACK " then "failed to start daemon " what should i do :S ????
Check that your usb drivers are correctly installed. Look at the FAQ in Nexus Toolkit thread.
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
parakalien said:
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
Click to expand...
Click to collapse
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
newellj79 said:
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thank you very much!! This fixed it and was super easy.
Appreciate your help getting me out of a sticky situation!