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
Related
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
Ok, so I flashed JT's Vanilla gingerbread rom using CWR 4 and everything seemed fine. I then flashed B Boy Blizzard theme and everthing ran fine for about twenty mintes, then I got what I thought was the sleep of death (only when I pressed the sleep button). I pulled the battery and powered the phone back on. The phone booted into recovery and I got and error 7 cache recovery unable to mount message. I really like what little of the rom I saw and the theme. I sure at this point I'll have to Odin back to stock as I can't do a recovery either (same error message). What I'd like to know is this just a problem I'm having or is there something wrong with the rom or theme? Please advise. Thx in advance.
I have had alot of problems with that rom aswell...not really sure whats going on. Sometimes the rom will install with cwm 4 other times it just boot loops. I have tried every install method for that rom and nothing yet seems reliable. I have no problems flashing other roms, so idk... just chillin with powerwash right now until the bugs get worked out w/ VGB(hopefully).
All of his themes (at this moment) are based on 080211 v2 VGB. And between v2 and v3 there were framework and other apk changes i.e. settings. So flashing that theme on top of v3 will surely lead to issues. Just reflash rom. And make sure the theme you try only says for v3.
good day.
Also, you wont boot into the right recovery using the 3 finger method. you need to use adb or the reboot options
Ive just installed Clockwork Mod v4 and Cyanogenmod (latest) and i am stuck on a screen loop with repeatively shows the Cyanogen loop with the blue droid on the skateboard with a circle around him- it keeps repeating the full cycle over and over again, i have taken the battery out but nothing, help?
Try re-flashing the rom, see if it changes
Yeah i managed to fix it thanks to another guy on these forums- reflashing Clockwork did the trick.
Had exactly the same problem with my G5, Flashed one. Fine. Flashed the 2nd one and it boot looped, flashed a different firmware and the same thing happened, weird! Closed/repoened odin Disabled auto reboot and flashed CM7 and it was fine
i experienced this too when I first tried flashing cm7.1, plus the I5503DXJP7 baseband, after using the MAD rom for a good 4 months or so. I reflashed the stock 5503 rom, then upgraded the baseband and again experienced the boot loop.
i found a 5503 rom on samfirmware that came with the I5503DXJP7 baseband i needed. that one booted up fine. then i flashed cm7.1. that worked fine too. so this turned out to be a problem with the baseband (i think).
but cm7.1 came with this crazy loud headset volume and i use the g5 a lot for calling at work. had to go back to MAD2.0.9, this time flashed using CWM (very cool: thanks to whoever got that onto the G5)
I fixed this problem a while back aha, thanks for the replies though
Currently awaiting for my phone to be repaired -.-
I had the same problem...I repeated the steps and obivliously it worked
I used the CM7 for a while. I reflashed the stock ROM and the bootloop started. Than i freaked out and reflashed all by odin. It works.
Sent from my GT-I5500 using Tapatalk
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
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