Develop Bugs

Random Root Problem

So i bought my incredible the second day they were released, and rooted it when unrevoked came out with their first one-click root program (so needless to say im not exactly a "new" root user). i've ran a couple roms, and lately have run stock leaks w/ added .zips for a little customization (about the past three months or so). i've been on the latest leak for like a month ish (i think its the latest one) possibly little bit longer than that. i never had a random reboot or even really any lag up, which was really amazing. then, i tried to install a custom flat black notifications bar, and i installed the update zip through recovery but it didnt do anything.
about two weeks later, i installed that new status bar power menu thing, and started to get the occasional random reboot and bog up. no really enough to really be a problem, but tonight right before bed my phone started boot looping after a random reboot (it would boot for a min or two then reboot after a lockup). so i pulled the battery and powered back on. then it loaded to the lockscreen, but every single app that should have started at startup began to repeatedly force close, so i couldnt use the phone. i tried three times but it happened every time. im nandroiding now, im sure that'll fix the problem, but any ideas what caused this? thanks!

just happened again on ruby 2.0.0, but this time all of the apps force closed AND the "click android to start" setup screen came up. I got a random reboot (which i rarely to never have), pulled battery and powered back up, it loaded to lockscreen, then it went into a soft reboot and froze at the looping bootscreen, then once i pulled battery again and powered up, i got the crashes. any idea what it is? this time, it did happen like 15 min after i had dropped my phone from about 2 feet off the ground, i guess that could be it? idk

For what it's worth, I was running 2.3 and it wouldn't mount internal or SD. This happened even after installing other ROM's. I downloaded the latest RUU, unrooted, and started from scratch.
I reformatted the SD card too. I re-rooted, and restored my SD backup. I re-downloaded the ROM I wanted, and installed it. It fixed the weird issues I was having. You may want to consider starting over from scratch.
Sent from my Incredible using XDA App

[VZW] Phone Random Shut Off?

Hello everyone,
I've recently rooted and unlocked my phone in order to partake in some Jelly Bean goodness. I've read and done the nandroid backups/cache wipes/dalvik cache/factory resets, and have flashed my first ROM (Vicious 10-20120808-UNOFFICIAL-toro 4.1.1). The installation went smoothly, and the phone was working great until a weird problem happened.
I was texting on my phone, put it down, came back to it a few minutes later and the screen was completely off, and it would not respond to the power button. In order to get it to work again, I had to remove the battery and place it back in for it to respond normally. Upon doing so it would boot back up normally and I'd be golden, but now I'm noticing it is doing the shutoff again every few hours when its idle.
Any ideas for a fix?

I am having the same problem. Went backdown ICS for now. Have you found a solution. I was using the JRO30 JB build.

Happens sometimes to some ROMS. I have no idea why it happens, but its nothing wrong with the phone itself. I recommend AOKP for awesome battery life, performance, and features
~Sent from my Galaxy Nexus VZW

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

Issues with no sound and boot looping

So i have a weird problem with my note 2. For some reason the phone has no sound whatsoever and when i try to make a call or play sound the phone shuts off or freezes. Also when i turn the screen off after 20 seconds or so the phone will not turn on unless i pull battery and power on.
Started after i pulled the battery last week while phone was on went in to replace the vibrate motor. After i booted touch became super laggy, system kept crashing. And phone kept powering on then shutting off after full boot. Probably a dozen times. Ended up damaging my sd card in the process. I've re flashed a few roms and nothing really helps. When i'm in recovery the phone is fine. I've wiped everything a few times also. Currently on 4.3, I was running sky note F1 update 3. I've tried stock, meanbean and even slimkat 4.4.2 but no success. I swapped my board out into another note 2 to see if parts were defective and still have same issue. I havens flashed a bootloader yet though don't see how that is going to change anything. Anyone have some input or help with this would be great.
Thanks.

[Q] Phone Keeps Soft Rebooting

I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.

Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?

Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?

Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.

Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow

UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.

_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.