Related
Hello,
Let me start by saying I have looked a searched through several other threads but cannot seem to find anything that mimics my problem 100%. I had rooted the Kindle Fire HD 7" a few weeks ago and have been going along with no problem. One day (cannot remember what I installed) the KFHD crashed on me and wanted me to Restore the device in a "download mode" type of screen (used the volume buttons to select restore and power to confirm selection.) The device restarted just fine and was working normally. I went through the KFFirstAide root process again, root checker told me it was rooted. Starting using the options in KFFA to diable OTA, install play store, install google apps, installed Holo Launcher.. Some of the programs did not seem to install properly and didn't like the way things were behaving so I went to the Settings/Device/Restore to Factory Defaults...
After that process finished I am not at an Android setup screen. It has a blue Welcome at the top, select Language below that, Start below that, and a green outlined Android guy below that. When I hit start it says Just a sec.... and eventually get the message Setup Wizard has Stopped.. I can no longer see Kindle Fire ADB in the Device Manger.. Nothing seems to work on KFFA.. I have tried using the fastboot command in a command prompt (says waiting for device) and never does anything..
Basically I would like to know, what steps I may have to take to get the device to load properly again, and hopefully root the device again. IIRC the software version I last saw was 7.3.1...
Thank you for your time and assistance and appologize if it has been discussed before, but I just couldn't seem to find it and not sure what this problem is called to be able to properly search for it..
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Krsmqn said:
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Click to expand...
Click to collapse
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
When I hold one of the volume buttons and press power on it says Safe Mode at the bottom of the screen. Might there be something I can work with in that? Is there another boot method similar to "download" mode on the GalaxySIII?
jhutch825 said:
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
Click to expand...
Click to collapse
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Is there a way to make on or do I have to order it?
Just ordered a factory cable ... what should I do when I get it?
onemeila said:
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Click to expand...
Click to collapse
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
codepoet82 said:
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
Click to expand...
Click to collapse
Ok. I will try that forum when it arrives.. To the best of my knowledge, I had not created a backup at any time so I will search out something from the Recovery Thread.
Thank you
-Joe
I am just 100% confused now.. I have searched and searched and everything I am reading is just making me more confused.
The cable will put the device into fast boot and will show up in Device Manager as an ADB Device.. I ran option 3 on KFFA and I don't believe the entire system image downloaded as now I am stuck on a screen with a red triangle asking to reboot or restore the device. Neither option does anything.
I have looked in recovery threads for fresh stock images but only find links and directions to TWRP.. Which, if I understand correctly, needs a 2nd bootloader.. And still will need a fresh stock image from amazon. Also, in KFFA it says to connect the device with a normal cable, not fastboot cable, in ADB mode for TWRP and the second bootloader.. I cannot get into the KF to enable ADB like it asks because I cannot get anything to load..
I have downloaded kfhd7-amazon-os-7.3.1 from goo.im and it comes in a zip file. I am not really sure of what to do..
I looked in the Android Development section of this forum and there are only 18 threads that don't talk about fastboot either. Do I need to go to a general Android Development section, not in the Kindle Fire Forum Sections?
I just want to go back to 100% factory original and start over from there..
Also, the KindleFireFirstAide dropbox seems to be overloaded and suspended, so I cannot get the images from there at the moment through their tool.
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
-a- said:
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Solved
Found a link, finally, to onemeila's KFHD System.img Restore tool... Used the fastboot cabled and got it installed and everything seems to be running flawlessly.
Same Story Here...
jhutch825 said:
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Click to expand...
Click to collapse
Hello, after looking through many, many threads..I have finally found this one. Same story here..I have not order the factory cable. I have the original cable that came with my kindlehd. Before I go and buy the cable I wanted to see if this question can be addressed?
Dnoob, it's been a while don't remember the solution but I did get a factory cable and worked everything out through fast boot
Sent from my Amazon Kindle Fire HD using Tapatalk now Free
Hello.
After hours of struggling and Googling (and reading mostly from this forum) I managed to root my KFHD 7.4.6 using bin4ry method. I have two questions about where I'm at right now.
Question 1: While struggling to get adb to recognize my KF, I realized that the problem was quite simple: after installing the special adb drivers, I would plug the Kindle back in and Windows would recognize the device and install the Microsoft drivers - completely ignoring the driver I had just installed. The only way I managed to get around this was to quickly interrupt Windows 7's driver installation and tell it to NOT install drivers from Windows Update.
However, I'm sure there must have been a more elegant way of accomplishing this. What would have been the correct way to do this?
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Thanks! :good:
SpidaFly said:
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Click to expand...
Click to collapse
I just found this:
http://forum.xda-developers.com/showthread.php?t=2271909
So the answer to my question appears to be "YES", correct? It appears that I need to flash back to 7.2.3?
Question 1 still remains unsolved.
Well you could downgrade it, I don't know if the latest update causes problems, but the thing that needs downgrading isn't the os, its the bootloader. I suggest the fireflash method in seokhuns tutorial, the one you linked. Just make sure to check the first box at the top in fire flash or you will have a red screen brick, which requires a fastboot cable to fix. Also I have never heard of windows update having drivers for the kindle, I mean I usually hit skip anyways, I believe the more elegant solution may have come with kindle fire first aid, not positive though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks!
I'm having another little inconsistency now.
I disconnect and power off my KF.
I run in cmd: fastboot -i 0x1949 getvar product
It says < waiting for device >
I then plug in my (powered off) KF, and it boots up NORMALLY, and fastboot doesn't return the expected tate-xxx.
Any ideas why?
My ADB is seeing the device. (ie. adb devices is returning one device).
Your fastboot drivers aren't working.
soupmagnet said:
Your fastboot drivers aren't working.
Click to expand...
Click to collapse
Indeed. Can this be solved by wiping existing drivers and reinstalling Amazon's USB drivers from sdk/extras/amazon ?
EDIT: I've attempted reinstall twice with no improvement. ADB works, fastboot won't.
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
SpidaFly said:
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
Click to expand...
Click to collapse
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
soupmagnet said:
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
Click to expand...
Click to collapse
Sounds good, thanks. I'm following that tutorial even though it's for 7.4.3, and I'm on 7.4.6. I hope that doesn't cause any issues - but 7.4.6 looks like it's pretty new, so I don't see other options.
Ok - I've followed the aforementioned tutorial precisely up to step 4. When I try to boot the kindle up, it shows orange logo, then blue logo, then looks like it's trying to boot normally, then sends me into TWRP.
Is this what is called "boot loop"?
At this point my PC doesn't see the sdcard so I can't get CM/Gapp copied over.
Would it be safe to push CM & Gapp to the sdcard using adb, then resume with TWRP?
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
SpidaFly said:
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
Click to expand...
Click to collapse
This ended up working.
However, now with CM 10.1, my PC isn't recognizing the device for MTP. It still does recognize it as an ADB device, but ADB doesn't see it.
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Got it working. Basically just uninstalled the existing drivers and reinstalled standard drivers. Works like a charm. I love CM, this is great! Thanks all, for the help!
I'll worry about getting adb going again later.
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.
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?
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.