Database Develop

[Q] Still stuck in fastboot after flashing back original system images??

Hi Folks,
I have checked through the various threads on xda about this but cannot find an answer so please be gentle.
I mistakenly flashed an incorrect kernel and so used fastboot to try and restore my orignal system backups. Now I am stuck on Fastboot screen.
I also cannot get ADB to see my device.
I have tried the other various unbrick tools on xda but had no luck. What are my options on this one?
thanks in adance.
Cheers,
Trev

You don't use adb commands to work with fastboot, so adb devices is useless. You have to use fastboot commands. As a test run "fastboot -i 0x1949 getvar product" it should return Tate if you posted this in the right device section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Hi stunts513,
yeah its tate. I was able to use fastboot see output.
C:\ Fastboot>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.008s
C:\ Fastboot>fastboot -i 0x1949 flash boot C:\Users\ADMIN\Downloads\stock-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.828s]
writing 'boot'...
OKAY [ 0.678s]
finished. total time: 3.508s
C:\ Fastboot>fastboot -i 0x1949 flash recovery C:\Users\ADMIN\Downloads\stock-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.828s]
writing 'recovery'...
OKAY [ 0.673s]
finished. total time: 3.504s
C:\ Fastboot>fastboot -i 0x1949 flash system C:\Users\ADMIN\Downloads\stock-system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.761s]
writing 'system'...
OKAY [ 73.290s]
finished. total time: 386.067s

So is it stuck in fastboot now or does it boot loop when you get out of fastboot?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

still stuck on Fastboot my friend. :crying:

Got it sorted. After issuing reboot I immediately pulled out the usb cable. Thanks for the help. :good:

Ah sorry, was going to advise that but I'm kinda busy trying to figure out how to compile this ROM, its so different than the stuff I'm used to compile so I'm kinda lost. Anyways glad to hear you fixed it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Ah sorry, was going to advise that but I'm kinda busy trying to figure out how to compile this ROM, its so different than the stuff I'm used to compile so I'm kinda lost. Anyways glad to hear you fixed it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
im having the same problem.. however unplugging the cable right after the reboot command still doesn't help. it goes right back to fastboot no matter what

[Q]-Bootlooping/possibly bricked 7' Kindle HD

Hi folks. SNagged an "untested" kindle fire HD 7 off ebay. Wanted to try my luck with the kindle tablet's since I haven't owned or rooted any of them. Sadly, it's not working. It turns on, comes to the kindle fire logo, does a slow lens flare, goes to the fast lens flare and cycles that a bit before briefly stopping the fast moving flare and starting it all over again.
I've tried powering it down, doing the "fastboot -i 0x1949 getvar product" with no other devices attached, attaching the fire and it won't work. It boots up exactly as if I just hit power. I never get anything saying it's going into fastboot mode. The PC doesn't give me the standard "new hardware doink" either. Is this a case for buying one of those factory cables and trying that?

That command only works on the 8.9" models, you need a fastboot cable.
Sent from my Amazon Kindle Fire HD using xda app-developers app

stunts513 said:
That command only works on the 8.9" models, you need a fastboot cable.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
So for the 7 inch version, in order for me to have any hope of trying to get this thing functional is to get that factory/fastboot cable?

Yes if you have a Samsung brand value you can make one by shorting on the micro end pins 1 and 4
Sent from my XT907 using xda app-developers app

NapalmDawn said:
So for the 7 inch version, in order for me to have any hope of trying to get this thing functional is to get that factory/fastboot cable?
Click to expand...
Click to collapse
Yes, you're in a bootloop and must have a fastboot cord now. You can make one or buy one off eBay for 10 buck or so. Then try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888

LinearEquation said:
Yes, you're in a bootloop and must have a fastboot cord now. You can make one or buy one off eBay for 10 buck or so. Then try using KFFA http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Thanks. I was poking around and saw a thread where the guy mentioned selling them. I just need to find that thread again.

I haven't been able to use the KFA to get this thing out of the boot loop.
Now that I have a factory cable, I can get the KF HD 7 into fastboot mode. When I run the utility, it seems I get errors. Here's a snippet.
Code:
OKAY [ 94.745s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.273s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
finished. total time: 150.026s
Would You Like To Wipe Data And Cache (y/n) ?
erasing 'userdata'...
OKAY [ 94.740s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
finished. total time: 150.024s
rebooting...
finished. total time: 0.001s
This happens when I restore to 7.2.3 or .1 I can unplug it from the PC, reboot it and come right back to the same bootloop as before. Goes through the fast movement of light on the logo, quick black screen, back to the logo and the lights again.

NapalmDawn said:
I haven't been able to use the KFA to get this thing out of the boot loop.
Now that I have a factory cable, I can get the KF HD 7 into fastboot mode. When I run the utility, it seems I get errors. Here's a snippet.
Code:
OKAY [ 94.745s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.273s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
finished. total time: 150.026s
Would You Like To Wipe Data And Cache (y/n) ?
erasing 'userdata'...
OKAY [ 94.740s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
finished. total time: 150.024s
rebooting...
finished. total time: 0.001s
This happens when I restore to 7.2.3 or .1 I can unplug it from the PC, reboot it and come right back to the same bootloop as before. Goes through the fast movement of light on the logo, quick black screen, back to the logo and the lights again.
Click to expand...
Click to collapse
Just so I understand, you went to KFFA and choose to restore your kindle to 7.2.3 option? Using Factory Cable? Just asking because this is what I did to restore my kindle from bootloop and it worked just fine

Wondrej said:
Just so I understand, you went to KFFA and choose to restore your kindle to 7.2.3 option? Using Factory Cable? Just asking because this is what I did to restore my kindle from bootloop and it worked just fine
Click to expand...
Click to collapse
Yes. However, did you notice the errors in my code? It seems that the tool is unable to format the KD HD 7 for some reason. Do you think it's possible that once I'm in fastboot that I can issue a command via normal fastboot (from the command prompt) that will force the format?
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 55.276s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
Click to expand...
Click to collapse

NapalmDawn said:
Yes. However, did you notice the errors in my code? It seems that the tool is unable to format the KD HD 7 for some reason. Do you think it's possible that once I'm in fastboot that I can issue a command via normal fastboot (from the command prompt) that will force the format?
Click to expand...
Click to collapse
one more question? how long have you let it on "boot loop" after you tried this? If I recall corectly I took me quiet a while to boot for the first time (like 2 minutes or so) I was actually worried at the time it didn't work, but I just let it be for few minutes and it booted.

Wondrej said:
one more question? how long have you let it on "boot loop" after you tried this? If I recall corectly I took me quiet a while to boot for the first time (like 2 minutes or so) I was actually worried at the time it didn't work, but I just let it be for few minutes and it booted.
Click to expand...
Click to collapse
I admit it was about only 1 min or so only because I watched it long enough to SEE the loop. It wasn't that the boot up was taking a long time, I saw it cycle at least twice from black to slow lens flare on the logo, then the fast flare, then a quick black screen and rinse/repeat. Being somebody who's flashed a lot of roms on tabs and phones for years, I definitely am patient with a "cook" time. This didn't seem like a settling in type issues since I saw the pattern repeat at least twice.

NapalmDawn said:
I admit it was about only 1 min or so only because I watched it long enough to SEE the loop. It wasn't that the boot up was taking a long time, I saw it cycle at least twice from black to slow lens flare on the logo, then the fast flare, then a quick black screen and rinse/repeat. Being somebody who's flashed a lot of roms on tabs and phones for years, I definitely am patient with a "cook" time. This didn't seem like a settling in type issues since I saw the pattern repeat at least twice.
Click to expand...
Click to collapse
I am with you, I am just trying to eliminate the easy problems first, before we start trying crazy stuff.

Wondrej said:
I am with you, I am just trying to eliminate the easy problems first, before we start trying crazy stuff.
Click to expand...
Click to collapse
Understood. When I get home, I'll boot it back up and let it sit for 5 mins and see what happens.
I can say that at least the factory cable did put it into fastboot mode properly whereas the stock USB cables did not. Is there a fastboot command that can be done to tell it to format those areas it is having problems with? The inability to format userdata and cache worries me.

NapalmDawn said:
Understood. When I get home, I'll boot it back up and let it sit for 5 mins and see what happens.
I can say that at least the factory cable did put it into fastboot mode properly whereas the stock USB cables did not. Is there a fastboot command that can be done to tell it to format those areas it is having problems with? The inability to format userdata and cache worries me.
Click to expand...
Click to collapse
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
[B] format <partition> format a flash partition[/B]
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
AFAIK KFFA only runs fastboot commands so I am not sure if you'll get different result by using fastboot directly, also I have no idea how to format the partitions properly tbh.

Wondrej said:
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
[B] format <partition> format a flash partition[/B]
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
AFAIK KFFA only runs fastboot commands so I am not sure if you'll get different result by using fastboot directly, also I have no idea how to format the partitions properly tbh.
Click to expand...
Click to collapse
I'll try a manual fastboot format tonight. I can say that I booted it up when I got home from work and let it sit for 10+ mins. Yep, definitely still in the bootloop. Does anybody have any idea what might cause the format to think the media is invalid? Could somebody have tried to flash the wrong kind of rom to this device?

NapalmDawn said:
I'll try a manual fastboot format tonight. I can say that I booted it up when I got home from work and let it sit for 10+ mins. Yep, definitely still in the bootloop. Does anybody have any idea what might cause the format to think the media is invalid? Could somebody have tried to flash the wrong kind of rom to this device?
Click to expand...
Click to collapse
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers

LinearEquation said:
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers
Click to expand...
Click to collapse
I'll give it a try tonight!

LinearEquation said:
Use the fastboot cord and this tool http://forum.xda-developers.com/showthread.php?t=1951254 wipe first then restore. This tool works great. Sounds like someone bootlooped their tablet and called it untested because they knew it was not working proper. Their loss will be your gain.
Sent from my Amazon Kindle Fire HD running Paranoid Android [4.3 JB] using xda app-developers
Click to expand...
Click to collapse
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.

NapalmDawn said:
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.
Click to expand...
Click to collapse
This will sound repetitive but try it again. One time it took five time. Also, when it first starts, it will blink 3 times and then stay solid on the KF logo and then look like a normal boot up. Let the ROM have some time to finish cooking. If it blinks more than 5 times, its another bootloop. A bootloop is pretty much always fixable.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
---------- Post added at 02:38 AM ---------- Previous post was at 02:33 AM ----------
NapalmDawn said:
Amazingly, not even this tool fixed it. It wiped without any errors and I picked the option to factory reset with root, apex, play store and I get the same boot loops. I think this thing was held up against a magnet or something lol. I wonder what somebody did to it.
It's defintiely an HD 7 because it has the camera and the stripe on the back.
Click to expand...
Click to collapse
Just checking that you have SDK installed http://m.youtube.com/watch?v=oaNM-lt_aHw&desktop_uri=/watch?v=oaNM-lt_aHw There is a guy on here named stunts and his modified drivers have saved many a KFHD. Maybe give them a try. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers

Just curious did you try the restore tool instead of kffa yet? Second question might try installing the second boot loader and see if you can get twrp installed then push a rom to it.
Sent from my XT907 using xda app-developers app

[Q] Orange logo for 2 seconds then black screen

I've got a broken Kindle Fire HD 7 with the following problem:
When I try to power it up, I get the Orange/White logo for two seconds, then a black screen.
While the logo is on, the rest of the entire screen is lit up grey.
After it goes to black screen there is still a tiny bit of light in the corners so it is not powered down.
When I hold the power button for 10 sec the bit of light goes away.
I have a fastboot cable and during the black screen fastboot -i 0x1949 getvar product yields
product: Tate-PVT-08
I tried using KFHD_SRT_v1.3.0 to Restore-Factory Rooted with SuperSU.apk and Restore-Factory Recovery but neither had any effect.
I also replaced the motherboard with one that I bought from a seller that said it was removed from a working Kindle Fire HD but with the new motherboard I am having the exact same problem.
I am really perplexed. Could a bad LCD panel be causing this problem?
Any help would be greatly appreciated.

Anchorman42 said:
I've got a broken Kindle Fire HD 7 with the following problem:
When I try to power it up, I get the Orange/White logo for two seconds, then a black screen.
While the logo is on, the rest of the entire screen is lit up grey.
After it goes to black screen there is still a tiny bit of light in the corners so it is not powered down.
When I hold the power button for 10 sec the bit of light goes away.
I have a fastboot cable and during the black screen fastboot -i 0x1949 getvar product yields
product: Tate-PVT-08
I tried using KFHD_SRT_v1.3.0 to Restore-Factory Rooted with SuperSU.apk and Restore-Factory Recovery but neither had any effect.
I also replaced the motherboard with one that I bought from a seller that said it was removed from a working Kindle Fire HD but with the new motherboard I am having the exact same problem.
I am really perplexed. Could a bad LCD panel be causing this problem?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you try using Kindle Fire First Aide? It's got a system restore feature built into it, and it's saved my sorry butt on more than one occasion.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s

Anchorman42 said:
Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
Hmmm... It looks like the script is working, and fastboot is working too. Is it finding the images on your computer? They're .img files, and they would be somewhere in the KFFA folder.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

Anchorman42 said:
Ok, I tried using Kindle Fire First Aide and here is what I get:
9. Display the Fastboot Status
product: Tate-PVT-08
finished. total time: 0.001s
05EC000200000001 fastboot
3. Completly Restore the KFHD 7 7.2.3
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
8. Erase the Kindle Cache and User Data
erasing 'userdata'...
OKAY [ 71.909s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 55.930s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.005s]
finished. total time: 127.853s
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
The procedures are finishing almost instantaneously. This should be taking much longer. Around an hour or so just for the files to flash onto your KFHD. I would try the Kindle fire System Restore Tool again (this one is for 2012 KFHD 7 only http://forum.xda-developers.com/showthread.php?t=1951254 Same one as you tried before and use it with a fastboot factory cord.
Here is a tip you can use with the standard USB http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm If you're using a standard USB cord it will not work because you are bootlooping and the option to boot into the bootloader with a standard USB cord is gone.

LinearEquation said:
The procedures are finishing almost instantaneously. This should be taking much longer. Around an hour or so just for the files to flash onto your KFHD. I would try the Kindle fire System Restore Tool again (this one is for 2012 KFHD 7 only http://forum.xda-developers.com/showthread.php?t=1951254 Same one as you tried before and use it with a fastboot factory cord.
Here is a tip you can use with the standard USB http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm If you're using a standard USB cord it will not work because you are bootlooping and the option to boot into the bootloader with a standard USB cord is gone.
Click to expand...
Click to collapse
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

Ph0enix_216 said:
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Click to expand...
Click to collapse
I wonder what the heck Chris is doing. I hope he is well what ever he is doing these days.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Ph0enix_216 said:
An hour??? Mine has never taken any longer than ten minutes to complete!
Anyway, I think KFFA attempts to download the images from @prokennexusa's Box/Dropbox accounts, which aren't active anymore. I think that may be why flashing via KFFA isn't working. There are no images to flash.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
Click to expand...
Click to collapse
You were right, the images were not getting downloaded from the Dropbox location. But the problem was that the wget command in RunMe.bat was failing because it couldn't verify the certificate. I had to add --no-check-certificate after wget and then the image files all downloaded. It did take about 10 minutes for system.img to download.
But now that the images are available in C:\KFFirstAide the command to flash them is failing.
I copied the flash commands from RunMe.bat into a CMD window and this is what I got.
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
But if I check the Fastboot status:
C:\KFFirstAide>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
It appears the Fastboot is working, but for some reason it can't flash the partitions.
I am using a Factory Cable but I don't see why that would matter.
And remember, in my original post I said that the original motherboard was acting this way so I bought another motherboard on eBay which the seller said that it came out of a working Kindle Fire and it's doing the same thing as the original motherboard. To me, it's really strange that both motherboards are acting the same way.
Tomorrow I plan on trying what LinearEquation suggested.

Anchorman42 said:
You were right, the images were not getting downloaded from the Dropbox location. But the problem was that the wget command in RunMe.bat was failing because it couldn't verify the certificate. I had to add --no-check-certificate after wget and then the image files all downloaded. It did take about 10 minutes for system.img to download.
But now that the images are available in C:\KFFirstAide the command to flash them is failing.
I copied the flash commands from RunMe.bat into a CMD window and this is what I got.
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
But if I check the Fastboot status:
C:\KFFirstAide>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
It appears the Fastboot is working, but for some reason it can't flash the partitions.
I am using a Factory Cable but I don't see why that would matter.
And remember, in my original post I said that the original motherboard was acting this way so I bought another motherboard on eBay which the seller said that it came out of a working Kindle Fire and it's doing the same thing as the original motherboard. To me, it's really strange that both motherboards are acting the same way.
Tomorrow I plan on trying what LinearEquation suggested.
Click to expand...
Click to collapse
You could also try flashing the partitions manually:
Code:
fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"
I don't think it's a motherboard issue. I've had problems where KFFA wouldn't flash partitions, but manually flashing them myself worked fine. Anyways, that's just my two cents.

Ph0enix_216 said:
You could also try flashing the partitions manually:
Code:
fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"
I don't think it's a motherboard issue. I've had problems where KFFA wouldn't flash partitions, but manually flashing them myself worked fine. Anyways, that's just my two cents.
Click to expand...
Click to collapse
I did try flashing them manually. In my reply that you quoted, where I said:
"I copied the flash commands from RunMe.bat into a CMD window and this is what I got."
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
I'm not sure what "target reported max download size of 1006632960 bytes" means. I think it means that the partition is not big enough to accomodate the image file being flashed, but (for example) boot.img is only 8,192 bytes.
I am now going to try what LinearEquation suggested yesterday and see if that helps...

So I tried LinearEquation's suggestion to try the Kindle fire System Restore Tool again. This time I downloaded KFHD_SRT_v1.3.5 where yesterday I had used KFHD_SRT_v1.3.0.
This time when I tried Option 1 Restore-Factory Rooted with SuperSU.apk it actually appeared to flash the system.img file. It took about 5 minutes to "send" the file and then another 5 minutes to flash it. There were no error messages such as "target reported max download size of 1006632960 bytes" during the flash And the batch files echoed "Welcome Back" when it was done flashing.
So then, I tried Option 3. Restore-Factory Recovery and again both recovery.img and boot.img appeared to flash normally, but of course much quicker.
Then, I dis-connected the factory cable and powered down the Kindle and then powered it back up. Still not working. The only difference is that now, I don't see the Kindle Fire logo on the grey background. It just goes immediately to the black screen. But when I power it down by holding the power button for 20 seconds and then plug it in via the factory cable I do see the logo for 2 seconds and then black screen.
Edit: I was mistaken, I do get the KF logo on grey background when powering up the KF.
The only thing I can think of that could be a problem is that I am using my laptop with Windows 7 and the USB ports are USB 2.0. I remember reading quite a while back that you shouldn't use USB 2.0 ports. Is that still the case or have things evolved to where 2.0 is ok now?

Windows 7 is fine, and the problematic usb is 3.0 not 2.0. What exactly happened that made it get in this state to begin with?
Sent from my LG-P769 using xda app-developers app

stunts513 said:
Windows 7 is fine, and the problematic usb is 3.0 not 2.0. What exactly happened that made it get in this state to begin with?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
My mistake, I should have said that all the USB ports on my laptop are 3.0. I don't know how it got this way. I bought it on eBay thinking that I would be able to fix it without too much trouble. I used to fix a few Gen1 Kindles that were stuck on the boot logo but I have since found out that Gen2 and above are different animals.

Anchorman42 said:
I did try flashing them manually. In my reply that you quoted, where I said:
"I copied the flash commands from RunMe.bat into a CMD window and this is what I got."
C:\KFFirstAide>fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
C:\KFFirstAide>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
I'm not sure what "target reported max download size of 1006632960 bytes" means. I think it means that the partition is not big enough to accomodate the image file being flashed, but (for example) boot.img is only 8,192 bytes.
I am now going to try what LinearEquation suggested yesterday and see if that helps...
Click to expand...
Click to collapse
The "target max size" just reports the total space available to use on the device. It reports that anytime you flash anything via fastboot.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

This problem turned out to be a defective LCD panel. I got another KFHD7 and swapped the motherboards. The unit with the questionable LCD and a known good motherboard still had the original problem in the initial post. The unit with the questionable motherboard and known good LCD worked fine.

[Q] Can't flash system. Is Motherboard toast?

I have a Kindle Fire HD 7in 2012 model that is stuck on the orange/white boot logo. I have a lot of experience flashing Kindles but this is the first time I have encountered this problem. The boot and recovery partitions seem to flash ok, based on time but take a look at the time it takes when flashing system and also the time it takes to clear cache and userdata. Is this motherboard toast? Any way to save it?
fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.016s
fastboot -i 0x1949 flash recovery images/recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 2.860s]
writing 'recovery'...
OKAY [ 2.829s]
finished. total time: 5.689s
fastboot -i 0x1949 flash boot images/boot.img
sending 'boot' (8192 KB)...
OKAY [ 2.875s]
writing 'boot'...
OKAY [ 1.235s]
finished. total time: 4.110s
fastboot -i 0x1949 flash system images/system.img
sending 'system' (907264 KB)...
OKAY [316.630s]
writing 'system'...
OKAY [ 1.235s] *** This should normally take 60 to 70 seconds **
finished. total time: 317.864s
fastboot -i 0x1949 erase cache
erasing 'cache'...
OKAY [ 1.235s] ** Normally takes approx. 50 seconds **
finished. total time: 1.235s
fastboot -i 0x1949 erase userdata
erasing 'userdata'... ** Normally takes 80 to 90 seconds **
OKAY [ 1.240s]
finished. total time: 1.243s
I also tried to format the system partition and this is what I get...
fastboot format system
< waiting for device >
After waiting 15 minutes I gave up on this...
Then I tried it this way:
fastboot -i 0x1949 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.016s
Any ideas???

No, your motherboard isn't toast. Those times are around how long it should take to flash. If you didn't notice, flashing system went fine. Fastboot format is weird on the Kindle Fires (it doesn't ever want to work properly), but the reason you were stuck at the "waiting for device" prompt is because you didn't add "-i 0x1949" to the end of the command. Notice that once you did, it went through fine (well, sorta). Your motherboard is not toast. If it was, you would not be able to boot it up at all, even to fastboot mode. Pressing the power button and/or any combination of key presses would get you absolutely nowhere. I would double-check you have the right images. What exactly are the boot/recovery/system image you're flashing?

r3pwn said:
No, your motherboard isn't toast. Those times are around how long it should take to flash. If you didn't notice, flashing system went fine. Fastboot format is weird on the Kindle Fires (it doesn't ever want to work properly), but the reason you were stuck at the "waiting for device" prompt is because you didn't add "-i 0x1949" to the end of the command. Notice that once you did, it went through fine (well, sorta). Your motherboard is not toast. If it was, you would not be able to boot it up at all, even to fastboot mode. Pressing the power button and/or any combination of key presses would get you absolutely nowhere. I would double-check you have the right images. What exactly are the boot/recovery/system image you're flashing?
Click to expand...
Click to collapse
Thanks for the reply. It's definitely a KFHD7 2012 model and I am using KFHD_SRT_1.3.5. The images are Version 7.3.0. I have used these images several times in the past to restore that model.
So you don't think it's unusual that flashing the system partition only took 1.235 seconds (usually takes 60-70 seconds)? Or that erasing cache also took only 1.235 seconds (usually takes approx. 50 seconds) and erasing userdata took 1.240 seconds (usually takes 80 to 90 seconds)? I am wondering if those partitions got corrupted but I don't know how to reset them when all I have to work with is fastboot.
And the bottom line is after reflashing all the above partitions, the Kindle is still stuck on the static boot logo. It's got me stumped. Any help would be appreciated.

Anchorman42 said:
Thanks for the reply. It's definitely a KFHD7 2012 model and I am using KFHD_SRT_1.3.5. The images are Version 7.3.0. I have used these images several times in the past to restore that model.
So you don't think it's unusual that flashing the system partition only took 1.235 seconds (usually takes 60-70 seconds)? Or that erasing cache also took only 1.235 seconds (usually takes approx. 50 seconds) and erasing userdata took 1.240 seconds (usually takes 80 to 90 seconds)? I am wondering if those partitions got corrupted but I don't know how to reset them when all I have to work with is fastboot.
And the bottom line is after reflashing all the above partitions, the Kindle is still stuck on the static boot logo. It's got me stumped. Any help would be appreciated.
Click to expand...
Click to collapse
Oh. I must have missed that. That does sound weird, but I'm not sure if your partitions got corrupted. Try running "fastboot oem format -i 0x1949" (this kinda "resets" the partition table to what it should be, in case anything is weird) then flashing the images again.

r3pwn said:
Oh. I must have missed that. That does sound weird, but I'm not sure if your partitions got corrupted. Try running "fastboot oem format -i 0x1949" (this kinda "resets" the partition table to what it should be, in case anything is weird) then flashing the images again.
Click to expand...
Click to collapse
D:\KFHD_SRT_v1.3.5>fastboot -i 0x1949 oem format
...
FAILED (status read failed (Too many links))
finished. total time: 1114.006s
Hmmm. Not sure if it worked... Proceeded to reflash all partitions. Got the same results. Flashing system and erasing cache and userdata all took less than 2 seconds.

Anchorman42 said:
D:\KFHD_SRT_v1.3.5>fastboot -i 0x1949 oem format
...
FAILED (status read failed (Too many links))
finished. total time: 1114.006s
Hmmm. Not sure if it worked... Proceeded to reflash all partitions. Got the same results. Flashing system and erasing cache and userdata all took less than 2 seconds.
Click to expand...
Click to collapse
That oem format thing didn't appear to have worked. Try rebooting to bootloader and trying it again.

r3pwn said:
That oem format thing didn't appear to have worked. Try rebooting to bootloader and trying it again.
Click to expand...
Click to collapse
I am out of town for the weekend so I will try it on Monday. In the mean time, how to I reboot to the bootloader? Isn't that what happens when you go into fastboot? If not, how do I use the command fastboot -i 0x1940 oem format?

KFHD7 teamwin logo boot loop

There's a lot of similar threads on this and I have tried every method I could find and nothing has helped.
Yesterday I took a stock KFHD7 and rooted it, flashed teamwin recovery 2.6.3.1 and freedom boot 7.4.6, and then flashed CM 12.1 and the appropriate gapps. Everything was working GREAT except I had a problem downloading the Google Play Games app through the App store (Error -505) and I read the wasiest way to handle it on a new install was to just Factory Restore through CM 12.1. It wasn't until AFTER I rebooted that someone mentioned that doing that on CM 12.1 on a KFHD7 could seriously mess things up.
Now when I turn it on it shows the orange kindle fire logo, the blue kindle fire logo, then the teamwin logo, and then it flashes off briefly and goes back to the teamwin logo for a few more seconds before repeating flashing and teamwin over and over.
I was told I need to reflash the freeboot and teamwin recovery via fastboot. I had a lot of issues in that "fastboot dvices" does not return anything. "fastboot -i 0x1949 getvar product" returns that I have the Tate. Attempting to use fastboot without the "-i 0x1949" parameter causes it to display "< waiting for device >" indefinitely. adb seems to work, but any shell commands I attempt to send return that the command is not found.
So I tried this:
Code:
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash boot kin
boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.173s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 2.749s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 flash recovery
kinrecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.182s]
writing 'recovery'...
OKAY [ 0.578s]
finished. total time: 2.763s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
C:\Users\ChrisS2.HQ\Desktop\kinfire\root\stuff>
It's repeating the same behavior.
I've double checked and triple checked my drivers. The device is listed as "Kindle -> ADB Composite Device". Everythign seems to be fine on that end. I am using Windows 7 x64. I tried the fk scripts on Ubuntu with no success.
Edit: I also made my own Factory cable. Doesn't seem to have any affect on the process.

Two days of trying to figure this out and I fix it minutes after I ask for help.
I retried using the KFHD SRT v1.35 to recover the system image, deleted all user data and cache, then reformatted the /data partition. It can now boot properly into the teamwin recovery and flash ROMs as usual.
Here's a good article for people who had the same issue:
http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/