Database Users

No CM9 Roms work for me

Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks

Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Make sure the kernel you using supports cm

Dasanko said:
Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)
Click to expand...
Click to collapse
Alright downloading now, hopefully this will work.
Edit:
Didn't work for me, I never saw a boot logo/animation.
fanaticprakash said:
Make sure the kernel you using supports cm
Click to expand...
Click to collapse
What kernel do you recommend?

I actually have the same problem. This CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"

I've been having the same problem for two weeks now, if anyone can solve this I would really appreciate it
Sent from my Kindle Fire using XDA

kwheel596 said:
I actually have the same problem. That unofficial CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"
Click to expand...
Click to collapse
I actually had it load completely after verifying apps, but once I rebooted it always froze at the boot animation.

Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk

Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.

erikikaz said:
Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.
Click to expand...
Click to collapse
This doesn't work either :/
Sent from my PC36100 using xda premium

I have the same problem too, all the ics roms do not work except for the one stated in this thread previously and the Hellfire ics rom.
It gets stuck at the boot screen.. I have tried wiping everything including sdcard..
And also, my kindle hangs frequently when running 3d games and I have to hold the power button to force shutdown it..
Is it a problem with the kernel?
The notifications button at the bottom right corner is also very unresponsive, I have to press it several times to open the menu..

ammubarak said:
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.

how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.

Raiden619 said:
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.
Click to expand...
Click to collapse
man thats so strange... cwm or twrp? when you flash it dose it flash really fast

DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
Its not that I'm not waiting long enough for the boot animation or anything. For example it will load up some the first time and get all the way past the spinning circle on the CM9 boot animation and get stuck on the "verifying apps" screen. Other times that i try to boot it it will get stuck with just the little android and the circle around him, not even 2 full seconds into the boot animation.

The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk

sej11 said:
The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Nice first post!
All signs are pointing to a ****ty wipe. The recovery's fault, so long as you didn't forget to wipe everything under mounts.

erikikaz said:
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.
Click to expand...
Click to collapse
i have switched over from twrp to cwm.. waited for at least 15 mins, but its still stuck at the bootscreen..

Pretty sure this would help alot of people, can someone try and solve this?
Sent from my Amazon Kindle Fire using xda premium

[Q] After flashing SmoothRom Version 5, Nexus 7 wont boot.

Hey.
i recently used TeamWin Recovery to flash SmoothRom version 5 but now i am having problems. I wiped both cache and system (userdata etc) and then flashed it. However. now my nexus 7 wont boot past the Google splash screen. I can still get to bootloader. Please help!

Simple - restore one of your many Nandroid backups.
You do make backups, don't you? If not, can you provide a single reason why you do not?
Normally you perform a "factory reset" in TWRP's wipe menu before you flash a ROM - that's it, no other "wipes" are needed. The ROM package installer will do the wiping of /system for you, and /cache barely matters at all. (Do NOT use the "format data" wipe in TWRP unless it is an extreme emergency - that deletes everything in /data INCLUDING the psuedo- SD card area stored under /data/media).
If you don't know whether it is your device or the ROM that is giving you fits, flash a different ROM. If it is hardware, most ROMs will fail.
BTW, when folks have bootloops or hangs on a given ROM that works for everybody else, it is usually because:
- they did a "dirty flash" (did not do a "factory reset" first), OR
- they flashed a kernel that was incompatible with the chosen ROM, OR
- they flashed a zip file that was incomplete and they failed to take notice of the error messages on-screen.
good luck

Thanks for your help. Yes I did backup my stock Rom beforehand and I have been able to restore it. I did all the steps you said but it still didn't work though. I will keep trying.
Sent from my HTC Desire S using xda app-developers app

Hicksy994 said:
Thanks for your help. Yes I did backup my stock Rom beforehand and I have been able to restore it. I did all the steps you said but it still didn't work though. I will keep trying.
Click to expand...
Click to collapse
I actually didn't give any steps at all, other than suggesting that you restore a backup if you have one - I only outlined the areas that cause problems, so I don't really know what you attempted.
Are you saying that you can successfully restore a backup, and everything works for that restored backup, or that you tried flashing other ROMs, and they worked, but not your ROM of choice, or are you saying that you can't get the tablet to boot correctly no matter what you do?
I think you will find that the more precisely you describe what you attempted, and what you observed when attempting those things, the more likely that people will come out of the woodwork to help you.
The very worst thing you can say is "it didn't work" without any details - when you think about it, you will realize that is only a single binary bit of information.

Sorry for confusion. I managed to restore my stock ROM. Then I tried to flash smooth ROM again, (doing everything you said) but it still got stuck on the Google splash screen
Sent from my Nexus 7 using xda app-developers app

Hicksy994 said:
Sorry for confusion. I managed to restore my stock ROM. Then I tried to flash smooth ROM again, (doing everything you said) but it still got stuck on the Google splash screen
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, Hicksy994...
When I flash a ROM I've never used before,... I do a COMPLETE WIPE...
(With Titanium backups done beforehand).
------
Here's how
Booting into TWRP 2.4.4.0... I first perform a NANDROID backup...
I then select the WIPE option; this gaves me the WIPE MENU.
By force of habit perhaps, I then hit THE FIRST THREE BUTTONS...
wipe CACHE
wipe DALVIK CACHE
FACTORY RESET- this button covers the first two, so mayhap they are redundant... but I press them anyway.
I then hit the SYSTEM button; (wipe system) - THIS WIPES YOUR CURRENT ROM -
- but WARNING!!! if you don't have a replacement ROM.ZIP to flash, currently stored on your internal storage... or a NANDROID backup to fall back on... you will have an unbootable device (unless you fastboot flash back to stock... or adb push from your computer).
But of course, if you have already have SmoothROM-v5.0.zip, in the /download folder, this shouldn't be a problem.
----------------------
So wipe everything - BUT ABSOLUTELY DO NOT TOUCH... OR WIPE.. EXTERNAL STORAGE, INTERNAL STORAGE OR FORMAT DATA - CONSIDER THOSE BUTTONS OFF LIMITS!!!.
These last three buttons, in TWRP, seemed to have cause no end of trouble for many - they should have been hidden away in some 'Advanced Option' setting... in my opinion.
----------------------
So to summarize...
In TWRP... (in the WIPE menu).
Factory Reset
Wipe SYSTEM - (clear out your current ROM, completely).
Then go to INSTALL... and flash the SmoothROM.zip
(there's quite an extensive installation procedure involved, requesting you choice of kernel, browser, etc)
Reboot... and you should be be good to go...
-----------------------
I flashed SmoothROM a couple of hours ago, using this method: seems kind of OK - only problem is... I can't seem to stop Google Backup from downloading and re-installing every bloody app I've ever installed since last November!.
But that's another story.. which I'm sure I'll figure out.
Rgrds,
Ged.

Firstly, thank you for your help. Unfortunately I followed your exact steps, went through the ROM set up (choose kernel etc) and it said successfully installed, so I hit reboot but it wouldn't boot past the Google screen.
Could the kernel I choose have anything to do with it, I haven't tried them all yet?
Sent from my Nexus 7 using xda app-developers app

Hicksy994 said:
Firstly, thank you for your help. Unfortunately I followed your exact steps, went through the ROM set up (choose kernel etc) and it said successfully installed, so I hit reboot but it wouldn't boot past the Google screen.
Could the kernel I choose have anything to do with it, I haven't tried them all yet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I suppose it could be a kernel issue... bit of a longshot though...
Stock AOKP kernel
Motley Build 249
Trinity 4.2.2 Alpha 1
Franco R47 (recommended
M-Kernel a38
LeanKernel v1.54 (recommended)
...which one did you chose? (I choose franco..)
Rgrds,
Ged.

Again, thanks for help, I tried a few such as motley but not the one you suggested. I will try again soon with that kernel.

Hicksy994 said:
Again, thanks for help, I tried a few such as motley but not the one you suggested. I will try again soon with that kernel.
Click to expand...
Click to collapse
Now tried with all available kernels as listed... no problems at all, booting beyond the Google logo.
Have you tried flashing any other ROMs? What happens?
Rgrds,
Ged.

Thanks for the info. I will try another ROM tomorrow and see what happens.
Sent from my Nexus 7 using xda app-developers app

Stuck on Samsung Custom Screen w/ Custom ROM

Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!

I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta

Flash a different kernel.
Period
your welcome

TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz

And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.

KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.

what procedures are you using for all of this? is there a specific guide you are following?

xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.

There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1

TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.

i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.

xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!

I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.

I am 1000000% sure of this.
are you really sure?
j/k, perfect.

TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.

jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.

Got rooted, installed custom recovery, lost root, now i'm confused...

So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks

Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent

ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.

Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent

Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.

iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent

ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.

Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta

daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.

iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.

iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?

ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?

iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.

ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.

Wifi has problems turning on sometimes

Hey everyone!
I have been a long time XDA member and was hoping someone out there could help me.
I have an MDL bootloader and am running CM11 currently. I have tried multiple kernels including stock CM11, ktoonsez, and Chronic and different ROMS. However I have a problem where sometimes my wifi refuses to turn on. I will click for it to turn on and it will say "turning on" but it just hangs there. This also happens if I soft reboot my phone( meaning I will lose wifi if I soft reboot at anytime) The only way to fix it is to give it a full reboot. I have tried with xposed unistalled and all. I can't possibly see it being caused by an app, but any help would be appreciated!
Thanks a bunch!
-Patrick

When your flash a rom do you do a Chen install? Wipe data, system and the caches
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
When your flash a rom do you do a Chen install? Wipe data, system and the caches
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yup!I've even flashing Roms for years and have never run into this. It seems like no one else mentions the problem in the posts for the ROms either. I think I'll try to run cm10.2 to see if its just KitKat roms

Pikezer1337 said:
Yup!I've even flashing Roms for years and have never run into this. It seems like no one else mentions the problem in the posts for the ROms either. I think I'll try to run cm10.2 to see if its just KitKat roms
Click to expand...
Click to collapse
I also had that problem for nearly a month, your EFS partition may be corrupt, Just ensure to be rooted open up Root Explorer and go to your EFS folder & select all files and folders, after that set all the permisions to everything, reflash stock or your prefered rom and it should be working fine, this is what fixed my problem.