Hey,
I'm worried that my phone is bricked, but would like to hear if there are some options of reviving my phone without sending it to repairs.
I was in ClockworkMod Recovery as I wanted to update my ROM from oxygen-v.2.0-RC7 to the latest version.
I had wiped all data and dalvik cache and was in the middle of installing the .zip when my battery popped out (don't ask how).
Now my phone won't boot up at all. When connected to a charger it vibrates 7 times, but the LED is not on and I cannot boot it, even when trying Power+Vol. button.
Am I screwed? Or is there a way to save it?
Nevermind! It suddenly decided to boot up into Recovery on one of my attempts and I managed to restore my old settings.
It seems it just needed some time.
Mods are welcome to delete this thread.
Related
Hi
im really hoping someone could help....
my phone decided to yet again throw another tantrum and crashed out, i first of all lost bluetooth like last time, and it kept hanging.
I restored the rom but no avail.
Stupidly i decided to wipe everything in clockwork mod and now the phone just shows up the android splash screen flashes and then shines again.
ive tried going into safe mode (vol - and power) but the phone fails to launch it. all it does is vibrate then continue onto the android screen
am i up the creek?
thanks for your help
http://forum.xda-developers.com/showthread.php?t=1104185
try the suggestions in this thread?
(simple search brought this up)
I'm curious, did you full wipe and then try to reboot without first flashing a rom? I've always wondered what would happen if you did that, not keen to try it myself
Recently I flashed RebelRom Beta 2, it resulted in a the LG logo being displayed on my phone but nothing would happen. So I did a restore from CWM, and the restore worked fine for a couple of days but at some point my phone lost power. Now whenever I turn it on I get boot loops and am unable to get into CWM. My question is is my phone bricked, and what can I do to avoid another brick? (Note I never formatted /data and I always follow installation instructions.)
KindaWack said:
Recently I flashed RebelRom Beta 2, it resulted in a the LG logo being displayed on my phone but nothing would happen. So I did a restore from CWM, and the restore worked fine for a couple of days but at some point my phone lost power. Now whenever I turn it on I get boot loops and am unable to get into CWM. My question is is my phone bricked, and what can I do to avoid another brick? (Note I never formatted /data and I always follow installation instructions.)
Click to expand...
Click to collapse
It's a known problem, at this point the solution is to restore you back and don't shut off your phone. Reboots work fine, but shut off will boot loop it.
Hmmm so I can't turn off my phone. What do you mean by reboot/how do I reboot? Also does this mean I can't flash roms anymore? And finally is there a fix on the horizon?
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?
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!
ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.
NOTE: This device is not mine, it belongs to my girlfriend and I am the one troubleshooting for her.
here goes:
Yesterday, while a friend of my girlfriend's was playing with her Galaxy Nexus (my GF's), it suddenly rebooted itself without warning.
From what I understand, Nexus bootloops that are caused by faulty flashing usually loops at the "Google" logo (correct me if I'm wrong). Her's is a different story, her Galaxy Nexus is pure stock, locked bootloader, un-rooted and definitely nothing custom on in; literally pure stock. Instead of looping at the "Google" logo, her GNexus loops at the "X" logo, my assumption is that there is something, maybe a rogue app, that is causing her device to bootloop upon reaching startup phase.
I know this isn't a software/ROM level issue since we were able to get to her lockscreen a few times and then the phone reboots after a few seconds. I've tried wiping cache but didn't work, and she won't let me try wipe data/factory reset because she has a lot of important files on her phone. So odin flashing and wipe data/factory reset is out of the question.
so here are some details that might be of interest:
1.) Her phone is not rooted and is pure stock android 4.1.2
2.) does not have custom recovery
3.) does not have usb debugging enabled (not sure, but I assume it's not enabled)
4.) can still boot to fastboot/recovery/download mode
5.) reboots at the X logo
So the basic troubleshooting methods are out, now I'm thinking of using adb pull to extract files from her phone via adb, but problem is, usb debugging is off! Is there any way of recovering her files at least without booting to the ROM itself so I can flash another version of android on it (via odin)?
I've also read about "safe mode" that boots the device without starting up 3rd party apps, only the core essentials. I'd like to go down that route if possible, but we've tried most of the guides on how to boot into safe mode but to no avail. There was one time though that the device booted up and she managed to: open power menu > hold power off > reboot to safe mode, but nothing happened, it just rebooted only to get stuck at the X again.
I may be overthinking this, so I've turned to XDA for help. I know you guys don't like people asking n00bish queries but I've exhausted everything I can think of and I'd like to try everything before I go down the route where I can possibly do even more damage.
I really need help with this, anyone have any ideas? We'd really appreciate it!
Unlock, flash custom recovery, wipe system, data, cache, dalvik cache and flash 4.3 factory image. Problem solved.