I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
List of devices attached
HXXXXXXXXXX device
Click to expand...
Click to collapse
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
flash radio
Click to expand...
Click to collapse
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
/Users/Liam/SDK/tools/fastboot flash radio /Users/Liam/SDK/tools/radio.img
Click to expand...
Click to collapse
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
fastboot reboot
Click to expand...
Click to collapse
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.
been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate
steve36 said:
been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate
Click to expand...
Click to collapse
Wrong thread. But the thread you want, and the answer, is here: http://forum.xda-developers.com/showpost.php?p=10113370&postcount=91
Do some searching first..
Anyways, yeah, now I can use my MacBook.
This seems to be an odd way of doing it.
Just download the fastboot-mac binary from the htc developer page. Drop it in the platform-tools folder of the androd SDK.
Start a Terminal and run:
/path/to/platform-tools/fastboot-mac flash radio radio.img
make sure you have radio.img in the current directory where you invoke the script.
I found it easier to drag and drop the files. Saves lots of typing and does the same job.
liam08 said:
I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.
Click to expand...
Click to collapse
Hi i did not notice your guide so i created one last night >>>>here<<<<
I use this:
http://qtadb.wordpress.com/
I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?
P1xelVandal said:
I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?
Click to expand...
Click to collapse
Use my guide downloaded the zip file read all of first post sorted
E=Mc2
leith51 said:
Use my guide downloaded the zip file read all of first post sorted
E=Mc2
Click to expand...
Click to collapse
it's a shame all the files are .exe and .bat *sigh* thanks anyway.
P1xelVandal said:
it's a shame all the files are .exe and .bat *sigh* thanks anyway.
Click to expand...
Click to collapse
localhost:~ Mac$ /fastboot/fastboot-mac flash radio /fastboot/radio.img
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)
localhost:~ Mac$
what am i doing wrong? (no i will not switch to PC))
This guy used my thread his problem was he didn't have eng s-off
E=Mc2
Related
I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason
Go to start -> run -> type in CMD
Navigate to the folder where adb is located.
Then type in adb devices to see if it finds ur device.
If not then make sure you have it plugged in and USB debugging is turned on in the phones settings under Development.
Also download the usb drivers/or the whole SDK if you havent yet.
nosaj13 said:
when i try to run adb, it open very briefly and closes.
Click to expand...
Click to collapse
If you try to execute a text mode executable in windows, it will close the terminal window as soon as the program finishes. If you run adb without any arguments, it will print the arguments out terminate. I could say the solution is to open run as and type cmd, but the true answer is to install Linux
nosaj13 said:
I come from the world of Windows Mobile and have just recetly delved into hacking my G1. While I've had no problems installing jesusfreke's images or themes...I'm struggling with how to get fastboot to work.
Perhaps someone can give me some guidance. Anyone willing to give me some simple step by step instructions. I've searched for this and i think I have everything i need, but I'm unable to get to a point where I can type in commands. when i try to run adb, it open very briefly and closes.
What am i doing wrong?
Thanks,
Jason
Click to expand...
Click to collapse
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun
when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?
nosaj13 said:
when i type adp devices i get an error that says "adp is not recognized as an internal or external command, operable program, or batch file"
what am i doing wrong?
Click to expand...
Click to collapse
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"
Datruesurfer said:
1. Download this
2. Extract the contents of the fastboot directory to the root of your C drive.
3. Go Start -> Run -> type 'cmd' (no quotes) and hit enter
4. Type 'c:' (no quotes) and hit enter
5. With your phone plugged in, you should be able to type 'adb devices' and it should return your phones serial number, which is usually in HTXXXXXXXX format. If it does not, make sure debugging is enabled on your phone and you have the adb drivers installed.
6. type 'adb shell reboot bootloader' and hit enter. The screen on your phone will go blank for a second and then you should be in the SPL with the skating androids. Make sure you see "FASTBOOT" at the bottom of the screen.
7. type 'fastboot devices' and hit enter. If you see your phone's serial number again, you have successfully established a fastboot connection with the phone and can run commands such as:
fastboot erase <partition> (erases the given partition)
fastboot flash <partition> <file.img> (overwrites and flashes given partition with given file. This is how one would restore from a nandroid backup)
fastboot reboot (reboots the device into user mode)
Hope that helps. Have fun
Click to expand...
Click to collapse
i did all the above steps with no problem at all till i got to number 7. when i typed in fastboot devices it just goes to the next prompt without my phone showing up.
If i plug in my g1 in normal mode i see it at the top under adb and in the usb section as a mass storage device.
In bootloader mode with fastboot on the screen it doesnt show up anywhere in the device manager.
Also when i follow the above quoted steps and type in the "adb shell reboot bootloader" and hit enter i hear the ding you hear when you unplug a usb device, and all instances of the phone then leave the device manager.
i have also uninstalled and reinstalled all drivers for the phone and all drivers that have to do with the usb ports on my win xp machine.
Anyone have any ideas i could try?
I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.
I7oobie said:
I think you need this program. I put it on my desktop, then just ran cmd, directed to it, and type in fastboot.
Click to expand...
Click to collapse
thats not it. i have that in the sys 32 folder and also on desktop
Fastboot mode not recognized
I'm having the same problem. I've installed all the correct drivers and in normal mode, I see the Android Composite Device (or something similar) in Device Manager.
As soon as I go into SPL mode (the 3 skateboarding androids screen), the device does not show up.
Anyone have any ideas? Thanks!
Datruesurfer said:
First, the command is adb devices not adp. Second, make sure you copied the contents of the fastboot directory to the C drive. Third, make sure you that when you type 'c:' into the command line, the command prompt actually changes to "C:\>"
Click to expand...
Click to collapse
When I'm in the Command Prompt and I type C:, the directory still reads C:\Documents and Setting\Reids. It won't change to only C:
Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.
bestwebs said:
Hi,
You have to do this to get back to c:
cd\
press enter
That should do it.
Click to expand...
Click to collapse
Ok, thanks a lot. Got it working now.
I need help trying to flash my cupcake images that I have stored in my fastboot folder. I attached the pictures below. I will accept any help I can get.
EDIT: Doh, I thought I was in another topic.
My bad.
Are adb & adb's dll files located inside the same folder as fastboot??? They are suppose too be.
Is your usb cord directly plugged into your system or thru a hub??
Your phone, i bet is under usb mass....to check, expand your device manager window.
Expand your USB-Mass storage list.
With your phone in fastboot mode, click on the camera key and the back key. With enough time inbetween for your system to recognize that there might be a device hooked up.
Notice any change in the list??
Anyone wanting good instructions
http://androidcommunity.com/forums/f28/nandroid-v2-0-full-nand-backup-and-restore-tool-9336/
Read post 2 and go!
this seems like the most easiest thing to do but i still cant get it to work
i have downloaded everything needed and see ADB Interface on my device manager with a yellow mark on it when i try to update the dirver it fails and i got the drivers and point them to it but seems not to work
my phone is on the fastboot screen with the android skateboards guys
i dont know whats going on if someone know what am also doing wrong can tell me please...
This is what i get
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img
I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!
So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.
Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img
williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash
The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse
I am new to the ASUS family of tablets, and j just can't figure out how to root. I have rooted many tablets and installed custom roms before but the i cannot follow the how tos listed here. For one fastboot doesnt work on my computer. It opens and closes immediately. What i would like is a detailed step by step guide with a trouble shooting guide. I mean now i reading about downgrading, blob files and a few other things i never dealt with on my galaxy. Someone help......would love to root this thing. Email me if u want [email protected]
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Check this thread, it has videos about rooting and whatnot, hope it helps:
http://forum.xda-developers.com/showthread.php?t=1663244
Northern-Loop said:
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Click to expand...
Click to collapse
Yes, Bootloader is unlocked. Ok, so I tried the flashboot command, so now what? I typed the command from the walkthru "fastboot -i 0x0B05 flash recovery recovery.img " but get an errorcannot load recovery.img. So what am I missing. I have the recovery image on my desktop.....
Put the recovery image in the same folder as your fastboot application and it should work.
xAshxMoneyx said:
Put the recovery image in the same folder as your fastboot application and it should work.
Click to expand...
Click to collapse
....what fastboot folder? I installed the ADK per the instructions, I downloaded the root and recovery image. I looked in the system for a fastboot folder and do not see it. Plus when I try to type in the fastboot command now, it says it is not a recognized command. I am sure this is something simple, but I am just not getting it. Is there a more detailed step by step somewhere that will actually walk you thru the steps without assuming you know what they are talking about? I can root my phone, my galaxy tab all day long and install and change ROMS, but this one has me upside down.
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
xAshxMoneyx said:
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
Click to expand...
Click to collapse
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
xAshxMoneyx said:
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
Click to expand...
Click to collapse
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
tccc143 said:
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
Click to expand...
Click to collapse
Ok, so reinstalled everything.....did a quick refresher on CMD directions and had it rooted with CWM in 10 minutes. I have been working in Android so long without the use of a PC that I forgot how to use the PC. Thanks for the help....now we wait for some nice roms.
Sweet, glad you got it, I've done this stuff a few times but I always have to refresh myself and take it slow on each different device.
tccc143 said:
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
Click to expand...
Click to collapse
You should not move the folder. This can cause all kinds of problems. in the cmd prompt just type
cd \folder\folder\etc.
The cd means change directory and you start off with a backslash to set the initial path to the root of your drive. if folder names include spaces then wrap the path with quotes, cd "\folder one\folder two\etc". the prompt should change from C:\windows or whatever to what you typed in.
if you've installed on a drive other than C: then first change to that drive by typing the drive letter followed by a colon, ie D:
Good old DOS will never die.
Sent from my SCH-I510 using XDA
Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!
Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!
Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse
post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!
Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!
Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?
So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?
Yes, exactly then!
Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.
I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!
Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.
I am not sure about that, how should I know?
Do you get the same error if you type fastboot devices ?
I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"
Please Admin/Moderator, lock this thread, my problem is now fixed!
Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem