I was on CyanogenMod M5 lately and everthing worked fine. After M6 was released and I flashed it my device started to behave strangly.
Basicly every action has the cance to freeze the device, making it unusable for the next 20 seconds to 2 minutes. These are the symptoms:
1. Screens goes black. Notification bar and software buttoins remain visible but unusable
2. Power button still works
3. screen goes blank eventually
4. Does not come back when power button is pressed, while still frozen.
5. Afrter a while screen can be reactivated
6. Notifcation bar is pulled down; disappears
7. phone is usable again.
I've tried a factory reset to no avail. After this I tried factory reset + flashing Omni Rom. Lastly I tried flashing OmniRom without gapps. I have no idea what i going wrong right now.
If this a known symptom for failing hardware, please let me know.
Kind regards
Maybe its because of their theme engine bug.. Might be solved in next snapshot..
Sent from my Galaxy Nexus using XDA Free mobile app
Yup, the new CM theme engine bug. Either you go back to M5 or use another ROM that doesn't have the new CM theme engine.
I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.
servellia said:
I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.
Click to expand...
Click to collapse
Did you do a clean install for the M4? People that updated to M6 and downgraded back to M5 without clean install still had the issues. You won't need wipe your SD card.
As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.
servellia said:
As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.
Click to expand...
Click to collapse
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?
jkleo said:
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?
Click to expand...
Click to collapse
Yep, done all of that.
What a shame, I love my gnex. Time to move on.
servellia said:
Yep, done all of that.
What a shame, I love my gnex. Time to move on.
Click to expand...
Click to collapse
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.
jkleo said:
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.
Click to expand...
Click to collapse
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SPIGEN case is payed for
servellia said:
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SIGMA case is payed for
Click to expand...
Click to collapse
Wow.. Well like they say, if the old doesn't go, the new doesn't come. Enjoy your Nexus 5 [emoji106]!
Related
Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
Okay, so I have been a flashaholic for the past couple of years and been on the AOKP nightlies for a very long time.
However, since the last month or so, every time I try to flash (clean and dirty) a new ROM or upgrade to a newer nightly, the flashing process goes on pretty smooth as expected. But, here is the thing.... after booting up fine, it starts to optimize the apps and I see it going through the entire cycle of apps. When all the apps are optimized, it says "Starting apps" and this is when I feel a vibrate and the phone reboots and does this over and over. My only way out of this is to boot it back into Recovery (TWRP 2.5) and restore my backup and sadly continue using what I had before this exercise.
I have tried various combinations of wipes, fix permissions, kernels, radios, etc. and am totally stumped here!!
Help please as it bugs me to no end when I see crazy new features the newer ROMs are dishing out and I cannot taste them
by clean what are your actual steps you mind elaborating a bit more of your steps, and with which ROM this happens on have you tried a stable as oppose to a nightly to see if it will fix your errors, as far as flashing do you ever format system in mounts and storage when you flash ROMs ???
Clean: Wipe Cache, Dalvik, Format System, Data. I haven't tried formatting the Internal SD or Preload partitions yet.
This happens with quite a few ROMs... I have tried SlimBean, CM 10.1, AOKP M2, PA so far. See the same behavior on nightlies or stables. I haven't tried Stock ROM yet... maybe should give that a try as well.
Let me know if I can give you more information to help me out.
since it seems to be happening on every ROM for you i would suggest you try going back to stock and re-root and try again, it doesn't take that long it just really sucks to do everything from scratch, but its the only way you are going to know where this problem is coming from also if you are on TWRP 6 that might be the problem everyone has been having lately it sometimes works sometimes doesn't have you tried opening ROM MANAGER and fixing permissions only from within the app...see if that squashes your bugs just trying to give some ideas ....
I would hate to go back to stock and re-root all over again. But if all else fails... I guess that remains as my only option.
I am on TWRP 2.5 for quite some time now and have successfully flashed using that numerous times before this problem started... not sure what you mean by TWRP 6 (you mean 2.6?)
I do not have ROM Manager on my phone, will give that a shot as well before resorting to the "Stock" option.
Thanks for your help!
yeah i ment 2.6 lol DOOHH!! and yeah you def sound like you know what you are doing so im sure you will figure it out just wanted to give you some ideas ... and for the record its always nice to take a break but good luck bro sorry i couldn't help you more
It was an issue with the Kernel I guess!!
Flashing SlimBean b8 + gapps followed by the UBER Kernel after wiping the hell out of everything as my last ditch effort I went past the "Starting apps" while I was feverishly holding onto the Vol UP + DN to get into recovery if it fails again.... to my surprise, it went past that screen and there was the start screen I have been looking forward to.... what drama )
I guess will follow all my flashes with the UBER kernel going forward.
awesome man!! glad you got it fixed - Like i said i knew you would figure it out good stuff man, now you got more knowledge and can help others if they run into the same issue happy flashing ! take care
Hello,
I installed today's nightly on my phone and once it would be done starting the OS, I would see the unlock page, then I assume it crashed and reboot over and over again.
I have tried installing older builds (a day old to a few days old) that used to work, still on sd card, but it crashes-reboots after the whole "optmizing apps" thing, and then gets stuck in bootloader loops.
I have wiped cache and dalvik, not yet done a factory reset as I'm hoping to find another solution if possible.
If not I'll just do that.. but hoping something else is feasible
Any idea?
Thanks!
edit: ooooh I just realized today's nightly was for 11.0, I guess no choice but a wipe then.
edit2: yup that was it, and it feels so much faster... or maybe it is because I have not bloated it yet...
/Thread
geearf said:
Hello,
I installed today's nightly on my phone and once it would be done starting the OS, I would see the unlock page, then I assume it crashed and reboot over and over again.
I have tried installing older builds (a day old to a few days old) that used to work, still on sd card, but it crashes-reboots after the whole "optmizing apps" thing, and then gets stuck in bootloader loops.
I have wiped cache and dalvik, not yet done a factory reset as I'm hoping to find another solution if possible.
If not I'll just do that.. but hoping something else is feasible
Any idea?
Thanks!
edit: ooooh I just realized today's nightly was for 11.0, I guess no choice but a wipe then.
edit2: yup that was it, and it feels so much faster... or maybe it is because I have not bloated it yet...
/Thread
Click to expand...
Click to collapse
Try a nandroid backup if you have any and then do a fresh install of the ROM?
UnknownTroll1 said:
Try a nandroid backup if you have any and then do a fresh install of the ROM?
Click to expand...
Click to collapse
Once I realized it was a 11.0 nightly, I wiped it out and it worked right away...
Thanks!
No problem
geearf said:
Once I realized it was a 11.0 nightly, I wiped it out and it worked right away...
Thanks!
Click to expand...
Click to collapse
Hit that little Thanks button eh buddy??
Have the ATT version. Over the last 2 weeks no matter what I do my phone will not hold onto a ROM. Have done restores, complete wipes and new
installs yet nothing seems to hold. Will do a complete wipe including internal, data, system, etc.. Have tried all different ROMs. From international, to I317. Have tried TW, AOSP, and MIUI. Sometimes can get through setup, but within 1/2 hour reboot into loop. Thought it might be the battery, not sure though. Any help would be greatly appreciated. Maybe Odin back to stock? Thanks for taking the time to read this.
Update
mdaigt said:
Have the ATT version. Over the last 2 weeks no matter what I do my phone will not hold onto a ROM. Have done restores, complete wipes and new
installs yet nothing seems to hold. Will do a complete wipe including internal, data, system, etc.. Have tried all different ROMs. From international, to I317. Have tried TW, AOSP, and MIUI. Sometimes can get through setup, but within 1/2 hour reboot into loop. Thought it might be the battery, not sure though. Any help would be greatly appreciated. Maybe Odin back to stock? Thanks for taking the time to read this.
Click to expand...
Click to collapse
Update. I tried Odin back to stock. Was able to update to latest firmware in between reboots. Didn't help. Still constantly reboots randomnly.
Again thanks for taking the time to read.
mdaigt said:
Update. I tried Odin back to stock. Was able to update to latest firmware in between reboots. Didn't help. Still constantly reboots randomnly.
Again thanks for taking the time to read.
Click to expand...
Click to collapse
Search this forum [General or Q&A] for "stuck power button". I recall seeing a few threads about a yr ago with constant rebooting issues.... turned out, by cleaning the power contacts it fixed issue for some folks. Good luck.
I agree with the good doctor...
The behavior of the device suggests a forced reboot via the power button...
The other prospect is not quite so simple...and involves hardware damage....but I would certainly pop the case open and clean those contacts first....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Well was lucky to solve my issue. It was the battery being bad. Have had the new battery in for a day now and no
problems what so ever. Thanks for everything. Love reading and learning from XDA:good: