Develop Bugs

[Q] recovery OK, flashing OK, but stuck on reboot

all,
don't really know how I got here, but I don't like it at all ...
I can get into recovery mode as always (clockwork 2.5.0.1) and flash any new ROM I pick up here. but whenever I reboot, my phone is stuck at the white HTC boot screen (I waited up to 2 hours just to be sure it's not my impatience).
I wiped everything (factory reset, cache, dalvik) at least 5 times each. I flashed the latest OD, DeFrost, and Neo ROMs a few times. but whenever I try to reboot, my phone stays forever on that initial white screen with HTC in the middle.
a Nandroid restore of a previously working configuration ends up at exactly the same place!
getting a later version of clockwork seems rasonable? but how do I update that w/o booting up to run RomManager (asked the noob )?
any ideas or suggestions how to fix this?
AtDhVaAnNkCsE
PS. sorry when this has been answered before. but all "stuck at bootscreen" threads I found had the same resolution: wipe, Wipe and WIPE and flash again - I did that plenty of times now...

format sd card and reinsert. be sure to backup important data.
btw wipe-flash-rewipe. post results

after that, try using a sense-based rom, like Pays2.0 or pinky's rom.
Some users find problems with non-sense roms. If you can get a sense rom to work at least you know that something works!
imo, Paysftw!

mariosraptor said:
format sd card and reinsert. be sure to backup important data.
btw wipe-flash-rewipe. post results
Click to expand...
Click to collapse
FUNTASTIC! thanks a lot!!
the test with sense based roms will have to wait till "next time" - formatting the SD card fixed my problem.
my windows PC could only handle the FAT32 partition - but I could still erase the rest and that's good enough for now
thanks again!

glad the community helps. personally i would suggest-if you want a nonsense rom- that you should go for the stable version of opendesire. it is 4.0.15.
regards
Marios
dampf said:
FUNTASTIC! thanks a lot!!
the test with sense based roms will have to wait till "next time" - formatting the SD card fixed my problem.
my windows PC could only handle the FAT32 partition - but I could still erase the rest and that's good enough for now
thanks again!
Click to expand...
Click to collapse

All of a sudden...Bootloop? WTF

So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?

kevinzone said:
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
Click to expand...
Click to collapse
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.

efrant said:
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
Click to expand...
Click to collapse
will this make my files be deleted? I would rather not have that happen please

kevinzone said:
will this make my files be deleted? I would rather not have that happen please
Click to expand...
Click to collapse
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...

efrant said:
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
Click to expand...
Click to collapse
Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused.
If this is the ONLY way , then can you please tell me how to do this, i'm confused.
If there is another way on to get out of this boot logo aokp thingy, without losing data , please tell me.
Note: i dont know if i'm doing anything, but i backed up via the recovery CWM
then after i deleted cache and dalvik, then flashed aokp,franco and then g apps. And nothing happened

Bump please. i really don't want to wipe my phone

Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.

Prod1702 said:
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Click to expand...
Click to collapse
Uhh i reflashed aokp, kernel and gapps. Nothing really. Two questions.
1. Anything else?
2. for the reflashing, i want to flash another rom, how do i put the files on the phone? Gnex doesn't have an sd card slot and i dont know how to access it on the computer if it is in recovery mode. So confused
EDIT: not entirely sure what flashing means, so what i meant by flashing in my case, was that i just re ran the zips. then reboot. Nothing . waited 5-10 minutes ish. Never had long bootups on my first try.

Bump please!

kevinzone said:
Bump please!
Click to expand...
Click to collapse
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)

efrant said:
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
Click to expand...
Click to collapse
But there is a problem. I cant access the phone. Since it won't boot up i can't access it from the computer.. Or can i? There's no sdcard slot either

Unfortunately, app has stopped. [Please help!][LogCat][Reward]

If someone can solve my app issue there will be a reward in the form of a donation! How's that for an incentive?
I understand I posted a similar thread before to this but I wasn't resolved and I am completely out of ideas.
Which ever rom I'm on, which ever kernel, after a random amount of time using my phone an app with crash,
which seems to set off a chain reaction and then all my apps begin crashing.
It's usually google apps that start it, such as messaging, play store or contacts. Apex launcher also often gets affected.
Killing all apps and restarting the phone occasionaly fixes the problem for a little while.
I have used different kernels, used different android builds, factory reset the phone, wiped the sd card, cleared cache etc etc. Is this a hardware issue?
Things that might be worth knowing
When entering bootloader I get the following error messages:
Code:
Sd Checking...
Failed to open usb master mode
[COLOR="Red"][Preload] failed to open usb master mode[/COLOR]
[COLOR="Blue"]loading PJ46IMG.zip image...[/COLOR]
Failed to open usb master mode
[COLOR="blue"]Please plug off USB[/COLOR]
I can not save images, in other words it seems I cannot write to the SD card, looking in mounts and storage in CWM
reads:
Code:
unmount /cache
mount /data
mount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
format /system
mount USB storage
Which implies that everything is unmounted? Surely this can't be right and this is why I cant write to SD? Mounting them fixes the writing to SD problem temporarily.
When I get problems occuring next time I'll try to capture screenshots. I really hope someone has an idea what's going on here, if it's hardware I guess I'm screwed as the phone is out of warranty? :S
I have attached logcat's from around when the crashing happened last time, maybe someone can skim through them and identify the issue? Thanks

did you try different gapps???

I've tried lots of different gapps, the miui Rom im using now came with gapps as well

Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.

tomascus said:
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
Click to expand...
Click to collapse
Ok I'll make a logcat now, cheers bud. And I have tried with multiple different roms so it seems unlikely its a download issue

Heres the files. It took me ages to get any results, its typical when you want it to crash, it doesn't! Can someone more tech savvy then me have a thumb through them and try to identify the issue? Thank you very much
I think there is errors in both the logs but more in the second!

Now offering a reward for some help leading me to resolving this issue

bump

Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app

hahhahhaaa said:
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cheers man, really appreciate it!
If it helps, my hunch (baring in mind I'm not that savvy with this) is something to do with partitions unmounting themselves? when looking in CWM
sometimes they are mounted sometimes they aren't

That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition

Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.

Vcek said:
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Click to expand...
Click to collapse
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
hahhahhaaa said:
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Click to expand...
Click to collapse
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?

[★] said:
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
Click to expand...
Click to collapse
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU

Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?

try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.

Vcek said:
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Click to expand...
Click to collapse
Alright I'll remember that next time haha! How come anyway?
Installed again, no tweaks, stripped it down with rom cleaner, disabled gps services and haven't (yet) synced my google account just to be safe, we will see what happens
Stuar said:
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
Click to expand...
Click to collapse
It's a real pain isn't it! Yeah man the sooner the new RUU (1.28 first please!) come out the better.
Vcek said:
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Click to expand...
Click to collapse
I get this error before installing any apps usually so I dont think 3rd party apps have the chance to cause trouble

First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?

[★] said:
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
Click to expand...
Click to collapse
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.

peedub said:
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
Click to expand...
Click to collapse
would this work for someone on jelly bean?

Virus???? Idk but phone is messed up

Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.

not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.

tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.

if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.

When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.

tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far

PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off

im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)

maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!

tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.

when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before

i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.

tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work

[Q] Can't Last One Day with a Custom ROM

Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!

So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?

UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...

It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.

Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one

Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help

So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.

avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?

UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.

I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.

UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.

avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something

hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.

Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol

I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?

UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?

Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.

UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!

Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!