Related
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Could you post what you did or tried to do that bricked it?
99 times out of 100 rebooting will fix the "waiting for device" problem, especially if the PC drivers are installed appropriately, but I'm guessing you already tried that. I'd do it a few times, why not?
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
soupmagnet said:
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
Click to expand...
Click to collapse
Win7 64bit Ultimate
Stock
It's a clean kindle with nothing on it that got bricked while I was rooting it, some how.
My experience is really only a 1 time root when i first bought it back in January.
Very familiar with my OS.
Average with command line interface
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
nchevaux said:
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
Click to expand...
Click to collapse
it stays on the kindle fire logo until i hard reset it.
I was using KFU when this happened.
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
soupmagnet said:
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
Click to expand...
Click to collapse
how am I supposed to put it on the kindle... Did you not read my other posts?
It won't let me do ANYTHING to it.
Did you install the drivers from kfu with your kindle plugged in?
needhelpplease3 said:
how am I supposed to put it on the kindle... Did you not read my other posts?
Click to expand...
Click to collapse
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
needhelpplease3 said:
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
Click to expand...
Click to collapse
Don't make a long story short. The more information you can provide, the better.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Click to expand...
Click to collapse
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
soupmagnet said:
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
Don't make a long story short. The more information you can provide, the better.
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
Click to expand...
Click to collapse
Sorry, I've just been really agitated by this whole situation. I've asked another forum and got back with horrible answers.
To start all over again, this is what happened.
I had my kindle fire at 6.3, unrooted (only unrooted because of the update), and decided to why not root it again, just so it's updated.
I got all the necessities to root the kindle, the same things I used when I first got it, and started up the process.
At first, the drivers were giving me issues, but that got settled quite quickly.
Then when I started up KFU, I did the perm root, but it somehow got canceled in the middle of it, so I'm guessing that's what has screwed it up.
Now when I plug it into either my Wall or USB adapters, it doesn't work.
I've tried that hard reset way, where you hold down the power button for 30 seconds, and that didn't work either.
So I got fed up, and came here for answers.
Right now, it's basically a dead Kindle Fire.
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
soupmagnet said:
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
Click to expand...
Click to collapse
Great... I'll try it. I'll tell ya what happens. Thanks
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
needhelpplease3 said:
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
Click to expand...
Click to collapse
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
soupmagnet said:
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
Click to expand...
Click to collapse
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
needhelpplease3 said:
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
Click to expand...
Click to collapse
Stop! before you screw something up.
More to follow....
soupmagnet said:
Stop! before you screw something up.
More to follow....
Click to expand...
Click to collapse
You're confusing me.
More to follow?
When I asked you "What happens when you try to power the device on?", I'm looking for specifics, i.e. "When I press the power button, nothing happens and the screen doesn't come on at all", or "The screen comes on, but the boot logo flashes on and off", or "The screen comes on, but hangs steady at the boot logo".
It is very important that you make this clear from the very beginning because it will help us in not telling you do do the wrong thing and potentially causing serious harm to your device.
I'm getting conflicting symptoms from you and it is making helping you rather difficult. If your screen doesn't come on at all the only fix for that starts with the "shorting trick". When you say that your screen was turning on and off it makes me think that it was doing that all along, which would require a completely fix.
If I'm going to help you I need to know exactly what is going on with your device along with any changes it has made and when they happened.
OK...I'm a first time poster to the Kindle Fire forum and I'm having issues. I'm a little above average with my Android knowledge. I've flashed CM9 onto three Toucpads and have been fooling with my phones for a few years. HOWEVER, I'm completely stumped. Here's what's happening and what I've done.
1) I downloaded Kindle Fire Utility to root. It all went fine, as far as I could tell.
2) I downloaded the aokp_otter_build-M5>0xD34D build for CM9
3) I downloaded the gapps-ics-20120429-signed zip
4) Booted into the TWRP recovery
5) Made a backup of the stock Kindle
6) Flashed the CM9 zip and the Gapps zip. Everything seemed fine with the TWRP. Never used it before. Very familiar with CWM and seemed similar
7 Rebooted.
The Kindle Fire logo came up and then went to a blank screen. It boot-looped (is that a verb?) five or six times. While I went surfing to find answers it looped once more and came up to this screen with a pissed off looking unicorn and the Team Kang logo. It's stuck there and won't go past. The screen is still animated. The battery is not dead. I've read dozens of posts where the first suggestion is to charge the Kindle. That's not the problem. I've restarted the Kindle a hundred times and nothing.
Here's what I've tried:
1) Every combination of holding down the power button/pressing the power button combination. Nothing.
2) Downloaded the Kindle Unbrick Utility. The computer isn't recognizing the Kindle, so this isn't doing any good. I've tried all of the six different UI buttons. Nothing.
3) I went back to the Kindle Fire Utility and reinstalled the drivers and then opened the CMD window. As I expected, it's telling me "waiting for device" and doing nothing.
I have no idea where to go from here. There's got to be a way for me to get this thing to be recognized on my computer. Please help. Any advice would be greatly appreciated. Thanks! -Jeff
It's like deja vu...
http://forum.xda-developers.com/showthread.php?t=1658205
Even the description of the bootanimation is eerily the same.
I think my assessment of his problem would apply to you as well. If you want to skip most of the discussion, my post is at (or very near) the end.
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
jeffjoleen said:
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999
Probably wouldn't hurt for you to look this over either...
http://forum.xda-developers.com/showthread.php?t=1552547
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Thepooch said:
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
Click to expand...
Click to collapse
Honestly...don't remember if I did a full wipe of dalvik. I assumed I would have, but really don't remember. No...I don't get the yellow triangle and my kindle fire logo color is white "kindle" with a yellow "fire". I used the kindle fire utility and I think that installs the twrp by default. I don't have CWM installed. Wish I did. I'm comfortable with it. I just can't get to any kind of a recovery screen.
soupmagnet said:
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Click to expand...
Click to collapse
Yes...the KFU went fine, I think. I was able to access twrp and created my backup before I flashed the ICS. The Kindle logo has the white "kindle" and yellow "fire". Pauses for a few seconds or two...screen goes black...then that damned pink unicorn shows up and stays there. The unicorn screen is animated. I can power it down from there and start over without any problem. Any ideas?
without a bootloader you wont have access to recovery regardless of twrp/cwm
One other thing that I'm not sure matters, but when I do power it off and back on, I head the little "bong" on my computer telling me that a new device has been plugged in. I go to the device manager and under the "Other" category it shows "Amazon" with the yellow triangle the black exclamation point symbol.
Reinstall your drivers
Thepooch said:
without a bootloader you wont have access to recovery regardless of twrp/cwm
Click to expand...
Click to collapse
I guess that's where I am a little confused with definitions. I understand about the twrp and cmw recovery set ups. What exactly is a bootloader? Thanks for not laughing...
Thepooch said:
Reinstall your drivers
Click to expand...
Click to collapse
Through the Kindle Fire Utility? If so, I've done that several times. Would trying a different computer and installing them there make any difference?
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
First, read this...
http://forum.xda-developers.com/showpost.php?p=23747567
You need to make sure your drivers are in order so you can change the bootmode to 5001 and reboot. A custom bootloader will let you do this easily but considering you don't have one you need to use adb instead.
Code:
adb shell
idme bootmode 5001
adb reboot
Thepooch said:
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
Click to expand...
Click to collapse
So, without a functioning bootloader I won't even be able to get to the twrp to access my back up I made. Nice. Just bought this damn thing yesterday. I'm kinda missing the one-click jailbreak software from my old iphone a few years back!
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
I just read through the basic instructions. I'll grab a usb thumbdrive and give it a shot. Thx
good luck hope you get through this is the not so fun side of rooting
Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks. It answered some of my questions. I guess it helped me relax a little, too. I know this is a problem that can be fixed. Just need to dig in an try each suggestion until I find one that works.
Today I tried loading 4.1 Jellybean on my fire, but it wasn't opening applications properly and being annoying so I unloaded it. I used KFU to root it, and had TWRP recovery on it. I then figured I'd revert it back to the default OS, so I grabbed a copy of the kindle fire 6.2.1 software from Amazon's page and renamed it to update.zip (it converted to a .zip with identical contents to the one directly from KFU).When I had TWRP, KFU recognized my device as online, but didn't have a version, so there was no help there. I wiped the entire thing using the recovery tool and then I hit "Install --> Update.zip". Everything seemed fine after this worked, so I rebooted the device. I thought it worked, but now it's stuck at the Kindle Fire default splash screen. When I plug iit into my computer, Windows doesn't recognize it, nor does KFU. I haven't tried letting the battery drain (since that would take awhile), but it seems like it's bricked. Please help!
EDIT: My main problem right now is that it can't even be recognized at windows. I feel like it's stuck in the wrong fastboot mode right now, but I can't even get windows to recognize it. Also, it's not running Fire fire fire, the splash screen shows the basic unanimated Kindle Fire logo. It's likely stuck on fastboot 4002 instead of 4000. I'm currently letting the battery drain so I can plug it in and see if windows will recognize it. My guess is that I can get it to work as long as windows will recognize it.
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!
soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!
Click to expand...
Click to collapse
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
shnish said:
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
Click to expand...
Click to collapse
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
I know that you know more about this than me, but I feel like if it's stuck on the wrong fastboot type, preventing the battery from draining would be a bad idea (or at least slow down the "fixing" processor). Sorry, but why does that seem so wrong?
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963
soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
soupmagnet said:
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
shnish said:
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
Click to expand...
Click to collapse
umm...
soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
Click to expand...
Click to collapse
soupmagnet said:
umm...
Click to expand...
Click to collapse
Alright. Looks like I might need a factory cable?
shnish said:
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
Click to expand...
Click to collapse
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
kinfauns said:
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
Click to expand...
Click to collapse
The device ended up losing power, but it still powers on properly when I plug it in (stuck on the kindle fire logo, of course).
I suppose it's not in fastboot mode, it's just stuck on the stock loader. I'm not quite positive, but it seems like I'll need a factory cable to get this thing working again. I really don't want to have to blow any money on this, if I can revert it back to stock settings easily, I'll never mess with it again. Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
shnish said:
Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
So if I install Ubuntu, I should be good to go? Ubuntu will recognize the kindle fire?
Read the post I gave you.
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
Yes. He has the exact same problem as me! I did the same thing as him, and I'm really hoping I'll be able to solve this issue. All I want is the stock kindle back so I can stop worrying. I've read through tons of these posts (I have 13 xda posts open in my browser), but none of them seem too helpful as to how I can get my computer to recognize the Kindle. My guess is that Ubuntu won't recognize the Kindle either, though. In that case, would a factory cable solve all my problems? I stupidly removed root access by simply updating my kindle fire without thinking of the problems that could have come with that. I figured it would just remove root access and start booting up normally. I was very wrong.
soupmagnet said:
Read the post I gave you.
Click to expand...
Click to collapse
I'm going to try it in Ubuntu, but assuming that doesn't work, I'll need to get a factory cable. What do I do to revert to stock settings once I have a factory cable?
I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
soupmagnet said:
I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
Click to expand...
Click to collapse
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
shnish said:
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
Click to expand...
Click to collapse
:good:
I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.
I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
jjdavola said:
I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
soupmagnet said:
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
jjdavola said:
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
Click to expand...
Click to collapse
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
soupmagnet said:
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
Click to expand...
Click to collapse
Thanks. I'm still holding out some hope, but I tried to charge it all night with a wall charger and it did nothing.
Since there's no replies, I'm guessing I'm really SOL. Anyone want to buy a brick?
Anyone???
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Thepooch said:
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Click to expand...
Click to collapse
Thanks for the reply. The strange thing is once I got the fastboot cable the green light on the KF2 was on, so I thought I had time. Then after trying to restore everything for a few minutes, the KF2 just died and never came back to life. Although I did connect the regular USB in that short time to see what would happen and it just bootlooping.