I was running CM7 7.02 from emmc with Dalingrin's 4/24/11 OC kernel, and was very happy with it. However, I got distracted by shiney... Rom manager gave me a pop up saying 7.03 was available, which it hadn't done in the past, so I figured, why not give it a shot?
I ran a full backup, installed the update, booted... and all my apps were gone. It was a fresh install instead of an install over my existing 7.02 like I would have gotten if I just booted from my CWM boot SD card and flashed. Well, crappy, but I have my backup, right? Still, might as well try the OC kernel and see how it runs real quick... oh, won't boot after the OC kernel. huh.
So I boot to recovery, and clear cache, and restore my backup.
Everything looks perfect. Back to my customized layouts... wait, where is my Honeycomb style bottom status bar? I'm back to the default look/feel. Ok, I can fix that... wait, why isn't my N button working? I've gone into ADW settings, selected several options for the "home button" functionality, rebooted, nothing works. I've got everything except a working N button. Why?
The only time it has worked is ONCE right after I installed a second home launcher, flashed 7.02 over 7.02, rebooted, and hit the button. It popped up and asked me which of the two launchers I wanted as default. After that, it hasn't responded.
Anyone have any idea what I did or what I can do to fix this? I'm fine if I have to format and start from scratch, I just would rather not since I'm stuck in an airport and waiting on a flight home, so I'd rather be reading/watching movies/playing music instead of tinkering... if it's something simple to fix, ya know?
That post just made me mental!
Sent from my Nexus S using XDA Premium App
I'm glad I could provide some amusement?
I ended up wiping data and system, installing 7.02, gapps, and 4/24/11, clearing cache and dalvik, then booting up and then refreshed my apps and data from Titanium. Everything worked great for a while and then the N button stopped again. No idea what happened. I've been working 16+ hour days for 7 days straight and can't think straight. On the up side, I was able to finish watching my movie on the flight home after my flight was delayed for 4 hours.
I need sleep. I also need to figure out why my button keeps dying. Works perfectly in CWM and to wake the device up, just not for it's intended purpose.
Had a similar problem with the N button not working with the 04/24 kernel. However it got working after a reboot...
One thing you could try is to use the 04/04 kernel instead. Might be a OC related issue.
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
Hey guys. I have a very interesting situation happening with a VZW Galaxy Tab 7.1 that I bought from someone (I own a business buying/selling/trading cellphones and tablets)..
As soon as you boot it up, every app starts to force close!
If you sit there long enough and accept them all, you can actually use it a little bit. Apps keep FCing as you play with it, though.
The only noticeable thing is that the wallpaper always stays the same. It was 2.3.4 (I believe) when I got it, but I've tried flashing stock ROMs and the Galaxy Cubed 3 ROM through Heimdall, but that wallpaper ALWAYS stays there!
I just flashed the Galaxy Cubed 3 ROM on there 20mins ago, and everything switched over (the look, the battery icon, notification bar, window animations) EXCEPT that wallpaper (which ironically is of B.I.G.) and the FC issues.
I read somewhere about JTAG or something, but it boots fine, just having software issues.
PLEASE, if anyone knows anything about this issue, I need to sell this thing so I can make some money =) Thanks in advance for the help!
im in the exact same boat with a customers tablet. ive tried everything. takes forever to boot and factory reset does nothing. 4 installed apps never uninstall either.
Do you have custom recovery installed? After flashing with Heimdall, enter custom recovery and wipe data and cache. Reboot. No more issues.
I can't find a way to get custom recovery to flash. I've tried every walkthrough. There's no explanation as to why factory reset/wipe doesn't work
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Sorry to hear, sometimes starting over cures 90% of all issues, and the os gets better each time.. If it were me, I would quit wasting time and odin.
Thanks, and good luck.
Don't Forget -
jedimyndtryx said:
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Click to expand...
Click to collapse
Don't forget to immediately freeze the ATT update apps... Or you will get the MF3 OTA... which, for now, is NOT-ROOTABLE & Custom Recoveries NOT-Installable.
I always factory reset,wipe both cache and format system.even when I use a back up.
Sent from my SAMSUNG-SGH-I337 using xda premium
Well I ODIN'ed and went back to CleanROM. So simple. I'm dying to try one of the VZW AOSP themed TW ROMs though. Decisions, decisions. Oh man....when I first got the phone it was on MF3. I spent 3 days on craigslist and found someone to trade me their non-updated phone. Still new to this Android business. So far I love it. Don't see why I spent so many years hating. Thank you all for the help.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks