I can't boot cm10 (unofficial) or Evervolv's JB preview ROMs. They both sit at boot screen. Also, Sometime mid July cm9 (unofficial) changed something that breaks my data somehow. Stock browser begins to load but stops and closes. Same with FB app. Any nightly (cm9) I use prior works fine and last Evervolv ICS release works great as well.
Is my Evo outdated? I've heard of some Evo's not handling some ROMs for whatever reason but I haven't heard of anybody having my problems with these new ROMs. I use Smelkus ver RA recovery and I have my SD partitioned, though I rarely use sd-ext. I'm always through on wiping and my hardware is 003 if that helps.
I have a pretty old EVO as well, and haven't had any issues getting any jb up and running. Have you tried redownloading? The most recent one I tried was here http://forum.xda-developers.com/showthread.php?t=1805348 and I liked it, just no camera so I had to go back to an ICS.
If you do a full wipe there shouldn't be any reason why ur not able to run those roms.
Thanks for the input. I flashed the ROM above (With evervolv jb gapps) and decided to wipe everything individually. I'm running JB now! Only thing I did differently was not use combo wipes and try this ROM. I wonder if that's it. Will try other ROMs now.
Just for an update I downloaded new Evervolv JB preview 5 and it booted so not sure what's going on. Unofficial CM10 still won't boot so maybe it is a download issue but I've tried multiple ways (3g and landline). Team Dirt CM10 booted though. I'm scratching my head.....
So basically I am just here to answer your question concerning if your HTC EVO is too old? Why, yes, yes it is, actually, any phone that comes out is usually obsolete within one to two months after debute.
I have booted cm10 to my evo with no problem. I have encountered a few issues with cm10 but that was expected. Can't wait for the camera to work. Only major setback.
Sent from my PC36100 using xda app-developers app
Related
I justest loaded CM 6.1.2 on my HTC evo and now every time i try to use my camera it freezes and has to force close. Any idea's? I'm new at this whole phone moding thing, so if I left out any important info just tell me. I had someone who is more experienced help me root my phone and load the rom so I don't think I messed up anything there.
Hmmm...that's strange.....I had the CM on my phone, and didn't experience any camera issues. Are you using a custom kernel?
Have you tried clearing the data and cache from the camera and then opening the camera back up? (Settings/Applications/Manage Apps/Camera) This has helped others on certain roms. Not sure on CM though.
Also, agreed with the kernel thing from filmaker. Sometimes that will do it. Try a different one.
Good luck!
I'll try that, thanks. I loaded a different rom on my phone and I'm having some problems with it, I'll reload cm and try what you told me. As to the custom kernel question, I dont believe I do. I also read on the cm forum about CM6.1.2 having issues with the camera pm newer evos and they talked about a fix but I couldn't seem to find it.
Having sorta the same problem... I switched to CM6 and the camera is just buggie... It either wont take a picture, lags really bad or FC's... I've tried clearing the data out of it but that seems to have made it worse.... Any other idea people? Thanks
Oh, I'm runnin CM6 with a stock kernel... maybe try a different kernel? And if so, can I just flash a kernel without changin anything elese like radios and what not?
Well I reinstalled cm and the camera worked prefect for a while but its not working now. I tried what you said and it didn't work. I have the stock kernal as well.
Sent from my PC36100 using XDA App
hhhmm... that's prolly gonna be a deal breaker for me if I can't get it fixed... I use my phone camera quite a bit
Did you wipe data, cache, and dalvik between ROMs? How about system?
Well I know I wiped data, cache and dalvik... and I think I wiped system (If that's an option in to do from recovery then yeah I did)..
What recovery are you using and what rev? When I first tried CM6.1.2 I was using RomManger, which was using ClockWork 3.x.x.x recovery. I couldn't get CM6 to run for more than a day without having issues. I was able to switch to Amon_RA 2.2.1 and flash a few other ROMs which ran fine for days without any issues. I have since loaded up the EvoNonsense 4.3.1 ROM, which feels a lot like Cyanogen but still has Sense, so everything works (4G, HDMI, Camera/Camcorder, etc...). Anywho, not sure if using Amon_RA recovery will fix your Cyanogen issues or not but it may be worth a try. If that doesn't work out then you may want to try the EvoNonsense ROM.
http://forum.xda-developers.com/showthread.php?t=758197
So im a long time lurker back all the way to the OG Incredible and never experienced a problem like this before. My problem first started with Cyanogen Nightly 71 I had been using it as my daily for a few days when the lockscreen started to no longer function.
The softkeys light up but the display is off and doesn't come back on. I figured restoring would fix the issue but ended with the same result. I've tried restoring older nighties, factory reset, clearing caches, fixing permissions, and installing other ASOP roms like liquid and the CM7.1 "Stable" but as soon as the phone locks it no longer wakes up. Currently i was able to restore to Newts Incredible HD but i cant live without ASOP if you have any ideas on what has happened or how to fix this please help out and thanks in advance.
I had the same issue and for me I switched to 4ext recovery, converted system to ext4 and aosp has worked since
Sent from my Incredible 2 using XDA App
CM 7.1.0.1
A new upload over in the dev section.
CM 7.1.0.1
Compass still an issue, but now there is a direction to post Issues...
Enjoy...
Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.
As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.
of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.
flashed to 7.2 RC2;
please lock.
vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.
**** Note, this thread is not pointing fingers at ROM Devs *****
So starting back when porting of ICS from skyrocket was done I never had any random reboots or crashes fast forward to about 2 weeks ago when sudden and many freezes, lock ups and random reboots started. I first started seeing it on darkside v3 and it continued to darkside v6 during which time I decided to bounce to AOKP which gave me the same results.
Things I have tested are:
[1] Different ROMs (all based on 4.0.3)
[2] 3 different SDCards, all brand new
[3] Running different radios
[4] No apps installed, basic default setup after ROM flashed with and without add-on launchers. Tested using TW, Nova and Apex.
[5] Formatted sdcard and internal storage
[6] New battery - pending results, ordered 2 days ago will be here Wednesday
[7] New bluetooth - pending results, ordered 2 days ago will be here Tuesday (Not sure if it would help but it was a good excuse to tell the wife)
[8] Flashed multiple times using CWM (non-touch) and TWRP
Anytime a ROM is flashed I always superwipe and on a few occasions I have manually select clear/format section via CWM. My flashing steps are perfect and followed to a T per AOKP and Darkside. Ive always flashed 100% battery charge and anytime I try to logcat I'm unable to get a log due to the random reboot because it won't save the log.
Once the new battery gets here and that doesn't work I'm completely lost with what else I can try. Does anyone who has experience and knows the file system of 4.0.3 > 4.0.4 know if something has been changed that may help or does anyone have any other method for me to find the issue at hand? Also keep in mind running darkside GB based on 2.3.6 is stable as hell.
Your assistance is much appreciated.
I had freezes and reboot when I went from 4.0.3 to 4.0.4
then I just started from fresh. I Odin 'd to stock, and I started fresh with apparently and data. Didn't use titanium backup.. have not had a freeze or reboot since. I really think most users issues are because they are restoring old data.
Edit. After re-reading your thread I see that you never flashed a 4.0.4 rom. I really don't know why u are having issues.. your method of flashing looks really sound
Sent from my SGH-T989 using xda premium
Oh to add to that I have never restored apps with data or apps. I always go to the play store and reinstall fresh.
How old is your phone? I've only had mine since Mar and I've flashed plenty, restored apps with data, and no reboots or freezes.
Sent from AOKP Goodness :-D
LoopDoGG79 said:
How old is your phone? I've only had mine since Mar and I've flashed plenty, restored apps with data, and no reboots or freezes.
Sent from AOKP Goodness :-D
Click to expand...
Click to collapse
Maybe 4-5 months old.
well if you wiped all that and you still getting random lags and you re flashed your CWM
just make sure you download count hasnt moved you know when your in download mode
cause it might be hardware and try
darkside v7
and AOKP B40
if its not the software then its the hardware
you could always try odin and start fresh that always seems to work on mine
Odin or cwm 5.0.2.7
Sent from my SGH-T989 using xda premium
Cookiem0sta said:
you could always try odin and start fresh that always seems to work on mine
Click to expand...
Click to collapse
I odin and started fresh and ran ICS stock for 3 days with no crashes or issues. I then rooted and flashed new ICS Rom and have not had any issues for the past 48 hours. Everything doing great. Something must have been stuck between all the upgrade/flashes that were causing the crashes.
Eugene fixed the reboots on AOKP, as far as AOKP, it was ROM related.
http://forum.xda-developers.com/showthread.php?p=28087997
Sent from AOKP Goodness :-D
LoopDoGG79 said:
Eugene fixed the reboots on AOKP, as far as AOKP, it was ROM related.
http://forum.xda-developers.com/showthread.php?p=28087997
Sent from AOKP Goodness :-D
Click to expand...
Click to collapse
Yeah I read that earlier on twitter and although there was reboot issues my phone was just tripping. After odin to stock and starting fresh I have no issues with darkside however I might grab the latest AOKP with Eugene kernel. I hear good things.
ScreamingSkulls said:
Yeah I read that earlier on twitter and although there was reboot issues my phone was just tripping. After odin to stock and starting fresh I have no issues with darkside however I might grab the latest AOKP with Eugene kernel. I hear good things.
Click to expand...
Click to collapse
The battery life is awesome, though probably not as good as Darkside.
Just be sure to flash the one from the link I provided. That one has the fixed kernel and ROM
Sent from AOKP Goodness :-D
My stock phone was just fine and then.. Crashing, freezing, random rebooting, call echo, missed calls and missed text. My phone was possessed by some android demon after upgrading to 4.0 from Samsung via Kies. A google search took me to XDA. I'm a noob and all but I read every post and I watched all your YouTube videos (thank you ScreamingSkulls, that helped a lot). TDJ posted the DARKSIDE v4 rom while i was reading his thread so I flashed my first custom rom. No major problems, the camera froze when I first opened it but I killed it and it worked fine after that (I later read that others had that happen too). I flashed the v5 rom then v7.. I did have an issue when I flashed the VENOM 03 #3 kernel. After I flashed it stuck for a long time on the S logo (animating). I got it to reboot successfully so I flashed it again just be sure and it worked. I also flashed the VENOM 03 #5 kernel yesterday and everything is running smooth.
My phone was running for about 52 hours before my doubletwist app started changing songs by itself and freezing lol, this isn't the first time it's happened, I've even done a clean install from odin, funny thing is, with GB could run my phone for almost 5 days or more straight if I let it with no issues, but ICS seems a bit more laggy, I think I'll wait for the dev's to whip up some extra mean stuff until there is an official repair for it.
Nice thread. Id been reading about that reboots. I can tell you im on jaminson' s rom and no problem here about that or apps fcs. Smooth and stable. Is nice to read that you fix it
Vibrant- Kankwich Kang CM9
Galaxy S2 T989 - An amazing machine on any rom.
Only issue I get sometimes is when I'm trying to text someone and the keyboard doesn't pop up
Sent from my SGH-T989 using Tapatalk 2
I had hellish problems with ics, echo randomly in speaker, headset, even bluetooth, on wifi and not. App crashes, camera hosing, reboots, major scroll lag, touch lag, i ended going back to ginger a few times.
What i found out is to NOT RESTORE OR TOUCH ANYTHING! I have always run tdj's roms since he started putting them out but used titanium back to restore nonsystem apps, used rom tool box to tweak a few minor things.
I am running darkside evolution with v5 of ds kernel, i did not restore anything with tb didnt tweak any thing os just settings wise. Only loaded bare min apps i need. I do highly recommend nova launcher, its nice and fast and better on battery.
Just loading the ROM fresh and nova only issues are a few echo calls but very minimal. Performance and battery life are insane, I'm currently 15hr at 65% battery on light to moderate use, incredible. Otherwise runs perfectly great. Probably apps are just not totally ics compatible not sure.
Sent from the Darkside
constantly crashes... aokp. reboots not yey
Sent from my SGH-T989
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS