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."
Related
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.
Hi there,
This is my first post to the group. I have searched and (I think) read through the appropriate threads before posting. I am having a problem with my KF and I think I know what the solution is, but I wanted to confirm my suspicions.
As of yesterday my device had TWRP with a Jelly Bean ROM on it and all was well. I needed to go back to stock so I downloaded the stock rom, renamed it to update.zip and flashed with TWRP. It completed the flashed but that was when the problems started.
My KF is now stuck in a reboot loop, but I don't think it's the fastboot loop that I've seen in a ton of different threads. My problem is the device starts up, gets to the home screen and around 10-15 seconds will restart. When I try to go to the main KF interface, I get a couple of FC errors:
The process android.process.acore has stopped unexpectedly. Please try again [FC]
The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again [FC]
Then the device restarts.
I have a Mac and a PC -- on the Mac I tried Breakdroid and on PC I tried the Kindle Fire Utility but can't connect/get access to the KF to install anything. Kindle Fire Utility v0.9.6 reports ADB Status: Offline and Boot Status: Unknown. I've read that this could be a battery problem but I don't think so since it happened immediately after flashing.
One thing I found interesting though is that on the Mac, when I can get the KF to mount the drive will stay visible through the restarts -- not sure if that means anything but thought I would mention.
The big problem is that I can't access fastboot or get access via Kindle Fire Utility or BreakDroid. My guess is I need a factory cable to get access to fastboot, but is there anything else I should try first?
Thanks in advance for your help. If this question has already been asked and answered then please accept my apologies.
Thanks!
Robert.
This is from not doing a factory reset in TWRP before installing the stock update.zip.
Unless you have access to the adb shell to change your bootmode to fastboot (4002), you'll need a factory cable to get into fastboot so you can reinstall TWRP and try again.
"That's a special kind of stupid. The kind that makes me laugh."
Thanks
soupmagnet said:
This is from not doing a factory reset in TWRP before installing the stock update.zip.
Unless you have access to the adb shell to change your bootmode to fastboot (4002), you'll need a factory cable to get into fastboot so you can reinstall TWRP and try again.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
----
Hey soupmagnet,
Thanks a ton for the info! Yes, you are correct I didn't do a factory reset in TWRP before installing the file. I just ordered the cable so I'm sure that will fix the problems.
Glad I could add some humor to your day.
Thanks,
Robert.
rlindsley said:
Glad I could add some humor to your day.
Click to expand...
Click to collapse
???
Are you referring to this?...
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I received that in a PM one day and thought it would be hilarious to have it as my tapatalk signature. It's all just fun and games.
I wonder how many people think it's actually directed toward them... :silly:
"That's a special kind of stupid. The kind that makes me laugh."
Too funny
soupmagnet said:
???
Are you referring to this?...
I received that in a PM one day and thought it would be hilarious to have it as my tapatalk signature. It's all just fun and games.
I wonder how many people think it's actually directed toward them... :silly:
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ahhh yes, I thought that was directed at me. What I did was kind of boneheaded, so I thought....well, I guess I kind of deserve that LOL.
Thanks again for your help. I can't wait to revive my KF.
Thanks!
Robert.
Please help!
I recently rooted my sons Kindle fire 2 using TWRP, all was going ok until reboot when screen would flash every couple of seconds, flashing the kindle logo even when at the carousel screen etc.. also slow and slow to react to touch of the digitiser screen. From here I think I have got it terribly wrong and have wiped the KF of its OS and with it also stuck in fastboot.
I have made wrong selections on TWRP, then used TWRP command to boot the KF into fastboot. Now have no way to get it out of fastboot, only recognised on windows 7 device manager as Kindle Fire - Android ADB interface and also as a Other Devices - coprocessor which has no recognised driver.
Please note: i think I used nearly all options in TWRP and this is why I think I may have wiped the OS from the KF.
The fastboot screen is the traffic light logo, the green light is the only light that flashes!
when holding for 20 secs then powering back up it boots straight to fastboot after 1 sec of kindle logo showing.
Has anyway managed to save a KF2 from this state?
use this tool to recover:
http://forum.xda-developers.com/showthread.php?t=2035047
otherwise read in the q&a section.
there are many more with similar probelms.
Thanks for supplying this info flopower!!
Lets give it a go!:fingers-crossed:
Totally Mental!
Ok, firstly I feel bad to all of you who do have a bricked Kindle but I have no idea how my Kindle has now recovered!
I bought another Kindle Fire as I made the conclusion that I had totally made my son's unusable. Tried all the recovery programmes with no joy. Was permanently stuck in fastboot mode with the assumption that no OS was on it after deleting all by accident.
My plan was to use the replacement box and put the bricked Kindle in it and return it to the store where i got the new one from, explain to the staff member that my son had just purchased this the other day and on start up and registering the device he was then informed that the Kindle needed to update the firmware. On reboot this Kindle would always show this fastboot screen, explain that I had a look also and could not get it back to its normal state. So I went round but switched off the Kindle first, informed the staff member of what has happened at the same time handing it over to her whilst switching on. I noticed that the Kindle logo as normal would come up but normally within a second it would go to the fastboot screen. This did not happen and I was like twat u twat you have brought round the new one by mistake! right enough the Kindle started up with the original first setup state. So I got myself away as quickly as possible and thought I will just do the same at another branch but this time put the right Kindle in the box. So now back at the house made a cup of tea and sat down, the Kindle which I left behind was on the table next to me and was switched off, I pressed the power button for some reason on it, to my surprise I was welcomed with also the orignal new set up screen! This was the new Kindle!!!!!!!!! I did take the bricked Kindle to the branch and for some reason it was now working, I have even just updated it from to 10.2.6 as it was on 10.2.0 with no issues, turned it on and off nearly 10 times all is perfect!
Unbelievable totally unbelievable! do not understand how the Kindle is now back in play!
I have rebooted tried all options of KFU, KFFirstAide etc etc..... always instantly rebooted in fastboot state! even upto an hour before going round to the shop it was still doing the same, I also tried to electrocute the Kindle so the mainboard would be fried! cant be believe it!
Sorry I will never be able to give an explanation of how it worked!
It seems as if you got off lucky. I incorrectly installed CyanogenMod, and got stuck on the boot anmation. Of course, I din't make a backup, and so I went to another thread and someone stupidly said to wipe the system. Now I'm left without an OS, as TWRP tells me. I don't know how I am going to fix this, as I can't post a thread because I have less than 10 posts.
AW: [Q] Kindle Fire 2 stuck in fastboot - No OS possibly installed
Restore your entire system with fastboot
Gesendet von meinem LG-P990 mit Tapatalk 2
soulcedric said:
It seems as if you got off lucky. I incorrectly installed CyanogenMod, and got stuck on the boot anmation. Of course, I din't make a backup, and so I went to another thread and someone stupidly said to wipe the system. Now I'm left without an OS, as TWRP tells me. I don't know how I am going to fix this, as I can't post a thread because I have less than 10 posts.
Click to expand...
Click to collapse
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks. I'll try it.
---------- Post added at 11:05 PM ---------- Previous post was at 10:58 PM ----------
chronicfathead said:
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks so much. I figured out that all I had to do was wipe the system. Now I have Jelly Bean!
Almost same problem
flopower1996 said:
Restore your entire system with fastboot
Gesendet von meinem LG-P990 mit Tapatalk 2
Click to expand...
Click to collapse
I'm running into similar problem, i "successfully" installed FFF1.4A and TWRP with it won't boot into recovery.
How can i Restore your entire system with fastboot ??
LUC4X said:
I'm running into similar problem, i "successfully" installed FFF1.4A and TWRP with it won't boot into recovery.
How can i Restore your entire system with fastboot ??
Click to expand...
Click to collapse
Read the dev section. Not sure why anyone would do anything with their device without learning how to unbrick first...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
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.
Hi! So now, I ran a recovery program, and I thought all went well, since the kindle booted up to logo, but now it'll show the regular logo, then a red screen, then the fastboot screen, and now it's stuck there. This whole thing has be a fail and now I just feel like SAFLHSKALFHSKKLSAHGSLKAHGLSKAHGSALKGHASLKHGLKAS
EDIT: After running a few recovery programs, and flashing over boot.img, recovery.img, and system.img files, it's back to just showing the kindle fire logo. For the last hour, it's just been showing the logo.
I only know one solution (the same thing happened to my nexus 10) which I would only recommend as a last resort. Keep searching for answers, bit if all else fails, try doing a factory reset or wipe and restore. But like I said, that would be a last resort.
Sent from my XT1254 using XDA Free mobile app
I feel like it's such a simple fix, but I can't figure it out for some reason.
Fleetwood Mac & Cheese said:
I feel like it's such a simple fix, but I can't figure it out for some reason.
Click to expand...
Click to collapse
Maybe try flashing the 8.1.4 bootloader file again? (taken from http://forum.xda-developers.com/showthread.php?t=2128175)
monster1612 said:
Maybe try flashing the 8.1.4 bootloader file again? (taken from http://forum.xda-developers.com/showthread.php?t=2128175)
Click to expand...
Click to collapse
Thanks. I tried that, but it's still just showing the "Kindle Fire" logo.