hi guys, i'm really sorry if this is really simple, but i just cant get my head around it and i've been googling for ages and i just keep getting more and more confused.
i'm basically trying to get fastboot enabled on my ubuntu linux install (11.04). would someone please explain to me in simple terms how to get it installed and running on linux, please? from the start would be great, as i find it harder to carry on half way through something. i appreciate the help. you guys are awesome
As soon as I get on my computer at home, i'll outline the steps and attach fastboot
(gimme an hour)
Update: it's taking me longer to get home than expected... Gimme till about 1pm cst (central standard time)
paxChristos said:
As soon as I get on my computer at home, i'll outline the steps and attach fastboot
(gimme an hour)
Click to expand...
Click to collapse
that would be brilliant!! thank you!!
Fastboot on Linux
I too had issues when I switched from Linux to windows (recently) and here's how I got it (just for documentation)
1) I downloaded android-sdk for linux, did the installs, but lo and behold, there was no fastboot...
2) Searched google for about 45 minutes
3) Finally figured out that HTC had it in their development website
4) Downloaded & chmod'd it so it'd work
5) Figured out that the r800x really can't be unlocked via all my attempts (so far...)
Here's a step by step as to how to get it without my hassle.
1) Attached is fastboot, download it, extract it (you can do this later in terminal if you feel like it, or you can do it now in the file explorer)
2) Open up terminal (if you don't have a shortcut for it, make one, it's the most useful thing in linux. ever.)
3) Type in su, enter your password (if you have it setup) and become root. (Or, you could call sudo whenever it is necessary, it's your preference)
4) goto the folder you downloaded fastboot to in terminal (the default chrome download place is /home/[insert your username here]/Downloads)
5) type in chmod [your preference for setting permissions here] fastboot
6) type in (sudo) cp fastboot /bin/
7) now you can call fastboot from anywhere in the terminal!!
This can also be done with adb
Any questions??
paxChristos said:
I too had issues when I switched from Linux to windows (recently) and here's how I got it (just for documentation)
1) I downloaded android-sdk for linux, did the installs, but lo and behold, there was no fastboot...
2) Searched google for about 45 minutes
3) Finally figured out that HTC had it in their development website
4) Downloaded & chmod'd it so it'd work
5) Figured out that the r800x really can't be unlocked via all my attempts (so far...)
Here's a step by step as to how to get it without my hassle.
1) Attached is fastboot, download it, extract it (you can do this later in terminal if you feel like it, or you can do it now in the file explorer)
2) Open up terminal (if you don't have a shortcut for it, make one, it's the most useful thing in linux. ever.)
3) Type in su, enter your password (if you have it setup) and become root. (Or, you could call sudo whenever it is necessary, it's your preference)
4) goto the folder you downloaded fastboot to in terminal (the default chrome download place is /home/[insert your username here]/Downloads)
5) type in chmod [your preference for setting permissions here] fastboot
6) type in (sudo) cp fastboot /bin/
7) now you can call fastboot from anywhere in the terminal!!
This can also be done with adb
Any questions??
Click to expand...
Click to collapse
^_^ thank you so much!! you have made my life so much easier!! just one question. if all i'm doing is flashing the occasional kernel with fastboot, or pushing/pulling etc with adb, do i still need all the adroid sdk stuff? or can i just delete all the stuff now?
solitarymonkey said:
^_^ thank you so much!! you have made my life so much easier!! just one question. if all i'm doing is flashing the occasional kernel with fastboot, or pushing/pulling etc with adb, do i still need all the adroid sdk stuff? or can i just delete all the stuff now?
Click to expand...
Click to collapse
Honestly, I don't know.
That being said, try copying all the extra stuff from where it is currently to another location, and try running adb and fastboot, if it works, delete the extra stuff, if it doesn't, don't mess with it
i am trying to do this with no luck. any suggestions
Where are you stuck?
Sent from my R800x using XDA App
In the terminal I get to waiting on divice. Can't get past that
Sent from my DROID X2 using xda premium
ninjasailas said:
In the terminal I get to waiting on divice. Can't get past that
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Are you in fastboot mode?? (Blue led on top)
(To get into fastboot mode on the Xperia Play, hold down the search button before and while you plug in the usb cord)
(If you are using a different phone, please google the button combination for fastboot)
I have a Droid x 2 and I have booted into fastboot mode
Sent from my DROID X2 using xda premium
good luck, but your problem is outside my (very limited) experience with devices, sorry.
Sent from my R800x using XDA App
That's ok I know its possable seen lots of dx2 users post there logo.bin files. might have to find a windows box. Also, what command do you recommended to fix permissions for fastboot. I used chmod +x fastboot
Sent from my DROID X2 using xda premium
I use numbers and honestly I do either 777 or 755
droid x2 is motorola, right? Don't you need boot strap or something for motorola?
Sent from my R800x using XDA App
update: check http://www.droidforums.net/forum/motorola-droid-x2/149566-droid-x2-boot-menu-recovery.html and see if that helps
For linux I found I had to add the "-i 0x0fce" before my commands or else Id be left with the waiting for device, try this:
fastboot -i 0x0fce getvar version
Also you may have to make the file:
/etc/udev/rules.d/51-android.rules
With this inside (note that 0fce is the idVendor for SE):
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
That being said I think this accomplishes the same thing as just putting the -i 0x0fce before your command
I navigated to /etc/udev/rules.d. but I cannot create file.
Sent from my DROID X2 using xda premium
ninjasailas said:
I navigated to /etc/udev/rules.d. but I cannot create file.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Create it I'm a different folder i.e. documents or downloads, them cp the file over to /etc/udev/
Sent from my R800x using XDA App
I actually created the file I had to use the command gksudo Nautilus. What version of Ubuntu do you have? I am using 11.10
Sent from my DROID X2 using xda premium
11.10, I run everything in terminal with root privileges : p
(don't forget to chmod if you cp!!)
Sent from my R800x using XDA App
What is cp
Oh copy paste?
Sent from my DROID X2 using xda premium
Related
can someone please explain it to me very detailed? i dont understand so much from the tuts i have read.
Are you rooted and s-off`d?
Blinkydamo said:
Are you rooted and s-off`d?
Click to expand...
Click to collapse
yes, i have
Put cwmod on the root of your sd card. Download terminal emulator from the market. In terminal emulator type
su
press enter
then type
flash_image recovery /sdcard/nameofrecovery.img
press enter
Replace nameofrecovery with whatever the name of the file is.
When you reboot into recovery it should be cwm 3.0.0.5 (should be amber font)
Sent from my Desire HD using XDA App
it shows file not found, even when i write the name of the file.
From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App
pwraggcan said:
From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i am running revolution HD, i just tried that and it said failed <remote: not allowed>
why must it be so damn hard? damn crap
Are you eng s off?
Try using adb shell from your command prompt then use the same commands you used in terminal emulator.
Sent from my Desire HD using XDA App
pwraggcan said:
Are you eng s off?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i think so, http://forum.xda-developers.com/showthread.php?t=857537 i used that tut. is it so many different S-OFF's ?
Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App
pwraggcan said:
Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i dont know, maybe. but im trying this now http://forum.xda-developers.com/showthread.php?t=855403 will it be a problem that i used the other S-OFF and now this?
I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App
pwraggcan said:
I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
if you mean the commands that is written in cmd, then i have already tried it, and it failed.
In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App
pwraggcan said:
In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I just installed it now thats why i want it, but do you know how i get back to the older cwm? do i just flash it in ROM manager?
Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App
You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice
pwraggcan said:
Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i used this and then the command worked
Cool. Glad you're sorted. Good luck with cm7.
Sent from my Desire HD using XDA App
Dousan said:
You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice
Click to expand...
Click to collapse
Hello
just tried that worked flawlessly
thank you
i just used fastboot-windows... to unlock the bootloader. But when i enter into the command prompt 'fastboot flash bootloader bootloader-maguro-primekk15.img' it says 'fastboot' is not recognized as an internal or external command.. i downloaded all the 4.0.2 files into the root of my hard drive what am i doing wrong? im stuck at the command prompt now lol
You don't have your paths set up. Change your environmental variables to include the folder that contains fastboot. It could also be that need to type "fastboot-windows" instead of "fastboot" depending on where you got it from.
Try "fastboot-windows flash bootloader bootloader-maguro-primekk15.img"
The command for Windows is "fastboot-windows ................"
greetz
//edit: too latee
It's only that if using the edited fastboot files. I have my system variables set up so I can run fastboot/adb from any location. A lot easier
Do I need sdk tools and stuff like that.. somebody take me back to the basics I haven't done this since nexus one was released.. environment variables?
Sent from my Nexus One using XDA App
mcguinness89 said:
Do I need sdk tools and stuff like that.. somebody take me back to the basics I haven't done this since nexus one was released.. environment variables?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Fastboot isn't dependent on Android SDK, Choose a place for fastboot to live (C:\Program Files\Android - perhaps?) then right click on MyComputer, Properties, Advanced and there should be an environment variables settings button somewhere, click edit and append the location to the end of the line, e.g. C:\Windows\System32;C:\Program Files\Android
This will allow you to call fastboot from whatever directory you're currently working from within command prompt.
Thank u all for your help I will try it all now, stand by! Haha
Sent from my Nexus One using XDA App
mcguinness89 said:
Thank u all for your help I will try it all now, stand by! Haha
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
do you have a galaxy nexus or nexus 1?
I recently purchased a nexus and i am new to this, i have tried everything to root this on a mac and had no success. Has any one else rooted this on a mac? If so could you walk me through it. Thanks in advance!
Are you sure you have ADB and fastboot setup correctly?
What part are you getting stuck at?
I dont think so, i downloaded some things called superboot and i keep messing up in terminal i think...did you use superboot?
Yes sir I did, also on a mac. Here, you might want to checkout this link to make sure you have everything set up properly before you start the superboot process:
http://forum.xda-developers.com/showthread.php?p=9842005
The guide will talk about fastboot towards the bottom, you can download a fastboot file from this page:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Okay, thank you very much, i will try it out and let you know if it wprks
Sounds good, let me know
on the (export PATH=${PATH}: part when your are supposed to drag the folder into text edit im getting just the folder icon instead of (export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools) like the guy said his looked, is that okay, or do I need to start over?
Nevermind, I got it!
Sorry! I was asleep haha if you need more help I'll be checking in
Sent from my Galaxy Nexus using xda premium
Thats fine lol, okay on the Fastboot part when you find SDK/platform-tools in terminal , i type in ls> desktop> SDK > platform-tools and it says its not there and its on my desktop. Am i skipping anything in terminal?
I actually can't get the ls part to work.. I just ignore that part haha but the fastboot file should be in your tools folder of platform-tools I believe
im on the superboot part now...is this a good method? http://www.helloandroid.com/content/root-galaxy-nexus-superboot
Yessir, that is the method I used but I found the instructions in the development forum of the galaxy nexus section.. should be the same method though
Sent from my Galaxy Nexus using xda premium
Okay , last question and ill leave you alone lol, where it says (MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh')
I have the sdk located on my desktop, how would i type that in terminal to find it so i can do this step?
Haha, no worries
To get to that folder in terminal, you want to type "cd ~" without the quotation marks, and then you can drag the folder into the terminal window and it the path to that folder should pop up in the terminal, then just hit enter
Okay, thanks alot man, i really appreciate your help
Anytime! Feel free to PM me if you have any other questions!
I installed the Android SDK, and did everything necessary for ADB to work. Fastboot is there as I can call to it and it will give a response, but when my phone is in Fastboot mode it wont say that it's there. I use the 'fastboot devices' command, and there is no error or anything, it just starts a new terminal line as hough the command had been carried out successfully. Does anybody have a solution to this? I really want to install FXP 109, but since I can't flash the new kernel, I can't do it.
brainard52 said:
I installed the Android SDK, and did everything necessary for ADB to work. Fastboot is there as I can call to it and it will give a response, but when my phone is in Fastboot mode it wont say that it's there. I use the 'fastboot devices' command, and there is no error or anything, it just starts a new terminal line as hough the command had been carried out successfully. Does anybody have a solution to this? I really want to install FXP 109, but since I can't flash the new kernel, I can't do it.
Click to expand...
Click to collapse
Do you have the right drivers installed? Have you tried flashtool? That's what I use
None of those things work under Ubuntu, remember. I also don't need drivers.
Sent from my Cyanogen R800x using the XDA app.
brainard52 said:
I installed the Android SDK, and did everything necessary for ADB to work. Fastboot is there as I can call to it and it will give a response, but when my phone is in Fastboot mode it wont say that it's there. I use the 'fastboot devices' command, and there is no error or anything, it just starts a new terminal line as hough the command had been carried out successfully. Does anybody have a solution to this? I really want to install FXP 109, but since I can't flash the new kernel, I can't do it.
Click to expand...
Click to collapse
Have you unlocked the bootloader? Newer verizon software locked fastboot mode, so if you don't have an unlocked bootloader, fastboot will not even recognise device.
Sent from my R800i using Tapatalk
Use the magic "-i 0x0fce" tacked on to your commands, ex:
fastboot -i 0x0fce getvar version
^^ what he said, you need to add the -i 0x0fce or else it won't recognize it (unless you added sony into your android udev rules)
Think you! I'll try it out in a bit. I'll also thank your posts when I get onto something that isn't my Android xD
How do I add Sony to my udev rules?
Sent from my Cyanogen R800x using the XDA app.
brainard52 said:
Think you! I'll try it out in a bit. I'll also thank your posts when I get onto something that isn't my Android xD
How do I add Sony to my udev rules?
Sent from my Cyanogen R800x using the XDA app.
Click to expand...
Click to collapse
Here's what i have in my...
it's located in /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM=="usb", ATTR(idVendor)=="0fce", mode=="0666", GROUP="plugdev"
easiest way (IMO) is to use terminal and type the following
1) touch 51-android.rules
2) vim (nano/pico/whatever you use) 51-android.rules
3) type in what's in the code section
4) exit out
5) chmod 644 51-android.rules
6) sudo mv 51-android.rules /etc/udev/rules.d/
(Use tab to complete filesnames/paths, it makes it very fast indeed)
(also make sure you add your username to the plugdev group)
Here's what I have in 99-android.rules:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce:815d", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
also, I tried the -i 0x0fce thing, and it doesn't even recognize it.
What are the permissions on 99-Android.rules?
I used sudo chmod a+rx /etc/udev/rules.d/99-android.rules
sorry, my post earlier was wrong (i've updated it) us a+r, no x (644)
I used this guide to do everything.
Also remember that ADB works just fine.
brainard52 said:
I used this guide to do everything.
Also remember that ADB works just fine.
Click to expand...
Click to collapse
Your bootloader is unlocked, right?
Sent from my R800x using Tapatalk
Yeah, it should be. I'm using FXP52 at the moment. It really all started to go to hell when I reinstalled Ubuntu.
brainard52 said:
Yeah, it should be. I'm using FXP52 at the moment. It really all started to go to hell when I reinstalled Ubuntu.
Click to expand...
Click to collapse
personally, I hate 11.04, 10.04 is the current lte available...
You could also try the Fastboot binary I posted here: http://forum.xda-developers.com/showthread.php?t=1277997
(I've used it on multiple distros with no issues)
Sent from my R800x using Tapatalk
Thanks, I got the binary to work. It was really strange, when I called to the binary you provided, it actually had the -i option. The one I've been trying to use didn't have the -i option. Oh well. Also, I'm not using unity. Unity can go corrupt itself for all I care. I'm using Gnome 3 ^^ I absolutely love it. It's similar to unity, but it's a hundred times better. I would advise checking it out.
brainard52 said:
Thanks, I got the binary to work. It was really strange, when I called to the binary you provided, it actually had the -i option. The one I've been trying to use didn't have the -i option. Oh well. Also, I'm not using unity. Unity can go corrupt itself for all I care. I'm using Gnome 3 ^^ I absolutely love it. It's similar to unity, but it's a hundred times better. I would advise checking it out.
Click to expand...
Click to collapse
My guess is that the newest version of fastboot has issues...
OT:
I actually use openbox on arch linux I like simplicity Gnome uses too many resources for my taste
(I use 10.04 for other stuff, just 'cause it works, and I don't like messing with stuff that works)
Yay for offtopicness. Now, TO TH PM'S! *marks case as solved*
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.