Database Develop

[Q] Harmless fastboot logo

Hi all,
I tried to install a 2nd bootloader on my rooted device (KF HD 7" - 7.4.6) according to this thread: http://forum.xda-developers.com/showthread.php?t=2128848, but I can't manage to make fastbooot mode work, even using a fastboot cord.
With the Kindle powered down, I type "fastboot -i 0x1949 getvar product" into a cmd window on my PC and it returns with: < waiting for device>
When i connect fastboot cable to the Kindle, it reboots to a "FASTBOOT kindle fire" logo.
Terminal window shows < waiting for device> and nothing else.
Device isn't stuck, anyway; if I power it off, unplug the cable and power it on, kindle works normally.
KFFirstAide won't help, too.
Any advice, please ?
Thanks

Sounds like you just need to install the driver for fastboot, while the device is in fastboot, look in your device manager, find the device with a triangle next to it, right click it and hit update driver. Download the driver in my signature and unzip it, and tell the update driver window to search the folder you extracted the driver in my signature to, it should install and the fastboot commands will then function.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Type. fastboot devices
And check if it returns any code/value.
If it doesnot return anything then your drivers are not working properly.
Go to Computer Properties>>device mamagment>> And check if it shows ur device fastboot drivers.
If it is not shown then plug out ur usb cable>>restart ur pc>>plug in the usb in usb port other than you pluged before.. and inatall your fastboot drivers.
If you don't have fastboot drivers. Googe it.
-------------------------------------
Hit THANKS if I Helped. :thumbup:

stunts513 said:
Download the driver in my signature and unzip it, and tell the update driver window to search the folder you extracted the driver in my signature to, it should install and the fastboot commands will then function.
Click to expand...
Click to collapse
Hi and thanks
It works: I updated the driver and now PC identify my kindle in fastboot mode as "Tate ...".

uhmblues said:
Hi and thanks
It works: I updated the driver and now PC identify my kindle in fastboot mode as "Tate ...".
Click to expand...
Click to collapse
Good deal, now use KFFA http://forum.xda-developers.com/showthread.php?t=2096888 Use this to restore, root, and Gapps and remove OTA updates. Use the thread Stunts posted above to install 2nd bootloader/TWRP or this thread http://forum.xda-developers.com/showthread.php?t=2271909 One is manually (recommended) and the other is by flashing which works just fine but remember to put a ROM on your SD disk before flashing as well or you may have another bootloop.

LinearEquation said:
Good deal, now use KFFA http://forum.xda-developers.com/showthread.php?t=2096888 Use this to restore, root, and Gapps and remove OTA updates. Use the thread Stunts posted above to install 2nd bootloader/TWRP or this thread http://forum.xda-developers.com/showthread.php?t=2271909 One is manually (recommended) and the other is by flashing which works just fine but remember to put a ROM on your SD disk before flashing as well or you may have another bootloop.
Click to expand...
Click to collapse
Hi,
2nd-bootloader, TWRP and CM10.1 up and running!
Can't connect to wi-fi network, so far (static IP), but I guess I'll find an answer searching the forum.
EDIT:
Wi-Fi now ok!

Kindle Fire HD7 red screen

So I was trying to install TWRP to my Kindle Fire HD7. I had successfully rooted and was using FireFlash to flash the bootloader.
When I pressed boot to recovery the device rebooted showed the kindle logo and then a red screen.
I tried making a fastboot cable but could not get the device to show up in ADB devices. Am I totally boned?
I have links to the directions I followed and a gif of the logo and red screen but I cannot post them since I'm new.

I had this issue also, I just made a fastboot cable, plugged it in and flashed stock files, I then rerooted, installed TWRP, 2ND bootloader, then CM11, finally with PAC-rom.
Sent from my Kindle Fire HD 7 running PAC-man

I can can agree with wire55. Have to have a fastboot cable to fix this. Reflashed stock then created my own personal port ROM.
Sent from my Kindle Fire HD running a Personal Ported Rom

I made a fastboot (by jumping pin 1 and 4 on a microusb) cable but it shows the device as disconnected in Device Manager.
Here is what it looks like when I turn it on i.imgur.com/TSUHsjW.gif

you dont use adb commands with fastboot mode, you use fastboot commands with fastboot mode. Try "fastboot -i 0x1949 getvar product" and see if it reports back. If it does all you will need to do is flash the older bootloader for your device first(check the md5sum plz so you don't hard brick), then restore with kffa or srt. Fireflash method should work fine now for sure once you have flashed the older bootloader.

concerning rdwidam
It says <waiting for device>
I will try again tomorrow, my friend is bringing over a fastboot cable that we know is working.
I'll report back if there is progress. Thanks.
stunts513 said:
you dont use adb commands with fastboot mode, you use fastboot commands with fastboot mode. Try "fastboot -i 0x1949 getvar product" and see if it reports back. If it does all you will need to do is flash the older bootloader for your device first(check the md5sum plz so you don't hard brick), then restore with kffa or srt. Fireflash method should work fine now for sure once you have flashed the older bootloader.
Click to expand...
Click to collapse

frakkingcylon said:
It says <waiting for device>
I will try again tomorrow, my friend is bringing over a fastboot cable that we know is working.
I'll report back if there is progress. Thanks.
Click to expand...
Click to collapse
ok that's good, if the command still doesn't respond after it says fastboot mode on the screen, then go to the device manager and look for a device with a yellow triangle next to it, once you find it download my drivers in my signature, extract them somewhere, and right click the device and hit update drivers, point it to where you extracted mine and let it install. If you are on windows 8 you will have to disable driver signature enforcement first.

OK, I got a fastboot cable but still no luck. Nothing shows up in device manager and no response to fastboot commands. I think I'm going to throw my self on the mercy of Amazon.

frakkingcylon said:
OK, I got a fastboot cable but still no luck. Nothing shows up in device manager and no response to fastboot commands. I think I'm going to throw my self on the mercy of Amazon.
Click to expand...
Click to collapse
So the fastboot cable isn't throwing it into fastboot mode, it is staying at a red screen? You are positive the fastboot cable is a fastboot cable? And i have to ask this even though its stupid but you are positive it was a kindle fire hd 7 and not an 8.9"? The fastboot cables don't work on 8.9" models is why i'm asking, those will go into fastboot with the command i mentioned but its slightly more complicated than that, the device would show up for a brief moment then disappear when turned on.

It is possible our fastboot cable is not working. I will try another one today. I measured the kindle and the view-able screen is 7 inches diagonally, while the whole body including the bezel is 9 inches.
stunts513 said:
So the fastboot cable isn't throwing it into fastboot mode, it is staying at a red screen? You are positive the fastboot cable is a fastboot cable? And i have to ask this even though its stupid but you are positive it was a kindle fire hd 7 and not an 8.9"? The fastboot cables don't work on 8.9" models is why i'm asking, those will go into fastboot with the command i mentioned but its slightly more complicated than that, the device would show up for a brief moment then disappear when turned on.
Click to expand...
Click to collapse

Ok, success! I got out my soldering iron and made a working fastboot cable. Now my kindle turns on and shows a fastboot logo on screen, and I have a device called Tate-PVT-08 in Device Manager. So I installed the android drivers to allow me to use fastboot commands. Then I used KFHD_SRT tools to restore the Recovery and Factory image.
Thank you everyone for all your help and knowledge. I was freaking out a bit, but all is well.

[Q] stuck at kindle fire logo! never been rooted! help!

just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.

joeyx2 said:
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
Click to expand...
Click to collapse
ok well in either situation your going to need a fastboot cable/adapter, i recommend getting the blackhat adapter mentioned in hashcodes 2nd bootloader + twrp tutorial. Now for the other thing i need to know, is this a 2012 or 2013 model? (2013 has no front facing camera)

It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.

joeyx2 said:
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
Click to expand...
Click to collapse
Ok lemme grab 2 links you will need.
The thread i was talking about it this: http://forum.xda-developers.com/showthread.php?t=2128848
I personally recommend a custom rom over amazon os so that tutorial could be useful to you in the future should you decide to flash a custom rom on it. There's a link towards the top that goes to the site where you get the fastboot adapter.
Alright and secondly you will need this: http://forum.xda-developers.com/showthread.php?t=2096888
Read its instructions or you might have issues. Also when you plug in your kindle with the fastboot adapter it will show up as a tate device in the device manager, download the drivers in my signature and extract them somewhere on your computer, then in the device manager right click the tate device and hit update drivers and choose a place to search for them and choose where you extracted my drivers and it should install the drivers. If you are on windows 8 you will have to disable driver signature enforcement first though. Once drivers are working you should be able to restore with kffa.

well i ordered the fastboot adapter and it does go into fastboot mode but i have tried a few utilities and they all seem to blow right threw the process. its like it seeing the phone but not doing anything. the only thing i can think of is USB debugging was not turned on and that may be why i cant get it to act right. of course i cant turn it on cause i'm stuck at the logo so is there a way around that or is there a program like Samsung has called Odin that i can use to flash stock everything on?

Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.

joeyx2 said:
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Kffa was one of the links I sent you.... download and extract it. Shift + right click it's folder and hit New command window here. Then run that command I mentioned.
Sent from my LG-P769 using Tapatalk

i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.

joeyx2 said:
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
Click to expand...
Click to collapse
well the good news is that means fastboot is working, it only is called a tate device in the device manager initially, once you isntall th edrivers it will show up a s a adb interface which is confusing becuase you don't use adb with fastboot. Anyways you should be able to attempt manualyl flashing the device from that command prompt now using certain commands like
Code:
fastboot -i 0x1949 flash <partition name> imagename
so something like
Code:
fastboot -i 0x1949 flash system system.img
it could be that kffa failed to retreive the files or something so it dint flash, sometimes its download links don't work, try srt i think linear posted the link to it, it might actually work out of the box.

Stuck in Teamwin after system restore

I just gave my KF HD 7" to my friend and he wanted me to set it back up as a KF since i had Cyanogen Mod cm-12.1-20160126-NIGHTLY installed on it but haven't used it in a while (read 1-2 years). He was messing around with it before i could get to it and thought hitting Restore to Factory settings would fix it. The device is now stuck on a flashing teamwin logo screen and wont go any further no matter what i've tried. My computer wont recognize the kindle to let me in from cmd so i've reached the limits of my modding knowledge. Could someone please point me in the right direction so i can fix this for him.

If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)

Or once you get fastboot working you could use the SRT tool to flash it back to stock with root.

install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?

TheN3wguy said:
install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?
Click to expand...
Click to collapse
Are you running Windows 8, 8.1, or 10?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Are you running Windows 8, 8.1, or 10?
Click to expand...
Click to collapse
Oh god sorry i thought i had said im running windows 10

TheN3wguy said:
Oh god sorry i thought i had said im running windows 10
Click to expand...
Click to collapse
No worries. All you need to do to get the fastboot drivers to install is to follow these instructions to temporarily disable driver signature enforcement. Once you've done that, install the drivers and reboot. After that, fastboot should recognize the kindle.

Above steps worked and KF is now working correctly thanks!

monster1612 said:
If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)
Click to expand...
Click to collapse
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after

AndroidLove231 said:
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after
Click to expand...
Click to collapse
Once you're in fastboot mode (rebooting into the bootloader from Android, for example), does fastboot -i 0x1949 devices show that the Kindle's connected?

Kindle Fire HD 7 2012 keeps rebooting

Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.

Gospelalex said:
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Click to expand...
Click to collapse
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."

vasolini said:
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
Click to expand...
Click to collapse
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...

Gospelalex said:
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Click to expand...
Click to collapse
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413

vasolini said:
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
Click to expand...
Click to collapse
Can`t install them - install failed.

Gospelalex said:
Can`t install them - install failed.
Click to expand...
Click to collapse
Got another cable. Was able to get to fastboot. But couldn`t get past it. Device was shown as tate unrecognized. Pushed to install driver and made it recognized by pc. Tried kindle fire utility v099 to run recovery. The kindle gone into reboot. So now it reboots into main loge, then changes into fastboot loge and then going into continuous reboot again. Windows in the same time stop recognize it. Shows it in usb unidentified for a second because it switches on and off again.
Update:
Managed to return it into fastboot. But in cmd when i run adb.exe devices there is nothing.

I know how to fix this problem. I ran into this 10 times before Android Studio suddenly went through my head.
In order to install the Kindle Fire ADB Drivers, you need to download and install the Android SDK Manager from Google Inc. Then when you install those drivers I mentioned earlier, you won't get errors. It's so weird.
You can try using the Ultimate Unbrick Tool, but I forgot the download link for it. There should be a thread about it here on XDA.
Lots of advanced technical stuff. I suck at explaining without making it a very long explanation because then people stop reading after 10 seconds.