Database Info

[Tutorial] How to flash a new boot.img via Fastboot

Hey Guys,
since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode)
If you have fastboot already installed on your PC it's very quick & easy!
Pls be aware that this could damage your phone & I'm not responsible for this. so only do this if you really feel comfortable with it & you know about the risks!
First of all you need to have fastboot & adb installed, as well as the drivers for the One S. If you haven't, move on to the second post in this thread!
Click to expand...
Click to collapse
If you are on a Sense-based ROM make sure you haven't ticked the fast boot option in the settings!
Click to expand...
Click to collapse
Step 0,5
What is the boot.img?
-> basically it contains the kernel & the ramdisk. But let's hear what the pros have to say:
"The boot.img is a small(ish) file that contains 2 main parts, the kernel (the brain of the Android system) and the ramdisk (a core set of instructions and binaries that begins the boot process and controls base aspects of the system, such as mountpoints, memory management and startup services)" Source
Click to expand...
Click to collapse
Further information can be found here.
Click to expand...
Click to collapse
Do I need to flash the boot.img manually in fastboot?:
No, if you're using TWRP and are on a Hboot-version lower than 1.13
Yes, if you're using any other recovery (like CWM)
Yes, if you're using TWRP and your ville has the Hboot-version 1.13 or higher
Click to expand...
Click to collapse
1.Step
reboot your Phone into the bootloader.
This can either be done via
- powering off and keeping volume up & the power-button pressed
- the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
- via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Code:
adb reboot-bootloader
& press enter. Your One S should then reboot into the bootloader
I personally prefer one of the last two methods, depending which way occurs faster to me at that specific moment.
Click to expand...
Click to collapse
2.Step
make sure it says "Fastboot USB" like in the following picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Source = Google)
Click to expand...
Click to collapse
3.Step
Test if it your device has been detected with the following command:
Code:
fastboot devices
if it gives you an answer other than a blank one or an error there you go
Click to expand...
Click to collapse
4.Step
copy the boot.img you want to flash into the folder C:\android\platform-tools\ & then execute the command
Code:
fastboot flash boot boot.img
(if your boot.img is named differently then adjust the last part of the command)
wait for it to succeed.
if it says okay two times & the prompt reappears everything should be fine
Click to expand...
Click to collapse
5.Step
reboot your device with
Code:
fastboot reboot
Click to expand...
Click to collapse
6.Step
If you want check
Code:
Settings -> About phone -> Kernel
if it matches the boot.img you just flashed
Click to expand...
Click to collapse
The whole process should look something like this in your CMD:
Click to expand...
Click to collapse
Here you go!
Quick & easy!
When I helped please press the thanks button!
If you have any suggestions to make it even easier of found a mistake, please tell me, it's already very late in Germany
BE AWARE THAT I'M NOT RESPONSIBLE IF IT DOESN'T WORK OR BREAKS YOUR PHONE! THIS IS JUST THE WAY I UPDATE THE BOOT.IMG ON MY PHONE!

Installing ADB and Fastboot
It's actually pretty easy!
1. Step
download the Android SDK from HERE
Alternatively you can also download the USB drivers & the runtimes for adb & fastboot as a standalone as provided by Inferi0r in the 4th post:
Inferi0r said:
USB drivers only & the adb/fastboot-runtimes only
Click to expand...
Click to collapse
[Download carefully, didn't test them for viruses or (mal)function]
Click to expand...
Click to collapse
2. Step
Run the downloaded file & change the extracting-folder directly to C:\
(..this will take some time...)
You should then have a folder C:\Android
Click to expand...
Click to collapse
3. Step
If you haven't installed the One S' drivers yet, download HTC Sync (e.g. from here, or here) & install it, which will also install the drivers needed for adb & fastboot to work.
If you have them installed already, skip this one & proceed to step 4.
Click to expand...
Click to collapse
4. Step
- go to C:\Android again
- press
Code:
Win + R
on your keyboard to bring up the Run dialog
- type in
Code:
sysdm.cpl
and hit OK
- now, the System Properties panel should open. Click on the Advanced tab
- in the Advanced Tab click on Environment Variables
- at the Environment Variables window find where it says Path in the Section of System variables, click on it, and press the Edit button
- when the new window opens, type in
Code:
;C:\Android
at the very end and klick OK
- now close all the windows, that's all, you're done!
Click to expand...
Click to collapse
5. Step
- go to C:\Android\platform-tools\ again
- right-click with your mouse while pressing shift
- select "open prompt here" & then you're ready to go to.
- most common adb/fastboot commands:
- adb commands
- fastboot commands
- by entering
Code:
adb help
or
Code:
fastboot help
Click to expand...
Click to collapse
When I helped please press the thanks button!

Sticky..

Here are links to usb drivers only and adb/fastboot runtimes only.

Inferi0r said:
Here are links to usb drivers only and adb/fastboot runtimes only.
Click to expand...
Click to collapse
Thank you, will implement them later!
[edit] implemented

Nice write up so cleanly written.

Thanks!
Thanks for posting!
Anyone have any sweet boot images they want to share? I'll see what I can dig up for our screen size and post some myself soon.

Excellent post, thank you. You could also mention the easiest way to boot into bootloader: a root enabled app like Quick Boot, or even Titanium Backup has the option.
Sent from my H1S using XDA Premium.

oh finally thank you ive been trying to find how to do this
i wish HTC phones were easy as samsung phones

So boot.img is basically a kernel?

ri123 said:
So boot.img is basically a kernel?
Click to expand...
Click to collapse
basically it contains the kernel & the ramdisk. But there also are some other things:
"[boot.img is a] custom android format consisting of a 2k header, followed by a gzipped kernel, followed by a ramdisk, followed by a [optional] second stage loader" Source
Click to expand...
Click to collapse
"The boot.img is a small(ish) file that contains 2 main parts, the kernel (the brain of the Android system) and the ramdisk (a core set of instructions and binaries that begins the boot process and controls base aspects of the system, such as mountpoints, memory management and startup services)" Source
Click to expand...
Click to collapse
Further information can be found
HERE
& Here
[edit] added this to the OP

fipsib said:
... 3.Step
Test if it your device has been detected with the following command:
Code:
fastboot devices
if it gives you an answer other than a blank one or an error there you go
4.Step
copy the boot.img you want to flash into the folder C:\android\platform-tools\ & then execute the command
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
You should consider adding an extra 3.5 step like this:
Code:
fastboot boot boot.img
This step is meant to test the kernel & ramdisk before flashing it. Of course, the phone might not be fully functional because the modules in /system/lib/modules might not be paired with the kernel in boot.img. But at least you can see your phone booting!

Why do I have to do that? Can't I just flash the kernel through TWRP or CWM?

iCaptivate said:
Why do I have to do that? Can't I just flash the kernel through TWRP or CWM?
Click to expand...
Click to collapse
You need to do this due to the restrictions that are given with S-On.
The team behind TWRP somehow found a way to flash the boot.img sometimes. But for me (or my device) this didn't work.

this is very confusing to me
i wish if there was an easier way

AlxMAX said:
You should consider adding an extra 3.5 step like this:
Code:
fastboot boot boot.img
This step is meant to test the kernel & ramdisk before flashing it. Of course, the phone might not be fully functional because the modules in /system/lib/modules might not be paired with the kernel in boot.img. But at least you can see your phone booting!
Click to expand...
Click to collapse
I don't think that this is necessary as it will only confuse people not so familliar with the matter, but thank you for your input

a doubt, I have a friend who wants to put the rom CM9, the question you have is: how to flash the boot.img fastboot in ubuntu?
Thanks!
שנשלח הוז שלי באמצעות Tapatalk2

cualla84 said:
a doubt, I have a friend who wants to put the rom CM9, the question you have is: how to flash the boot.img fastboot in ubuntu?
Thanks!
שנשלח הוז שלי באמצעות Tapatalk2
Click to expand...
Click to collapse
should be exactly the same, only with the difference that the Android SDK should be located at
Code:
~/android_sdk/platform-tools/
or
Code:
~/bin/

i have a problem with step 5
i dont have a folder called "platform-tools"
i got two folders
platform
and
tools

qwerty warrior said:
i have a problem with step 5
i dont have a folder called "platform-tools"
i got two folders
platform
and
tools
Click to expand...
Click to collapse
while installing the android sdk did you download "tools", too?

problem with recovery

Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.

giganielsie said:
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
Click to expand...
Click to collapse
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.

DeuXGod said:
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
Click to expand...
Click to collapse
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error

giganielsie said:
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
Click to expand...
Click to collapse
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now

DeuXGod said:
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
Click to expand...
Click to collapse
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?

giganielsie said:
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
Click to expand...
Click to collapse
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now

DeuXGod said:
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
Click to expand...
Click to collapse
Also don't work
This is the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In that folder are all of the files I needed so it should work though he don't work
And my phone also recognize as Android ADB Interface.
Edit: It's working!!! My brother fixed it! Thanks for the replies!!!:good::victory:

Now I have recovery but now I have another problem. When I reboot my phone, I can't go anymore to recovery. I see then a green android with a open stomach. Anybody a solution? It looks like there is something went wrong with the install of the recovery but what?
And I have root permission now but with rom manager I can install recovery but when I reboot into recovery, the green android with open stomach come back...

Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! It looks like it works! Thanks for youre fast replies:good::good:

I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.

GripR said:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have just flash CWM from the fastboot, enter in recovery and do a full wipe and install another ROM or even the stock image. Don't forget to remove the system/etc/install-recovery.sh file if you flash the stock ROM so CWM won't be overwritten every time you do a reboot.

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
from the dead droid reboot with power+ vol up
enter jb and with a file manager (like es file..or something else) delete both:
-/system/recovery-from-boot.p
-/system/etc/install-recovery.sh
reboot and reinstall cwm via fastboot

Only problem with that is he will require root access to do that.
Which I am assuming he currently doesn't have.
Anyways as someone already stated. Unlock bootloader if it isn't already. That will wipe your data off the phone.
Boot or flash a custom recovery.
Flash su.zip or supersu etc to get root
Boot up and make sure you actually have root.
Do as above poster said and remove those files.
Either flash recovery from a app like goo manager or rom manager. Hell now that that I think about it. I think rom manger has the option to remove those files for you when it flashes cwm. Or reboot into the bootloader and flash the recovery with fastboot. It will stick. Keep in mind that you need to download the fastboot version of the recovery if you go that route. It will be a .img. the others will be a .zip .
If you don't know how to use fastboot. Read the quides/stickies etc.

[Q] Erased recovery

Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago

4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557

how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.

buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP

4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob

buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error

4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.

buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~

4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.

buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it

4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.

buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?

4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?

_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why

4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob

buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding

OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please

4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.

buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work

4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.

Is my Nexus 5 bricked?

Last night I tried to flash CM 11 through TWRP. I wiped factory and it failed. This morning I rebooted and no sim card or sd card could be found. I went to fastboot, tried to unroot back to stock and now my phone is stuck on boot loop. I can still boot into twrp but now my backup is missing and its not recognizing the sd. Can anyone help?

there's an sd card slot?!?

dicecuber said:
there's an sd card slot?!?
Click to expand...
Click to collapse
No, just the internal sd.

is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701

Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk

jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Thanks, trying this now.

jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
It's saying fastboot is not a recognized as an internal or external command

FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Where are these stickies at? I'm not finding one in either development forum.

You skipped a step somewhere
Which method are you using? If you are using method 2, you have to set the path (or change directory) - depending on where you installed abd/fastboot to.

Top in general and top in question&answer forum.
Sent from my Nexus 5 using Tapatalk

FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Was it necessary to be rude? Would it have been more helpful to provide a link?
Engineer4life said:
It's saying fastboot is not a recognized as an internal or external command
Click to expand...
Click to collapse
Engineer4life said:
Where are these stickies at? I'm not finding one in either development forum.
Click to expand...
Click to collapse
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701

i would also suggest you to try to use some toolkit and bring it back to factory setting and then re root it...

housry23 said:
Was it necessary to be rude? Would it have been more helpful to provide a link?
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.

Engineer4life said:
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.
Click to expand...
Click to collapse
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5

Pirateghost said:
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5
Click to expand...
Click to collapse
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'

Engineer4life said:
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'
Click to expand...
Click to collapse
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here

bilago said:
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here
Click to expand...
Click to collapse
Sorry, I used the right slashed in cmd and it's the same error

Engineer4life said:
Sorry, I used the right slashed in cmd and it's the same error
Click to expand...
Click to collapse
try making a simple folder . Move all the files from this directory to C:\nexus5\ .
open a command prompt and type this:
Code:
pushd c:\nexus5
then type
Code:
fastboot flash bootloader bootloader.img
what is the results

open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
You should be at that directory now. and it'll say
Code:
C:\image-hammerhead-krt16m
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
without having to try and navigate to them every time. This worked for me. If you have adb drivers installed correctly and the "adb version" and "fastboot devices" command both work, you're good.
EDIT : Just as a heads up, the last command "fastboot erase cache" messed up something on mine. It wouldn't hold APNs or connect to any network, so I had to run fastboot flash cache cache.img

Synyster06Gates said:
open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
Click to expand...
Click to collapse
Its a lot faster and efficient to just type
Code:
pushd c:\image-hammerhead-krt16m
Your method will not work if the user has their documents folder on another partition, which is a smart way to set up your computer.

[Q] Can't Flash 5.0 Image

I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?

ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
It means you've not copied the files into your ADB folder as it can't find the fastboot files

ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.

gamer.11 said:
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
Click to expand...
Click to collapse
This won't work if fastboot binary isn't in env PATH.
EddyOS said:
It means you've not copied the files into your ADB folder as it can't find the fastboot files
Click to expand...
Click to collapse
"Into your FASTBOOT folder". adb's got nothing to do with this.

http://forum.xda-developers.com/showthread.php?t=2513701
Follow method two in this guide.

beekay201 said:
This won't work if fastboot binary isn't in env PATH.
Click to expand...
Click to collapse
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.

Easiest way is to extract the sh1t out of the Google file until you eventually see all the img files. Then extract the fastboot zip into the same folder they're in and open a command prompt there.
Fastboot zip -
https://www.dropbox.com/s/b8wxmwfi2ekdw3a/Adb And Fastboot.zip?dl=0
Sent from my Android 5.0 Nexus 5

gamer.11 said:
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Click to expand...
Click to collapse
Because it's in your PATH.

beekay201 said:
This won't work if fastboot binary isn't in env PATH.
"Into your FASTBOOT folder". adb's got nothing to do with this.
Click to expand...
Click to collapse
People refer to the folder with ADB and fastboot in it as the ADB folder (If you had adb/fastboot in the system path this wouldn't even be required)
Do you really think I meant them to use ADB? Come on, now

beekay201 said:
Because it's in your PATH.
Click to expand...
Click to collapse
oh "env" meant environment, sorry did not understand your shot hand.
by the way OP? solved your issue?

EddyOS said:
People refer to the folder with ADB and fastboot in it as the ADB folder
Click to expand...
Click to collapse
I refer to this folder as the platform tools folder

nikon120 said:
I refer to this folder as the platform tools folder
Click to expand...
Click to collapse
Makes more sense I guess, just more to type! This is where being in PATH makes life better