I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium
Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
I have been running MIUI on an x2 for a few days and I went to use my Camcorder and it crashes. I tried several different ones and it just keeps failing. It starts to record and then does a FC. I downloaded different cameras and they do the same thing. I even tried some different once through downloading the Apks from this device and from the Atrix.
Does anyone have any ideas?
Probably a silly question but did u manually do a reboot, or go into applications and clear the catch and data. Also when you installed the miui did u do the three wipes first?
Sent from my DROID X2 using XDA
Lol good question. I have done these. I can try to reflash it?
Sent from my Milestone X2 using XDA
Lol, sorry if that was obvious but I know I usually over look the easy stuff. I have only ever had these problems when I didn't wipe the data and catch after I flashed
Sent from my DROID X2 using XDA
I am going to try to do that. Thank you for trying though.
No prob hope u get it
Sent from my DROID X2 using XDA
From what I have been able to read its something to do with permission settings for the camcorder. If I can just get help how to change this to the proper settings that would be great!!
This is a bug that has been with the rom since the beginning.
I hope you find a workaround.
If you follow Aceoyame on twitter you can see his progress on the next release based on Dragonkillerz work on cm9. Some are saying this summer, just in time to take some video
Sent from my DROID X2 using XDA
lol, Yeah from what I have been reading I think its about the permissions. But I am trying to figure out exactly what file.
I wanted to give an update. Talked with Ace and he said there will be an update out to fix this sometime in the next week. Great news!
Sent from my Milestone X2 using XDA
That is great news. Good on ya mate.
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
joshahouck said:
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
Click to expand...
Click to collapse
Nand backup your miui and let Ace know of your discovery! He's trying to find a correction
Sent from MB870 W/ Cm7.2 Rc1
SUCESS I THINK YES...
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?