Database Develop

[Q] Kindle Fire HD 7 bricked?

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".

[Q] Need Help. Will pay for solution.

Here's the deal:
I have a unlocked/t-mobile variant Moto X. It was running 4.4.3, stock, rooted, twrp, xposed framework installed. In a moment where I was a bit preoccupied, I hurriedly accepted the 4.4.4 OTA update. After realizing what I had done, I pulled my phone out of my pocket to see that I had swiped the, "factory reset" prompt in TWRP. After some half-assed attempts to fix the problem (I was at work), this is where I sit:
unlocked bootloader
TWRP installed
no ROM installed
no backups
no ROM saved on my storage
When connected via USB, my phone (regardless of whether its in fastboot, recovery, or the "unlocked bootloader warning" screen that I can't boot past) is not recognized by my computer (running windows 8.1).
I suck with command prompt, and don't even know where to begin to push a file to storage to flash through TWRP
Ideally I want to end up back to completely stock, but I'll take a quick flashable (probably a stable cm11 build) fix at this point.
Can anyone help?

http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
Can you go to bootloader?

You need to update your driver. While in fastboot and connected to your comp via USB go into your device manager, right click on the device> properties > drivers tab> change settings as administrator> update driver> (you need the android SDK for this next bit) click on "browse computer for available drivers> under one of the first few options (I can't remember which) look for MOT adb interface. That should make your comp readable to fastboot. Then just manually flash to stock.
I've probably left out some info but that's the gist of it. I'm gonna post some links to help you but they aren't 100%accurate on finding the right driver, but with minimal searching you can find it
http://forum.xda-developers.com/moto-x/moto-x-qa/fastboot-drivers-w8-1-t2880299
And returning to stock with fastboot
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

Great advice guys, thank you. I think I'm back in business.

And the payment? ?

What would be considered fair for sharing the link?

Nothing. This is what XDA is about. ?

Fire bricked/ bootloop

Hey guys,
hope you can help me. Have a little problem: After trying to root my fire, it is in a bootloop and i don't know what to do. Hope you can help me. I guess it is bricked.
Thanks
EDIT:
I tried to sideload the software bin, but it didn't worked. Also my computer doesn't show the devices with "adb devices".

Also my computer doesn't show the devices with "adb devices".
Click to expand...
Click to collapse
Others have found that the fire will only show up on your pc after you select the sideload option on the fire. If it still doesn't show, try unplugging / replugging the usb. It seems to help some people to get it to appear. Also note that some devices will intentionally not allow you to flash bin if the battery level isn't high enough. It's a safety measure since running out of battery during a flash = brick. Be sure you're fully charged.

thanks, but..
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do

cl.lio said:
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
Click to expand...
Click to collapse
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc

Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow

EVOL-LOVE said:
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
Click to expand...
Click to collapse
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery

sd_shadow said:
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Click to expand...
Click to collapse
:good: Awesome thank you very much, I thought about doing just that but figured I better ask the pros first.
I somehow missed that post on unbricking... :silly:

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk

Installed Magisk APP and flashed Magisk v14.0 (BRICKED)

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