I have a conglomeration of issues with my Kindle Fire HD 7. I'm currently in the process of ordering a factory cable from SkOrPn, but wanted to make sure there are no other avenues for me to attempt.
I'm very noob here, so bear with me. I've searched around, and attempted all the fixes that I've found, but for some reason, none are working.
My KFHD7 is currently stuck at the boot logo, non-animated. It came back to my company this way, so I'm not sure exactly what the person that had it before me was attempting to do with it. If I plug it into my PC, with Windows 8 Pro, I do NOT hear anything that tells me that the computer recognizes that the device is connected. I also do NOT see the device in the Device Manager. I attempt to install the drivers from the KFU, but for some reason, those fail every time.
I've installed Ubuntu, to attempt Soupkit, and Firekit. It isn't detected there, either.
Do I have any other options, or is a factory cable the way to go? Also, if/when I order the factory cable, will my computer then be able to detect the KFHD7?
I'm sorry if this question has been answered a hundred times already, but after searching for 3 days, and attempting everything I saw, I've reached the end of my rope.
Boot into the Ubuntu that you have SoupKit installed (will eliminate Windows driver problems), open a terminal and enter the following:
Code:
fastboot -i 0x1949 getvar product
Then reboot (hold power button for 10 seconds) when you see "waiting for device". That will get you into fastboot. From there you can flash a system.img and restore your device. Onemelia has a system.img restore tool in the HD7 dev forum that has a system image included so check it out.
[Edit:] Considering you don't know exactly what was done to the device, you should probably restore the stock recovery and boot partitions too. I've had situations where I've installed Hashcode's stack override, along with the custom boot and recovery images and my device acted the same way. Since the stack is on the system partition, overwriting it with a new system partition and leaving the custom boot and recovery partitions in place would presumably put the device in a hard bricked state, from which there is no recovery.
Will it be a problem that I have Ubuntu 12.10 installed, rather than 12.04 that you reference? Maybe that was half of my issue there.
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
honberiz said:
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
Click to expand...
Click to collapse
Get the cable. It's worth way more then the price. After you get it, check out the first aide link in my signature. Good Luck!
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
honberiz said:
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
Click to expand...
Click to collapse
Onemelia's system.img restore tool in the development section has a system image...I'm not sure about the boot and recovery images though. If not, PM me and I'll send you copies.
As far as which version of Ubuntu, it shouldn't matter. The key packages are 'dpkg' which comes with all Debian based distros that I know of, and 'apt-get' which comes standard on all Ubuntu based distros I believe, so you should be fine either way. If you're using a 64bit install, I'd suggest you switch to a 32bit install. And make sure you aren't using a USB 3.0 port. As a matter of fact, you should probably switch to a dedicated usb port rather than a hub. A good way to check to see if Linux can even see your device is with the 'lsusb' command...you should see a device called "Lab 126".
Related
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.
Sorry for the noob post. I promise I did my homework before posting.... I f'd up and accidentally wiped the OS from my phone (lesson learned: never play with fire when you're tired). Background info: it came unlocked/rooted (purchased used). It's a 1st gen MotoX XT1056 with TWRP 2.6.3.1 on it. I can get it to boot into the recovery mode, however ADB sideload doesn't seem to want to engage. I've been unable to get either of my computers (both Win 7) to even see the phone in device manager in any way, shape, or form. I have the Google and Motorola drivers installed, as well as the SDK, et all. I can't push the OS since it isn't being recognized. I've followed the steps from the following sources:
http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-soft-brick-help-t2734375
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
http://android.stackexchange.com/questions/57011/windows-doesnt-recognize-nexus-7-in-recovery-mode
https://www.youtube.com/watch?v=YmCBVTgSXnY
http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
How screwed am I? What else can I try to force detection? Should I try animal sacrifice? I'm going to give the linux dev box at work a whirl tomorrow to see if that makes a difference, but at this point my hope is waning (been at this since 7PM Eastern.) Any suggestions are appreciated.
First, update that twrp. Go to https://dl.twrp.me/ghost/ and download the latest twrp on your computer. Make sure you have the correct device drivers for moto x 2013. (you might want to try different cables and/or USB ports, as these can be funky in Windows).
Boot to bootloader (power button and volume down). Using mfastboot, flash the new recovery (mfastboot flash recovery recoveryname.img).
Reboot to recovery. Mount USB. Should show up in Windows.
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254
Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:
I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me
Hi,
about 3 weeks ago I came across a kindle fire hd 7 tablet at the value world thrift store for $8. I purchased it without testing it at all. once I brought it home, I plugged the device in to find that it would not boot past the kindle fire screen (fire is in orange). I attempted booting recovery, download mode, fastboot, bootloader with the buttons before doing any research but nothing happened. After looking around online I found out I could unbrick this device with a cable I would have to purchase off eBay. I purchased the cable and it came a week later.
I charged the device overnight that day when I went to be to ensure the device was 100% charged, so when I attempted the restore I wouldn't run into a low battery issue. after the device was charged up it was back on the kindle fire screen still waiting to be restored. i searched everywhere and came across tons of dead link, but eventually found the restore tool that was called Kindle Fire First Aide . after forever I setup the program properly and that included the drivers ( had to use adb composite), environment variables (path to the tool), Java development kit and running the bat file as admin. once I got that setup I ran the bat file and then I got more errors which all seemed to be dead link problems.
when that happened I decided to attempt a manual restore via fastboot through cmd commands. I didn't know about " -i 0x1949 " at first so I ran into waiting for device errors. after learning that about that from editing the bat file in the first aid kit I was able to complete a system, boot and recovery image flash. after flashing I cleared user data and cache manually also. Then I ran a reboot command and the device screen went flash and would reboot over and over about 15-30 times before coming to a stop and not bootlooping anymore. I found out this from leaving the cable in the tablet after running the reboot script, my windows laptop would make the sound notifying me over a new device being plugged in. when that happened I decided to open the device manager so I could see if it was unknown or anything. it didn't show anything at all. windows prompted me with an unknown device error also on every boot loop reboot. after that occurred I assumed the script was wrong but that wasn't possible because the device did the reboot. so I looked for another restore tool.
I ended up finding another tool called Kindle Fire Hd System restore tool. that tool was a lot more easy to use than first aid tool kit because they put way too many options in the program. making it so the program had to be set up one way and one way only. I tried the system restore tool and it resulted in the same error, the device would reboot with the boot loop when I tried to boot into normal mode and when I didn't and manually powered down and back on. the device would be stuck on the kindle fire screen again for hours until it would die.
at this point I don't know what to do, I have tried to boot into recovery and looked into more options. maybe I didn't try everything I should have but I feel like I cover all the ground properly. I tried to flash twrp and the freedom boot image but those didn't work either. it could be possible that twrp did install and the volume button it damaged so I can't boot because of that.
if anyone has an idea or tip let me know. please and thank you. going through all this trouble was fun, to be honest, but now after investing so much time, i would really like to use the tablet with a custom ROM. if there is a hardware issue or you think there could be another problem preventing it from ever booting again. please let me know! thanks again
first aid restore tool: https://forum.xda-developers.com/showthread.php?p=38409721#post38409721
KFHD Restore tools: https://forum.xda-developers.com/showthread.php?t=1951254
adb fastboot drivers: https://forum.xda-developers.com/showthread.php?p=42407269#post42407269