Hi! First of all, I tried searching the forum, but I failed find any specific help on this. I hope someone can point me in the right direction, or knows how to solve this.
I tried to install manually an OTA uptade on my desire, and I think I may have screwed up something.
When I power up the phone, it's stuck in booting: boots, HTC logo comes up, vibrates, then the whole cycle starts.
I was able to get to the screen, with the skating droids, but when I tried to choose recovery, an image of a phone comes up with nothing but a red triangle.
Does anyone know how to fix this? Any help would be appreciated.
Stock android 2.2, rooted with unrevooked.
to leave the triangle-screen:
-press Volume up ("+") and the power-button.
-select "Reboot system now"
..and you're done!
tried that, but it still ends in an endless boot loop. Also tried factory reset.
Nevermind, looks like there was some kind of hiccup the first time. I started the OTA update manually (after leaving the triangle screen with the vol. up + power combo) and after some rebooting it wokrs now. And it's updated too. Thanks anyway!
deino said:
tried that, but it still ends in an endless boot loop. Also tried factory reset.
Click to expand...
Click to collapse
Google: red triangle of death.
Good luck.
Related
I need a bit of help with a stock HTC One X. As of this morning it won't boot up. I have made no changes to the ROM, everything is stock.
Tried entering the recovery panel and turning fastboot on then restarting but every time the system stops at the "HTC One" page after making a startup sound. Sometimes the screen will go black and hitting the volume keys will bring up the volume changer but that is it.
There was no warning of an OTA update or anything like that.
When charging the screen stays on and dims, but stays on the "HTC One" screen.
Factory reset HOX and it booted, but next day same issues. This is 3 times I've had to factory reset now.
Every time I restart or cold boot it freezes on the "One X" screen.
This exact same thing has just happened to me! Just 10 minutes ago
I have no idea what to do.
I have not attempted root or anything like that everything is stock (Optus from allphones).
All I did was restart and now I cannot get into the phone.
I can get to those options (fastboot) by holding down the volume down button and the power button but restarting it or powering it off there does not help.
I havn't tried a factory reset yet as I'm scared about loosing all my data.
Can someone please help!
Please please
I'm suprised someone else is having the exact same issue what the hell is happening
Have you tried using the Recovery option from the Bootloader?
Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.
Pyrope said:
Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.
Click to expand...
Click to collapse
Fair enough, if you're thinking of Rooting and installing ARHD etc then feel free to use my Guide : The Stock to Custom ROM Awesomeness guide
It'll take you from Stock to having ARHD on your phone ok
(Shameless plug)
http://forum.xda-developers.com/showthread.php?p=30471180#post30471180
Took it into HTC last night and had the firmware flashed. No problems now... 12 hours with numerous restarts just to make sure.
It looks like it was a corruption in the software. I noticed HTC turned off the fast boot option before giving the phone back to me. Took 30 minutes in total.
If it happens again, try to hold the power button and the "Homepage" button at the same time. You should see a grey box saying "Continue holding to restart".
Thats a full restart rather than a shell restart.
That may help.
Hey all, so I have a Stock Galaxy nexus running whatever the latest OTA update is that is stuck in the boot process right now at the "X" screen with the changing colors.
This is pretty much all I know about the situation:
I was sitting around with my phone next to me, decided to look to see if I had any messages, so I hit the power button to turn on the screen, nothing happened, so I pressed it a couple more times. Still nothing. Assuming the phone had frozen or something (although I haven't had any issued with this in the past) my instinct was to take out the battery and reboot it. After I did that it started to boot, showed the Google logo, moved on to the X screen and stayed there for about 15 minutes. I did some googling and people said it can occaisionally take a while to boot but after 20 minutes I figured there might be an issue so I once again took out the battery and tried again. This brought me right back to the same X screen and it's been sitting there for some 30 minutes now. Any suggestions or ideas of what's going on?
EDIT: I also just booted into recovery and tried clearing the cache, but that didn't really do anything.
EDIT2: I just wiped all my data through recovery and it booted fine. Is there anything I can do in the future to avoid having to start from scratch though?
Any help is appreciated.
Thanks for your time.
More details might evoke more replies. What did you do immediately before rebooting the device the first time it got stuck at the boot animation?
Same problem! Stuck at 'X' for infinite time ..
I have faced this problem second time now.
One of my friend who also has Galaxy Nexus faced this problem once!
Both of us have 4.1.1
When problem occurred ? -- (me both time)
I turned on Bluetooth using widget on homescreen, it halted for a second or two and suddenly 'X' logo appeared which didn't go away ! I tried taking off battery and turning on phone again. While starting it "Passed Google logo" and on next screen at "X" logo it stuck.
When problem occurred ? -- (my friend once)
While changing from flight mode to Normal mode.
to : Junior Member - OP
" I just wiped all my data through recovery and it booted fine." I have not done anything by myself yet, so don't know how to do that. can you please explain in detail ? It will really be helpful . Thanks ..
4.2.1 is the latest version, not 4.1.1.
Without any logs, it's that much harder to tell.
Sent from my i9250
Have you rooted your phone?If yes then head over to recovery=>then Clear cache partition=>factory reset=>advanced-clear dalvik cache
Then reboot..now your phone should work fine.
As per your problem stated you might have different rom and got OTA,which finally messed with your system and hence got bootloop..
my phone not rooted
hello,
If phone is not rooted, can I reach recovery mode and clear cache ?
Is there any other way to do this with not rooted phone? or can I root my phone in this condition?
---------- Post added at 09:42 AM ---------- Previous post was at 08:51 AM ----------
Also can to install yakju image freshly while my phone is stuck in bootloop?
With procedure given here
If I can install it, then will it solve the problem ? (stuck at X logo)
Thanks a lot..
You can enter recovery by turning the phone off and first pressing volume down + volume up + power =[bootloader], and then use the volume arrows to scroll so recovery is across the top, then press the power button to accept the selection. In recovery, android with red triangle, press and hold power then press volume up to bring up menu, and you'll see clear cache option. Otherwise, adb will allow you to erase cache, as well as rebooting to recovery. Fastboot is how you'll flash fresh factory images. And yes, that should fix your problem. Why not go with takju rather than yakju? If you do, i believe you'll have to do a factory reset, as well as the cache and dalvik wipes.
Ok so I have a bizarre and painful one here.
Recently the micro-usb slot faulted so I had to replace it, managed to do it but the volume rocker whose connector was soldered on was removed.
A week later I change roms get the recurring start up animation so go to manually put it into fastboot. Except of course my volume rocker is disconnected. And as the phone can only do recurring animation or off I don't think adb is going to help me.
I have a feeling the answer is going to be fix the volume rocker, if so anyone know how? Or better yet another way to get into fastboot in my current predicament?
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
I'm unfortunately stuck in a very similar situation.
I was updating the firmware on my tablet to 4.4.2 downloaded off Sammy mobile, uploading using Odin. I've done this dozens of times since my S2 which was 12 handsets and 6 Android tablets ago. This time, about a third of the way through the process hung for a few minutes then the device restarted without warning and now its stuck in a loop where it starts normally
http://imgur.com/MTwiE5V [1]
Then says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery.
Then this
http://imgur.com/Ua1nmhi [2]
and stays on that screen for short periods before rebooting and starting the above again.
Thanks in advance for any tips or help you guys can provide!
SleepyDonald said:
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
Click to expand...
Click to collapse
Have tried factory reset/clear cache/clear dalvik?
shayind4 said:
Have tried factory reset/clear cache/clear dalvik?
Click to expand...
Click to collapse
Thanks, but it turns out the solution to my problem was simple. I took it to the place I got it from and the guy just pressed power, vol and menu button long enough until it rebooted. I'm quite a noob it seems.
I'm not sure if it will help you Nationalmaverick, because my problem was slightly different.
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
TROJAN4EVR said:
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
Click to expand...
Click to collapse
Hi,
Yes.... I stumbled across that today on searching. I tried with a little iPazzport usb keyboard/mouse that I use to program with, but I'm going to try another keyboard as well just in case it is the keyboard. I tried at least 20 times over and over again with nothing at all happening. I appreciate the suggestion though and will try again with the different keyboard tomorrow. I'm a little burned out on it tonight! I'm afraid what I might have done is to change from the CWM bootloader to that one when I did it. Hopefully not, but there's no way to tell since all I can get now is the loop when I boot the unit up. I tried not only when I got the failed update message, but at all different times during the boot operation just to see if i got any response at all, but nothing so far seems to break into that cycle.
Thank you!
fxbill,
Sometimes you just have to walk away and then get back to it later. I use a low cost dell usb keyboard and what I found out is that you have to do press all three keys at once in unison and at a steady rate until you get a response. Just try to press all three at once and I guarantee you'll get it done. Try it when you're ready to get back to it. Have a good night!!!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
rbox said:
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
Click to expand...
Click to collapse
Well.... CWM was in.... I got the install from zip screen, but at that late hour and as tired as I was it's possible that I somehow removed it when installing your boot program. If so then I can live with it and yet I will try again tomorrow to see if I can fast boot or use a different keyboard for trying to alt/pnt scrn/i and see if that works.
I did do another unit tonight and installed your boot program before installing CWM,,,,again in error, but this time it booted to the same screen and then rebooted back into the preloaded unit! I then installed CWM and everything else went smoothly. I'm assuming your program is still in there, but is there a way to verify that it's still there? I updated to the newer 4.0 firmware with no issues and Netflix is again working and the firmware shows 4.0 installed. Is there really any reason to update any father than that? Is there anything new in the latest rooted firmware that justifies updating any more than I already have? If not I'll leave it as is...everything works extremely well at present.
Thanks so much for the advice and help!
@fxbill, so were you able finally to get this fixed? i'm in same situation when my device constantly reboots after counting down to 0 in rboxes menu . tomorrow i will by trying to find an USB keyboard and see whether im in luck of getting to recovery. hopefuly that works. i'll keep you posted.
A notification came up for a new update and tried to install it. The update failed on the update screen and the phone tried to reboot. I gave it half an hour but I'm certain it's stuck on the screen with the white dots circling a red one. Held down the power button to restart but still stuck.
I can get into the options menu, but selecting recovery seems to just restart. When selecting fastboot, there's no number after bootloader and baseband version.
I have little experience with rooting and flashing or whatever. Not sure what to do, any suggestions?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
I used this linked and it worked!
It was a bit sketchy but hey
Dygijle said:
A notification came up for a new update and tried to install it. The update failed on the update screen and the phone tried to reboot. I gave it half an hour but I'm certain it's stuck on the screen with the white dots circling a red one. Held down the power button to restart but still stuck.
I can get into the options menu, but selecting recovery seems to just restart. When selecting fastboot, there's no number after bootloader and baseband version.
I have little experience with rooting and flashing or whatever. Not sure what to do, any suggestions?
Click to expand...
Click to collapse
This is what we call a bootloop. Now you can try a factory reset, but installing TWRP si way better if you encounter these issues in the future. Try to wipe System then flash OOS and it should be fine.