I have recently upgraded my HTC One XL to CM10.2 using a stock kernel and each time when I try to reboot my phone, it goes into a boot loop and only boots up after rebooting a few times. Sometimes it boots up and then hangs, then I'm forced to restart it and then again it keeps rebooting before I can actually use my phone. Does anyone know how to fix this?
That's a pretty common problem with recent builds of cm unfortunately, if you have a read through the ROM/q&a threads for cm some people have overcome this by flashing a boot.img from an earlier build. You could also try the Torched kernel. When you say stock kernel what exactly do you mean?
Sent from my Evita
Seems to be fixed now. Flash that latest CM10.2 and boot.img separately via fastboot and clear your cache/dalvik.
Related
For the past few days now, I've been attempting to flash $droyd$'s unofficial AOKP and thicklizard's komodo kernel, with no success. I've fastboot flashed before and/or after, wiped everything, run wipe scripts, chanted voodoo prayers, but nothing has worked. It either hangs on the boot animation, or occasionally makes it to the welcome screen before freezing and rebooting. I've been flashing ROM's on this thing for a while, and have been using unofficial cm10.1 so far as my daily driver. What the hell am I doing wrong?
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
AKToronto said:
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Still no dice unfortunately, I guess it's just not meant to be. CM10.1 is running great so I don't have much to complain about.
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
trathiang said:
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
Click to expand...
Click to collapse
Are these kernels being flashed with arioma installer... If you go to my aokp thread 2nd post you will see a tweaked 4.2 version-- it already has komodo modules installed and komodo is the boot.IMG inside the zip... Do this no skipseys---download that rom-- fastboot the boot.IMG in my zip---boot to recovery and wipe every thing INCLUDING SD CARD..x3---- now mount your phone to PC and copy and paste the ROM zip to your SD card..it will look weird cause it will be the only thing on there. ----- now install ROM then wipe only the caches after that--- hit reboot----system
And enjoy aokp with komodo kernel... Now to explain---every time you re flash that kernel you are stacking modules that is why you won't boot and also why you now need to do the spring cleaning wipe.... If you follow those steps exact no skipseys you will get it done---
Sent from my Nexus 7 using xda premium
Eureka! Did adb bugreport while it was booting to see what was going wrong, and I saw that there was something up with the voltages. Set the clock speed to minimum and then turned up the voltages in kernel tuner and VOILA, working overclock! I guess my phone, for whatever reason, disliked the undervolted voltages.
Soooo I've been on CM10 for awhile now and haven't had any trouble before. I've been updating from one nightly to the next. But as of recently the team made the next update to a CM10.1 (4.2) nightly. I've tried out CM10.1 and would of kept it as my daily driver if it weren't for the screen tearing and lack of LTE by default (earlier builds). Anyways, long story short I decided to update to the CM10.1 nightly by dirty flashing it and it didn't work. So I tried to restore to the backup I made and it didn't do anything! I just stayed at the CyanogenMod boot up screen. I literally let it sit there for a good 5 minutes and nothing happened. I thought about flashing the boot.img but see my data cable is busted
Can someone throw me some ideas or reasons for why I my restore isn't working? Do I still have to flash the boot.img even though its just a restore? PLEASE HELP!
ItsKarriD said:
Soooo I've been on CM10 for awhile now and haven't had any trouble before. I've been updating from one nightly to the next. But as of recently the team made the next update to a CM10.1 (4.2) nightly. I've tried out CM10.1 and would of kept it as my daily driver if it weren't for the screen tearing and lack of LTE by default (earlier builds). Anyways, long story short I decided to update to the CM10.1 nightly by dirty flashing it and it didn't work. So I tried to restore to the backup I made and it didn't do anything! I just stayed at the CyanogenMod boot up screen. I literally let it sit there for a good 5 minutes and nothing happened. I thought about flashing the boot.img but see my data cable is busted
Can someone throw me some ideas or reasons for why I my restore isn't working? Do I still have to flash the boot.img even though its just a restore? PLEASE HELP!
Click to expand...
Click to collapse
Depending on your HBoot, yes you will have to flash the boot image for the rom. Even if you back up in TWRP the boot image is lost when you flash over. I found it out the hard way. The best recovery is one with a built in aroma installer that will work with your HBoot. One is a Scott and one is a Nocturnal. I was lucky and recovered Viper XL 3.1.0 on top of 3.2.3 boot image but I would not want to try it again. Unless you have strored the boot image in recovery, find a cable and flash image. Hope this helps.
AT&T HTC OneX
Android 4.1.1
ViperXL
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
I'm having exactly the same issue with my one s, when it bootloops the only way to recover it is to boot into recovery, power off & reboot. Tried multiple CM/AOKP roms with the same issue.
As far as i know i'm on the latest firmware (how do you check in CM or is it baseband?) as it was RUU'd to 3.16.xxx then s-off'd, i'm not superCID currently as I had to change it back to HTC__001 to run the RUU. Hboot: 2.15, baseband: 1.11.50.05.28_10.27.50.08L
Its a European (UK) phone with the S4 if that makes any difference
Annoyingly I cant seem to get it to do it when I have a PC with ADB set up on it nearby!
Is there any more info that might be helpful that can be provided?
I also experienced the same thing. Hope senior member help us. :crying:
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
aosp 4.3.x need a hboot >= 2.15.x
have the ville with hboot 2.15, S-OFF, SuperCID, latest firmware (afaik)
Sent from my One S using Tapatalk
Which version of HTC one S? The Villec2 or Ville?
Kerjifire said:
Which version of HTC one S? The Villec2 or Ville?
Click to expand...
Click to collapse
the ville
I am having the same problem with my s4 ville hboot 2.15, S-ON, latest frimware
Any solution guys?
I spend the whole day running RUU's, re-locking, unlocking the phone, flashing different 4.3 AOSP ROMs but every time I boot the same thing happens: Sometimes I can't even get the rom to boot, but if it does, it usually crashes back to the splash screen after a couple of seconds. I am out of ideas. Any help?
I flashed the JB firmware as per the firmware thread and it has mad my current rom (beanstalk, couple of builds ago) slightly more stable, however flashing anything else results in a bootloop.
Incidentally as well, starting maps navigating, hitting home, then going back into maps again results in bootlooping
Edit
Attached a logcat of the phone bootlooping caused by the maps issue above, did have one of it happening in maps but I fat fingered my cmd prompt and overwrote it. I'll grab another once its recovered
Reading through it it doesn't seem to have captured the actual bootloop, i used 'adb logcat < file.txt' to record it, or is there a better method of capture, using the -f flag as per the dev website gave me a read only error either 'adb logcat -f file.txt' from a path i have write access to or 'adb logcat - f <filepath>file.txt' can I get adb to continue writing between device reboots?
Just flashed the awesome kernel cleaner script and then flashed bubba kernel so far it seems to be working, will report whether it worked or not after i test it more...
UPDATE: crashed into a bootloop