Develop Bugs

Phone continues to lock up

Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App

Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.

I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.

Did you wipe the caches in recovery?

treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything

still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.

IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"

bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should

odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers

movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/

I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.

KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )

IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also

tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.

I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium

htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.

Galaxy Nexus reboot every 3 min...

Hey i just bought this Galaxy Nexus from a Guy. At first it worked perfectly but after a few minutes it rebooted non stop.
So after i got home i've reflashed the Stock Google rom with the Toolkit, it change nothing so i put a custom rom on it, it change nothing (tried ParanoidAndroid, CM9, Kang...).
SO flahsed a different Stock rom through GN Toolkit. Stil the same. Flashed trought ODIN nothing (even thought the Odin rom was an old).
Right now it boots. I can use it 4 or 5 minutes and:
-The android system restart and go to the Bootanimation.
or
-The shutdown very quickly in a *pop sound. Et restart from beginning.
I think i'm going to send it to the repaire center. But i had 2 alaxy Note which i've bricked due to the SuperBrick problem. And i took the GN to have no issue with Android. Turns out i have...
I'm sorry if this has been before but i can't find a solution. And i'd like to have a phone tomorrow.
Thanks to everyone who will help me or even read this.

Atomos33 said:
Hey i just bought this Galaxy Nexus from a Guy. At first it worked perfectly but after a few minutes it rebooted non stop.
So after i got home i've reflashed the Stock Google rom with the Toolkit, it change nothing so i put a custom rom on it, it change nothing (tried ParanoidAndroid, CM9, Kang...).
SO flahsed a different Stock rom through GN Toolkit. Stil the same. Flashed trought ODIN nothing (even thought the Odin rom was an old).
Right now it boots. I can use it 4 or 5 minutes and:
-The android system restart and go to the Bootanimation.
or
-The shutdown very quickly in a *pop sound. Et restart from beginning.
I think i'm going to send it to the repaire center. But i had 2 alaxy Note which i've bricked due to the SuperBrick problem. And i took the GN to have no issue with Android. Turns out i have...
I'm sorry if this has been before but i can't find a solution. And i'd like to have a phone tomorrow.
Thanks to everyone who will help me or even read this.
Click to expand...
Click to collapse
Well, have you tried doing a battery pull, leaving it for 1-2 hours and then restarting the phone?
That's just one way... Before freaking, chill...
Whether you want it, or not; I'm going to tell you, what your phone is doing.
It's not restarting, every time it restarts with the *pop* sound, it's rebooting, from a crash. Every time it restarts, directly to the bootanimation, it's doing a hot reboot...
You're doing a very sensible thing, sending it in, because this is a definite hardware issue, that's why the guy probably sold it... Anyways, before you send it in, relock the bootloader (Enter fastboot and type
Code:
fastboot oem lock
)
Then make sure you have a stock firmware...
What I think is causing these problems? The guy who sold you the phone probably overclocked & overvolted that phone too much and for too long.

familyguy59 said:
Well, have you tried doing a battery pull, leaving it for 1-2 hours and then restarting the phone?
That's just one way... Before freaking, chill...
Whether you want it, or not; I'm going to tell you, what your phone is doing.
It's not restarting, every time it restarts with the *pop* sound, it's rebooting, from a crash. Every time it restarts, directly to the bootanimation, it's doing a hot reboot...
You're doing a very sensible thing, sending it in, because this is a definite hardware issue, that's why the guy probably sold it... Anyways, before you send it in, relock the bootloader (Enter fastboot and type
Code:
fastboot oem lock
)
Then make sure you have a stock firmware...
What I think is causing these problems? The guy who sold you the phone probably overclocked & overvolted that phone too much and for too long.
Click to expand...
Click to collapse
Thanks! I just wanted to make shure it wasn't a software problème. I thought about the overclocking and overvolting i just wanted to make shure it wasn't software.
It's been two day. I left the phone without battery for two days.
You think if i flash a custom Rom and undervolt and underclock the processor it will work? Is it a good idea? I need a phone tomorrow ^^'

Atomos33 said:
Thanks! I just wanted to make shure it wasn't a software problème. I thought about the overclocking and overvolting i just wanted to make shure it wasn't software.
It's been two day. I left the phone without battery for two days.
You think if i flash a custom Rom and undervolt and underclock the processor it will work? Is it a good idea? I need a phone tomorrow ^^'
Click to expand...
Click to collapse
Sure, why not? It's worth a try. Just don't undervolt too much, leave the CPU at min. 700 MHz, and set voltage on 700 MHz, to 900-950 mv.
Do that, and it may just be daft enough to work

Thanks!
Fast and great answer!

If you have already flashed stock image then you would have had the stock kernel which runs at stock speeds and stock voltages. If it didn't work then lowering the CPU clock speed won't work. Its not even a solution to your problem.
If it won't work with completely stock image then all you can do is send it back, sounds faulty to me.

nodstuff said:
If you have already flashed stock image then you would have had the stock kernel which runs at stock speeds and stock voltages. If it didn't work then lowering the CPU clock speed won't work. Its not even a solution to your problem.
If it won't work with completely stock image then all you can do is send it back, sounds faulty to me.
Click to expand...
Click to collapse
I didn't say that, either. I said it's worth a try. Read my first post (I think it was) and you'll see that I said it's better to send it in ^^
But this is worth a try, just to double-check...

Jelly Bean saved my Nexus
Was having this same problem, flashed CM9, AOKP, stock (every version) to no avail. Saw that JB dropped on XDA and flashed that just to play with it, thought my phone was borked but I just wanted to screw around. Totally revived my phone. Haven't had a single reboot in the 12 hrs I've been using it (coming from a reboot every few min). Just as a further note I was wiping everything when I flashed (battery stats, Dalvik, data...). PS JB rules hardcore!

I myself have been having random reboots with this nexus.
Actually picked up this phone 3 days ago new from Verizon so the phone hasn't been rooted/unlocked yet.
I want to love this phone. But the bootloops,etc is making it difficult for me.
Might have to succumb to the sgs3 as the last resort. :L

Galaxy S3 bricked... sometimes??

So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?

I agree with your assessments.

I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app

what's your setup as of right now?

Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%

It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.

I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure

mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2

I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.

I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki

[Q] Random Bootloop

So I was sitting in class today using snapchat, when all of a sudden my phone shut off. It started to reboot so I put it back in my pocket and would end up checking it in 5 minutes. However, when I took my phone back out it was stuck in a bootloop, and I don't know what to do now. I don't have a cord, and I haven't backed up my data in a few months as my phone has been running fine.
I'm Rooted using Vanilla Rootbox v4.0.1. This rom has been perfectly fine for the past few months, and this is the first boot loop that I have encountered. Any ideas of what to do without having to wipe my phone?

MrDynamo said:
So I was sitting in class today using snapchat, when all of a sudden my phone shut off. It started to reboot so I put it back in my pocket and would end up checking it in 5 minutes. However, when I took my phone back out it was stuck in a bootloop, and I don't know what to do now. I don't have a cord, and I haven't backed up my data in a few months as my phone has been running fine.
I'm Rooted using Vanilla Rootbox v4.0.1. This rom has been perfectly fine for the past few months, and this is the first boot loop that I have encountered. Any ideas of what to do without having to wipe my phone?
Click to expand...
Click to collapse
Which governor are you running? I had this problem on my GS3 & HTC EVO LTE, both running CM based ROMs. I changed kernel governor to "on demand", haven't had any problems ever since. It may take a little more battery, but well worth it to me.

Random power offs

This has been happening for about 2 months now and has progressively started happening more frequently.
I've narrowed it down to a set of apps that are running when it happens.
Apps in use:
Screen On ( to keep the screen on while driving)
Waze (If you don't know what this app is stop reading now)
Play Music (Streaming through the Pioneer head unit)
It doesn't happen all the time but when it does the screen freezes for about 5 seconds then goes black and music stops the instant the screen freezes. Once the screen is black I try holding down the power button. Sometimes it'll power back on but most times I have to do a battery pull.
I've tried multiple ROM's and it still does it.
I've formatted my internal and external SD.
The last thing I still need to do is ODIN back to stock and then re-root.
Its taken me two weeks to get a logcat when the phone locks up. I'm not sure how much is needed so I'll attach the 2 hour logcat
Get Logcat here.
If someone can help me out and check out the logcat it would be extremely helpful. I can't ODIN back to stock yet because I'm on call all week and need a semi functioning phone till Friday.

I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?

p_synthesis said:
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
Click to expand...
Click to collapse
I had similar experience when using my phone as gps device in a long distance drive. Maybe because it got hotter?

Yesterday I was at the hospital with my son (he just had his tonsils removed). We were watching a movie Netflix and my phone locked up and rebooted 4 times within a 30 minute span. I finally had time afterwards to Odin back to stock and updated to NF4 then CFautoroot, TWRP latest and flashed Hyperdrive. I had hoped all was good but when i was cleaning out my car (streaming to the BT stereo) it locked up 10 minutes into my playlist.
Should I take it back to T-Mobile? Is there something else that I can do to troubleshoot?

Are you guys using any cpu apps?

Not that I'm aware of. I am using the compulsive kernel that is bundled with the latest hyperdrive.

Kernel issues, try other kernels.:good:

If you have a custom kernel, don't use setcpu in addition with the specific cpu governor app for that kernel. Also, don't set you minimum at 300 or lower. It's been documented to cause random reboots.

Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.

wonderbread24 said:
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
Click to expand...
Click to collapse
if u want to try something, when u ODIN flash the firmware, after it boots up, I ODIN flash TWRP then use my Stock Odex not rooted roms,then if u want root just flash SU from chainfire and install busybox,from the playstore, keep a copy on the sdcard and install.. and LEAVE the STOCK KERNEL, I use stock kernels and have no issues this way,
make a copy of my rom, remove the files u don't want from system/app and system/priv-app then flash that rom and SU right after that install busybox, and test that way. if u want I also have on the 3rd page a tethering rom, I have all the version, http://forum.xda-developers.com/showthread.php?p=51812491#post51812491
try it out, If u have problems, try not restore any data if u use titanium backup..