Related
After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.
That doesn't sound good. Press and hold the on button for like 20 seconds and see if anything happens.
jaredkzr said:
After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.
Click to expand...
Click to collapse
Try the Hard reset option as explained by GBH2 and if it doesn't help, then please list down what exactly did you do to root your device, stock FW version etc.
Sent from my GT-I9100 using XDA App
I have already tried the hard reset but to no avail. I have no idea what happened to it. I think I will just have to get a replacement. I followed instructions off of mobilemag and of course I can't place the link in this post.
I literally just had same issue... holing power button for 20+ seconds did the trick here.
Running CM7 w/ MAC address fix.
mine's bricked too
I also have a bricked Kindle and not sure what to do about it.
I had my KF rooted and working. Then, I followed these instructions to get a better keyboard. In short, I edited one row of the secure table in settings.db, trying to enable Hackers Keyboard. I followed the instructions very carefully, including changing permissions. When I rebooted, it stuck at the kindle fire logo, and it is still stuck there.
I can connect via adb, but can no longer burrito root. Can't run 'su'. I'm searching these forums trying to figure what to do next.
do you have twrp available ?
if not you could follow this post: http://forum.xda-developers.com/showthread.php?t=1414832
fixed
Thanks. I found that thread via http://forum.xda-developers.com/showthread.php?t=1356257&page=61 and it saved the day.
I was able to fastboot, twrp, and eventually solve my problem.
I had updated settings.db, then used `adb push` to put it in the right place. Then, I chmod-ed it as the instructions warned. However, it was owned by root not system! With twrd, I was able to get back into adb. Chown-ing and chgrp-ing that file to system solved my problem.
(Unfortunately some of the other stuff I did along the way broke a few apps... anyway I'm happy to have a working KF again.)
good to hear !!!
Did you ever get your KF to work? I can not get mine to turn on after KFU 0.9.5 used to do perm root. Now nothing works at all
Kindle fire wont power on /boot
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue
hi vertcam9 how do you force boot it please.
omniac
omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
I think my issue is a busted USB port already.
ok thanks tried that, but it is deader than that.
omniac
Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.
Seriously people...
vertcam9 said:
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue
Click to expand...
Click to collapse
vertcam9 said:
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
Click to expand...
Click to collapse
Normally I would assume you had a 2nd generation device and tried to modify it, but I see your first post was made back in April and then edited two days ago?!? Is this a new problem or the same problem you had eight months ago?
I'm pretty sure your USB port isn't bad and you just have a broken bootloader. If you have a 1st generation device, the Firekit w/shorting trick to put the device in USBboot will do the trick.
omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
omniac said:
ok thanks tried that, but it is deader than that.
omniac
Click to expand...
Click to collapse
How about some details...better yet, start a new thread...In the Q&A section.
Smmoph said:
Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.
Click to expand...
Click to collapse
This sounds like a completely different problem. You should probably start a new thread as well...In the Q&A section.
I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!
samiultahir said:
I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!
Click to expand...
Click to collapse
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs
sd_shadow said:
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs
Click to expand...
Click to collapse
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:
samiultahir said:
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:
Click to expand...
Click to collapse
post in the correct forum
Sent from my sailfish using XDA Labs
I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".
I don't no what happened I was running ics on my fire when I decided to go back to stock so I downloaded the file from amazon renamed it update.zip flashed it and it is now stuck at the orange and white logo no twrp or any thing I have a factory cable coming in the mail I have tried kindle fire unbrick and reinstalling drivers manually changing boot modes nothing is working I really need help I use this device for school
http://forum.xda-developers.com/showpost.php?p=38488967
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=38488967
Click to expand...
Click to collapse
The kindle
Is not recognized by my computer from what I have read it seem to be in fast boot already
Well at least your looking in the right place...
Do you have access to a Linux machine so that you can run Soupkit?
Sent from my Amazon Kindle Fire using Tapatalk HD
jma9454 said:
Well at least your looking in the right place...
Do you have access to a Linux machine so that you can run Soupkit?
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
No I only have windows 7 home premium
Bruce8289 said:
The kindle
Is not recognized by my computer from what I have read it seem to be in fast boot already
Click to expand...
Click to collapse
I'm sorry, I should have been more specific...Q:16
soupmagnet said:
I'm sorry, I should have been more specific...Q:16
Click to expand...
Click to collapse
I have tried that with no luck I have been doing research for a week before posting
Bruce8289 said:
I have tried that with no luck I have been doing research for a week before posting
Click to expand...
Click to collapse
Oh so you already got a factory cable and used it? What happened?
soupmagnet said:
Oh so you already got a factory cable and used it? What happened?
Click to expand...
Click to collapse
No I have not used it I'm a very cautious person I don't no what to do when I plug it in
Bruce8289 said:
No I have not used it I'm a very cautious person I don't no what to do when I plug it in
Click to expand...
Click to collapse
Another thing I should add it will not charge on the normal charger
Bruce8289 said:
Another thing I should add it will not charge on the normal charger
Click to expand...
Click to collapse
What happens when you plug it in? If it turns on, hold the power button for about ten seconds, and come back about 2-3 hours later.
It should be mostly charged if not completely charged by that point.
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself as higher than anybody else.
jma9454 said:
What happens when you plug it in? If it turns on, hold the power button for about ten seconds, and come back about 2-3 hours later.
It should be mostly charged if not completely charged by that point.
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself as higher than anybody else.
Click to expand...
Click to collapse
Can I then change boot modes
Did you do what I recommended? What happens when you turn on the kindle now? Do you see a screen with a blue and white kindle fire logo?
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
Bruce8289 said:
Can I then change boot modes
Click to expand...
Click to collapse
I tried telling you twice what you need to do, so let me explain it again...
The Frequently Asked Questions post I directed you to clearly explains in several places that failure to wipe data (factory reset) in recovery before flashing a ROM will cause problems. It also tells you that when users revert back to stock without wiping data, they get stuck at the Kindle Fire logo (Q:16). When FireFireFire gets overwritten by the stock bootloader (which is what happens when you revert to stock), there is no access to fastboot for changing the bootmode to recovery so that data can be wiped (which is the only way to fix the problem). Also, without FireFireFire installed, the only way to access fastboot is through the shell (which is obviously not possible in this case) OR with a factory cable. I believe I hinted to the need for a factory cable in one of my previous posts?
So try to pay attention to the information that is available to you or you'll risk getting yourself into another situation that you cannot get out of in your own capacity, and you'll then have to rely on the accuracy of the information given to you (and the limited patience) from a******s like me
soupmagnet said:
I tried telling you twice what you need to do, so let me explain it again...
The Frequently Asked Questions post I directed you to clearly explains in several places that failure to wipe data (factory reset) in recovery before flashing a ROM will cause problems. It also tells you that when users revert back to stock without wiping data, they get stuck at the Kindle Fire logo (Q:16). When FireFireFire gets overwritten by the stock bootloader (which is what happens when you revert to stock), there is no access to fastboot for changing the bootmode to recovery so that data can be wiped (which is the only way to fix the problem). Also, without FireFireFire installed, the only way to access fastboot is through the shell (which is obviously not possible in this case) OR with a factory cable. I believe I hinted to the need for a factory cable in one of my previous posts?
So try to pay attention to the information that is available to you or you'll risk getting yourself into another situation that you cannot get out of in your own capacity, and you'll then have to rely on the accuracy of the information given to you (and the limited patience) from a******s like me
Click to expand...
Click to collapse
I'm sorry this on top of my school work this is hard I will read much more carefully my factory cable is coming today in the mail
Bruce8289 said:
I'm sorry this on top of my school work this is hard I will read much more carefully my factory cable is coming today in the mail
Click to expand...
Click to collapse
When I plug the device in with the factory cable the screen starts
Flashing on and off
Plug your device into USB (oem cable) and hold the power button until it shuts off and let it charge overnight.
soupmagnet said:
Plug your device into USB (oem cable) and hold the power button until it shuts off and let it charge overnight.
Click to expand...
Click to collapse
ok will get back to you when done
Bruce8289 said:
ok will get back to you when done
Click to expand...
Click to collapse
i was able to install fire fire fire the version with the white and blue logo but i can not install twrp now
Bruce8289 said:
i was able to install fire fire fire the version with the white and blue logo but i can not install twrp now
Click to expand...
Click to collapse
You're going to have to be a little more specific. Just saying "i can not install twrp" doesn't give anyone any clue as to why.
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
I would reflash the rom.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
jonduben said:
I would love to, but I can't get it to connect to the PC long enough to do anything, how can I do that?
Click to expand...
Click to collapse
This is my problem exactly as well! I got rid of the error messages by clearing the data of contacts, contacts storage and calendar applications.
You can do this from settings -> applications -> all applications
Any help for the continuous lock screen -> home screen -> boot logo -> lock screen -loop would be appreciated!
I ran TWRP and had a custom rom on it before, but then reverted back to stock rom and am now running 6.3.2 from Amazon itself without any custom bootloaders.
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
kesman said:
So I got mine working, and now I feel really super embarassed.
Not sure which trick finally did it, but here's what I did:
I can't paste links yet as I am a newb user on the forum, but google for "kindle fire usb debugging" and open the result saying "Setting Up Your Kindle Fire Tablet for Testing". Note that there are two steps in that guide, first install the Amazon provided USB-driver and then prepare your Kindle.
Then the embarassing part: change the USB-port. I tried with three different cables and four different ports. Apparently the ports on the front of my desktop pc aren't good for this. After switching ports to behind my pc, Kindle Fire Utility all of a sudden was able to push in TRWP and FireFireFire bootloader!
4th: Wipe EVERYTHING using TRWP. Everything might not be necessary, but I figured why not. Even the SDcard had to go.
5th: Push in an older TRWP with instructions from here: teamw.in/project/twrp2/79
The instructions are a bit messy, after "idme bootmode 4002" you should exit the adb shell and run the fastboot command.
Having the older TRWP seems to be the only way to install Amazon's stock rom, newer ones give me errors. The version I used was 2.2.2.1.
I also installed the 6.3.1 version of the stock rom just to be sure, and let Kindle do the update afterwards on its own.
Everything seems to be working now, hope you'll get yours working too!
Click to expand...
Click to collapse
you can also install the flashable zip version of 2.2.2.1 in current TWRP.
jonduben said:
This is somewhat unique, I haven't found an exact duplicate of this problem yet, but basically I have 2 original KF's. I rooted them months ago, and installed android 4.2 on them. I got a couple new tablets and decided to bring these back to factory defaults, so I went through the process. One worked great and is currently able to do everything as per usual. The second is in a perpetual boot loop. I can't get FFF or TWRP to install because it won't stay booted long enough. It will boot usually with the Kindle Fire gold and white text, and then go to the unlock screen. Once I swipe to unlock, I get a handful of errors about processes not working properly. I can navigate around for right about 20 seconds before it immediately reboots. There is no shutdown process, just a black screen and then the KF logo again. I have a full charge and I am at a loss, any suggestions?
Click to expand...
Click to collapse
I'm having the exact same issue. Were you able to fix yours?
fooz said:
I'm having the exact same issue. Were you able to fix yours?
Click to expand...
Click to collapse
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
sd_shadow said:
kindle had a custom rom, and then you installed stock update.zip and now it's bootlooping?
Click to expand...
Click to collapse
Correct. I wiped everything first, then renamed to update.zip and flashed stock.
Which update did you use? Bin name?
sd_shadow said:
Which update did you use? Bin name?
Click to expand...
Click to collapse
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
update-kindle-6.3.3_D01E_4112920.bin
fooz said:
This one. https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin[/QUOTE]Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely that will work, with 6.3.3
.
sd_shadow said:
file should be 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
update-kindle-6.3.3_D01E_4112920.bin
Click to expand...
Click to collapse
Probably need a fastboot cable to fix, Amazon has locked that version down pretty good.
see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
if the md5 checksum matched
could try the [UTILITY] Kindle Fire Unbrick Utility V1.1
but think it is unlikely t will work, with 6.3.3
.[/QUOTE]
Thanks for your help. Will try this and report back.
Okay, let's get this party started. I rooted my Gen1 Kindle Fire a few weeks ago and installed Cyanogenmod, CM11, I think. It worked pretty well. Kinda sluggish, but it's an old tablet so whatever. At one point or another, I had to turn the tablet off and restart it after a few days. And then it broke completely. Still not entirely sure why, but that's not why I'm here. Rebooted to Recovery, and the next five hours were filled with failed install attempts, factory resets, full wipes, and mounting. I stopped doing all of this and went to bed at about 1 AM, so it was all kind of a blur unless state-dependent memory kicks in tonight.
Flash forward to this morning, I get back to work on my Kindle Fire and find that, much to my dismay, I can't mount it. Not even in TWRP. I used to be able to, but now I can't. At first I thought it was the computer, so I went to another computer, and that one didn't work either. No biggie, I'll just use ADB to sideload an OS and then I'll be able to transfer files on there. I install the new OS and the Gapps, but it still won't connect. The next 12 hours at this point are spent googling and trying everything.
So now I'm here. I'd say it was because I damaged the USB port, or wasn't using the proper cord, but I've been using the same cord I always use, and every time I hook it up, it says it's installing drivers, but that installation eventually fails. When I go to Device Manager, The F drive under Portable Devices is usually missing, and the failed kindle driver is under Other Devices.
Now, I could just use ADB, but it's just kind of a pain and needlessly obtuse compared to simple drag and drop, and I'm a little worried at this point because, as previously stated, it won't even mount in TWRP.
If I weren't desperate, I wouldn't have made an account to beg and annoy you fine folks for help, but I've looked everywhere else and can't seem to find anything.
Thanks in advance.
Which bootloader? Have you tried Fastboot commands?
Sent from my XT862 using Tapatalk
sd_shadow said:
Which bootloader? Have you tried Fastboot commands?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?
Imasargent said:
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?
Click to expand...
Click to collapse
Some people worked very hard to prepare guidance material for beginners like you. So you just have to allot your time and attention reading that.
I am sure this post might help you to deal with kindle drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Imasargent said:
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?
Click to expand...
Click to collapse
Fastboot devices
Fastboot reboot
Sent from my XT862 using Tapatalk