Develop Bugs

[Q] [Help] Constant force closing on certain ROMS

So I've got a strange one for you...
Here is what I CAN do:
I can ODIN back to stock 4.0 or 4.1 without issues
I can flash AOKP and Liquid Smooth roms without issues
Here is what I CAN'T do:
I can't install Cyanogenmod10, Hellfire, and Paranoid based Roms without continual systemui.exe force close errors and many many gapps force closures as well. It makes the ROM no longer usable.
I always factory wipe and clear both cache when flashing a new or different ROM. (I've done the whole "fix permissions" thing too, seems to make it worse)
I've even ODIN'ed back to stock and reflash to see if that fixed anything... NOPE!
I'm at a loss for what I've done to get these errors...
1. I have edited some files for the Google Wallet to work, but I no longer care about Google Wallet. Not sure if this would be a cause but its something right?!
I've been at this since G1 days, and I've never run into anything like this before.
Appreciate whatever assistance you can provide.

Have you tried a different gapps file? I've been seeing a lot of issues with different ones
Sent from my SGH-T999 using Tapatalk 2

bfranklin1986 said:
Have you tried a different gapps file? I've been seeing a lot of issues with different ones
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I always flash the Gapps that is associated with the ROM. Usually a dev recommends or modifies one to use.

Why is this happening to my Gnexus?

Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.

I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD

Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.

4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway

nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..

crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2

Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app

plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens

Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!

lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.

Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related

Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.

Alright will do as suggested

How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!

update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.

nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..

Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far

So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.

AOKP Unresponsive Black Screen ... Help?

Hey guys,
I installed aokp_d2tmo_jb-mr1_build-6 via Goo Manager and for some reason at random times, the phone becomes unresponsive. No buttons, combination of buttons or swearing gets it to work. I have to do a battery pull before it reboots and everything goes back to normal ... until it happens again.
Does anyone have any thoughts on what the heck is going on? Am I just on an unstable ROM?
TIA

these sound like issues a full wipe would take care of. what procedures did you follow? i would:
Wipe data/factory reset
Wipe Cache
Advanced and Wipe Dalvik Cache
Mounts and Storage and format /system
Flash the ROM and gapps
Reboot system. Once the phone is booted, let it sit for 10 minutes, reboot again
you may have already done all this.

llcooljayce said:
Hey guys,
I installed aokp_d2tmo_jb-mr1_build-6 via Goo Manager and for some reason at random times, the phone becomes unresponsive. No buttons, combination of buttons or swearing gets it to work. I have to do a battery pull before it reboots and everything goes back to normal ... until it happens again.
Does anyone have any thoughts on what the heck is going on? Am I just on an unstable ROM?
TIA
Click to expand...
Click to collapse
Bug with new 3.4 kernel. Wait till they develop it more.
Sent from my SGH-I747 using xda app-developers app

Try checking the minimum clock speed and possibly increasing it a step or two?
Sent from my SGH-I747 using xda app-developers app

dima470 said:
Bug with new 3.4 kernel. Wait till they develop it more.
Click to expand...
Click to collapse
Is there a build that is recommended (ie stable)?

llcooljayce said:
Is there a build that is recommended (ie stable)?
Click to expand...
Click to collapse
Look for the last 3.0 build.

llcooljayce said:
Is there a build that is recommended (ie stable)?
Click to expand...
Click to collapse
yes. builds that are using the 3.0 kernel. the ROM OP will list when the release features in the changelogs.
if you like aokp, i have been running their 4.1.2 milestone since december. very stable when coming from a full wipe. within the next week or 2 they will be releasing their 4.2.2 milestone. i will be updating to it then

[Q] Quantum Rom issues

Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.

It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow

DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.

iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.

also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.

What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.

Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)

DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things

DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...

supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.

[Q] Clock app not working with CM11

I just flashed the unofficial CM11 onto my DINC yesterday, and the clock app is not working. Is there something I can do to fix it or should I just find an alternative and disable it?

More information plead. Did you come from another Rom without wiping? If you came from cm10.2 or earlier cm versions you may just be able to clear data in the app screen for this app.
Do you get force closes or any particular errors?
It's recommended to wipe coming from sense for sure. AOSP ROMs you may be able to get away with not wiping but the general idea is to wipe when coming from a different Rom.
Sent from my HTC One using Tapatalk

tiny4579 said:
More information plead. Did you come from another Rom without wiping? If you came from cm10.2 or earlier cm versions you may just be able to clear data in the app screen for this app.
Do you get force closes or any particular errors?
It's recommended to wipe coming from sense for sure. AOSP ROMs you may be able to get away with not wiping but the general idea is to wipe when coming from a different Rom.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I was coming from a non-sense stock JB ROM, not CM. Maybe I'll try wiping properly