Related
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
I remember the instructions for the skorpn factory cable says to plug it into your computer first and then your device. Make sure you hold the power button for 20 seconds to shut it down first.
I just read through more information. I don't think this factory cable is even getting me into fastboot mode. What's my screen supposed to look like if it is in fastboot? I can't find any info on what that looks like.
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Thepooch said:
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Click to expand...
Click to collapse
Is firekit the one where I need to crack open the back case? I really hope not...
jeffjoleen said:
Is firekit the one where I need to crack open the back case? I really hope not...
Click to expand...
Click to collapse
You're fine. I watched your video. The first time you plug it in, I think you hit the power button with your forefinger before you plugged it into your computer and the KF booted normally. When you turned it off, back on again, and then it got "stuck" on the "kindle fire" logo... that's what's supposed to happen with the factory cable. Your KF should now be in fastboot mode. Now you have to get your drivers working so that the computer sees the device properly and you'll be able to issue fastboot commands.
Look at this link...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
compare what you get in the device manager with the table in the middle of that post. You should be seeing "Android Phone -> Android Composite ADB Interface" in the list. Then it's a matter of opening up the Windows command prompt program and sending the KF some fastboot commands to have it boot into recovery. That's in one of the posts you already mentioned in the OP.
EDIT: My bad... that should be "Android Phone -> Android ADB Interface"... no "Composite" in there.
This is new...I now go to the Device Manager and it shows under the main "Martin-PC" I now have "Android Phone" with the "Android ADB Interface" nested underneath it. I don't think it's going into fastboot mode like the factory cable is supposed to do. What is it supposed to look like?
Unfortunately Jeff it is but I really wonder about your situation because your not getting to the fff bootloader but you may be getting to the stock one . So get it where your just looking at the kindle fire logo not the pissed of unicorn go to kfu shift+right click on the tools folder choose open command window here then type fastboot devices post the results here if any
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
I don't want to discourage you guys from trying to help people here who find themselves in trouble, but please try to understand the problem before offering guidance. How can you fix something without understanding the situation?
Hyperrunner said:
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
Click to expand...
Click to collapse
The system software on his device is broken and will not boot. Setting the bootmode to normal with KFU or otherwise doesn't fix anything. That would just put him right back into the situation he's trying to get out of in the first place. He doesn't want to get out of fastboot mode the way you're suggesting, he's trying to get into fastboot as the first step in flashing a new ROM.
xiaohewu said:
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
Click to expand...
Click to collapse
The OP and his followup posts show that he doesn't know if he's even in fastboot mode. Your question doesn't even make sense in this context.
Guys, this post isn't meant to chastise you for trying to help. Just don't throw out random things to people who are already flustered and confused as it is.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you fix your KF?
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:
First off, I have successfully installed CM10 on two different Kindle Fire's. One was using a linaro build from Hash, and the other was using the Aliem Rom v 2.0. I just tried to install CM10 on a third Kindle Fire using Alien Rom 3.0 and it sat at the alien bootscreen for 10 minutes. I figured, maybe the build is a bit buggy, loaded the Alien Rom v2.0 and it just turned off the screen after about 3 seconds of trying to boot. Loaded another linaro build afterwards and it is now sitting at a screen that says "Cyanogen Mod" with rotating circles. Not sure what is going on here, yes my FireFireFire is up to date (1.4a), yes my TWRP is up to date (2.2.2.1) and I have wiped Cache/dalvik. Any idea as to whats going on here? Tried searching the forum and have found nothing.
Thanks
Did you wipe system and factory reset?
soupmagnet said:
Did you wipe system and factory reset?
Click to expand...
Click to collapse
What will happen once I do those two things?
When you change ROMs you absolutely have to format the existing system and data partitions or you will experience exactly what you are experiencing now.
soupmagnet said:
When you change ROMs you absolutely have to format the existing system and data partitions or you will experience exactly what you are experiencing now.
Click to expand...
Click to collapse
Thank you so much, was exactly what needed to happen.
God Bless,
Jay
Thanks too! I was having this exact problem, you guys are life savers!
ericvolp12 said:
Thanks too! I was having this exact problem, you guys are life savers!
Click to expand...
Click to collapse
I have same problem, but how do i go back in to recovery to do factory reset and wipe? I am stuck on cyanogen loading screen!!
That depends. What does your boot logo (not boot animation) look like?
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
That depends. What does your boot logo (not boot animation) look like?
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
It says "kindle fire". White kindle, orange fire
I also forgot to mentioned that the KFU can't find the device. Keeps saying waiting for device.
gottabekin said:
It says "kindle fire". White kindle, orange fire
I also forgot to mentioned that the KFU can't find the device. Keeps saying waiting for device.
Click to expand...
Click to collapse
See my post here:
http://forum.xda-developers.com/showthread.php?t=2088864
"That's a special kind of stupid. The kind that makes me laugh."
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Read This
elmolisa885 said:
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Click to expand...
Click to collapse
Read This :good:
I Looked at it and it doesn't seem to solve my problem
serendipityguy said:
Read This :good:
Click to expand...
Click to collapse
I read the unbricking section of the guide and it doesn't help me very much. I think the one I need to do Is buy the special usb cable and I don't want to do that....I there another way? I'm so confused....
elmolisa885 said:
I read the unbricking section of the guide and it doesn't help me very much. I think the one I need to do Is buy the special usb cable and I don't want to do that....I there another way? I'm so confused....
Click to expand...
Click to collapse
I could be wrong, but it sounds like you are stuck in fastboot mode after flashing twrp. I don't think you are bricked. You can confirm this by using fastboot from your pc.
FWIW, wiping system is ok when flashing a rom - but wiping internal storage before flashing will leave you without any file to flash. Simply push the rom to the sd card on kindle (google it). You may have to reboot recovery for twrp to show the newly added file.
So bottom line - change the bootmode from fastboot to normal. Boot into recovery. Push new rom/gapps using adb. Reboot recovery. Flash new rom and gapps.
I think with so many threads like this folks are just sick of directing people to all the other multiple threads that would tell you how to fix this. Next time please use the 'search' feature (not trying to be rude here, but the first rule of XDA is to search).
elmolisa885 said:
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Click to expand...
Click to collapse
If you flashed update.zip sounds to me like you have a broken or missing shell. In which cases you will need a factory cable found here post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . This will force it into fastboot so you can reflash fff and twrp then add a running OS.