Develop Bugs

exec 'system/bin/sh' failed no such file or directory (2)

Hello,
I'm very new at this rooting stuff and I saw a lot of benefits from it so I thought I'd give it a try.
I've followed this root guide on MoDaCo, but I can't post a link here.
I also did the custom recovery image part (although I don't know what it is used for)
And I didn't make a goldcar either because someone told me I didn't have to do that as I don't have a carrier.
But my problem is I can't change anything as cmd keeps giving this error when I enter adb shell:
- exec ' system bin sh' failed no such file or directory (2)
I'm in my phone recovery and my usb cable is plugged in. This is the what I do and what it says:
C:\androidsdk\tools>adb shell mount /system
- exec ' system bin sh' failed no such file or directory (2) -
C:\androidsdk\tools>adb pull /system/usr/keylayout/bravo-keypad.kl c:\
remote object '/system/usr/keylayout/bravo-keypad.kl' does not exist
Any help is very welcomed as I've been searching the net for quite a while.

I'm not 100% sure what you are trying to achieve here. Are you trying to root, or have you already rooted?

socktug said:
I'm not 100% sure what you are trying to achieve here. Are you trying to root, or have you already rooted?
Click to expand...
Click to collapse
Sorry for being unclear. I've already rooted.

OK, and are you looking to remap the hardware keys?
As far as the goldcard goes, you don't need it if you rooted without one.

socktug said:
OK, and are you looking to remap the hardware keys?
As far as the goldcard goes, you don't need it if you rooted without one.
Click to expand...
Click to collapse
Yes that is correct, but when I enter adb shell it gives the error given above.
I don't think it's supposed to give that error.

Take a look HERE it might be of help.

socktug said:
Take a look HERE it might be of help.
Click to expand...
Click to collapse
Yes, that's the post I used to try it.
But it seems I can't pull the file. It says the file doesnt exist.

I'm not really up to speed with adb commands etc. I'd maybe try posting this in the dev section. Or chuck a post in there pointing to this one.
Sorry I can't help you more.

socktug said:
I'm not really up to speed with adb commands etc. I'd maybe try posting this in the dev section. Or chuck a post in there pointing to this one.
Sorry I can't help you more.
Click to expand...
Click to collapse
Ok, will do, thanks for the help!

I think I've found my problem. I've installed the app: rom manager and I can get into the custom recovery from there.
It seems I was uncapable of going in the custom recovery myself (probably because I'm doing something wrong). But I'd still like to know what I did wrong.

If you've got rom manager installed, flash into clockwork recovery and go to the partitions menu and mount system then re-do you adb commands.
There's also a fake-flash that provides an update.zip to boot you in recovery mode.
Sent from my HTC Desire using XDA App

dnlgee said:
If you've got rom manager installed, flash into clockwork recovery and go to the partitions menu and mount system then re-do you adb commands.
There's also a fake-flash that provides an update.zip to boot you in recovery mode.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Yes I've installed that fake flash, but I thought after installing it in the normal recovery it would take me directly to the custom recovery. Instead it just said the installation is complete without going to the custom recovery.

Everytime I want recovery mode I just load up rom manager and click reboot into recovery. However I find I can't mount my system directory through advanced cmd itself so have to mount through the partitions menu in clockwork.
Sorry of this doesn't help, I don't fully understand the issue..
Sent from my HTC Desire using XDA App

A little help needed, Am I still rooted?

I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.

travazz said:
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
Click to expand...
Click to collapse
easiest way to know if you are still rooted is to download android terminal emulator from the market and type in su on the screen... if you get a # sign then you have root... if you get permission denied then you don't.
find that out first then we can answer the other questions.

Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it

travazz said:
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
Click to expand...
Click to collapse
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.

viccyran said:
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
Click to expand...
Click to collapse
Where do I get the custom recovery file and how do I install it/use it?
Sorry that these are really dumb questions, but now that I know I still have root, this is getting exciting again.

See the stickied thread recovery reflash tool.
-------------------------------------
Sent via the XDA Tapatalk App

Now I'm trying to follow the recovery steps and I'm having the following errors. Can anyone please help?
When I try to install the modified USB drivers I receive the following errors:
Error 0x80004005: Unspecified error on these specific dll files.
WdfCoInstaller01007.dll
WUDFUpdate_01007.dll
WUDFUpdate_01007.dll
When I go to install the reflash-bundle, everything installs, but it fails installing the reflash.exe saying that the file is corrupt.
I'm using Windows 7 Ultimate x64, if that helps out

This is a development sub-forum. Please post your questions in the General section. Thanks.

where do i put a file i want fastboot to see

I have no idea where to put the new ra-evo recovery file so that fastboot sees it. I have looked sorry for the stupid question

your fast boot should be installed in ur android sdk tools folders so if thats where ur fast boot is then put the file in the tools folder

Fastboot flashes files from your computer not on the sdcard or anything.
Ex. Fastboot flash recovery /User/downloads/recovery.img
Sent from my PC36100 using XDA App

i am so confused
so if I am rooted and unlocked and I already have the original amon recovery i just put the new amon recovery in the tools folder. then how do I get it on my phone

if you already rooted you should have android sdk installed
easyest way
go to start
my computer
c drive or your main drive
android sdk or sdk (wat ever you named it)
tools folder
put recovery in tools forder
open a command prompt and
cd \android-sdk
cd tools
now your in the tools folder
fastboot flash recovery /recovery.img
it is easyer and faster no searching for the files if you put the recovery in the tools folder its already there no going to filesfoldersdownloads you dont need them commands its faster and easy look through the adb and sdk guides it has all commands and most recover forums tell you all this

so i need to change the name of the amon recovery image to recovery.img

No he was just using recovery.img as a example.
Sent from my PC36100 using XDA App

Here's how i did it this morning, downloaded file to pc, connect phone as disk drive, opened disk drive, placed the amon file into the sdcard, changed phone back to charge only, went to astro to verify that the amon file was on the home list of files, then wen to market and downloaded terminal emulator free, and just follow Amon's instructions to apply using terminal or adb, it was reall easy that way, i kept trying to load the fastboot way and just couldn't figure it out, so i tried this was and perfect, new recovery, and hopefully i can wipe dalvik now.

You don't need fastboot to flash a new recovery image. Like tomh said in the post above this one, put the new recovery on the root of your sdcard, open a terminal emulator on your phone and type the following:
flash_image recovery /sdcard/name_of_recovery.img
I haven't used my computer to update a recovery image since I first got my Hero.

with a terminal app you'll want to use this exact cmd's
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
that's just as amon_ra has it, same as what i used as well.

thanks for the help

shawnten said:
thanks for the help
Click to expand...
Click to collapse
Somewhere on your PC. You just have to give the path to the fastboot command.
Sent from my HummerPhone using the XDA App

i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.

ro2themax said:
i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.
Click to expand...
Click to collapse
Root your phone..

i jsut use rom manager. I am to lazy to do everything else currently rom manager has the latest amon ra you can tell it to flash as an "alternative" recovery. takes 2 seconds and no typing out "long" commands in terminal.

i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.

ro2themax said:
i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.
Click to expand...
Click to collapse
Huh, that's weird. What rom are you using?
If you're using a rooted rom then you should be getting a # when you type "su" into the terminal..
Do you have the SU app installed? Did you get an SU Permission request when you opened the terminal for the first time? If so, did you grant the terminal emulator SU permission?

im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
i also forgot to mention that i also put a "netarchy kernal" on their also which appears to me, works as it said. right now if i want to go into recovery it goes through clockwork, but i want to get amon ra's recovery on there instead.

ro2themax said:
im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
Click to expand...
Click to collapse
hmm.. which 2.1 stock? Was it a rooted stock (with busybox and su already in there) or did you install the su app?
Although sounds like it already had busybox if setcpu is getting permission.
If you are near your computer see if you can get a # using the adb shell. I'm a little stumped here..

the 2.1 stock came with the "su" already. i just posted a quick update on the my previous post that i flashed a netarchy kernal on my evo also. i dont know if that helps but i just forgot to mention it...
please bare with me, im by my computer and to go into adb shell do i need to plug my evo in as charge only and open a cmd from android tools to see if i get # ???

[Guide] How to recover your semi-brick

YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html

before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?

Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.

I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App

Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App

renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.

you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.

Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.

reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?

{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.

fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.

Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?

im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...

-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....

^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!

marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?

it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file

fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?

[GUIDE] Flash CWM Manually (for noobs)

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.