Hi together!
Since this is a topic where people ask regularly, I try to make a little TUT.
I hope it is helpful.
I am a noob myself, so please don't go on me
Please feel free to correct me if I am wrong or if I missed some important stuff.
What you need:
1.
SDK Tool (type in your browser: developer.android.com/sdk/index.html)
Once you are on that page, download the package and install it.
2.
after the install process has finished, you have to install some packages.
Important is the platform-tools package (there you find the most important commands)
3.
Locate the folder on the harddisk of your PC
4.a)
Push the Windows(Start) Buttom and type: cmd
This opens the command prompt
Now get into the root of the android folder (e.g. cd.. until you get into root of your harddisk)
(on my PC, it looks like this:
cd android
cd platform-tools)
4.b)
Just one thing to make it a little easier to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu.
Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easily type the commands without navigation through folders.
credits go to Neo XL
5.
Your phone has to be in fastboot-USB mode and connected to PC in order to understand the commands
6.
Once you are in platform-tools folder, you can type commands
Most common commands are:
fastboot erase cache (sometimes helps if phone is in HTC bootloop)
fastboot flash boot (name of boot image / e.g. boot_1.2.3.img) (this is, like the name says, to flash a boot image)
fastboot flash recovery (name of recovery.img
fastboot oem lock ( to relock your phone, in case you have or want to flash a RUU)
fastboot flash unlocktoken Unlock_code.bin (to unlock again, if you already got the unlock key from HTCDev)
Flash firmware.zip using following terminal commands:
Please rename first downloaded .zip package to firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
This is almost obsolete, since we have the new Recovery 5.8.3.1 with Mount USB, but it is still good to know
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!
Or try following:
Copy rom to your adb-directory on PC
Switch OFF phone
Connect phone to PC
Wait until you hear the "USB-Connect"-sound on PC
Go into command window in adb-directory
Type "adb push rom.zip /sdcard/"
(where rom.zip is name of rom-file)
pushing is rather slow so it will take a while. Eventually you get an "OK". Then you can go into recovery and flash it.
Credits go to Jotha
Updated link
[TOOL][27/04] Automated Fastboot Commands For HTC One X continued
http://forum.xda-developers.com/showthread.php?t=1634786
credits go to TeAm Hex
For now, this is what I can think of, for sure there are many more commands, but hopefully we don't need them, but like I said, feel free and put them in here
I hope this will help some noobs, like myself!
If this helped you, please push THANKS
thanks! this will stop us noob's, spamming up dev's thread's.
Thanks for you efforts
First time with real android phone, this is good!
Thanks mate
Sent from my HTC One X using xda premium
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Just one thing to make it a little easyer to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu. Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easyly type the commands without navigation through folders.
incident said:
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Click to expand...
Click to collapse
Would be great, if this is possible! But as far as I know, it not possible.
Edit:
It is possible now! Updated post!
Sent from my HTC One X using XDA
hello I have problem with loading boot.img in fastboot
sdk is open, phone is conncted to comp on fastboot usb mode , image is on disc c in folder fastboot and still recive this info
c:\fastboot>fastboot flash boot boot.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
c:\fastboot>
pls help me with that
ok I fix this, that was problem with missing fastboot.exe and was no connection betwen phone and computer
this link helps fix that
http://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
You have to copy the Boot.img into the folder, where fastboot-, adb commands are situated (c:/andoid/platform-tools)
Then Open cmd. Go to platform-tools folder and from there it should work.
Sent from my HTC One X using XDA
Thanx man, but is fixed now, I did this by follow the instr. in page from my last post, and goes perfect. I just flashed new rom with 1.8 base and iam now on the bright side of life.
PS sorry for my english
@OP, last time I tried fastboot boot command it gave me device not found message(no problem when fastboot flash). What's the correct approach to make it work? I recently updated to 1.28 and I want to stay in stock for the mean time.
Sent either from my Arc or One X using xda premium
You can add the adb and fastboot directory path to the environment path in windows settings. You can then use adb and fastboot outside of the platform tools directory, but still in command prompt of course
Sent from my HTC One X using Tapatalk 2
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Stuart.upton666 said:
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Click to expand...
Click to collapse
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
In point 3, it is not supposed to boot into recovery. Its for booting your recovery.img (e.g. recovery-clockwork-touch-5.8.3.1-endeavoru.img ) from PC. After this step you will automatically boot into Recovery. From there you can use adb commands.
Did you try "adb devices"?
I tried it myself and it works!
This guide is great... Thanks!
Sent from my HTC One X using xda premium
tonyhagger said:
This guide is great... Thanks!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thank you, Sir! Some kind of feedback is always appreciated !
Hi about Push to SDCARD command
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Take the newest CWM recovery.
Sent from my Desire HD using XDA
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
TEKONG84 said:
[/COLOR]
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
Click to expand...
Click to collapse
Rom should be on root of Sd.
If this is not working, you can try to use the command while phone is powered off. I am not a dev, but I read something like that:
"Switch off your phone, connect to pc, wait until it is detected by windows and use: adb push nameofrom.zip /sdcard/" thats what Jotha told someone on ARHD Thread.
Try that and tell us if it worked.
Sent from my Desire HD using XDA
Related
Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)
Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App
Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(
From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???
superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows
superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.
I am trying to change my recovery with this tool but have come up against problems. I open up the program and then select recovery. The phone then reboots into fastboot usb as expected and then it say can not find recovery.img. I obviously have put the recovery img in the data folder and have also tried renaming it recovery.img. I am sure I am being thick but I have spent a bit of time and thought someone must have a quick answer?
Thanks in advance
You have to put the recovery.img in some place on your computer, not on the phone.
Swyped from my HTC Desire using XDA App
The recovery image is on the computer in the date folder that is created by unzipping andriod flasher, all the drivers are installed and I am s off etc.
I hope the recovery you want to flash is for your phone?!
I would give up android flasher, and do it directly via fastboot:
Copy recovery.img in the folder of android sdk, open command line, go to tools folder of android sdk, boot your phone into fastboot, connect it to your computer via usb and enter:
Code:
fastboot flash recovery recovery.img
Swyped from my HTC Desire using XDA App
I am simply trying to flash CWM 3.2.0.1 I think it is, think I might just leave it with the alpha rev recovery that came as part of the s off procedure
hi,
to do what mattdroid says, you need adb sdk install or brwse to your android flasher with cmd line.
best is to declare variable environnement into win.
quiet simple:
1/righ click onto my computer sekect property
2/select adnvanced tab
3/ hit environment varaiables button
4/first part [user environment variable for (users)]
===> select new - a popup come up into variable name write [path] whitout bracket
==============================>variable value write [c:\the path\whereandroidflasheris] whitout bracket.
now just log off and log in.
open dos prompt and just type:
Code:
fastboot erase recovery
fastboot flash recovery c:\wheretherecoveryis\recovery.img
fastboot reboot
should do the trick
hope this help
Hi,
I want to have a custom Rom on my htc one x but I have problems with installing clockwork. After entering '' fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru'' I get an error: cannot 'load recovery-clockwork-touch-5.8.4.0-endeavoru'. I followed all the steps but everytime I get that. Anyone know what I should do to install it.
hitb73 said:
Hi,
I want to have a custom Rom on my htc one x but I have problems with installing clockwork. After entering '' fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru'' I get an error: cannot 'load recovery-clockwork-touch-5.8.4.0-endeavoru'. I followed all the steps but everytime I get that. Anyone know what I should do to install it.
Click to expand...
Click to collapse
Easier to rename the img file to CWM
Place it in the folder that contains fastboot, adb etc within android sdk on your pc.
Put phone into fastboot usb
Open cmd on pc
CD C:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
(you need an unlocked bootloader obviously to do all of the above)
Sent from my HTC One X using Tapatalk 2
You have forgotten to use the extension .img in the filename.
eyosen said:
You have forgotten to use the extension .img in the filename.
Click to expand...
Click to collapse
I did try with extension .img I received same error
Are you using international one x with tegra 3 cpu? If so, try renaming the img file to something like cwm.img as chris suggests and try flashing. Phone must be in fastboot mode showing fastboot usb on the display. You can use fastboot devices command to make sure phone is recognized.
chrisjcks said:
Easier to rename the img file to CWM
Place it in your fastboot folder within android sdk
Put phone into fastboot usb
Open cmd on pc
CD C:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
(you need an unlocked bootloader obviously to do all of the above)
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I changed filename to CWM.img and replaced it in the map platform-tools
This is the location: C:\Users\Hosseini\AppData\Local\Android\android-sdk\platform-tools
What should I type into the cmd now.
Many thnx
chrisjcks said:
Easier to rename the img file to CWM
Open cmd on pc
CD C:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Change your directory to with
Cd C:\Users\Hosseini\AppData\Local\Android\android-sdk\platform-tools
and use above command
hitb73 said:
I changed filename to CWM.img and replaced it in the map platform-tools
This is the location: C:\Users\Hosseini\AppData\Local\Android\android-sdk\platform-tools
What should I type into the cmd now.
Many thnx
Click to expand...
Click to collapse
Bloody he'll,
Where have you installed android sdk to on your pc?
Default is to the root of C:/ (c:/android-sdk)
But some people choose to install within program files
-----
I'd recommend re-installing android sdk, because your location is just a big pain in the buttcheeks.
Basically, the first command after your phone is in fastboot usb is the location of this folder,
CD C:/location of platform-tools folder
The second command is
fastboot flash recovery imagename.img
(yes, you have to put img on the end)
---
If you chose to keep the location of your Android sdk, the first command must include the full path of your platform tools folder (which inside has your cwm img)
Your choice
Sent from my HTC One X using Tapatalk 2
Hello,first of all I apologize if posting in wrong section..I have a Acer iconia tablet A100..have to say love it..well other day did some reading and searching and decided to root it,I followed the following proceed( http://forum.xda-developers.com/showthread.php?t=1531646).worked perfect with no issues..thanks xda for making it simple. My question is what's the best way to install recovery and what are some of the good roms recommended I can use...I appreciate for the help..thank you..
Check this thread out http://forum.xda-developers.com/showthread.php?t=1711125 it has recovery and rom info plus alot more
OK do I download the unlock boot loader n extract files.and run it..just a lil confused bout the codes on the thread..
Cheony81 said:
OK do I download the unlock boot loader n extract files.and run it..just a lil confused bout the codes on the thread..
Click to expand...
Click to collapse
Go in order you'll be fine.
Root, which you already did.
Install the boot loader, just extract the files and run the script with it connected on USB.
After that, and only after, install a recovery and you can turn install custom ROMs. That guide covers it all if you spend some time reading before jumping in, always a good idea.
Sent from my HTC DNA
thank you..when it says volume up and volume down to pick,what happens if you hit the wrong one..( i hit wrong key and said cancelled or time out..hit the reset button and then started over and picked correctly this time and hit power buttom to restart tablet..Am i doing ok now..
pio_masaki said:
Go in order you'll be fine.
Root, which you already did.
Install the boot loader, just extract the files and run the script with it connected on USB.
After that, and only after, install a recovery and you can turn install custom ROMs. That guide covers it all if you spend some time reading before jumping in, always a good idea.
Sent from my HTC DNA
Click to expand...
Click to collapse
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
im a lil confused on this part..i downloaded the image just confused on the steps and adb? command promt? and do i put debug on or off?
ok i found on how to open cmd. i follow instructions when i type adb devices it tells me adb is not recognized as internal or external command ?am i missing a step or doing something wrong.. 1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
Cheony81 said:
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
im a lil confused on this part..i downloaded the image just confused on the steps and adb? command promt? and do i put debug on or off?
Click to expand...
Click to collapse
Cheony81 said:
ok i found on how to open cmd. i follow instructions when i type adb devices it tells me adb is not recognized as internal or external command ?am i missing a step or doing something wrong.. 1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
Click to expand...
Click to collapse
That means you aren't in the folder where your adb.exe is. It'll be in with your rooting files usually.
Sent from my HTC DNA
ok the files i have downloaded so far are(ICS_rooting_A10x_A5xx) used this one to root device. (fastboot recovery) which i used to unlock bootloader..what steps do i have to do now and do i need to have debug on?
pio_masaki said:
That means you aren't in the folder where your adb.exe is. It'll be in with your rooting files usually.
Sent from my HTC DNA
Click to expand...
Click to collapse
Cheony81 said:
ok the files i have downloaded so far are(ICS_rooting_A10x_A5xx) used this one to root device. (fastboot recovery) which i used to unlock bootloader..what steps do i have to do now and do i need to have debug on?
Click to expand...
Click to collapse
Debugging should be on.
Copy your chosen recovery.img to the folder where your adb.exe is, if its in the rooting folder, put them there.
For ease I would make a folder called root so its like this
c:\root
Place the adb and fastboot files in there with the recovery image.
Open a command prompt and type
cd c:\root
Type
adb devices
Should now work properly and list some numbers
Then do
adb reboot bootloader
Then
fastboot flash recovery recovery.img
Where recovery.img is the name of the recovery image you downloaded and copied to the folder with adb.exe
Sent from my HTC DNA
ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
pio_masaki said:
Debugging should be on.
Copy your chosen recovery.img to the folder where your adb.exe is, if its in the rooting folder, put them there.
For ease I would make a folder called root so its like this
c:\root
Place the adb and fastboot files in there with the recovery image.
Open a command prompt and type
cd c:\root
Type
adb devices
Should now work properly and list some numbers
Then do
adb reboot bootloader
Then
fastboot flash recovery recovery.img
Where recovery.img is the name of the recovery image you downloaded and copied to the folder with adb.exe
Sent from my HTC DNA
Click to expand...
Click to collapse
i did a lil more reading can i use A100 TWRP recovery (TeamWin Recovery Project) 2.2.0+..seems a lil more easier to be honest instead of cwm?
Cheony81 said:
ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
Click to expand...
Click to collapse
Cheony81 said:
ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
Click to expand...
Click to collapse
Once again, the folder that has adb.exe is where you need to be working from. Open a command prompt, cd to wherever that folder is, then do the commands. You can also hold shift and right click in the folder and choose command prompt to open it right there.
Sent from my HTC DNA
ok something is not right...you talking bout adb.exe.but when i look in the files that i mentioned earlier the only thing there is adb image and adb command window icon which if i click on it it runs for a sec and closes//
pio_masaki said:
Once again, the folder that has adb.exe is where you need to be working from. Open a command prompt, cd to wherever that folder is, then do the commands. You can also hold shift and right click in the folder and choose command prompt to open it right there.
Sent from my HTC DNA
Click to expand...
Click to collapse
Cheony81 said:
ok something is not right...you talking bout adb.exe.but when i look in the files that i mentioned earlier the only thing there is adb image and adb command window icon which if i click on it it runs for a sec and closes//
Click to expand...
Click to collapse
Your show extensions are off. The one that opened the prompt was it. Its not run directly, its used in a command prompt with a command. Open your prompt there or change its directory to where it is, then carry on with the instructions.
I take it all your other rooted devices had one click setups, this is a very basic device to work on, it just doesn't have a program doing it for you. This seriously should take as long as it took me to write this post to do from start to finish.
Sent from my HTC DNA
ok figured it out now i put all files together now..should i leave it in my documents or put it in my c folder..
is it power+vol up or down
I think its power on with the volume closest to the power button for fast boot, its been awhile though it may be the other one.
Sent from my HTC DNA
i just did it and showed android guy then showed him laying down with a red triangle simble coming out his stomach
Cheony81 said:
i just did it and showed android guy then showed him laying down with a red triangle simble coming out his stomach
Click to expand...
Click to collapse
Then try the other one.
Sent from my HTC DNA
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.