Database Info

[Q] Cant unbrick Kindle Fire.

Iv read up on the other threads and I can not find one that works.
1. Bricked Rooted Kindle Fire Using Kindle Fire Utility
2. Plugged In device not seen by Device Manager.
Shows up as USB not recognized.
3. Adb Devices shows no Devices
4. New Drivers, New adb, etc.
I'm kinda Scared. IFU!

What happens when you turn on your kindle?
- Splash screen then blackness?
- Splash screen freezes and sits there permanently?
- other???

Fixed!
I fixed my problem. I used adb and ran a command to fastboot. At first I did not try this for the fact that no adb and no Device manager. But I tryed. And worked. Added TWRP and added CM9 now.

Chat_Ghosty said:
I fixed my problem. I used adb and ran a command to fastboot. At first I did not try this for the fact that no adb and no Device manager. But I tryed. And worked. Added TWRP and added CM9 now.
Click to expand...
Click to collapse
May i ask how you did this? I am in the same situation you were

please let me know how you fixed i think i killed my daughers kindle

mine just flashes the boot screen then black screen over and over again......

[Q] Nearly bricked Kindke Fire and looking for any remaining options

I have a 1st Generation Kindle Fire (DO1400). I had been running 6.3.1 prior to my first attempted root. I am running windows 7 on one pc and Ubuntu Live USB on a second machine. I've been working on this about a month and a half and read and re-read the posts here on Xda and have finally run out of ideas on what to try next to fix my kindle fire.
So how did I get to where I am:
I attempted to Root Device failed using KindleFirerootNew631 tool. The process appeared to get stuck (I should have documented more at the time but was in a hurry to leave for a trip) So I did a forced shut down and left. When I came back and booted the device I ended up viewing a screen that I later learned was commonly known as 'FIREFIREFIRE'.
To resolve this issue I downloaded and ran 'Kindle Fire Utility 0.9.6'. Ran the 'InstallDrivers.bat' script. then started the app. I was able to get Root and then install TWRP, Latest FireFireFire and Google Apps. Everything is working and so I figure hey fixed it once I can again so not why not play around some more. I decide I want to look around in TWRP and see what it offers. I then end up deleting my Kindle ROM (didn't make a backup prior to messing around which was another mistake) So at this point I've got TWRP and I can mount it within windows but have no ROM.
Figuring since I have no ROM I then download the latest stock image from amazon, mounted the device using TWRP, transferred the file in the /bin directory on the kindle. I'm not certain what I selected next but I think it may have been restore defaults. The device powered off, restarted and then remained on the static kindle fire boot loader screen. Checking kindle fire utility I found that the device that ADB Status: Connected. Boot status: Unknown' When I attempted to use adb I could reboot the device, but any attempt by kindle fire utility resulted in the error ' error: exec '/system/bin/sh' failed: No such file or directory' The next time I unplugged/replugged my kindle I was not longer able to ever get the 'ADB Status: connected'. I have since found that if I uninstall the drivers provided by Kindle Fire Utility, unplug/replug in the device I am able to get it to show up as Online but still have status of unknown.
Next after reading I found that many people had utilized a Factory cable to successfully recover. So I set about creating a factory cable using a breakout board from sparkfun and following pinout shown here: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html The factory cable didn't seem to have any impact on the kindle which was confusing to me as I expected it to automatically allow me to connect. I have triple tested the pin outs to verify there are no shorts (excluding the jumper between pins 1 and 4) From further reading I think I found out the kindle fire 'factory cable' to work it must have a working boot loader.
From reading other posts I figured my last attempt would be to try the 'shorting trick' used in conjunction with FireKit Live USB repair kit. (detailed in the post http://forum.xda-developers.com/showthread.php?t=1430038 and http://forum.xda-developers.com/showthread.php?t=1650738 ) I removed the back cover without any issues. The Kindle fire still shows the static 'Kindle Fire' boot loader screen and is detected on both Windows and Ubuntu machines.
Launch Ubuntu on live usb and started firekit. Then ran firekit with command 'usb_fix_parts_and_install_fff_twrp. But was stuck waiting for the device. I also tried with the commands usb_boot_twrp, fix_parts commands while repeating all the shorting/connecting steps and tried with the battery always connected and without it connected and then reconnecting it part way through. I read that some of the firefirefire versions check that it is connected and wil halt if it is not connected. But was never able to get the fire fix to detect the device.
So where am I now:
Currently I am able to charge the battery (I verified this by leaving it running with the static bootloader screen until the battery died, then plugged it in using the charging cable over night, next day I unplugged it for 15 minutes to just see if the boot loader screen would remain on, which it did, I would guess it would go several hours on a charge as that is what it was doing when it last worked). I can still adb device connected but status is unknown. I can also issue reboot commands to the device through ADB. But can not get any tool to find the device in any attempt to install a new boot loader.
So are there any options remaining? Is there something I missed? At this point all I can think of is either trying to replace the sd/mother board or purchase an entirely new kindle fire.

I used the kindle fire utility for the 8.9 and rooted it I was where I was just trying everything and it unbricked it
Sent from my SAMSUNG-SGH-T989 using xda premium

I am in the exact same situation. If I come across a solution i will let you know. I have tried what the other comment said with no luck. If you figure something out let me know.
Sent from my PantechP8010 using xda app-developers app

[Q] kindle fire hd 7 brick help

ok. i successfully rooted this kindle with "root with restore by Bin4ry." i am pretty sure i was on version 7.2.1. i made an attempt at installing a second bootloader with TWRP using seokhun's noob-proof tutorial, step by step. bam, brick. maximum bootloop. i then went to use KFHD System.img restore tool, to no avail. KFFA, no-go. i made a factory cable to get it into fastboot, and it works- the only life it shows is fastboot screen or bootloop with the kf logo. only in fastboot with a regular usb does adb recognize a connection. now, my main goal is to just recover from this brick and carry on. i have scoured the forum and got the same thing every time. is it a permanent brick?
i'm not a complete noob, i have plenty of experience rooting and flashing several models of htc androids. this is just super confusing, cuz i can usually fight thru stuff like this. any guidance is appreciated!

[Q] Bricked?

Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit

willdev13 said:
Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit
Click to expand...
Click to collapse
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped

nightwalker said:
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped
Click to expand...
Click to collapse
I can't flash it with anything, but thanks anyway

willdev13 said:
I can't flash it with anything, but thanks anyway
Click to expand...
Click to collapse
If this is the situation then submit it to S.C

Convert from "Roth Diagnostics" to Regular Shield(STOCK)?

I recently got a Shield for $85 because the ebay seller said it was missing apps.
I've got it rooted with the custom towelroot, but i'd like to use a recovery and restore to normal shield firmware instead of the Diagnostics it's on.
Basicaly, it's The shield, stripped of google services, & OTA update, with "Input Viewer," and "Mfg Test" added.
It's on 4.2.1 Build- rothdiag-userdebug 4.2.1 JOP40D 7947_223.4068 test-keys
Kernel- 3.4.10-g6f428d8 [email protected] #1 Tue Aug 27 16:37:56 PDT 2013
Model number is Roth Diagnostics
It runs everything fine, I just need to put it to stock shield as a normal user would have, since I can't stream from my laptop to it with how it's setup now (It has tegra zone, but won't detect my pc)

I just recently acquired a Shield Portable as well, and of course, now I’m doing the research to get all I can from the device.
When I got mine, I immediately unlocked and rooted it, installed TWRP recovery, flashed the Roth 1.6 updates, and flashed CM12.1 Nightly with Open GApps ARM 5.1 Micro. All went well, and works fine, though I’m still uncertain as to the best recipe to bake my Shield with.
As for your question, how to get back to stock, well, from what I did, it’s actually quite simple.
Take my method with caution!! I’m still new to the Shield, and whenever flashing a device you always run the risk of bricking, so be damn sure you know the do’s and don’ts. Also, this method should completely return you to stock, including removing any custom recovery you installed.
Keep in mind, when I flashed back to stock, my Shields bootloader was unlocked, had a custom recovery, and CM12.1 installed. I’m not quite sure if this makes a difference, I’m just pointing out my configuration at the time.
One last thing, I flashed from a Windows 10 rig, and my instructions will be noob friendly for those that stumble upon this post and need to know what to do from the beginning.
1. Connect your Shield to your PC, and boot your Shield into Fastboot mode by simultaneously pressing the Back + Home + Shield button. Your shield will boot to a black screen displaying menu options such as Continue, Restart Bootloader, Recovery Mode, among some other options.
2. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) Now, make sure your Shield can be seen on your PC.
In Windows, go into Device Manger, and if there’s an exclamation point next to your Nvidia Shield device (it might read Fastboot device or Roth), then you’ll need to fix that problem so Windows installs the proper drivers.
I’m running Windows 10, and the following method worked for me to get the proper driver installed.
Right click Nvidia device in Device Manager then click the following... Update Driver > Browse My Computer for driver software > Let me pick from a list of device drivers on my computer > Android Device > Android Composite ADB Interface > Click Next and that should install the driver.
3. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) If you have the driver properly installed, you can verify Windows sees your shield by running fastboot devices.
To do this, one method is to download Shield Root files courtesy of CriticalComposer from this link https://www.dropbox.com/s/mr8ro1gx2axynwg/Shield Root.zip
Extract the file, go into Shield > Shield Root. The ABD files are located there.
Press the shift key on your PC keyboard as you right click in that folder, then select “Open command window here”. This will open a command prompt pointing to the Shield Root folder.
Now type fastboot devices in the command prompt and press enter. If Windows sees your Nvidia Shield a serial number will appear. If nothing appears, that means you may not have your Nvidia driver properly installed or in Fastboot Mode.
4. Now that your Shield is connected to your PC and can be seen by Windows, you’ll need to download the Stock image from Nvidia.
Here’s the link https://developer.nvidia.com/gameworksdownload
You might have to create an account to download.
I believe NVIDIA SHIELD Portable Recovery OS Image Update 106 is the latest as of this post. Download it and extract it to your PC.
5. (THIS STEP STARTS THE FLASHING PROCESS) Open the extracted folder, and simply double click flash-all.bat. That should start the flashing process, and it will flash everything needed to return to stock. If it doesn’t start the flashing process, re-check to ensure Windows has the proper drivers installed.
6. Once it completes flashing it will display “press any key to exit” in the DOS box, do that, then reboot your Shield.
7. When your Shield reboots, it should display a screen with NVIDIA and its logo, and might take up to 5 minutes to finish booting.
8. Hopefully all goes well, and you should now be back at stock with Lollipop 5.1 and Nvidia update 106.

Same Situation Different Issue??? NoWiFi??
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.

simmpledeals said:
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.
Click to expand...
Click to collapse
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.

loismustdie555 said:
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.
Click to expand...
Click to collapse
I know how the process works but I tried so many times and searched all over and I cannot find a radio.img for this device, do you know how or where I can find it, it would be amazing to get this too work at its full capability, cause it pretty much sucks without wifi.

Sorry to ask a dumb question but, why not restore the sock image from Nvidia's site?
It sounds like you all bought failed attempts to use CM.
Sent from my HTC One_M8 using Tapatalk