So my desire is rooted then I s off'd with revolutionary and loaded a new recovery, now I want to change hboots so I put an pb99img.zip file on the scard and booted into bootloader but the zip file is not found.... Am I missing something?
Sent from my HTC Desire using Tapatalk
It will be best if you start using fastboot, it's fastest easiest and safest way to do so.
Look for ADB/Fastboot guide (they are all over the place..), you need to setup it once and then you just flash hboot by simply executing few commands for example:
fastboot flash hboot cm7r2.img
fastboot erase cache
fastboot reboot-bootloader
And you're done, so just learn how to install and use adb.
If you want to use the pb99img.zip method, make sure that the file really is called PB99IMG.zip. Windows is default set that it doesn't display file type endings, so it would show "PB99IMG.zip", but the file really is called "PB99IMG.zip.zip", which won't be recognized.
Anyway, I prefer fastboot. If you can't use it (e.g. no own pc with adb around), the zip method also works. But fastboot is faster (as the name says!) and you don't have to mess with files on your sd.
Ok so readup a bit about adb and fast boot then installed jdk then installed the sdk then installed platform tools which included adb and fast boot and added path to adb folder under path environment variable. Connected phone and booted into fast boot. All good so far.
Running adb or fastboot devices command lists my phones serial number so all looks like its working so then I put the ing files I want to flash in the same folder as the adb.exe file then run the command - fastboot flash hboot bravo_alphaspl-oxygenr2.img but I get an error failed to load etc etc
Did I miss something? Am I putting the img files in the right place? Should I use the alpharev zip files instead of the img files?
Sent from my HTC Desire using Tapatalk
What errors exactly are you getting, it will be best if you paste whole log including commands that you were executing.
Sent from my HTC Desire using xda premium
see attached for error message
Just put the PM199IMG.ZIP File to the root of microSD card and goto boot loader and it will detect the update file and ask you if you want to update or not there just press yess and then goto recovery and restore your nandroid backup. Or flash New Rom.
Sent from my HTC Desire using XDA
Don't you mean PB99IMG.zip file not PM199IMG.zip? If so have tried that as per first post. If not then I'll try that too.
Sent from my HTC Desire using XDA
Maybe you have misspelled the img name, rename it to something shorter like oxygen.img also make sure you're in fastboot mode while flashing it! (power off, then hold vol- & power on, select fastboot)
And the last thing the img file has to be in same directory as the fastboot.exe
Sent from my HTC Desire using xda premium
Cuz, sorry to confuse you, but seriously, forget all about adb, terminal emulator, PB99IMG.zip etc. Just install Android Flasher, plug your phone to PC (leave on main screen, it'll be fine) and push .img file to phone.
It seriously is a piece of piss, mate. You will have no dramas.
There's a thread in dev section to give you the how-to.
E: If coming from another HBoot, make sure you push "downgrader" (from alpharev) first.
777ace said:
E: If coming from another HBoot, make sure you push "downgrader" (from alpharev) first.
Click to expand...
Click to collapse
No need.
10chars
kiwiflasher said:
Don't you mean PB99IMG.zip file not PM199IMG.zip? If so have tried that as per first post. If not then I'll try that too.
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
Typing error Sorry
kiwiflasher said:
Ok so readup a bit about adb and fast boot then installed jdk then installed the sdk then installed platform tools which included adb and fast boot and added path to adb folder under path environment variable. Connected phone and booted into fast boot. All good so far.
Running adb or fastboot devices command lists my phones serial number so all looks like its working so then I put the ing files I want to flash in the same folder as the adb.exe file then run the command - fastboot flash hboot bravo_alphaspl-oxygenr2.img but I get an error failed to load etc etc
Did I miss something? Am I putting the img files in the right place? Should I use the alpharev zip files instead of the img files?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
You are on right track, you just need to put the img file to the location of fastboot.exe .
Dunno why you guys are talking about adb...that's a completely different story and you can't flash hboots with adb.
Apart from that i am quite surprised about how far you got,given the partly confusing answers.
You either use fastboot or android flasher (which is basically a fastboot GUI I think) or the PBblabla.zip hboot-zip method. Don't mix them up - you are using fastboot (which is the safest and in my eyes most straight forward way) , so stick to it You're almost there!
Sent from my HTC Desire using xda premium
Ok so I put the image file in the same folder as the fastboot.exe file so sounds like I did nothing wrong and it should have worked? Must be something wrong with the jdk or sdk install so will try using the Android Flasher method.
Sent from my HTC Desire using XDA
Yay for Android Flasher that did the trick, thanks to all...
Sent from my HTC Desire using XDA
kiwiflasher said:
Yay for Android Flasher that did the trick, thanks to all...
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
Sweet as!
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
okay so i downloaded the recovery.img. and i already have s-off btw. but i dont want to mess up my phone and i dont know how to flash the recovery..someone please help me out here
Ok, so I'm guessing you have ADB installed and able to communicate with the phone.
The way I flash recovery is to use the fastboot command (part of the Android SDK, located right along side ADB). To do this, reboot your phone into hboot (power off, then hold vol down & power). Once in hboot, select the fastboot option on the phone. Then plug the phone into the computer and issue this command:
fastboot flash recovery <your recovery file here.img>
If you are not certain of what you are doing I would recommend reading up a bit - flashing recovery is something that can definitely cause problems if not done correctly.
JTB
okay so in my command prompt i have it set up to my android sdk. and i keep getting errors when i try trying in something. it says is not reconized as an internal or external command
ok well do you actually have fastboot.exe? (it should be in the sdk/tools directory).
no i do not. where do i get that?
Look in platform-tools. It should be in there. If you don't have your platform-tools set in your environment variables, you have to cd to it in command prompt.
Sent from my T-Mobile myTouch 3G Slide
music man you just talked a whole bunch a jibberish that i did not understand lol. i just need the fastboot.exe file. can someone post a download link of that please?
mechlixt said:
music man you just talked a whole bunch a jibberish that i did not understand lol. i just need the fastboot.exe file. can someone post a download link of that please?
Click to expand...
Click to collapse
Within the android sdk, there should be a folder called platform-tools, in addition to tools. Fastboot.exe should be in platform-tools.
In command prompt, type this:
cd C:\locationofandroidsdk\platform-tools
And THEN run this:
fastboot flash recovery C:\locationofcw3image\filenameofcw3.img
And let it run it's course. I would do a nandroid backup first, in case it screws up your /system and /data partitions like it did mine.
Sent from my T-Mobile myTouch 3G Slide
You can also use the android terminal emulator from within android to flash it. In terminal emulator type these commands to do it from within android:
su
flash_image recovery /sdcard/cw3name.img
You have to have the image on your sd card, and you have to have a cyanogen rom I think. Cyanogen roms are the only ones I know of that are packaged with the flash_image command. Otherwise you have to fastboot flash it from windows.
Sent from my T-Mobile myTouch 3G Slide
Where do you get a .img for CWM? I was able to find this link but it's a zip file with a bunch of other stuff in there.
They're floating around. There's a development thread about cm7 rc0, it had a cw3 img attachment in the op I believe. I'd link you but I'm on my phone.
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
They're floating around. There's a development thread about cm7 rc0, it had a cw3 img attachment in the op I believe. I'd link you but I'm on my phone.
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=915680
This one here? Just thought I'd step in and link to help out, haha.
SefEXE said:
http://forum.xda-developers.com/showthread.php?t=915680
This one here? Just thought I'd step in and link to help out, haha.
Click to expand...
Click to collapse
Yeah that one, thanks haha
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'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.
i was trying to install a rom,and in the CWM i formated the sd along with the others by mistake,now i can't reach the rom i transfered and the phones won't boot for sure
i tried to flash the google stock with gnex toolkit (using step 9) and i downloaded the file but it fails and what is shown to me is what you have in the attached image,it gets stuck at the "sending radio"
what should i do,i really need urgent help here
please just know that i'm a total noob so please tell me what to do step by step so i could understand
What Nexus do u have gsm or verizon? If it's Verizon you picked the wrong version and it's flashing a gsm radio. If it's gsm it could be a bad download or you picked the wrong version not too sure about that I have a Verizon nexus
Sent from my Galaxy Nexus using xda premium
it's a GSM,and i chose the right version stated in the toolkit thread and the one i installed the drivers and unlocked the bootloader and rooted the phones with it
is there a way to transfer a file in the CWM mode? can i transfer the rom in this mode?
You should do these commands in fastboot instead of using a toolkit.
Here is a step by step guide how to get back to stock. http://forum.xda-developers.com/showthread.php?t=1626895
Edit: to answer you question about pushing a file in recovery, you can. You must use adb. The command is adb push nameoffile.zip /data/media
Sent from my Nexus 7 using xda premium
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Put the zip in the same folder and hold shift and right click select open command prompt here. Then adb push the zip onto your phone.
You got clockwork recovery? If so, you need cwm flashable version of radio, boot loader and ROM
Sent from my Galaxy Nexus using xda app-developers app
rok3r said:
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Click to expand...
Click to collapse
Yes move it to the same directory. Open the command window in that directory. (Shift+right click > open command window here)
Then type: adb push rom.zip /data/media
Sent from my Galaxy Nexus using xda premium
OMG!!! Device not found,same message i got in the toolkit when i tried to push the files (((((((
drivers?
Yes most likely a driver issue. Type adb devices in command. If if returns a device number everything is set up correctly. If not reinstall the drivers.
Sent from my Galaxy Nexus using xda premium
If you are trying to push in bootloader adb won't work. Get in to recovery cwm works fine than do the adB push
THAAAAAAAANNNNKKKKSSSSSS!!!
seriously thanks for the help,i am totally new to this and felt like i killed my phones with my inexperienced self
i was a driver problem and i used the toolkit to uninstall and install again the driver and then used the toolkit to push the files but it said something like adb is already in root access or whatever so i headed to the adb.exe and it did it!!!!
thanks man for the great help again!!!!!:good:
this will make me learn to do a nandroid hahahaha
@atifsh i was in the CWM,it was a driver problem after all,thanks for your reply