Related
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse
devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3
Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app
Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!
This must be in Fastboot USB mode while doing?
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.
Just tried that and its still stuck... I'll mess with it more tomorrow
Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.
I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?
Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP
Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.
I managed to get S-Off even though it never said complete at the end. I used the alpharevx. Somehow I kept trying it and even though it never said completed, I now have the Alpharevx bootloader.
I tried to install clockworkmod since I don't have it, and I did this in linux(ubuntu). I downloaded the fastboot files and the image. Ran terminal and ran
fastboot devices while my phone is in fastboot usb mode. I get "command not found." I try to flash the image too and I get the same error.
Is there a step i skipped?
How are you running your command?
Well i run sudo /home/selayan/android-linux-tools/fastboot flash recovery <recoveryimagename.img>
I also went as far as installing the android sdk and adb in linux and it still will not work.
selayan said:
Well i run sudo /home/selayan/android-linux-tools/fastboot flash recovery <recoveryimagename.img>
I also went as far as installing the android sdk and adb in linux and it still will not work.
Click to expand...
Click to collapse
All of the procedures I have seen show that you should run sudo in the same directory as fastboot and the recovery image are in:
sudo ./fastboot flash recovery recoveryimagename.img
The problem is alpharevx did not install ClockworkMod for me so I need to do it manually. In this case I have to install JDK, and anddroid SDK plus ADB too I think in order to get everything working. I saw a post on how to flash CWM manually but it was for windows not linux.
selayan said:
The problem is alpharevx did not install ClockworkMod for me so I need to do it manually. In this case I have to install JDK, and anddroid SDK plus ADB too I think in order to get everything working. I saw a post on how to flash CWM manually but it was for windows not linux.
Click to expand...
Click to collapse
If you can do it via Windows, you only need four files: adb.exe, AdbWinApi.dll, cwm-recovery-vivow.img, fastboot.exe.
That was all I used when I did it last night. Yeah, I went through the hassle of installing the JDK and SDK for Android, but it probably wasn't necessary. You can pull the first two files from the temp root download, and they'll probably work fine.
Well I'm on a macbook pro so I need to do it on Linux, I could try running windows 7 in vmware and just doing it that way, but I think since I have linux set up, it would be easier to do it that way. I hope it works, I will reinstall ubuntu, and then go through the android sdk install instructions.
This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
robopilot99 said:
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
Click to expand...
Click to collapse
I had the same issue. Tried it on windows (though I hate windows ) and it worked on windows. I am STILL trying to figure out how and why?
I had the same problem on Ubuntu 15.04, and I fixed it by uninstalling the outdated version of fastboot in Ubuntu's repositories and replacing it with the binary from the Android SDK platform tools.
The fastboot protocol may have changed slightly with Lollipop, and Ubuntu's fastboot and ADB packages say they're from 4.2. Remember to run fastboot as root unless you have the udev rules set up. Hope that helps!
yes i had a similar issue on ubuntu with the repo version. I actually got an error message saying i needed a newer version
Thanks. Using the version I got from the internet worked fine. I'm now getting and error about fingerprinting and stuff. Looks uke I'll have to wait for a way to unlock the bootloader on the latest version.
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
bhoth said:
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
Click to expand...
Click to collapse
You will want the Android SDK tools. Here is the download page:
https://developer.android.com/sdk/index.html#Other
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
joel.maxuel said:
You will want the Android SDK tools. Here is the download page:
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
Click to expand...
Click to collapse
yeah that's what I ended up doing. It's a pain to find it in the huge download but it's kinda your only option.
im currently on the same problems as you too.. cant use fastboot on ubuntu 14.04 lts.. but i found this article online, didnt test it yet since im on my windows right now to use fastboot.. who knows this may help in updating to latest adb bin..
http://bernaerts.dyndns.org/linux/74-ubuntu/328-ubuntu-trusty-android-adb-fastboot-qtadb
Click to expand...
Click to collapse
wait i was wrong, the cmd there is to update adb to latest version and not for fastboot.. cant help anyway, unless download the whole android sdk as mentioned above..
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Edit: for some reason sudo -s finalize_device device/nextbit/ether worked but have some other issues with building efi droid.
AnierinB said:
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Click to expand...
Click to collapse
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
VenomMOD said:
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
Click to expand...
Click to collapse
Darn it.. it's been getting to me for a few days now and I even got lk.img to boot and configured so alls that needs to be done is the finalize_device and then off to compiling uefi. Oh well, at least I got that close :crying:
Windows it works without it but cant compile jack on that xD
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
bback78901 said:
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
Click to expand...
Click to collapse
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
AnierinB said:
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
Click to expand...
Click to collapse
Forgot to add, I only use it on Windows 10.
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
valhallen.282 said:
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
Click to expand...
Click to collapse
Got it to bypass needing -i 0x2c3f just by typing sudo -s before my fastboot cmd.
Try it