Disclaimer: Just in case something does happen to your kindle it isnt my fault, but I can help you but I am not responsible for none of it.. hope ya got the extended warranty like I did.
EXTRA: BTW I bricked my phone once and metropcs was suppose to void it but they didnt know what it was so 1+ for me...
Alright guys I am going to start this off from the middle of the rooting process, the adb part, you guys know how most of you have a emulator5554 pop up? Well I have did a ton of research and if you have BlueStacks or a simular application installed I suggest you uninstall it if you want to root your kindle, its what I did, also when I rooted my Kindle I flashed TWRP in, please do not flash TWRP until you get the go ahead around the forums because people have been reporting that they cant get into recovery so just use ClockWorkMod for now,
[Stuck in logo] Are you stuck on the "Kindle Fire" logo? [Stuck in logo]
Well if you got stuck in your kindle fire logo from using KFU you might be able to press 1 and get into bootmode and start your kindle in normal mode even if the Boot Status and ADB status says Offline and Unknown, and your kindle should boot right into normal mode and your saved .
Dont forget to donate to me so I can buy some goodies: [email protected]
You are a fricken life saver!
I installed KFU, but then decided to ensure that TWRP was up to date on the KF, but whilst it was upgrading the version it got stuck on the load screen. Also it was registering as offline in KFU.
Following your instructions (Boot mode -> Normal Mode) did the trick!
Dysanovic said:
You are a fricken life saver!
I installed KFU, but then decided to ensure that TWRP was up to date on the KF, but whilst it was upgrading the version it got stuck on the load screen. Also it was registering as offline in KFU.
Following your instructions (Boot mode -> Normal Mode) did the trick!
Click to expand...
Click to collapse
No problem....
I just get < waiting for device > ... I assume this means I'm still going nowhere? Is there a simple way to get out of this mess?
Thank you
thank you very much :good::good:
I was scared because my kindle was stuck on the logo, but your trick did it !!
Related
I tried to install TWRP last night. I had the img file in the same directory as fastboot, but I received an error message saying "Fastboot not found" I had followed the instructions on the TeamWin site for the Kindle. When I gave up and unplugged my Fire, it appeared fine, but then I rebooted and ever since I've been stuck on the "kindle fire" splash screen. I checked to make sure the drivers are still installed from when I rooted, they are, but my computer won't recognize my fire. I also just tried the new Kindle Fire Utility, running it with admin priveledges and I get message that Fastboot is offline and pressing 1 for Normal just tells me "Waiting for Device..... then The system cannot find the path specified". I also held the power button for 20 seconds to totally shut down and restarted, didn't help. Am I hosed?
Sounds like you are in fastboot (I can be wrong) first make sure you have fastboot installed on your computer (Guide: Link ) next is when its on the kindle splash screen run - fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Thank you. I may be getting closer. That did something. I saw the teamwin logo, and now I'm on the yellow triangle. I am not unplugging my Fire yet. Is there a next step? I'll continue researching, but if you can help, I'd really appreciate it
good then your basically done. Just hold the power button down when you start up the kindle until it changes colors and then you will be in recovery mode, then just hit reboot in recovery mode and your good to go.
Also the yellow triangle is the bootloader firefirefire which is bundled with TWRP 2.0
Thank you. I found the answers here: http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222. Rebooting my PC didn't do the trick, I actually had to shut it down for a few minutes and then I followed those instructions. All good and Twrp is verified as installed. Thanks again.
sweet, glad you got it all worked out.
Just did my first nanoid backup Takes up about 500 megs, but now I have the piece of mind! What we need now are some really good roms to choose. Maybe a replacement for Amazon video so we don't have to temp unroot! I think I've been spoiled by my EVO 3D
I rooted my kindle fire with the Kindle Fire Utility. Installed TWRP, and installed the rom - MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D. After doing this, I reboot and I am stuck at the Yellow Triangle. If I push the power button to get into TWRP the power button turns orange and is still stuck at the yellow triangle . if I power off and on again , do nothing Windows detects the kindle for a few second and then it disappears and then is detected again and then disappears, so I cannot access the device through ADB ,
Any ideas or do I now have a paper weight instead of a kindle fire
Kindle fire Utility should work even without being recognized (well it did for me after turning on and off 3 times).
Does the device at least get's the firefirefire logo? If so, this is what I did
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
==========================================
This is what worked for me (I've been tossing this around awhile now, and it even worked for two of my friends).
The link to the unbrick utility is: Here
Mine got stuck on the triangle as well and I thought I was screwed, but appears you are just stuck in fastboot.
What I did was use the KFU (vashypoo has made an awesome utility) and even though it didn't show as recognized when I opened the KFU, I was able to use Option 1 - Bootmode Menu, Then Option 1 - Normal.
My Fire restarted normally after that.
Give it a shot.
Check out this post: http://forum.xda-developers.com/showthread.php?t=1520826
Zane had to cycle a couple of times to get it to take.
Are there alternative download links for this utility....I keep downloading it from the site that this site provides and I keep getting viruses or incomplete downloading. I have been trying to unbrick my kindle for weeks and this seems like my last route...
Try this Linux solution. It was the only thing that worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Solution for This: I had the exact same problem
http://forum.xda-developers.com/show...02&postcount=4
I had the exact same problem and b63 posted this as a reply. My Kindle was stuck on yellow triangle and was not recognized by ADB. When I tried to boot into twrp the power button turned orange but stayed on the yellow triangle. The thread above is what I used, worked perfectly.
Good Luck!
Kindle Fire Bricked and Windows doesn't recognize it.
First off, thanks for all the development and help in getting the Unbricking utility and the KFU for all of us noobs. I have been searching threads for hours before I decided to post, and I can't find the answer. I rooted with KFU and have TWRP installed. I ran MIUI several months until I decided to try MIUI 4.0 after I flashed 4.0 it rebooted to the yellow triangle and the power turned orange. I ran the unbricking utility and now the light is green, but it won't go any further. When I first plug in the kindle windows recognizes it for a second and then it disappears from the device manager completely. I have updated the driver several times, tried the KFU to get it to boot (4000) and nothing works. if I turn off the kindle and turn it back on KFU and windows will recognize it for a second and reboot it, but then it gets stuck on yellow triangle and never goes anywhere. Then I don't see it in the device manager anymore, not even 'unknown device'.
I did forget and leave the Kindle plugged into the computer while it was flashing MIUI 4.0, I don't know if that would have killed it. I never got a chance to see 4.0 it's been bricked ever since.
Any help or ideas would be greatly appreciated. I'm sorry if this specific situation has been covered anywhere in the forums and I missed it.
Thanks
this should help you:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
I rooted my Kindle Fire and installed CM9 on it using TWRP 2.0. I updated CM9 to CM9 Alpha but realized that I liked CM9 better. I then tried to flash MIUI 4.0.3 to my Kindle to see how that would work and got it to work but didn't like that either. I booted back into TWRP and then attempted to restore. Once I my restored it I hit the reboot system button and my Kindle got stuck on the yellow triangle. I unplugged and plugged it and attempted most if not all the suggestions by various threads. The problem is that every time I plug my Kindle into my computer while it is off it displays the yellow triangle and is only recognized for 10 seconds. After it disappears it reappears for 5 more seconds and then completely disappears. I attempted to use KFU to reboot it in normal 4000 by having KFU open plugging in my Kindle and quickly hitting the reboot in normal 4000 mode. KFU said that it told the Kindle to reboot in normal mode but when it started up again it stayed on the yellow triangle. I am really frantic as I love and use this tablet every day! Any help is appreciated!
bricked?
it seems like i keep finding people with the same problem as me that noone wants to help ;; this is madness
When you were connected to KFU and attempted to put it in normal bootmode did you attempt a hard reset when it said "Waiting for device...."? Sometimes the KF hangs and needs a 20 second hard reset
Try this using Ubuntu linux booted from a stick. Worked for me when nothing else would.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
b63 said:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
Click to expand...
Click to collapse
This worked for me after hours working on it last night. Follow all those steps as they make the most sense and actually work compared to all the other threads I've read
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
After having problems with my amazon app, and all my google apps, I figured it was a good time to try and learn how to put a new rom in. So I picked CM9 and tried to no avail. I was getting the same problem as alot of guys on here where it said something about /media. But unlike the others, mine wouldn't load like the others. I also was unable to go back to CM7. I was stuck in TWRP. So I tried my back-up and still nothing. Then thinking maybe I had a bad download I tried another CM9 and nothing. Then I tried MUIU. All three said failure to install. Then after trying the MUIU, my computer quit recognizing my KF and it stopped loading into TWRP and just went straight into yellow triangle. I followed the other threads and added the line under the 1949 in .bit file. I reinstalled the drivers in my newly downloaded KFU. Then tried the adb and nothing works because my computer won't recognize the KFU.
Had the same problem as the op. This solution also worked for me.
Sent from my Transformer TF101 using Tapatalk
installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.
Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.
Let it charge, then just flash a new rom.
left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.
shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.
There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode
He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.
FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.
darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.
Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.
Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.
This entire thread is ridiculous.
I have a 8.9 rooted, i have safe strap installed, and i even backed up the device.
I was trying to hack a game and i needed to install Xpiracy on the Xposed framework. I installed and rebooted, than the kindle went into boot loop (kindle logo - kindle is upgrading and repeat) BUT ITS NOT GETTING TO THE SAFESTAP SCREEN so i cant restore it.
I did see the boot loop help form, but was wondering, since i already had safestrap installed and backed up that it might be easier than that process...
Any thoughts?
Bear6009 said:
I have a 8.9 rooted, i have safe strap installed, and i even backed up the device.
I was trying to hack a game and i needed to install Xpiracy on the Xposed framework. I installed and rebooted, than the kindle went into boot loop (kindle logo - kindle is upgrading and repeat) BUT ITS NOT GETTING TO THE SAFESTAP SCREEN so i cant restore it.
I did see the boot loop help form, but was wondering, since i already had safestrap installed and backed up that it might be easier than that process...
Any thoughts?
Click to expand...
Click to collapse
try hold power button for cca 10-15 sec while bootlooping, your kindle should turn off, then turn it on, you should see "recovery - continue" screen - this helped me with boot loop after messing with system apps
Fixed for now
Lol, I just went into adb and issued a reboot command, seems to be working ok...
I was freaking out a little bit! haha
Thanks