Hello guys,
My nexus has a weird issue of TWRP recovery, sometimes after a reboot to the recovery it does not respond to the touch only a battery pull and rebooting again into recovery says battery % drop from 19-4, last time it was from 22-8 and this had started happening now. Tried reflashing recovery also but it didn't solve anything....
Any one do have an explanation for this ??
Related
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.
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.
Okay, so it all happened when I flashed Insertcoin a few weeks ago, it's not really a typical bootloop as the boot anim. loads for a few seconds and only then it reboots, I tried flashing the latest Renovate today but still, 1 sec. of animation and reboot... the thing is that with Insertcoin, I succeeded booting after a few times, altering with turning it off/on, but now, nothing orks, i think i damaged my bootloader, if it's even possible.
Please Help!!! i'ts driving me mad!!!
Nevermind guys, I fixed it, I just flashed the normal CWM 5.8.4.0 Recovery instead of the PhilZ one I had, it was probably causing the bootloops
PhilZ recovery isn't the culprit here! You must have forgotten to : fastboot erase cache after flashing the boot.img or recovery.img! :silly:
for some reason after flashing cm13 updates in twrp 2.8 the first reboot always results in a black screen (almost like a power off) but if i battery pull then reboot everything is fine... very strange anyone have any idea what's happening. I haven't tried not pulling battery maybe i will next time maybe for some reason the phone i just shutting down instead of rebooting from twrp. (im manually flashing the file because i also flash some other zips too then going to reboot -> system.)
Hello my friends phone is stuck in a weird bootloop that doesn't let me to boot in recovery or in fastboot. What can happent with it??? Can i fix it?? Here is a video about this problem.
https://www.youtube.com/watch?v=i6K_Xr0YZ6I
Hello I have exactly the same problem. I was working with cyanogen rom for a year and had no problem. Suddenly yesterday I get this bootloop even in fastboot mode. I can not even enter in recovery. If anyone could help. I think that we don't have enough time to flash the rom through fastboot. Maybe we could flash a new recovery and then flash the rom through the recovery.
Any Luck??
I am stuck with the same thing over the last couple of days, any luck with the issue? Could you please post a solution if you find one.
Hi, my phone worked after one day. Therefore, I think the problem is at the power-volume buttons and has nothing to do with the software. I have ordered a new button set and as soon as I replace it I will let you know.