Develop Bugs

Bricked Kindle, bought factory cable, got to stay in fastboot, then bricked it again

I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"

Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s

Hmmm did you try the kfu or the kindle fire unbrick utility?

Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you

You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.

three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s

When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.

Kindle HD 8.9 recovery steps:

First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.

i ****ing love you, may you breed with amany and spread your DNA far and wide

Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks

larryb1951 said:
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
Click to expand...
Click to collapse
had the same problem on windows 8.1 moved to my windows 7 box and it worked so 8.4.8 didn't kill fastboot at least

I get to.....
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
FAILED <remote: write partition>

Can anyone help?

Got my kindle back
Just want to vouch for this procedure. I followed it and got my Kindle back to its stock settings. It is 8.4.8. I was able to root it, but when I tried installing the bootloader, I must have done something wrong (wrong version maybe?). It hung on a reboot and just sat there with the orange Kindle Fire logo. Volume buttons did nothing. I was able to get it to go into fastboot, so I figured it wasn't a total loss. After trying about everything else, including using KFFirstAide just by itself, this procedure finally did the trick. I unrooted it now, and I don't think I'll make a second attempt.

what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian

I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!

mrgv said:
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
Click to expand...
Click to collapse
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.

Damocles66 said:
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Click to expand...
Click to collapse
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?

KatanAlive said:
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
Click to expand...
Click to collapse
Not sure what Kindle you have since you did not say.
The HD Kindles as far as I know will not boot into fastboot using commands so, your is normal.
Regards
---------- Post added at 07:31 AM ---------- Previous post was at 07:26 AM ----------
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
I am pretty sure your tablet is not recoverable depending on what fastboot commands you were trying when it stopped booting.
Do you remember what you were attempting to do?
If an incorrect non-signed partition was flashed to the tablet (e.g., from some other Kindle model), the tablet will be bricked.
If the wrong image was flashed to the bootloader partition, you are also bricked since the bootloader is key to turning on the tablet.
If your tablet is warm when plugged in, it means it charges at least.
Since the tablet will not turn on, or get into fastboot using the command line on your PC, there is nothing else to do.
The 8.9 tablet does not support the use of a fastboot cable.

Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers

ant17 said:
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
Click to expand...
Click to collapse
Do I need to let it update before root and twrp install?

mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
Hi, my Kindle 2nd gen 8.9" HD will not power up at all either after flashing the wrong bootloader. Did you ever figure out how to start up your Kindle. Thanks.

Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?

My 8.9" gets to the TWRP 3.0.2.0 splash screen, but not past that... adb sees the device as being in recovery, but the device doesn't respond to adb commands, and fastboot doesn't see the device.
The 2-min power button trick powered the device off, but not back on.
Any recommendations?

llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
Hi there! Can Windows 8 be installed? As?

brilliant
ibrahimsow1 said:
i ****ing love you, may you breed with amany and spread your DNA far and wide
Click to expand...
Click to collapse
simply superb , it was brutal trying to find the recovery img as all links were to dev host mostly. i got an old recovery.img file from an old zip . hey were back to stock. time to root again . thanks m8 excellent guide and work

llleonid said:
Hi there! Can Windows 8 be installed? As?
Click to expand...
Click to collapse
Hello illeonid. Yes you have to search thread for disable driver signature enforcement. There is a thread somewhere on here with how to do windows 8 driver for firehd. I haven't time just now to find it. Will post back later
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
You cannot install these on the firehd the chipset just is not capable of handling such sofware with the paltry 1gb ram being main culprit. This is mostly tied up with fireOS and system apps already

Using Mfastboot.exe to Flash a Motorola device

Mfastboot
Although Mfastboot.exe works with most Motorola Devices, the exact files and flash commands may vary, best to see specific forum/threads for the device.
I haven't updated this thread for a while.
Mfastboot still works, but the flash commands have changed for newer devices.
See Guide: Motorola Firmware
Motorola devices only.
Can be used with Windows/Linux/Mac but this thread will only have instructions for Window (10)
Instruction for using Mfastboot on Linux/Mac should be similar as standard Fastboot for Android
[UNIX][mFastboot] mFastboot on Linux and Mac OS X, and how to use it by danieliop
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS - lifehacker
Watch Videos
[Video]Using Mfastboot.exe to Unbrick a Motorola device
How to Firmware Restore your Motorola Device on Windows 10 without RSDlite by RootJunky
Download
Motorola Drivers
Mfastboot files: Mega - AFH - XDA - Drive - DevHost no longer Safe -
Firmware for your Device
Verify Files
Compare File Size with file size form download site
Use Hash Checksums
mfastboot-v2.zip (1.36 MB) MD5 Sum: 83650a3589d2ecd7c8115ce860d45a23
Install Moto Drivers
Extract files from zip
Run Motorola_End_User_Driver_Installation_....msi
Reboot PC
Setup Mfastboot.exe
Extract mafastboot.zip to a local drive
Example - C:/Mfastboot
Open start menu and type CMD
Right click on CMD > select open file location
Find cmd.exe, right click and copy
Paste into Mfastboot folder
Show known File Types
Open C:/Mfastboot folder
Select View>options>Change folder and Search options
In Folder Options Select Tab View
Uncheck Box: Hide Extensions for Known file Types
Select OK
Short Version - Flashing System Only
In some cases only System.img is necessary
Type commands
Code:
mfastboot flash system system.img
and
Type commands
Code:
mfastboot reboot
Press enter
if Device does not boot try Long Version
Long Version -Using Mfastboot to Flash Firmware
Note: The exact files needed will very by device model
Extract files from Firmware xml.zip
Copy
Code:
NON-HLOS.bin
system.img
boot.img
recovery.img
to Mfastboot folder
Boot Device to AP Fastboot Mode (Power Off, Hold Volume Down, Press power button for 2-3 secs then release)
Note Click here If you see Low Battery, Click here if you see Fastboot Reason: Sticky bit factory_fastboot
Run cmd.exe in Mfastboot folder
Type commands
Code:
mfastboot flash modem NON-HLOS.bin
Press enter
Type commands
Code:
mfastboot erase modemst1
Press enter
Type commands
Code:
mfastboot erase modemst2
Press enter
Type commands
Code:
mfastboot flash system system.img
Press enter this may take several minutes to finish and be flashed in several segments.
Type commands
Code:
mfastboot flash boot boot.img
Press enter
Type commands
Code:
mfastboot flash recovery recovery.img
Press enter
Type commands
Code:
fastboot erase cache
Press enter
Optional Data Wipe: Type commands
Code:
fastboot erase userdata
Press enter
Type commands
Code:
mfastboot reboot
Press enter
Device should boot normally, If not see RSD Lite or House of Moto

Troubleshooting
Q1: Error: Cannot load system.img: Not enough space.
Solution: try flashing system.img in chunks with
Code:
mfastboot flash system system.img -P
- Thanks to @Merconium for the tip​
Error: UTAG "bootmode" configured as fastboot
Solution 1:
Code:
fastboot oem fb_mode_clear
fastboot reboot
Solution 2:
Code:
fastboot erase motoboot
fastboot flash motoboot motoboot.img
fastboot reboot

Credit: [GUIDE][FAQ][KK] How to Root, Boot Unlock & More by ATTACK

Saved #4

Saved #5

AndroidDude7 said:
Ah okay, will you send a link to me when you do?
Click to expand...
Click to collapse
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device

sd_shadow said:
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device
Click to expand...
Click to collapse
Thanks so much!

sd_shadow said:
Video up
[Video]Using Mfastboot.exe to Unbrick a Motorola device
Click to expand...
Click to collapse
So I just did as you showed in the video but it said unable to partition 'system.img' or something like that

AndroidDude7 said:
So I just did as you showed in the video but it said unable to partition 'system.img' or something like that
Click to expand...
Click to collapse
I would try RSD Lite.

THANK YOU very much!!!!!!!! You saved my life, when I didn't know what else to do (RSD lite didn't recognice my device and I coudn't flash anything by twrp). You're amazing and I can't comment your video so... Awesome post

Sadly to say, but seems like mfastboot is outdated for now. I get error trying to flash SU6-7.7 ROM for Droid Maxx. RSD Lite 6.2.4 is ok.
e:\Motorola\XT1080\QLOAD_firmwares\CFC-obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
sending sparse 'system' (768973 KB)...
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
OKAY [ 49.390s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.967s
Click to expand...
Click to collapse

s5610 said:
Sadly to say, but seems like mfastboot is outdated for now. I get error trying to flash SU6-7.7 ROM for Droid Maxx. RSD Lite 6.2.4 is ok.
e:\Motorola\XT1080\QLOAD_firmwares\CFC-obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
sending sparse 'system' (768973 KB)...
error: write_sparse_skip_chunk: don't care size 524509064 is not a multiple of the block size 4096
OKAY [ 49.390s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.967s
Click to expand...
Click to collapse
I may need to update thread
to something like this
http://forum.xda-developers.com/showthread.php?t=2542219
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot[/QUOTE]
Sent from my XT1080 using XDA Labs

sd_shadow said:
I may need to update thread to something like this
Click to expand...
Click to collapse
LOL. I found the cause. Being Moto enthusiast I'm using mfastboot of latest version renamed to "fastboot.exe" for very long time, but recently copied foreign file and mixed up with mine, so that was the cause
Thanks for the hint!

added How to Firmware Restore your Motorola Device on Windows 10 without RSDlite
Rootjunky.com

I have to start the phone manually
I´ve made my phone run, but when I turn it on, it boots in bootloader mode and I have to start the phone manually

UTesla said:
I´ve made my phone run, but when I turn it on, it boots in bootloader mode and I have to start the phone manually
Click to expand...
Click to collapse
no errors?
what is after boot reason?
which device?

But my phone's ROM doesn't have a system.img file. The files in it are shown in the picture.

But my phone's ROM doesn't have a system.img file. The files in it are shown in the picture. Please help quick...

YM_SNIPER22 said:
But my phone's ROM doesn't have a system.img file. The files it have are shown in the picture. Please help quick...
Click to expand...
Click to collapse
Change the file extension for system_signed so it's
system_signed.img
Sent from my sailfish using XDA Labs

Thanks sd_shadow!!!!!!!!!!!! You saved my phone again!!!!!

Install TWRP and then to root.

Hello please can anyone advise me and forgive any wrong terms..
I am trying to push twrp to my lg g4 H815 20g using adb and fastboot but everytime it comes back with
error: cannot load 'twrp.img': No such file or directory
PS C:\Users\Anthony\Desktop\ADB>
i have tried renaming twrp file to various things and changing the command fastboot flash twrp.img or fastboot flash recovery.img
but i keep getting errors of one discription or the other..
I have followed guild after guild but still not made the magic happen..
Bootloader is officially unlocked via LG and twrp for lg g4 downloaded from twrp site.
Been trying for two days to install a recovery so i can also root but having no luck.
please any help or advise would be appreciated..

you must put the "twrp.img" into to your "ADB" folder and then exec this:
Code:
fastboot flash recovery twrp.img

Hi thanks for your help
yes I have the img file in adb/fastboot folder and been doing this and still comes back in cmd as no such file etc..
Tried renaming twrp img file and changing fastboot flash line to match but still no joy..
Tried earlier g4 twrps same outcome it’s as if downloaded recovery’s are corrupt or something as they don’t appear to be being seen..
What is best name for the twrp image or do you leave it as it came downloaded and run the
fastboot flash recovery twrp.img Regardless of what twrp called when downloaded..
Thanks

Have you changed directory to the sdk folder? Or shift + right clicked in folder "open cmd here"?
The command is "fastboot flash *whatever recovery is called in adb folder*"
I ended up changing the name to "twrp3.1.1" or whatever cause it had a hell of a name when downloaded. Just name whatever you want as long as you call it same thing when flashing.
Make sure you also have a copy of it on your SD too because it wont stick and when you reboot to the recovery you then need to reflash the image from in there.

Hi I think it was successful i changed name of twrp on second attempt and it seemed to work..
only problem was when i tried to manually boot into recovery via volume down and power i did something wrong and accidentally reset the dam thing instead of booting into twrp......will have to do it all over again but hopefully i have it sorted..
PS C:\ADB> adb reboot-bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
PS C:\ADB> fastboot flash recovery twrp.img
error: cannot load 'twrp.img': No such file or directory
PS C:\ADB> fastboot flash recovery twrp-3.1.1-1-g4.img
target reported max download size of 536870912 bytes
sending 'recovery' (33952 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.219s
PS C:\ADB> fastboot reboot
rebooting...
finished. total time: 0.031s
PS C:\ADB>

Hello! I reopen this tread.. I have an issue with flashing twrp, via adb I start into bootloader, but when i put the command to flash it.. <waiting for device>. Why?

"cannot load recovery.img.IMG" LineageOS, Pixel 4

Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards

caraman said:
Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards
Click to expand...
Click to collapse
Ok, I managed the problem, I guess.
I startet power shell from the "platform tools" folder.
Now there is a other issue:
PS C:\Program Files\platform-tools> fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.535s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.836s
PS C:\Program Files\platform-tools>
The problem seems to be the partition, but I have no idea where to start troubleshooting...
Still reaching out to you for a little help, please...
Thx, regards