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.

Bricked?

Sorry for the double post, I realized afterwards this was a better place for the question
I recently followed the unrevoked guide to root my phone and put on the clockworkmod custom recovery image (for slcd http://forum.xda-developers.com/showthread.php?t=748618). Everything appeared to go smooth, unrevoked said it was a success, been using it for a few hours now and all of a sudden it wont boot sits at the htc screen, I also can't boot into recovery mode (shows a black line at the top of the screen then powers down). Its a brand new telus desire. Anyone know where i go from here to trouble shoot this/reset the device.
last thing I did was copy over a froyo rom to the sd card and try to install it using clockworks rom tools from the sd card, however that process just rebooted my phone. So i assume it didnt do anything.
Is there a way to try to reflash the recovery image without being able to boot into android?

what do you get when u hold volume down and power button? do you not get hboot screen?
if you do then not bricked

I can get to the screen, but I cannot enter recovery, when I choose recover it vibrates, htc logo comes up then powers down. I cant boot into android , cant get to the recovery screen, so Im at a bit of loss what to do next.

rock_80 said:
I can get to the screen, but I cannot enter recovery, when I choose recover it vibrates, htc logo comes up then powers down. I cant boot into android , cant get to the recovery screen, so Im at a bit of loss what to do next.
Click to expand...
Click to collapse
you need to install recovery again then, i messed mine worse then yours and sorted using this guide
http://forum.xda-developers.com/showpost.php?p=6710081&postcount=2
you have to download that ISO and burn it on cd and boot the linux and follow the command as if it was the 1st time you are rooting, if step 2 does not work then skip it and see if it boots into recovery. i remember i had to play with it for a bit

I had something similar, Volume UP, then hit power? Select recovery, then wait 30 seconds, then update zip, then get it from there? Worth a try?

that wont work with the 0.83 bootloader will it ?

Anyone else have a solution?
I assume I may need to wait for a tiny linux version compatible with hboot 0.83? so that I can restore my recovery image? unless i can boot android
I cant connect in Win. because it wont boot..
How does fastboot work ? could I copy a slcd image over the microsd ( i dont have a card reader to test right now)card run fastboot, and have android boot long enough to sync windows and attempt to reapply the unrevoked recovery image?

[Q] Non-functioning Volume buttons, Recovery Screen.

Hey all!
I have a question, I recently tried to flash the stable CyanogenMod 7 for Wildfire. The ROM flashed but when it was installing no dialogue came up, I decided to reboot my phone to see if it had worked. I discovered that the ROM had not actually installed because my phone stayed on the HTC boot logo forever. I even left it on before I went to sleep to see if it would eventually boot into the software but no, it was still on the boot logo when I woke up. The logical solution to this would be to boot into the recovery screen but there's a problem with that, I can't. In getting my screen replaced in the past the volume buttons have been broken and therefore I cannot select the recovery option on the bootloader screen :\ Would anyone be able to offer me an alternative to booting into the recovery screen as I currently have no way of fixing my phone and am beginning to get pissed off with the ZTE Racer I'm using as a replacement...
Any help would be much appreciated!!

Try installing a RUU of 2.1 and then see if your volume buttons work. If not then contact HTC for a repair.

You misunderstand my problem, I think. I can't run the RUU because there is literally no software on my phone right now so RUU won't even recognise that it is connected to the PC because I can only access the Bootloader screen but cannot select any options because of my non-functional volume buttons. I'm pretty sure I can't send it back to HTC because my warranty is voided by the fact that I've rooted the phone and failed to install custom firmware on it and therefore it has been modified, please tell me if I'm wrong but I'm really in a predicament here. If I'm wrong about having voided my warranty would I be right in thinking any repair would be free?
EDIT: I managed to fix my phone. Pretty much all I had to do was load the bootloader, select fastboot, plug it into my PC and using the correct RUU I managed to restore my phone to stock ROM Thanks for the help!!

Stuck on Google Screen after JB Update

Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..

bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup

Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?

Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.

Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!

this has happened twice today and i think it from using volume+

Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot

[SOLVED] Android Pixel XL Boot Loop, Never Seen Before

My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.

I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.

piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709

piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe

sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!

piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.

piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S

Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!

rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.

Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...

rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?

Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...

rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.

Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!