Develop Bugs

White triangle with yellow exclamation point (!). battery pull?

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.

[Q] CM 7.0.3 cannot connect to wifi

hey guys, i've just flashed CyanogenMod 7.0.3 to my device and the wifi turns on, can see wifi networks and accepts my WEP password, however hangs at "Obtaining IP address...", eventually disconnecting and trying all over again.
I was previously running the 7.0 release with no problems and in my newb naivety i failed make a backup of the ROM.
Any suggestions?
EDIT: Now i cant boot into recovery. I just get the bootloader screen (i think? the white one with the skateboarding Androids at the bottom?) and selecting Recovery just sends me back there. This has now gone from an expected easy fix to something thats starting to get me worried. Can anyone help?

Do a full wipe and re-install the rom again, chances are something corrupted the 1st install which does happen apparently.Don't worry too much mate, over the past 2 weeks ive installed and re-installed about a dozen times and on a few occasions been in exactly the same spot your in.

thanks, but no can do. I cant boot into recovery and thus cant wipe and re-install...

Dumb question, you are holding down the volume(down) and power button at the same time to get into recovery mode??

Wow that's weird, try going into ROM Manager and flashing a different version of Recovery.

thanks for the responses guys. Yeah im doing the vol down + power to get to recovery. I cant get further than the white skateboarding Android screen. ROM manager doesnt let me flash new recovery versions because there aren't any.

You can flash a older recovery, scroll to the bottom when in RomManager and select All ClockworkMod Recoveries and try to flash something like 3.0.0.6
Sent from my Desire HD using Tapatalk

yeah when i do that i get "No legacy recoveries found"
EDIT: i turned on my mobile data and now i can choose older recoveries from ROM manager but i still cant boot there regardless of which one i choose
PS can a mod change the title of the thread cos i realize now my problem is more to do with booting into recovery rather than the wifi issues. Thanks

reading around it seems like i need to use fastboot to reflash the recovery.img from my computer. will try it tonight

Could not do normal boot error

Hi,
I was trying to get CWM recovery onto my phone but I believe something went wrong. Whenever my phone turns on, it goes straight into download mode with the message in red saying "could not do normal boot" with the ODIN mode and such listed underneath it. What do you recommend I do next to resolve this issue?

Flash to stock and start again. You're al good... :thumbup:

Thank you, that resolved my boot error issue. I tried flashing recovery-clockwork-touch-6.0.1.0-i9300.tar with ODIN, but whenever I try to reboot into recovery, it loads a message saying "rebooting into recovery" then my screen goes black. I have to reset the phone after that to get it to reboot. Any suggestions?

Wait... Edit... Why are you using a i9300 file... Isnt the att gs3 i747? Easiest way to install recovery if you can boot to homescreen - download goo manager from play store and hit menu and install recovery.

That would explain a lot... When I'm in Goo, I only have the options to install OpenRecoveryScript and reboot recovery. I installed the script then tried to reboot recovery but have the same issue with the blank screen.

Neverymind, it loaded up perfectly. Thank you for all your help!

Is my M8 bricked?

Hi XDA-Fellows
1) thanks for all the help of this community so far
2) my problem: I had my HTC One M8 rooted, installed TWRP (I think in the end I had 2.7.8.0 as last version) and Cyanogenmod with a nightly build of around 18. March 2016 installed! THEN the big mistake happened. In advanced developers menu of cyanogenmod I activated the option that was called something like "on update of system also replace recovery software". That obviously was stupid.
Upon rebooting normally TWRP launched and installed the latest nightly. This time I see the white screen with HTC logo on it, red text in bottom, top part of the screen shows "ENTERING RECOVERY", 3 seconds later I see a black screen and every like 2 or 3 seconds it looks like the screen gets powered, it flashes darkgrey shortly (again, looks like it gets powered but instantly shuts off immediately).
This just can be stopped by pressing either P+U or P+D for like 10 seconds. Then again, white screen with HTC logo and ENTERING RECOVERY and the screen switch on/off-loop.
Is my device bricked? What can I do now?
Any help is appreciated.

Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..

BelDev said:
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
Click to expand...
Click to collapse
Yes I can enter bootloader. How should I go on from here on?

Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..

BelDev said:
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
Click to expand...
Click to collapse
Thanks. I will give it a try and give feedback.

It worked. I could enter bootloader, switched to FASTBOOT mode, installed ADB Drivers for windows and replaced recovery with latest TWRP! THanks a lot for your help! I thought I could throw away my M8

Well. It worked not completely. I was able to reboot my phone into the Cyanogenmod. But upon entering recovery mode (which I expected now to be TWRP) I get the same result again ... Screen off/on within seconds, repeating endlessly

I think you need to reflash the boot.img and the ROM completely. Because i don't know why do you have a black screen.

I activated root access for apps and tried ROM Manager first! It failed, then I used flashify which worked. Automatically downloaded latest TWRP (3.0.0.1) and flashed it, reboot into recovery. Everything works like a charm again! Thanks again for your help!

TWRP/CWM Recovery starts Boot Loop

Hi,
Trying to root the following unlocked phone of mine..
Current Mobile version : HTC Desire 816 A5_DWG "India" - Dual Sim
Software version : 3.14.720.1 / Marshmallow 6.0 with HTC Sense 7.0
I flashed 5/6 different TWRP/CWM versions via ADB/Fastboot as the phone is accessible... but when I try to enter the Recovery, in CWM the screen goes blank while with TWRP, the Phone actually starts an infinite boot loop with "Entering Recovery" -> Down - > "Entering Recovery".. the connected phone is not available to ADB/Fastboot during this time... and I have to wait for Phone battery to exhaust, so I can start the phone in Bootloader and restart as normal.. Can anyone point me to the actual TWRP/CWM or any other Recovery image for the model & version? The phone has no external card, not sure if that could be a limitation in the process? Also do I need to unlock the phone every time I put Stock Recovery back?
thanks in advance

I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.

dduck2683 said:
I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.
Click to expand...
Click to collapse
Thanks a lot for both the pointers... TWRP, the old version did work and also the up volume+ power is working fine.. But after getting into TWRP and wiping partitions & data, the system is now booting to always hung state (stuck on white HTC boot screen).. Can get to bootloader/fast boot, but ADB doesnt detect the device now.... When I enter TWRP, the phone is detected in adb in the "recovery mode" , but fastboot doesnt work.. How can the stock recovery/other recovery be installed at this hung state..
thanks in advance

If you have a ROM (or a backup image), you can flash it when you're in recovery mode; I don't think you need ADB to do that?
And also, what is the cid of your phone and what image did you use?
Sorry for the delay.

dduck2683 said:
I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.
Click to expand...
Click to collapse
I have the same problem with latest version 3.1.0-0, though older versions working fine. Could you manage to get the latest version working? or the image file has bug?

panijsr said:
I have the same problem with latest version 3.1.0-0, though older versions working fine. Could you manage to get the latest version working? or the image file has bug?
Click to expand...
Click to collapse
It's quite difficult to find a suitable image for my phone so I ended up using the old version of TWRP. I don't really know if it's a bug in the image file or TWRP itself.
But then again, why do you want to use the latest version of TWRP?

dduck2683 said:
It's quite difficult to find a suitable image for my phone so I ended up using the old version of TWRP. I don't really know if it's a bug in the image file or TWRP itself.
But then again, why do you want to use the latest version of TWRP?
Click to expand...
Click to collapse
Previous versions of TWRP were not able to decrypt/ access my 'adopted SD-card' (merged with internal memory).
I was hoping , the latest version would be able to do that.