I flashed a rom not compatible with my device and it bricked it. I later got a fast boot cable and after some research tried to fix it but just made it worse. When I connect it to the the computer it gose to the kindle logo to the fast boot logo to a black screen on the fast boot logo it connects to the computer but then at the dark screen it deconnects. Can someone please help me fix this?
OK so it will briefly go into fastboot mode and is detected by the PC in fastboot mode but then keeps rebooting? I can only assume something is messed JP with either the boot.IMG or bootloader, the good news is it might be fixable, the bad news is if what I want to recommend doing fails you could be left with a hard brick depending on what you flash. I suggest using Ubuntu 13.10 since I thinks its got a faster response time and no issues like installing the fastboot driver when the device is only briefly showing up (as opposed to windows). Then after installing the android-tools-fastboot package from apt or w/e I would recommend attempting to just flash the bootimg of a ROM meant for your ROM, like the freedom boot image or a cm boot.IMG. if you can get it to say flash success full after plugging it in when it says waiting for device, you may have some good results. Since this occurred after a ROM flash attempt I'm thinking this is more likely the bootimg rather than the bootloader. As a test run you could try "fastboot -i 0x1949 getvar product" and see if you can get it to respond. Bootimg bricks are a bit foreign to me, I've heard people say they have hard bricked kindles with bad bootimg's, but that confused me all the note since the bootloader loads either fastboot or the boot.IMG, not to mention I built a ROM and in the testing stages had issues making a suitable bootimg for the kindle and it just made the kindle pop into fastboot mode.
Sent from my Amazon Kindle Fire HD using Tapatalk
kindle connection
stunts513 said:
OK so it will briefly go into fastboot mode and is detected by the PC in fastboot mode but then keeps rebooting? I can only assume something is messed JP with either the boot.IMG or bootloader, the good news is it might be fixable, the bad news is if what I want to recommend doing fails you could be left with a hard brick depending on what you flash. I suggest using Ubuntu 13.10 since I thinks its got a faster response time and no issues like installing the fastboot driver when the device is only briefly showing up (as opposed to windows). Then after installing the android-tools-fastboot package from apt or w/e I would recommend attempting to just flash the bootimg of a ROM meant for your ROM, like the freedom boot image or a cm boot.IMG. if you can get it to say flash success full after plugging it in when it says waiting for device, you may have some good results. Since this occurred after a ROM flash attempt I'm thinking this is more likely the bootimg rather than the bootloader. As a test run you could try "fastboot -i 0x1949 getvar product" and see if you can get it to respond. Bootimg bricks are a bit foreign to me, I've heard people say they have hard bricked kindles with bad bootimg's, but that confused me all the note since the bootloader loads either fastboot or the boot.IMG, not to mention I built a ROM and in the testing stages had issues making a suitable bootimg for the kindle and it just made the kindle pop into fastboot mode.
Sent from my Amazon Kindle
Can you list out a series of steps for me to follow so that I can try it out. If not my kindle doesn't work anyway so o well but please list out some steps and I will try that out.
Click to expand...
Click to collapse
OK I' assuming that at this point you never see the blue logo when you try to boot normally. Go grab copy of system restore tool for your kindle and stick it on a flash drive if you have one, we only need the bootimg it includes. Go grab a Ubuntu 13.10 live CD and either burn it to CD or make a bootable usb. Now boot into Ubuntu live os and copy the boot.img from SRT to the desktop. Now launch a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
cd Desktop
fastboot -i 0x1949 flash boot boot.img
At this point you should be able to plug the kindle in with a fastboot cable when it says waiting for device and see if fastboot will successfully flash the boot partition.
I hope this will fix it, normally such behavior would make me think that the bootloader needs reflashing but a ROM flash shouldn't have touched the bootloader itself so I'm inclined to think its a bad boot image. Also not positive if that apt-get command has the correct package name, I don't have my laptop booted into Linux right now so I can't check, if it says something like "package not found" then tell me and I will look it up, might also be in a repo that's not defaultly enabled on Ubuntu.
Yay I retyped this post, if it doesn't post again I'm going to throw this kindle...
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK I' assuming that at this point you never see the blue logo when you try to boot normally. Go grab copy of system restore tool for your kindle and stick it on a flash drive if you have one, we only need the bootimg it includes. Go grab a Ubuntu 13.10 live CD and either burn it to CD or make a bootable usb. Now boot into Ubuntu live os and copy the boot.img from SRT to the desktop. Now launch a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
cd Desktop
fastboot -i 0x1949 flash boot boot.img
At this point you should be able to plug the kindle in with a fastboot cable when it says waiting for device and see if fastboot will successfully flash the boot partition.
I hope this will fix it, normally such behavior would make me think that the bootloader needs reflashing but a ROM flash shouldn't have touched the bootloader itself so I'm inclined to think its a bad boot image. Also not positive if that apt-get command has the correct package name, I don't have my laptop booted into Linux right now so I can't check, if it says something like "package not found" then tell me and I will look it up, might also be in a repo that's not defaultly enabled on Ubuntu.
Yay I retyped this post, if it doesn't post again I'm going to throw this kindle...
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Can you link me to the system restore tool kit I can't find it . Also it said package not found, PLEASE HELP.
Checked on Ubuntu package list and the name was that, still haven't been in Linux to verify it.
Heres the tool, if your on a 7" then this should be what i was talking about: http://forum.xda-developers.com/showthread.php?t=1951254
I will have to check what repo that package is from, because I remember Ubuntu doesn't always have all the default repos enabled, might have to enable it in the manager, would be simpler if it came with synaptic still...
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Checked on Ubuntu package list and the name was that, still haven't been in Linux to verify it.
Heres the tool, if your on a 7" then this should be what i was talking about: http://forum.xda-developers.com/showthread.php?t=1951254
I will have to check what repo that package is from, because I remember Ubuntu doesn't always have all the default repos enabled, might have to enable it in the manager, would be simpler if it came with synaptic still...
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you soon much I will definitely try it out. What is a repo package though and how do I install it to read the command for the fast boot download.
OK put simply ubuntu uses a very nice package management system called apt, it basically connects to repositories set in a file that have tons of precompiled programs and such for that specific version of Ubuntu or more broadly Linux. It retrieves some manifest of all the packages in each repo, each package has a specific name. If you want to use a better interface try typing this, "sudo apt-get install synaptic" then run "sudo synaptic" and you can search for fastboot in the nice visual package manager. Sorry I haven't been in Linux, I have left Firefox running with a form for a job application up waiting for some info I need and I don't want to reboot and have to fill it out again. I will boot my desktop up into Linux tomorrow if I can, I may be going out to do something though.
Sent from my Amazon Kindle Fire HD using Tapatalk
ok i finally rebooted into linux, it turns out teh package is indeed called android-tools-fastboot, so that being the case open up the settings app and click software and updates and everything on the first tab under downloadable from internet should be checked with the slight exception of source code which for me has a line through it when you try to check it off, it should as k you to reload, you can do that or run "sudo apt-get update" again. As long as this is the 13.10 version of ubuntu then it should have that in the repos, i don't think it was in the repos before 13.10.
Thank you so much, what you said worked with my friends kindle who had kinda the same thing happen but the problem with mine is that it can't stay connected to the computer. It connects but then unconnected like 2 seconds after and it can't stay connected or I could fix it . Any suggestions?
Pray that what you did works on his, though I would ask what did he do that made his do that? Because if you can get it into fastboot even briefly, as long as the PC has the fastboot command already running so it says "waiting for device" it should attempt it. Depending on what he did is oukd recommend what I told you, its either the bootloader or the boot image, I don't go for bootloader unless I have to because an incomplete flash on that would be far worse, though the bootloader is quite a bit smaller than the bootimg last I checked so it would take less time to flash. Also is his also the 7” HD?
Sent from my Amazon Kindle Fire HD using Tapatalk
My friend booted into recovery and it bricked it to the logo but what you said worked. With mine my family's getting a new computer so when when we do I will definitely try it out and let you know how it works. And again thank you so o much.
Very good news, what you said worked, my kindle fully connected to the computer in fast boot mode. I was able to install the abd composite drivers to my kindle and it runs fast boot commands. IT is stuck on the fast boot symbol and was wondering if you had a way to reset the kindle, a factory reset that wipes it clean or anything that would make the device work again. Thank you for all your help so far, it is greatly appreciated.
Adam h said:
Very good news, what you said worked, my kindle fully connected to the computer in fast boot mode. I was able to install the abd composite drivers to my kindle and it runs fast boot commands. IT is stuck on the fast boot symbol and was wondering if you had a way to reset the kindle, a factory reset that wipes it clean or anything that would make the device work again. Thank you for all your help so far, it is greatly appreciated.
Click to expand...
Click to collapse
You want to flash factory images through fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
You want to flash factory images through fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please link me to a website where I can download these images and list some steps for me to follow to flash those.
Kindle fire first aid does it for you as well as SRT, kffa is in the 7" general section. I think I should add links to this stuff in my signature... Maybe I will add them tomorrow.
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk
Related
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.
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Nikaroo said:
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Click to expand...
Click to collapse
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
soupmagnet said:
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
Click to expand...
Click to collapse
Thanks for the pointer - I think it got me a tiny bit further. After finding the package and 'fixing' drivers - woo-hoo - my computer is saying that the device is working properly now, I can see it as 'Kindle Fire' in my device manager. However, it still is showing up as 'Tate-PVT-08' under Devices and Printers, and it cannot be found (isn't communicating) with ADB. I feel like I'm missing something so small to be able to move forward and reflash this thing - it's so incredibly frustrating to not be able to find it. :/
I also have tried editing the adb usb file to include the 0x1949, having gone through the adb kill/start-server commands several times, which hasn't changed anything. Is there anything I am missing to get windows and adb to communicate with it? Or is my only option at this point trying 'non-Windows based options'?
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Click to expand...
Click to collapse
Sooo, I feel even stupider now. I do have KFFA, so I tried to reflash the system image. It went through and gave me a success, although it did have an issue with erasing user data and cache. It said to disconnect from the computer/usb and power down, then restart. I did that and was super hopeful - it went through the boot screen a few more times than normal... but then BAM. Right back to the Kindle Fire System Recovery screen that it can't get past. Ugh. I must have really screwed something up on it.
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here. Going through that, I checked my hardware IDs, and one of the numbers are off, which according to the guide means that my Kindle isn't in fastboot mode (and this is while using the fastboot cable). If I use a regular USB cable, it doesn't show up at all anywhere. The more I research, the more confused I get. Everything seems geared towards fixing your device if it is stuck in a bootloop (mine goes through that and sticks at the recovery screen) or being able to get it into fastboot, which I cannot seem to do even with the cable. I guess I'm going to try to uninstall and reinstall the drivers for it again, but I'm starting to believe that whatever value I changed while in super user mode before my problems began are going to make it impossible to fix...
The hardware I'd should be 0x1949, and at this point I'm guessing maybe something is wrong with something in the data partition or you have a bad kernel. I don't know how to wipe the data partition from fastboot though. I don't know if kffa reflashes the boot partition, but you could always try that since a system reflash didn't work, or you could try reflashing the system image again, there's another tool in the android development section called kindle fire system restore tool, maybe it will work better for you. Here's the other tool: http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part about that adb command, that's only for of your kindle can actually boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Nikaroo said:
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here.
Click to expand...
Click to collapse
Be very careful of what guides you use around here. Some of them (fastboot guide in particular) are made with the original Kindle Fires in mind, and can lead you to do irreversible damage.
I'll try that in the morning... I spent most of my day at this and need a break! Thank you so much for trying to help me out. I really appreciate any and all pointers.
OK, here's the thing...
I hadn't used my Kindle Fire HD for a few days but when I went to read a book (Yep.. Someone who actually uses their KFHD to read books!) I found, much to my disappointment that Amazon had managed to completely wipe it by doing one of their (in)famous OTA updates!
Being totally hacked off at this, I decided to follow the advice on here and Rooted it, which was surprisingly easy and went without a hitch.
I also decided to follow the advice and prevent further OTA updates by removing the "otacerts.zip" file but, on restart I still got an "Updating..." message.
In the same folder as otacerts.zip there was also an "otacerts" folder, which I also removed and this stopped the "Updating...." message.
Excellent, I thought except when I went to Re-Register the device, I get a "No Network Connection" error message which requests that I connect to a wireless network - except that the device IS connected and I can browse the internet quite happily.
Everything I have tried since then has failed to get rid of this error - even multiple Factory Resets have not cured it - and an hour chatting to one of their Tech Bods couldn't resolve it either.
I have tried downloading the latest update from Amazon but, as it is the same version as on my device, it does nothing.
I thought if I re-instated the otacerts stuff it might cure the problem - except during the many updates it seems to have been dumped as I can no longer find the files on my device.
I guess the bottom line is that I don't have to register with Amazon to get my device working, I have purchased a number of items from them and these will not reinstall if I cannot register the device.
So, here's my question: Can anyone help me please?
If you have a local copy of otacerts.zip that you can let me have (I have scoured Google trying to find a downloadable without success), I can try re-installing that and see if it corrects the error.
Failing that, does anyone know how to force a KFHD to do an "update" to the same software version - or can the software be rolled back and then re-updated?
Any help/advice/suggestions would be gratefully received.
Many thanks in advance.
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks.
stunts513 said:
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many thanks for the quick reply.
I'll grab KF First Aid and see what I can do.
Any recomms about where to grab older system images?
Ta.
Update - ALL DONE!!
stunts513 said:
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
BIG THANKS!!
It took a while to figure out and work through but I now have a fully rooted, fully working, fully registered KFHD, complete with Google Play and Live Wallpapers!!
Now, all that's left is to re-install all the stuff I lost....
Wish me luck!
Thanks again for your guidance - much appreciated!
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.
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
HappyTNMom said:
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
Click to expand...
Click to collapse
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Thank You
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Sorry Didn't work
HappyTNMom said:
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Click to expand...
Click to collapse
ok, so I now have SKD and tried the command you gave me with no luck
I also tried SRT again and it looks like it is working on my cmd screen
I did step 1, step 3, step 4, step 6 and they all said they finished but it still reboots then goes straight to the FastBoot screen
Got my Factory Cable Today still stuck on fastboot
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
ok I have tried using this new cable and running SRT with no luck. I am still stuck on FastBoot. It seems to work, but as soon as I do the Reboot to Normal, it goes to the Kindle Fire homescreen, then immediately goes back into FastBoot. I am going to keep trying and hopefully you or someone will see this and respond with more suggestions. Thanks for the help, much appreciated...