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:
Related
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
A clean flash of cm 6.1.2 should not give you any issues. Are you using a custom kernel?
ald3n3 said:
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
Click to expand...
Click to collapse
Random reboots are usually always caused by a custom kernel that your phone does not like.. I could be wrong but that is my experience anyway...
i had the same exact thing except i actually had 6.1.2 clean with no custom stuff. the only thing custom would be the galaxy s theme i put on it.
i would be trying to go to sleep and i would feel my phone vibrate and then i noticed its rebooting, the rebooting is pretty frequent.
i wiped and restored my original backup and installed all the new stuff (radio/wimax/etc.., except hboot)
right now im gonna install a clean 6.1.2 and see how it goes
No custom kernel. Maybe i just need to manually flash cm6 so i can wipe data 3 or 4 times. I kinda don't trust the rom manager and clockwork work recovery method i feel like it doesnt really wipe everything clean before installing.
Sent from my PC36100 using XDA App
How do you un-install a custom ROM
I installed a custom ROM and now (a month or two later) I'm getting reboot after reboot. How do I get rid of the custom ROM?
Also, what does it mean when the phone reboots, then vibrates 5 times and locks up?
To get rid of the custom rom just do wipe through recovery...
And the the locking up? I have no clue why that is... sorry
Sent from my PC36100 using XDA App
Good evening everyone,
I've been scanning the forums and everyone's problems seems a little different. First of all, i was running CM10 and missed some of the sense features, so i jumped to ViperX.
1. Everything seemed fine on first run, got the snakey tail, but then i noticed it was hanging just after this with the "Htc quietly brilliant" screen and snakey long gone!
2. So i reboot my phone, this time, it just hung on the first start screen and never so much as flinched.
3. I booted into recovery (CWM) and couldn't even get there, it was like a blink of the recovery screen and then it vanished and rebooted, I wiped everything clean by doing a factory reset and tried to reboot again. Same result.
4, Flashed TWRP and managed to get into recovery mode and install ViperX again but on reboot I'm stick at that same ol' "quietly brilliant" screen, this time with no snakey.
I can get into hboot to use fastboot and into recovery in TWRP but cannot get into the OS. I'm not clear as to whether this is a problem with hboot or the way the rom is installed but any suggestions or such about how i've gone about things and how to go about getting around this problem would be great! Gracias! :good:
Did you flash the correct boot.img?
BenPope said:
Did you flash the correct boot.img?
Click to expand...
Click to collapse
Strangely, and by the luck of trial and error, I tried 2 boot images. The first was for CM10 (again, this was trial and error) and now i've just rebooted from the ViperX one and managed to get back in. Back up in progress! Phewww!!!!
You get my thanks for replying anyhow!
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 ??
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.
I was having boot loop while installing cm 12.1 i could boot if i unplug the battery and leave te phone for half an hour. When booted the phone has no problems. But the problem is while booting. It gave me constant bootloops. So i decided to do a complete factory rom change. So i flashed fastboot rom vi mi flash tool. Still the problem persists te phone is looping with a blue flash at the top.
A bit too late, sorry, but I think I have had some minor issues after flashing a fastboot rom few times.. I think it can be solved by entering MiRecovery, cleaning cache and then rebooting from recovery to system. If the system is not booting up in 5 minutes, it's not fixed. On the other side, maybe you haven't done it right or something is wrong with your file. I recommend doing it again with v45 Miui5 fastboot Rom. That one always works for me.
Anyone to help ??
Only way to make it booting is installing rr rom. With beast v5 kernel. That too with multiple reboots while android upgrading progress
I tried miui5 and i have twrp. I think this is happening by improper kernel configuration.
As i told earlier i can use phone awesomely by installing RR rom with beast v5 kernel.