I've tried two different ROMs already and got the same problem...
All of a sudden around a month ago I installed Cyanogen nightlies, and they were doing great, some were actually very stable. Lately any ROM I flash, whenever I reboot the phone, the Home and Search buttons cease to function, and the brightness is turned all the way up. This creating absolute chaos out of my ROM. And then I need to reflash something else. But this isn't just like one time, every time I reboot.
I always flash cleanly, wiping data/cache/dalvik and formatting system. WTF is happening?! My incredible legit feels broken, it happens every time .
Related
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
ernbrdn said:
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
Click to expand...
Click to collapse
I've never seen that before. Interesting. What rom are you currently using? Do you have an unusually large amount of apps installed? The first thing I would do, is make a nandroid backup of your current setup, and then do a full wipe and flash a format all.zip, then reflash a different rom. Or just simply restore a nandroid of a known good setup, and see if the problem persists. If it stops, I'd say it was something specific to the rom/kernel/setup that you were running before. If it continues happening on a clean install of a different rom, then I'd probably unroot, restore to stock, and then see if the problem continues. If it does, take it to Sprint. If it stops, and everything is fine, re root it and start over. That's just what I would do, but I've never been presented with an issue such as that.
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
ernbrdn said:
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
Click to expand...
Click to collapse
If it started happening right after you swapped out the kernel, that could be the culprit. If you want to try the gingersense rom, I'll all for it, and will tell ya that they ran super incredibly smooth for a factory rom. However, if you don't feel like changing roms just yet, maybe try a different kernel. I'd be suspect of that, if the problem started shortly after changing to a different kernel. I say try out a gingersense rom, you shouldn't be disappointed (unless your phone still hangs at the splash screen upon reboot, lol).
I have been having a problem every time I change roms where after it boots up, i get maybe 5 minutes to play around and then the home screen crashes. It reloads, finds a signal, media scanner running etc, just like i just turned the phone on. Before I can do anything, it crashes again and repeats forever. Its not boot looping though. But it makes the phone useless.
This happened last time i tried the 12 lockscreens mod (im on calkulins 2.8.1), so i had to wipe and reflash calks rom since my backup was bad. Then i made another backup to be safe, which is working. Today i tried flashing blu kuban by rujelus22. Same thing happened. Which makes me thing there is a deep seated issue somewhere in the phone.
Every time i flash a new rom, i wipe cache and dalvik, and format system. I also tried a factory reset. Nothing solves my problem and I cant find anything similar anywhere.
I really hope one of you has a brilliant idea for me because I really love this phone, but If im stuck with one rom forever I would be a very sad panda
BTW i have to thank all the devs for all the sweet roms and hacks, you guys rock
Download calkulins wipe all.zip
Run that then try to flash your rom
Also in CWM run the fix permissions option....that usually fixes alot of issues
Sent from the near past
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
My wife's phone is having issues with the capacitive menu button.
It doesn't matter what ROM is installed, it will work for a little while and then it stops working completely.
What I have done already:
Wipe in cache and davlik cache in TWRP.
-No change
Wipe/Factory reset in TWRP
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
Flash different ROM
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
This began about 2 months ago and she just lives with it. I cannot, too many things she does not have access to without it.
Any ideas? If not, I may just bring it to sprint and see if there is a physical issue with it. Strange that it works for a little while though.
We both had the same phone for a while, just upgraded mine, but she does not have anything installed that was different from mine or different from what she used for the first few months of owning it. Everything was working fine for a while.
Thanks for the help.
I've recently started having trouble with my N7100 freezing/locking up.
I bought it shortly after launch, so it's a little over 1 1/2 years old. I had flashed one of the first rooted 4.1.2 firmware that was available, and never bothered updating because it was stable and got great battery life and I didn't feel like dealing with ROM stuff. But recently with the official 4.4.2, I decided to finally update, and decided on trying out DN3. So I flashed the latest TWRP, did the usual backing every thing up, flashed the MJ5 bootloader, and flashed it. It kept bootlooping, so I figured something went wrong, so I restored my 4.1.2 backup. This was where the freezing began. It was to the point where I couldn't use it. Tried rebooting a few times, but every time it would freeze as soon as it booted or shortly after. I assumed something just went wrong with the backup, so I tried flashing DN3 again. This time it booted successfully, but would occasionally freeze, most often when loading an app, but sometimes just randomly. After a couple days it seemed to subside. Then I decided to try out OmniRom. Same thing -- it would occasionally freeze up, then after a while would be fine. (Note: these were both clean installs.) Seems like every time I'd flash an updated version of Omni, the freezing issue would flare back up. Just now, I flashed the latest homemade build, and the freezing was really bad again, to the point where I can't even use it. Sometimes it'll freeze the instant it finishes booting, sometimes it'll freeze a few seconds after, sometimes it'll finish booting and will be fine until I load an app, then would freeze, and sometimes it would be fine for a couple minutes and the just freeze randomly. What's odd about it is that the screen is still responding to touch. Every thing's locked up, but when I touch the screen, the capacitive buttons light up as though it's still working fine, but nothing else works. I've even had a couple times where I let it sit for about 10 minutes and then it started responding again.
What's really frustrating is that I can't find a common cause here.Started on 4.1.2 (which had never had any issues beforehand), continues on a clean install of DN3, and continues on a clean install of OmniRom. Disabling Xposed and removing my SD card had no effect. It boots fine into recovery and download modes.
Does anyone know what the issue could be here?
EDIT: And now I've done a complete wipe, again, and reflashed DN3, again, and it appears to be working fine. Go figure.
It's not suddenly death?
see this: http://forum.xda-developers.com/showthread.php?t=2093599
sorry my english