tried to boot in to recovery and got a screen with a white triangle and a yellow exclamation point inside above an android robot.
the suggestion is to battery pull. anyone else have this issue? if so, what's the procedure on reboot?
thanks.
I think that's the Stock Recovery Menu ( i kept getting it when i was trying to install the Patches from Fresh & used Clockwork Recovery because the two weren't compatible ).
Do you definitely have a Custom Recovery installed?
You pressed the power button instead of the optical trackpad when trying to reboot from custom recovery
Optical trackpad? What Evo has one of those? LMAO!
Flash Clockwork recovery or AmonRa recovery. You have stock (no recovery).
It is hard to answer your question without further specifics.
For example:
1.) Are you rooted?
a.) If yes, what are you trying to boot into recovery for? - flash radio/wimax or rom???
b.) If no, go to Android Development and read how to Root and install a custom recovery.
2.) If you have a custom recovery, what is it?
to put it simpler than this.
1. What ROM do you have?
2. What custom recovery do you have?
3. What step did you do to get into recovery? - from android or from boot up?
*If you pull a battery while trying to flash a radio, you might have the coolest looking paper weight in your part of the town
Hello shawnathan9!
I have similar problem with my Nexus one.
I have a rooted phone (used superoneclick to root)
Installed clockworkmod and flashed it with the recovery image.
Since I wanted to install latest cynogenmod I used clockworkmod to install the latest radio for it. Now when the phone rebooted it is hung diplaying a white triangle with and exclamation mark inside it. I haven't removed my battery yet and have plugged it to a power source. Can you help me ?
You're rooted, but you are trying to access recovery, but you don't have one loaded. Search google for Amon_RA or clockwork recovery to flash. If you have rom manager, you should be able to flash either or and it should work.
I did the unrevolked 3 and got it rooted. Then I booted it up into the recovery mode and ran clockworkmod. Now how do I get a rom (like mikfroyo 4.5) on it? I tried booting and selecting a zip from my sd card(which mikfroyo 4.5 is on it in zip form still) But it would not finish/aborted ? What am I doing wrong? I have the sptint HTC EVO 4 g phone with all the latest hboot ect on it.
charlieborg44 said:
I did the unrevolked 3 and got it rooted. Then I booted it up into the recovery mode and ran clockworkmod. Now how do I get a rom (like mikfroyo 4.5) on it? I tried booting and selecting a zip from my sd card(which mikfroyo 4.5 is on it in zip form still) But it would not finish/aborted ? What am I doing wrong? I have the sptint HTC EVO 4 g phone with all the latest hboot ect on it.
Click to expand...
Click to collapse
It did say no sd-ext found, skipping backup of sd-ext. in Clockworkmod. Still getting the white triangle with the yellow ! in it?
bhaismachine said:
Hello shawnathan9!
I have similar problem with my Nexus one.
I have a rooted phone (used superoneclick to root)
Installed clockworkmod and flashed it with the recovery image.
Since I wanted to install latest cynogenmod I used clockworkmod to install the latest radio for it. Now when the phone rebooted it is hung diplaying a white triangle with and exclamation mark inside it. I haven't removed my battery yet and have plugged it to a power source. Can you help me ?
Click to expand...
Click to collapse
That is part of updating the radio. Just let it finish and it will reboot into recovery. The phone has to go to that screen to update the radio. You may be able to save it by booting into that screen and just let it sit there for a while...eat dinner...take a dump...do whatever and come back and see if your phone is in recovery. I would turn it off and charge it first to make sure you have enough battery to finish the update.
I have the same experience, when I updates to Gingerbread (OTA).
housry23 said:
That is part of updating the radio. Just let it finish and it will reboot into recovery. The phone has to go to that screen to update the radio. You may be able to save it by booting into that screen and just let it sit there for a while...eat dinner...take a dump...do whatever and come back and see if your phone is in recovery. I would turn it off and charge it first to make sure you have enough battery to finish the update.
Click to expand...
Click to collapse
Hello thank you so much for your information. I will leave the phone in that mode (screen hung with triangle an exclamation mark inside + android green logo below) and plug in the charger, until tomorrow morning. Then I have a question if tomorrow the phone still hung in that screen mode, what I have to do?
If you can give me solution, I would be very thankful. Happening in August 23, 2011.
Android_maniac said:
Hello thank you so much for your information. I will leave the phone in that mode (screen hung with triangle an exclamation mark inside + android green logo below) and plug in the charger, until tomorrow morning. Then I have a question if tomorrow the phone still hung in that screen mode, what I have to do?
If you can give me solution, I would be very thankful. Happening in August 23, 2011.
Click to expand...
Click to collapse
After 2 days, trying to download updates firmware (OTA) GingerBread on HTC Evo 4G, I failed because the phone has been rooted, I found a "superuser permision" app. in the the All apps menu.This meant it is a rooted android phone, which will not permitted to update firmware OTA, is this true? If yes, this is the cause of screen hung at triangle with exclamation inside, and android green logo below.
August 26,2011.
Thats what my phone is doing the clockworksmod menu will not come up only see the
white triangle with the exc symbal with the android symbal. have to pull the battery out ot reset but phone still loads up and works.
So I have had my kindle fire rooted for about a month now and have been running ICS on a cyanogen ROM since then and it has been working fine. However I decided to unroot and I realized that when I boot up the kindle fire to access TWRP recovery there is no triangle. I get the original Kindle Fire boot logo. Like I said the ROM is working fine and everything I just don't know how to access TWRP. Does anyone know another way to access it? I have tried holding down the power like you would if the triangle was there but still nothing.
How exactly did you unroot? Flashing an official stock ROM? If so, both FFF and TWRP are gone, meaning you'll have to install them again.
PS: The yellow triangle is a pretty old version of FFF. The latest one will show the "Kindle Fire" logo with the word 'Fire' coloured in blue. It's very important to keep the bootloader and the recovery up to date!
I have not unrooted it yet so it should still be there. Also the logo isn't blue it is the regular boot up logo colors.
Then, are you still on the ICS ROM? Does "adb reboot recovery" help when issued from within the ROM?
Yes I am still in the ICS ROM. And I don't have the option to reboot it like that. That is something that I tried first.
trident123 said:
And I don't have the option to reboot it like that. That is something that I tried first.
Click to expand...
Click to collapse
What do you mean? It's not an option in the ROM, it's a command you type in the command line, in whatever folder you have ADB set up. For example, in the "tools" folder that KFU includes.
However, if "adb reboot recovery" does nothing for you, then give "adb shell idme bootmode 5001" and then rebooting a try. If that does not get you into TWRP, then TWRP simply isn't there, meaning you'll have to install both TWRP and FFF (even if you decide to go stock later, it's also a good idea to keep those two installed).
I understand what you mean now. I am probably just going to reinstall them so I will have the most updated version. Thanks!
Ah well, glad you got it sorted out one way or another.
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.
So I teas trying to get a jb rom on here. I'm stuck at the blue boot screen and it never fully boots up and I followed all the directions but I'm pretty crappy at all this stuff. I forgot to put the rom and gapps on before and So I got into twrp and every time I try to get adb side load to work it never works just get caught at starting side load feature or whatever and never changes .
I know there's stuff somewhere on the forum but it's all to confusing to me. I've had this thing for one day and now I've got a pretty sweet paper weight
I followed a video by zedomax on YouTube
Not to good at cmd prompts either so be easy on me
jhillyer253 said:
So I teas trying to get a jb rom on here. I'm stuck at the blue boot screen and it never fully boots up and I followed all the directions but I'm pretty crappy at all this stuff. I forgot to put the rom and gapps on before and So I got into twrp and every time I try to get adb side load to work it never works just get caught at starting side load feature or whatever and never changes .
I know there's stuff somewhere on the forum but it's all to confusing to me. I've had this thing for one day and now I've got a pretty sweet paper weight
I followed a video by zedomax on YouTube
Not to good at cmd prompts either so be easy on me
Click to expand...
Click to collapse
Stunts did a write up on just this thing. This link http://forum.xda-developers.com/showthread.php?t=2459498 will get you fixed up.
1. To get into recovery, turn the KFHD off (hold power button for 20 seconds.)
2. Now turn it on and when you see the yellow Kindle Fire screen push up on the volume until the Kindle Fire logo turns blue and hold it for three seconds, then release the volume up button.
3. Now that you are in TWRP you can push the ROM and Gapps and will you be sorted out.
Didn't want to start a new thread, so I'll ask here. I had the same problem as the OP, but the thing was I couldn't get into the recovery. Kindle just booted up to blue logo, and then nothing happened. I tried to install CM, and everything was fine, but after having installed TWRP and 2nd bootloader I couldn't get into the recovery, and ADB suddenly stopped recognising my Kindle. I tried to install/reinstall the drivers, but to no avail... So I ended up recovering Kindle via SRT, and now I have 8.1.4 device (I went through red screen problem and at some point I wasn't able to flash anything even via fastboot)... I still want to install CM, what can I do to ensure that the recovery works correctly? Now Kindle is shown as portable device in device manager and there also is a line "android composite ADB interface", is it ok now? Thanks in advance.
I can't believe you pulled it back from the red screen. That does not happen often, good job. Did you wait until you saw the KF yellow logo and push up on the volume rocker and hold it for three seconds after the blue KF logo and let go? That's how you have to into TWRP.
Did you flag or push the files last time?
Sent from my Amazon Kindle Fire HD running Paranoid Android using xda app-developers
LinearEquation said:
I can't believe you pulled it back from the red screen. That does not happen often, good job. Did you wait until you saw the KF yellow logo and push up on the volume rocker and hold it for three seconds after the blue KF logo and let go? That's how you have to into TWRP.
Did you flag or push the files last time?
Click to expand...
Click to collapse
Thank you for the input! I think I did, I tried many times.
Well... I followed Hashcode's bootloader & TWRP installation tutorial step by step, so pushed the stack file and it went well.
Now my device seems fine running 8.1.4_user_1413620 and even rooted, the only issue is that it doesn't detect my home wi-fi network for some reason.
Erentel said:
Thank you for the input! I think I did, I tried many times.
Well... I followed Hashcode's bootloader & TWRP installation tutorial step by step, so pushed the stack file and it went well.
Now my device seems fine running 8.1.4_user_1413620 and even rooted, the only issue is that it doesn't detect my home wi-fi network for some reason.
Click to expand...
Click to collapse
Hmmm, if that continues, you may have to do a factory reset to see if that fixes the issue and then retry again.
I've connected the device to another network, it updated and now wifi is perfectly fine. Maybe it had something to do with OS version. Now my Kindle seems to work flawlessly, and I can start experimenting from scratch
Sent from my DROID RAZR Maxx HD using xda app-developers app