Hello everybody. I need some help. I actually tried posting my problem in a thread which was labelled noob-friendly problems solved, something like that. But I didn't get any support from there. No replies, nothing. Its been 2 days. So I made a decision to post this as a new topic. I'm sorry but it is a little serious. So here is the problem-
I flashed Color OS on MultiROM, with CM12S as the primary ROM. I have kexec patched AK kernel on my CM12S. Later I got to know that Color OS doesn't work as a secondary ROM, so I swapped my CM12S with Color OS, and everything worked well. I also took a backup of CM12S before swapping. But when I flashed kexec kernel of 4.4.x on Color OS, it didn't boot up, but the other ROMs did(as I was on MultiROM). Then I reflashed Color OS without that kernel. This time Color OS worked but MultiROM didn't as it said that it needs that kernel to boot into other ROMs. As I use CM12S as a daily driver, I decided to make it my primary ROM again. So I swapped Color OS with CM12S and now CM12S became the primary ROM. As Color OS was of no use, I deleted it. Now if I boot my phone, the Color OS boot image appears and there is a delay of about 2 seconds after which a white screen flashes and then the boot animation of CM12S starts. I tried recovering my previously taken backup but the problem persists. Any kind of help would be appreciated.
Thanks!
7u5h4r said:
Hello everybody. I need some help. I actually tried posting my problem in a thread which was labelled noob-friendly problems solved, something like that. But I didn't get any support from there. No replies, nothing. Its been 2 days. So I made a decision to post this as a new topic. I'm sorry but it is a little serious. So here is the problem-
I flashed Color OS on MultiROM, with CM12S as the primary ROM. I have kexec patched AK kernel on my CM12S. Later I got to know that Color OS doesn't work as a secondary ROM, so I swapped my CM12S with Color OS, and everything worked well. I also took a backup of CM12S before swapping. But when I flashed kexec kernel of 4.4.x on Color OS, it didn't boot up, but the other ROMs did(as I was on MultiROM). Then I reflashed Color OS without that kernel. This time Color OS worked but MultiROM didn't as it said that it needs that kernel to boot into other ROMs. As I use CM12S as a daily driver, I decided to make it my primary ROM again. So I swapped Color OS with CM12S and now CM12S became the primary ROM. As Color OS was of no use, I deleted it. Now if I boot my phone, the Color OS boot image appears and there is a delay of about 2 seconds after which a white screen flashes and then the boot animation of CM12S starts. I tried recovering my previously taken backup but the problem persists. Any kind of help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Just dirty flash the CM12S rom and also the latest firmware. Also wipe cache and dalvik only.
You cannot run a secondary rom with Color OS running on Multi rom. When you want to use secondary rom, you need to flash the patch and boot to secondary and when you want to use color os back again, you need to flash the boot.img (Stock kernel for Color) again and boot into it. You might have messed up in this process of flashing.
Let me know if the problem still persists after flashing stock kernel of CM12S (Dirty Flashing).
venky61 said:
Just dirty flash the CM12S rom and also the latest firmware. Also wipe cache and dalvik only.
You cannot run a secondary rom with Color OS running on Multi rom. When you want to use secondary rom, you need to flash the patch and boot to secondary and when you want to use color os back again, you need to flash the boot.img (Stock kernel for Color) again and boot into it. You might have messed up in this process of flashing.
Let me know if the problem still persists after flashing stock kernel of CM12S (Dirty Flashing).
Click to expand...
Click to collapse
I have already flashed the CM12.1 Nightly of 02/06 and it is much smoother than CM12. The battery backup has also improved tremendously! And yes, the problem is also solved. Thanks for your help anyway.
7u5h4r said:
I have already flashed the CM12.1 Nightly of 02/06 and it is much smoother than CM12. The battery backup has also improved tremendously! And yes, the problem is also solved. Thanks for your help anyway.
Click to expand...
Click to collapse
You are welcome Keep flashing
venky61 said:
You are welcome Keep flashing
Click to expand...
Click to collapse
Haha, sure. :v
Related
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
GarnerArms said:
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
Click to expand...
Click to collapse
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
S1L3nTShaDoWz said:
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
Click to expand...
Click to collapse
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
GarnerArms said:
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
Click to expand...
Click to collapse
No no sorry if I confused you or said that wrong, wipe, flash Liquid Smooth & flash the GApps (Same way as before will work as long as its after the ROM) then wipe your cache/dalvik cache(best do this before and after flashing) and attempt booting into it.
Tell me the results of this once you've tried it.
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
GarnerArms said:
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
Click to expand...
Click to collapse
Some ROM's simply require it and others don't. On the ROM versions, whatever version the ROM you are flashing is based off of is the ROM version. So if Liquid Smooth is 4.4.4 then that means it is based off of the 4.4.4 update for either another edition of the device (Sometimes since Verizon doesn't release anything timely) or YOUR version (Verizon in this case) of the device.
Thanks bud. Followed your directions and boom it worked. Time to play with some custom Roms!
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
AppleGeek911 said:
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
Click to expand...
Click to collapse
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
the same situation here.
i did everything that i can do. wiping everything and full clean flashing include.
Use an older version of twrp maybe?
nunojsa said:
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
Click to expand...
Click to collapse
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Update: Flashing the boot.img from the Cataclysm .zip via Fastboot had no effect on anything. Also, I haven't tinkered with the filesystem of my /cache or /data.
AppleGeek911 said:
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Click to expand...
Click to collapse
try flashing the image from googles developer page to end the boot loop
Pranjal53 said:
try flashing the image from googles developer page to end the boot loop
Click to expand...
Click to collapse
I have a backup in TWRP that I can always restore from, so I'm not stuck in a boot loop. Thanks for the suggestion though.
flar2 said:
Use an older version of twrp maybe?
Click to expand...
Click to collapse
I'll try it, thanks so much. Edit: Flashing Cataclysm/ElementalX using TWRP v2.6.3.4 solved the problem. Thanks so much, it's great to see you interacting with the community
Hi everyone! First of all, I was wondering if is it worth it to install CM12S having already CM12.1 last nightly; and if you say so, is it enough to make a clean install and flash the CM12S zip? Cause I don't wanna mess it up forgetting about flashing the correct boot.img or something and make my One a wonderful paperweight.
Thanks!
I haven't used 12.1 for a bit, as I went to 12S and have remained there until the official full 12.1S release arrives, but my suggestion is always to do a clean install. It provides the most assured way to have the most secure/error free system, and it takes a very short time, as well.
So there's no need to flash any boot or kernel?
sdert said:
So there's no need to flash any boot or kernel?
Click to expand...
Click to collapse
No, the kernel is included in the zip. But always clean install.
SI have revert from the CM13 to Resurrection Remix (which is also a CM) however Im wanting to change to a predated ROM or even a different ROM and it isnt allowing me. In both CWM and TWRP it says the it installed just fine but when I boot up its still Resurrection and yes I have done all the wipes that should be done and still same thing happens.
How can I fix this?
OK
johneflik said:
Jut use advanced wipe in TWRP then wipe everything except the external SD. I guarantee no thing will boot again unless you flash it.
Click to expand...
Click to collapse
That did the trick, was able to flash again and put back on the ROM before it got stuck on RR. Idk what went wrong in that ROM change, had to edit Updater-Script and got CM13 going again