[Q] Nearly bricked Kindke Fire and looking for any remaining options - General Questions and Answers

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

Related

[Q] 3.2 Update Problems, trying to understand APX

I had rooted/cwm'd my tf101 when I first got it. It was running the 3.1 update at the time. I followed the pure root posts here on XDA.
Sadly I had never tested CWM, and perhaps since it went so easily I didn't really understand/read enough on CWM to understand what is happening. When I ran the 3.2 OTA (OK so I shouldn't have done that, I know now) the TF froze on the initial splash screen.
I've tried many things and read tons of posts here on XDA and other sites, and I'm not getting anywhere, but part of it is I don't know for sure what I'm trouble shooting.
I was using a dual boot laptop in Windows mode when I did the initial update. I had the drivers working and succesfully rooted my system.
What I am trying to do is restore a stock rom for now and I've tried several methods.
1) Asus download SOP - It detects the image on the SD card, checks validity of the firmware, shuts down and reboots and hangs at the first splash screen.
2) CWM recovery, if I understand this right, I Power+ vol_down. I hit the vol_up to enter The screen says
Checking for RCK. press key <Vol_Up> in 5 sec to enter RCK.
I do that and it hangs at:
Booting recovery kernel image
3) I've tried several nvflash posts out there. NVFlash does not seem to be working, I've now done this on two windows boxes. Both the one that used to work, and a clean windows XP machine I had lying around. In both cases, I can get the nvidia APX drivers loaded and the device is seen. However, adb doesn't show any devices, and from pulling apart the batch files and doing some reading, I tried nvflash -r --getpartitiontable myfile.txt and some other commands which always hang. Eventually if I disconnect the tablet - then I get a read error of some sort.
4) quick reboot - every option leads to reboot and freeze at first splash screen.
So questions that I can't seem to find an answer too.
1) If I'm connected in APX mode, should adb show a device? Like I said the PC recognizes it as the APX device and loads the nvidia drivers instead of the normal transformer MTP drivers when I do the power + vol_up.
2) Is there a simple test to use for nvflash? The device shows up, is there anyway I can confirm whether APX mode is working or not?
I'm only starting to piece together the boot process in my own head, and my guess is that niether the stock recovery image or the cwm recovery boot image is working. Would that be a reasonable assumption based on behavior? I will admit I really don't understand the boot loading process in android.
FYI, if I go through Power+Vol_down, wait for rck to skip and then boot without wiping, the TF is fine after that. Meaning as long as I don't try to update, it will work and reboot normally. Root also still seems to be working.
I tend not to suspect a driver issue, since one machine was confirmed working, it's how I got root - and 90% of the time that machine is run as linux. I almost never boot into windows. I'm pretty sure the last time I did was to root the TF.
What happened is you overwrote the cwm when you installed the new update. You can't just randomly install things once you're rooted.
If you have a B7O machine, you need to check that you have the old or new sbk. Go to the general transformer forum, and there's a thread about the new sbk locked bootloader. Follow the test to see if you have one that you can use nvflash with. If that is the case, then go to the dev forum, and look through the nvflash unbricking thread.
Thanks for the reply
First off, you're right and I should have known better. Almost nothing I own runs it's stock firmware, and I just got dumb and didn't do the full research excited for HC 3.2 goodness.
I have a B50 machine, or at least the my serial number indicates that.
I've already tried several nvflash debricking instructions, but it seems that nvflash is not working either. I have several copies of prime and the .11 release from asus. But since nvflash is not behaving as expected, all of those threads are not helping.
I do have the nvidia USB recovery device show up in device manager, but every nvflash command fails hangs at
nvflash started
[resume mode]
ADB devices shows a serial when I'm normally connected, but it doesn't show up when I'm in APX mode. I'm just not sure if the device is in a functional APX mode, since nothing actually runs, despite it showing up in device manager. I've tried googling that situation, but I can only find posts that tell me how to get it to show up in dev manager... It seems like when that happens everyone else has been fine.
WHILE GOOGLING FOR MORE INFO ON b70 - I managed to get NVFLASH working, and now I get what the first command and -r do.
3.2 Update Problem SOLVED
So look at the original post for the strange condition I had gotten into.
Somewhere along the line, the transformer had stopped responding to adb even not in APX mode.
I uninstalled PC Suite and Asus Sync. Then reinstalled only ASUS sync. ADB started working when TF was connected normally
I did not reboot my PC, win7 64 bit. Shutdown transformer, it hung at the splash screen. WHILE HUNG, I held power and vol_up until device manager showed nvidia USB recovery device
I used the stock rom replacement from tabletroms. Sorry I can't include the link as I am too new to XDA.
Got the transformer back up, set up my account, restored data. However OTA from there was not working.
So I went to ASUS, grabbed the .11 image and updates via SDCARD following the SOP instructions.
After reboot, checked for updates, and there was one. Let it do the OTA for 3.2 and now I'm back at having stock 3.2 updated TF.
I will probably root, but may not CMW this time.

[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!

Help! Can't flash stock!

Just bought a used Nvidia Shield (1st gen, not the k1). It was already rooted and I wanted a clean install. Wiped the data with TWRP, downloaded the stock zip from Nvidia and tried to install it in TWRP. No luck, I get "Failed to sysMapFile 'sdcard/longzipname.zip' Error flashing zip..."
So I tried to do it manually with fastboot. Have no problem doing any adb commands, but fastboot does nothing, just always 'waiting on devices'. My device shows up when doing 'adb devices' but not 'fastboot devices'.
Something tells me there could be a driver issue on my computer (Windows 10), but Windows won't let me update the drivers I downloaded from Nvidia, it always automatically installs its defaults.
I'm bootlooped now, but can get into TWRP and the bootloader. Halp!
UPDATE: New problem. Got the driver deal resolved (see below). Got stock reflashed onto the device, booted back and began going through first time set up process. While connecting to my wifi (the first part of the setup process), everything went black. I saw TWRP come on the screen for just a second along with a script of some kind (didn't get a chance to see what it was), and everything went black again. Now my device will not turn at all. Can't boot into bootloader either. Device will charge when plugged in (there's a light). Additionally, the computer does recognize it (APX Device?). I'm still researching at the moment, but any help would be appreciated.
Did you flash newsest firmware? You have the links kn the CM thread
I did download the latest. I do want to reiterate, I'm not trying to flash CM, but stock.
Got the driver thing sorted it seems. When plugged in and in fastboot, I needed to update the fastboot driver in the device manager. flashall.bat didn't seem to want to work, but manually flashing the items seems to doing things. Working on it and hoping!
In case anyone else needs this in the future, I could run adb commands no problem, but couldn't do anything with fastboot. I downloaded the Nvidia drivers from their website, but the Device Manager wouldn't let me update the drivers for my Shield tablet. How I fixed: when in fastboot on the tablet, I pulled up my Device Manager. There was one specifically for fastboot and (surprise) the driver was no good. Updating that one with the ones I downloaded from Nvidia did the trick.
But I now have a new problem. Edited first post.
sounds like you bought a recalled tablet. If the seller did not tell you that then you need to chat with him.
This is what I was worried about. There's a thread in here to determine if your Shield tablet is slated for the kill switch update. It looks like mine was. Then I found the Nvidia recall website and it does appear that a claim has already been submitted on this tablet. So if I understand that process correctly, whenever the claim was done by whatever previous owner, Nvidia activated their kill switch. I think maybe the fact that it was rooted and didn't have the latest update protected it. Until I flashed the latest stock. The moment it connected to my WiFi, boom.
Is there anyway to fix the bootloader (which appears to be corrupted)? I found threads where people were talking about NVflash, but no real specifics.
True, lots of people come in and say they can fix but never do. I think they hope someone else will fix for them.
In reality it is also posted many times that this is not fixable except by nvidia itself.

TWRP Bootloop [SOLVED]

Hi all
I've had my Tf700 for a long time now. I've had it unlocked and rooted and had CROMBi before trying OMNIRom and then finally moved to KatKiss7.1 last year. All was well until today when, having enabled screen rotation, the background went a strange looking pink colour and would flicker back and forth to black. Then the WiFi started to misbehave so I rebooted it. But instead of rebooting, it just went into a bootloop.
I used power + VolumeDown to access the recovery mode and tried to get to TWRP (2.8.7.4) via the RCK option but without any luck. At that stage, all it was doing was resuming the loop. I tried booting into Android but got the same result. I tried for TWRP a few times and it always failed.
My next move was the Wipe Data option. Turned out to be a bad one. I hadn't done anything with the device in so long that I forgot about the "don't use the Wipe Data" instruction and I didn't read up before doing anything else. The device rebooted itself and then appeared to be going into TWRP - I could see the logo coming up - but my hope was short-lived as the device then proceeded to go into a bootloop where it displays the TWRP splash screen, but then reboots.
About the only thing I seem to be able to do is access APX, but I didn't know about APX or NVFlash until today when I started trying to read everything to do with anything that might help.
I run Linux on my PCs and have installed ADB so that I can try to use fastboot or adb. Neither seem to work in that nothing shows up when issuing either "fastboot devices" or "adb devices". But on a more basic level, nothing shows up in lsusb. The mouse is listed, as is my card-reader, but the TF700 isn't. The thing is, I haven't connected the device to a PC in a long time and the last time, it was windows, so I can't say for sure that the PC is definitely seeing it or not.
And so to my questions:
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup?
(I've seen instructions for the TF201, but can't see anything for the TF700)
Any help would be really appreciated.
With thanks,
Scouser27
I don't like the sound of this. This "background went a strange looking pink colour and would flicker back and forth to black" business makes me suspect a hardware failure. Maybe something got fried on the board - don't know.
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
Click to expand...
Click to collapse
Yes, it should, something like this:
Code:
...
Bus 003 Device 009: ID 0bda:57af Realtek Semiconductor Corp.
Bus 003 Device 016: ID 0b05:4d01 ASUSTek Computer, Inc. Transformer Prime TF201 (debug mode)
Windows is not going to help you. If it doesn't connect in Linux it definitely won't in Windows....
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
Click to expand...
Click to collapse
Not unless you get a connection in either fastboot or adb
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup? (I've seen instructions for the TF201, but can't see anything for the TF700)
Click to expand...
Click to collapse
No, nvflash files are device specific
If you cannot get it to boot into fastboot or get an adb connection - however briefly - it is a brick.
Install Hardinfo in Linux - it is very similar to Windows Device Manager - and open the USB page. Then reboot into TWRP. If you are lucky you may get a few seconds before TWRP loops where the PC has an adb connection and sees the tablet. If that works, follow this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Still a tiny chance but better than nothing.
If bootit.ko kicks it into the bootloader and you get fastboot you can reflash the recovery, format data in fastboot and all that good stuff.
But my guess is: No dice
Try it anyway - good practice.
I still have a couple of TF700 lying around, one with a so so screen. If you want it, you can have it for the cost of shipping. You can either swap the screens or m-boards...
PM me if you want to go that route.
Good luck
Update
Thought I'd post something in case it's useful to anyone having similar trouble to what I described. This applies to my instance of TWRP booting in a loop and never exiting until the battery was flat.
Ensure your cable is working correctly.
If it's not, you won't see anything on your pc. (I use linux and nothing was showing up in lsusb or dmesg)
If this is the case, borrow a cable if you can or invest in one. I did - best 5 Euro ever.
Get the bootit.ko file that's mentioned in a few places such as here.
While you're getting that file, read the instructions there a few times and also have a look at the details over at this page (same one @berndblb links above)
Connect your tablet and boot it. As soon as you see the TWRP logo, it's time to try to run commands.
If you use linux, you can issue all commands at once like this:
Code:
sudo adb devices; sudo adb push bootit.ko / ; sudo adb shell insmod bootit.ko
Note the "/" after "push bootit.ko" - that's not a typo. If you leave it out, it won't work.
I don't know if sudo was strictly needed, but I wanted it to work and it didn't cause any trouble.
I haven't used Windows in a long time so I don't remember if you can do the same, but you could put the various adb commands into a batch file and run that. Don't forget to drop the sudo.
If it has worked, the tablet will reboot. You should now be able to get back to the bootloader.
Follow the fastboot erase instructions at this thread.
I found it useful to write the commands as
Code:
fastboot -i 0x0b05 erase boot
The last version of TWRP that I was using was KANG TWRP
I downloaded that, extracted the blob file and flashed it:
Code:
fastboot -i 0x0b05 flash recovery boot.blob
I used that because I wanted to install TimDuru's KatKiss 7, but you could presumably install whatever Recovery you wanted and proceed as normal.
And that's it. I flashed KatKiss7 and SU and all was well again:laugh:
Big thanks go to @berndblb for his help on this - If, like me, you didn't read his posts before, you really need to read them now. And maybe, just maybe, you'll be able to recover.
Thanks to all other contributors whose post's I've linked or whose work contributes to this solution - you've all just saved me having to buy a new tablet. Nice one!:victory:

Resurrect my tf101

I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?

Categories

Resources