Ok... so here is the pickle I am in...
Press power button
Kindle logo displays
fastboot logo displays
screen goes black
unable to get it started for like 2 more minutes
Last action before accident: attempted to flash twrp recovery on kindle.
actions since crash
- flashed stock-boot, stock-recovery attempted to reboot. still no luck.
Hell Bomb said:
Ok... so here is the pickle I am in...
Press power button
Kindle logo displays
fastboot logo displays
screen goes black
unable to get it started for like 2 more minutes
Last action before accident: attempted to flash twrp recovery on kindle.
actions since crash
- flashed stock-boot, stock-recovery attempted to reboot. still no luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#32
Check first post, already attempted to load the stock recovery/boot and openrecovery-twrp-2.4.3.0-blaze.img
Hell Bomb said:
Check first post, already attempted to load the stock recovery/boot and openrecovery-twrp-2.4.3.0-blaze.img
Click to expand...
Click to collapse
I have a feeling you are in the wrong place. Are, by any chance, the images you described earlier explicitly named "stock-boot.img" and "stock-recovery.img"? If so, there's a good chance you are in the wrong place. What software version was your device running before this happened? Could you describe this so-called "fastboot logo"?
On the off chance that you do have a 1st generation Kindle Fire and not a 2nd Generation Kindle Fire, flashing the boot and recovery images will do nothing for you in your situation. You would have to reinstall the ROM as described in the FAQ listing that I referred to earlier. :silly:
Ok, so I decided to flash my KF with CM10. To do this I did the standard KFU superuser, installed TWRP, and fff. After I flashed with TWRP the Google apps and CM everything worked okay, but I noticed that my Google apps are nonexistent. So, I thought I would reflash with TWRP, which is where the problem lies. Whenever I reboot my device I get the KF logo, except white and blue, telling me to press power button to change boot, which I have tried but to no avail, and it goes straight to the CM10 boot. I thought okay maybe I can get around this by downloading Goo Manager onto my device to flash the GApps. This didn't work. So finally I just assumed my TWRP screwed up so I downloaded the recovery package from Goo Manager. This also didn't work. Also, KFU doesn't recognize it.
Right now I'm assuming the problem is fff because I've never seen this blue boot screen. If someone could help me just get TWRP back to working or even just stock KF I would be much obliged.
If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.
votinh said:
If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.
Click to expand...
Click to collapse
From what Brandon is saying, I think you hit it on the head.
One note: it takes several seconds to access the recovery from the fff 1.4a blue kindle fire logo. Once that screen pops up, hold the power button for about three seconds till recovery is selected at bottom.
It doesn't appear that you actually have a problem, either, but just a misunderstanding of what your kindle should look like.
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
votinh said:
If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.
Click to expand...
Click to collapse
When I attempt to boot to recovery I get no TWRP. The screen flashes then the normal Kindle Fire boot screen shows, then another flash and back to blue sccreen
Again, I assume you know how to do it, how to boot into recovery.
If you do it correctly and still can't get in then reinstall FFF using KFU.
If you don't know how to, then search Youtube, there's tons of videos showing how.
votinh said:
Again, I assume you know how to do it, how to boot into recovery.
If you do it correctly and still can't get in then reinstall FFF using KFU.
If you don't know how to, then search Youtube, there's tons of videos showing how.
Click to expand...
Click to collapse
Except as I said earlier KFU doesn't recognize my device. I mean I'll check my drivers, but looks doubful.
brandonstrat said:
Except as I said earlier KFU doesn't recognize my device. I mean I'll check my drivers, but looks doubful.
Click to expand...
Click to collapse
Did you bother to try what I suggested?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
jma9454 said:
Did you bother to try what I suggested?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
Click to expand...
Click to collapse
Yeah and it worked, but after restoring back to stock kf it kept sayin that process had stopped working and never allowing me to actually set the damn thing up. So reflashed CM10 and it keeps looping the boot screen, showing a quick image of the home screen then restarting the process. Long holding the power restarts the device, allowing me to get to fff but I still can't seem to get TWRP to show up unless I tell it to fast boot on the computer and since it never actually gets to TWRP or the OS I see no way to mount it.
brandonstrat said:
Yeah and it worked, but after restoring back to stock kf it kept sayin that process had stopped working and never allowing me to actually set the damn thing up. So reflashed CM10 and it keeps looping the boot screen, showing a quick image of the home screen then restarting the process. Long holding the power restarts the device, allowing me to get to fff but I still can't seem to get TWRP to show up unless I tell it to fast boot on the computer and since it never actually gets to TWRP or the OS I see no way to mount it.
Click to expand...
Click to collapse
How did you restore to stock? That isn't what I told you to do...
When you plug it into the computer, what happens?
And also, when you reboot it, and you hold the power button at the blue screen with the menu at bottom, what happens? Does it cycle through three choices? If it does, wait till it selects the second one and let go.
Sent from my Amazon Kindle Fire using Tapatalk HD
jma9454 said:
How did you restore to stock? That isn't what I told you to do...
When you plug it into the computer, what happens?
And also, when you reboot it, and you hold the power button at the blue screen with the menu at bottom, what happens? Does it cycle through three choices? If it does, wait till it selects the second one and let go.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.
brandonstrat said:
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.
Click to expand...
Click to collapse
Follow what you are saying is really a headache. You keep saying you did this and did that and that and this and I'm lost. Slow down.
Go one by one, answer what jma asked.
Forget what you have done to your KF, tell us what it is like now.
1. Can you get into the recovery? I ask again 'cuz you previously claimed you knew how to, then you didn't then you did.
2. During power up, do you see Kindle Fire with blue logo?
3. Right after that do you hold the power button?
4. Do you see it cycle through the menu of 3?
.
.
.
votinh said:
Follow what you are saying is really a headache. You keep saying you did this and did that and that and this and I'm lost. Slow down.
Go one by one, answer what jma asked.
Forget what you have done to your KF, tell us what it is like now.
1. Can you get into the recovery? I ask again 'cuz you previously claimed you knew how to, then you didn't then you did.
2. During power up, do you see Kindle Fire with blue logo?
3. Right after that do you hold the power button?
4. Do you see it cycle through the menu of 3?
.
.
.
Click to expand...
Click to collapse
Alright, sorry bout that I guess
1. If by recovery you mean TWRP, then no I don't believe so
2. Yes
3. Yes
4. Yes, but all options take me to the CM10 boot except recovery which takes me to regular stock orange kf boot for a few seconds then back to blue without the options but just boots
Hope that's a bit more clear, I guess I'm kindave panicking with my kindle being on the fritz and all. But you my good sir have been very patient and for that I thank you.
brandonstrat said:
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.
Click to expand...
Click to collapse
Okay, two things:
1) The reason you keep getting stuck at the CyanogenMod logo is because you're not wiping data (factory reset) before installing the ROM.
2) I'm very concerned because it seems that you may not know what generation of Kindle Fire you're using. You are posting in the 1st generation KF forums, but by your description you seem to have a 2nd generation KF. You need to clarify which device you have before someone gives you directions that would permanently brick your device.
soupmagnet said:
Okay, two things:
1) The reason you keep getting stuck at the CyanogenMod logo is because you're not wiping data (factory reset) before installing the ROM.
2) I'm very concerned because it seems that you may not know what generation of Kindle Fire you're using. You are posting in the 1st generation KF forums, but by your description you seem to have a 2nd generation KF. You need to clarify which device you have before someone gives you directions that would permanently brick your device.
Click to expand...
Click to collapse
1. That would make sense because I was I'm a hurry
2. It's first gen, I would have clarified had this not been a forum specifically geared towards first gen, but I appreciate your concern.
brandonstrat said:
1. That would make sense because I was I'm a hurry
2. It's first gen, I would have clarified had this not been a forum specifically geared towards first gen, but I appreciate your concern.
Click to expand...
Click to collapse
Well, you never know around here...
Since that's the case, it seems like you have a bootloader installed on the recovery partition. Your device's original bootloader is working as it should (orange KF logo), but when you change the bootmode to recovery, it boots into what should be the custom recovery, but instead is the FireFireFire bootloader. BUT...that's a best guess based on what I can piece together from the information you've provided. (I've avoided responding to this post for exactly this reason).
The problem is, your information is all over the place and much of it contradicts itself. In one post, you say you have the blue KF logo, but then in the same post, you say don't. Then you say you used TWRP to install a custom ROM, but then you can't access TWRP? But then you say you restored the device to stock using TWRP, and yet you can't access TWRP after that.
Perhaps you could explain in a clear and concise manner what your problem is, being as detailed as humanly possible, because as it stands now, you're not making any sense.
soupmagnet said:
Well, you never know around here...
Since that's the case, it seems like you have a bootloader installed on the recovery partition. Your device's original bootloader is working as it should (orange KF logo), but when you change the bootmode to recovery, it boots into what should be the custom recovery, but instead is the FireFireFire bootloader. BUT...that's a best guess based on what I can piece together from the information you've provided. (I've avoided responding to this post for exactly this reason).
The problem is, your information is all over the place and much of it contradicts itself. In one post, you say you have the blue KF logo, but then in the same post, you say don't. Then you say you used TWRP to install a custom ROM, but then you can't access TWRP? But then you say you restored the device to stock using TWRP, and yet you can't access TWRP after that.
Perhaps you could explain in a clear and concise manner what your problem is, being as detailed as humanly possible, because as it stands now, you're not making any sense.
Click to expand...
Click to collapse
Okay I'll try again, the only times I have actually been able to use TWRP is when installing it in kfu. I don't believe that it actually installed anything but it just sends it to fastboot, now I could be incorrect but what I believe is happening is the kfu is telling the kf to go to fastboot to install but TWRP is already installed because nothing ever downloads.
Is that what normally happens when you hit recovery on the fff screen? Does the TWRP require fastboot or is mine just really messed up?
brandonstrat said:
Okay I'll try again, the only times I have actually been able to use TWRP is when installing it in kfu. I don't believe that it actually installed anything but it just sends it to fastboot, now I could be incorrect but what I believe is happening is the kfu is telling the kf to go to fastboot to install but TWRP is already installed because nothing ever downloads.
Is that what normally happens when you hit recovery on the fff screen? Does the TWRP require fastboot or is mine just really messed up?
Click to expand...
Click to collapse
Something about this just doesn't add up.
Try this...
1) Download the recovery flashable .zip of FireFireFire1.4a
2) Reinstall TWRP using KFU and boot into it.
3) Use TWRP to flash the recovery flashable fff-u-boot_v1.4a.zip and reboot.
If the problem persists, take a video of it, and post it here so we can get a better idea of what's actually going on.
soupmagnet said:
Something about this just doesn't add up.
Try this...
1) Download the recovery flashable .zip of FireFireFire1.4a
2) Reinstall TWRP using KFU and boot into it.
3) Use TWRP to flash the recovery flashable fff-u-boot_v1.4a.zip and reboot.
If the problem persists, take a video of it, and post it here so we can get a better idea of what's actually going on.
Click to expand...
Click to collapse
Ok but when could I actually mount the device
brandonstrat said:
Ok but when could I actually mount the device
Click to expand...
Click to collapse
Better yet, go ahead and post a video of the problem. I need to confirm something before you flash FFF.
soupmagnet said:
Better yet, go ahead and post a video of the problem. I need to confirm something before you flash FFF.
Click to expand...
Click to collapse
note: the screen that flashes is from my previous rom sooo, yeah. Factory wiping is a good thing.
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
chevy383surfing said:
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
Click to expand...
Click to collapse
Next time you loop, vol up and power for 10 seconds with phone Unplugged, then vol down and power to go to boot loader
If for some reason it doesn't restart put the phone close to a bright light
Similar problem
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
aputtapa000 said:
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
Click to expand...
Click to collapse
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
jshamlet said:
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
Click to expand...
Click to collapse
Tank you for this quick reply :good: . I will try to get back into my stock recovery but if it is on my device, how will I access this on my computer and force flash it on my tablet. I only need help making the tablet responsive/workable. Once this is done I should be able to figure out the rest.
Thanks
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
rfgamaral said:
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
Click to expand...
Click to collapse
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Tarima said:
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Click to expand...
Click to collapse
Tried to reflash Maximus, didn't work, still didn't boot. Backed up everything I could and wiped everything, I'm now on Lineage OS 16.0. Thanks for your reply.
I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.