Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
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.
Was trying to root kf . started "Install Permanent Boot, etc." all seamed to be going OK. Went as far as TWRP was installed. At that point the OS for the fire was GONE. Fire is hung at TWRP. No operating system for anything. Plz HELP
If TWRP is still functional, then you can just "mount USB," put a rom and gapps into the folder, flash them, then boom! You'll have an OS again; just basic protocol haha.
I would also wipe data/cache, dalvik, etc. just in case...
...But if you want stock Amazon Gingerbread then you're going to have to look way back in time in the forums for the stock rom.
What happens when you reboot system? Does it go right back to TWRP?
Me Too
I have no OS on my kindle fire. I wiped the memory and now I lost my roms and backups. I heard you can try ADB, but I couldn't get it to work. Mine just boots to the kindle fire logo but nothing else happens. It's basically collecting dust.
Take a breath, relax, and take comfort in the fact that there is nothing wrong with your Kindle. It is doing exactly what it was told to do. Your problem is easy to fix, but you need to know what's going on first.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it. Then read it again. And while you're at it, go ahead and read it a third time. Do this before anything else.
[Edit:] Oh yeah, and read this too.
http://forum.xda-developers.com/showthread.php?p=25730650
Ahh, what the hell, read this one as well.
http://forum.xda-developers.com/showthread.php?p=26435498
soupmagnet said:
What happens when you reboot system? Does it go right back to TWRP?
Click to expand...
Click to collapse
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
"
Click to expand...
Click to collapse
jerryhndy said:
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
Click to expand...
Click to collapse
Wow, very interesting, and welcome back.
Weird. It's almost as if you have TWRP installed to the system partition. Selecting "reset boot" on FFF1.4 changes the idme value to 4000, so your device should boot to the system partition no matter what. But you said the boot logo changes from blue to red. What's actually happening, is the bootloader finishes doing it's thing and then boots to the system. The red and white Kindle Fire logo you see then is the stock boot animation, which makes everything really strange. "Recovery" boot shouldn't show the boot animation at all. And if you have recovery installed to the system partition, you shouldn't see the boot animation there either. WTF did you do to your Kindle?
My best advice would be to get into fastboot and reinstall TWRP to the correct partition so you can reinstall your ROM. From the sounds of it, you will likely have no access to the adb shell, in which case you would need to get a factory cable.
So, boot into recovery and enter the following command to see if you even have a working shell:
Code:
adb shell idme bootmode 4002
no os
jerryhndy said:
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
Sorry, above is the correct info that I sent in. #2 is "recovery. Sorry for the confusion.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
soupmagnet said:
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
Click to expand...
Click to collapse
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
jerryhndy said:
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
Click to expand...
Click to collapse
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
soupmagnet said:
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
Click to expand...
Click to collapse
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
jerryhndy said:
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
Click to expand...
Click to collapse
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
soupmagnet said:
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
Click to expand...
Click to collapse
I found a keyboard in TWRP in the KF, however it would only let me type #'s. I think I am lost here. Do you accept KF's (sent to you), for
repair or what ever to get it to root ?? If so, I could sent it to you etc. [email protected]
Soupmagnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Thepooch said:
Soup magnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Click to expand...
Click to collapse
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
jerryhndy said:
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
Click to expand...
Click to collapse
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Thepooch said:
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Click to expand...
Click to collapse
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
to
jerryhndy said:
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
Click to expand...
Click to collapse
I sent you a pm Jerry. I would not charge you. Lets take a look and see if we can`t fix it without you even having to ship it.
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:
Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!
notiboy07 said:
Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!
Click to expand...
Click to collapse
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<
!
11fan said:
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<
Click to expand...
Click to collapse
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!
notiboy07 said:
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!
Click to expand...
Click to collapse
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike
11fan said:
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike
Click to expand...
Click to collapse
Thanks again @Mike. However, i wasn't able to do my factory backup images. and secondly, what did you use to restore the images? Did you use KKFA or the KFHD SRT? i'm sorry, i kinda scared now to proceed on my own.
From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!
notiboy07 said:
From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!
Click to expand...
Click to collapse
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Thank you for the prompt reply. So now i know those wouldn't work. Yes, fastboot is working - it says fastboot on the screen of the kindle fire 8.9. Ok, so i need to get that recovery image - however, i think you were not able to link that thread. I'm sorry, can you please paste the link again?
I'm on google hangouts now. [email protected]
Thanks a lot @Mike!
I have been reading XDA for years, My KFHD 8.9 recently stopped booting also
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)
Umisguy said:
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)
Click to expand...
Click to collapse
I dont think this is the same case @Umisguy as you have not tinkered with your tablet (100% stock), while mine happened while trying to install a custom ROM. Maybe the amazon guys can help you?
Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files
11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Folks,
I got in to the same trouble able to mess up the KF and get a redscreen but used KFHD SRT to reflash the 8.1.4 system image, boot image, recovery image but now I ended up in the boot loop mode where it shows reboot kindle or Reset to factory Dafaults but as I flashed every thing am unable to reset to factory. As I got the tablet recently it came with 8.5.1 so I need to try with the latest image I can get.
If there are any suggestions i can try please let me know.
Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike
11fan said:
Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike
Click to expand...
Click to collapse
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.
I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk
11fan said:
I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
That will be great Mike.
Thanks,
Krishna
krishnasanga said:
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk
krishnasanga said:
That will be great Mike.
Thanks,
Krishna
Click to expand...
Click to collapse
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike
11fan said:
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike
Click to expand...
Click to collapse
Mike,
I tried with this new boot and recovery images but still stuck in the loop , can you upload your backup files of 8.5.1 system.img,boot.img,recovery.img I think that will be my last shot to try to unbrick this device.
Thanks,
Krishna