I am currently running EvoKings GB RC3 and loving it. But since I can't leave well enough alone, I want to update to the RC4.
I just have a couple of questions concerning this ROM.... I see where he mentions its based on CM7... is it based on CM7 7.0.0.0 or CM 7 7.0.2.1?
Also will I need to do the GPS fix again and update PRL, as I assume I have to wipe dalvik/cache to update from RC3 to RC4 (as it seems its more than just an update)?
Speaking of the GPS fix, when I did it, I was on RC3 of the EvoKings GB rom, and this is the steps I followed:
Booted into recovery
Made a Nandroid backup
Wiped All Data
Flashed into a backup sense rom I have (Mikfroyo 4.6)
Performed GPS fix and updated PRL
Booted back into recovery
Performed Nandroid restore (no data wipe)
Back into RC3
Was that correct... that I dont do a data wipe and just do a nandroid restore? I have been reading so many conflicting reports on this. My assumtion was to always wipe data before doing a restore.
Thanks everyone.
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
dougjamal said:
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Ok cool, thanks. When doing the GPS fix, is the info stored somewhere else, which is why it doesnt get removed when doing a wipe of stuff?
Trying to figure that out... since yeah I am worried about having some type of conflict when switching from a sense to an AOSP rom. I havent had any issues so far with RC3 doing that, minus some issues with the screen not coming on with a button press while playing music.. but not sure if thats just something with the ROM itself or the GPS fix.
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
whiterider13 said:
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
+1.....I've never had to apply a GPS fix and I, too, have switched between AOSP and Sense numerous times. As a matter of fact, my current rom is Salvage-Mod and the GPS works as it should and I still didn't have to apply a fix.
posting & replying via the XDA Premium app.
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
whiterider13 said:
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
Thank you both, thats what I wanted to hear. I havent wanted to switch roms because I got the GPS working and I didnt want to switch roms and have it broke again. Thank you!
No prob man, just glad I could help.
Sent from my b3 Infected Evo using Tapatalk Pro!
What build of CM 7 is this rom built off of?
Related
ok new guy here..well not that new i used the how to that toast made then did the various AmonRA-sp updates all the way up to fresh 3.0
heres the problem (so far):
1.market opens then immediately closes, though this isnt a force close...?idk?
2. my contacts are there but they arent: people isnt working it force closes on me and i i cant recover any phone numbers through google or my sdcard backup.
well those are my problems, again im running the latest Fresh rom used Amon RA and did the apps2sd(the right way)
im really at a loss here fellas, i dont know what to do but im not gonna do anything until i can get some insight into this debacle.
thanks in advance
easy answer.... do it all again
or
dont use fresh
use Evio 1.1 or 1.2
i have tried most of the popular roms and this is by far the best, including the best battery life, stability, compatability, etc.
screw the havs and crap.. i tried those and got the worst battery life EVER from those. 6 hours tops... Evio i can go 2-3 times that, true... i get far farrr better battery life out of a pseudo stock rom than i do all the custom "stuff"
just flash with another rom... fresh is unique in itself and doesnt always play nice with certain other add-on's (from what i have read)
that is why in other threads you see custom builds for people using "fresh roms"
why mess with something that is so unique it requires its own builds for certain things.
so do i have to do apps2sd again
Just wipe your cache and davlick cache
have you tried wiping your cache & dalvik-cache and flashing gapps?
no not yet....gapps? where can i find that...forgive me i dont use forums ever lol
okay tried wiping both caches....same results.
how do i flash gapps? i searched the forums and all i get is the Fresh 3.xxx thread titled GApps and no source on the file itself.
OP of CM6. Just flash from recovery. You shouldn't need to wipe anything. But if you're gonna, just cache and dalvik.
Sent from my FROYO'D EVO using xda app
dglowe343 said:
OP of CM6. Just flash from recovery. You shouldn't need to wipe anything. But if you're gonna, just cache and dalvik.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
flash teh rom? ok then will do!
No, there's a separate download for gapps. Sorry, I could've been more specific.
Sent from my FROYO'D EVO using xda app
dglowe343 said:
No, there's a separate download for gapps. Sorry, I could've been more specific.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
okay that was what i was searching for...where is that download link located? searcdh function seems to not be helpful
It's in the CM6 OP just below the rom download link. Should say something like gapps8172010.
Sent from my FROYO'D EVO using xda app
nope didi all three and still no market and com.w/e.people still force closes.
i dont have time for this so im flashing back to 1.0.1
thanks for the effort
I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.
Edit:
In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.
If you choose to format the SD card, be sure to back up your important files first.
If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
sjpritch25 said:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
Click to expand...
Click to collapse
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Edit: if you experienced this it may help to figure it out
JAS_21 said:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Click to expand...
Click to collapse
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I've seen more than one user with the issue. One is a long time forum member.
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from
I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.
I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.
I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.
I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.
All sense ROMS work.
I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.
I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.
Sorry for all the info. I just tried to give as much detail as possible.
Hope this helps,
Matt
Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.
Also, if anyone has a fix it can be posted here.
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
dch921 said:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
Click to expand...
Click to collapse
Were you running a sense ROM before Miui?
I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.
Sent from my mobile typewriter.
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
ftmaniac948 said:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
stelv said:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
Click to expand...
Click to collapse
No, you should be fine.
Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also
JAS_21 said:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Click to expand...
Click to collapse
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me
ftmaniac948 said:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.
Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.
Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.
I've got an evo 4g, I've been rooted for about a year. i flashed cm7.1 and it was running for about 3 months and last week wifi and 4g just stopped working. i used rsa checker to check my keys and they're still there. i think the problem is my ip address. its unavailable on wifi and 4g. i dont really know where to look. can someone point me in the right direction?
Did you just flash a new kernel?
Try flashing Tiamat... see what happens.
i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?
biggda said:
i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?
Click to expand...
Click to collapse
Just flash Tiamat and see what happens. This is almost definitely kernel related. Make sure you wipe dalvik cache and cache (preferably with Amon RA or TWRP recoveries).
I love you man, I'm talking serious bromance! Can you explain why that worked? Did my old kernel go bad? Thank u so much!
Sent from my PC36100 using XDA App
it broke again, I flashed again. It didn't come back.
Sent from my PC36100 using XDA App
Try a different version of CM7. You can also try an entirely different rom for troubleshooting purposes. Generally 4G & wifi issues stem from the kernel. Are you flashing any mods or running anything that makes system changes, like V6 Supercharger? If you're using V6, undo the kernel tweaks.
Best bet is to flash a different version of CM7, even if you have to downgrade. Do a full wipe - data, cache, dalvik, system, boot, SD-ext, .android_secure - and flash only the rom and gapps. Try 4G & wifi before restoring anything. If they work, you can then restore anything you've backed up with TB, just try to avoid restoring system apps/data. If the problem comes back then it may be something in one of your apps or the data you've restored... though unlikely.
If this doesn't work, do a full wipe again and flash a fully stock rooted rom. Update your radios etc with the combo zip. If that fails, RUU.
There are plenty of options, but I don't think you'll have to go as far as running an RUU. Start from the top and work your way down.
Supersonic Evo 4G | MIUI | Tapatalk
I went to 7.1 rc then I reflashed 7.1 without gtalk . Works fine now. Thanks.
Sent from my PC36100 using XDA App
the only thing I could see that broke it was font installer app or google talk. Its fine now. Ill keep u updated. Thanks
Sent from my PC36100 using XDA App
Hey guys, I was looking through the xda threads on the inc2, and I saw that the user truelefty has posted a few cm7 builds that are updated to 7.2
I want to update to this version, (here) but how do I get to that point?
Can i just flash the cm7, gapps, and kernel right over my current setup w/o wiping cache/date/dalvik cache?
If i need to wipe my data, how can I back it up before I flash? (apps+app data)
And what does the kernel do/mean?
(sorry. noobs have to learn at some point)
yoseir2 said:
Hey guys, I was looking through the xda threads on the inc2, and I saw that the user truelefty has posted a few cm7 builds that are updated to 7.2
I want to update to this version, (here) but how do I get to that point?
Can i just flash the cm7, gapps, and kernel right over my current setup w/o wiping cache/date/dalvik cache?
If i need to wipe my data, how can I back it up before I flash? (apps+app data)
And what does the kernel do/mean?
(sorry. noobs have to learn at some point)
Click to expand...
Click to collapse
Well, a full wipe is almost always recommended, but you can back up your apps easily using an app like titanium backup or mybackup root. You should be able to just flash the new build with new gapps, and aero's .8 cfs or bfs kernel with only wiping caches, but if you experience problems at all, jusy wipe data (if you want all your apps back, make sure you do a backup of all your apps [not system info at all, as this will screw you over] before you flash the new cm7) and reboot, re set up your stuff (restore your apps, and such) and you should be set.
Sent from my Mikrunny'd Superphone using my Ice Cream Sammich flavored Tapatalk
yoseir2 said:
Hey guys, I was looking through the xda threads on the inc2, and I saw that the user truelefty has posted a few cm7 builds that are updated to 7.2
I want to update to this version, (here) but how do I get to that point?
Can i just flash the cm7, gapps, and kernel right over my current setup w/o wiping cache/date/dalvik cache?
If i need to wipe my data, how can I back it up before I flash? (apps+app data)
And what does the kernel do/mean?
(sorry. noobs have to learn at some point)
Click to expand...
Click to collapse
I would download titanium backup to backup your Alps and data. Not all data files will restore OK though. I personally don't reccommend just flashing without wiping. Most of the times you will get errors and then blame the software because it couldve been easily avoided but lazyness set it. Go to CWM and do a backup of your current rom just incase something gets messed up then wipe all your data and just flash the cm on his post with the gapps and you should be just fine.
Now someone may correct me on this next part, but my understanding of the kernel is essentially its the drivers for Linux or your phone in this case. It also governs how your phone will run as far as clock speed and some other items as well. I've always thought if it as the instructions for the brain (CPU)
Sent from my Incredible 2 using xda premium
tylerlawhon said:
Well, a full wipe is almost always recommended, but you can back up your apps easily using an app like titanium backup or mybackup root. You should be able to just flash the new build with new gapps, and aero's .8 cfs or bfs kernel with only wiping caches, but if you experience problems at all, jusy wipe data (if you want all your apps back, make sure you do a backup of all your apps [not system info at all, as this will screw you over] before you flash the new cm7) and reboot, re set up your stuff (restore your apps, and such) and you should be set.
Sent from my Mikrunny'd Superphone using my Ice Cream Sammich flavored Tapatalk
Click to expand...
Click to collapse
Damn you for beating me! LOL I'm using miui right now and haven't changed my keyboard from the original stock one.. hate this keyboard
Sent from my Incredible 2 using xda premium
faehsemc said:
Damn you for beating me! LOL I'm using miui right now and haven't changed my keyboard from the original stock one.. hate this keyboard
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I'm just a forum stalker. Lol
Sent from my Mikrunny'd Superphone
Same here.. been on leave for 2 weeks with a newborn... can't sleep so I'm constantly on here... that'll slowdown as of Thursday. First day back
Sent from my Incredible 2 using xda premium
just a follow up questions, whats the difference between the BFS and CFS kernels?
yoseir2 said:
just a follow up questions, whats the difference between the BFS and CFS kernels?
Click to expand...
Click to collapse
Google my friend. Google. I cannot tell you, but the great master google can hahaha.
Sent from my Mikrunny'd Superphone
I've got my evo rooted, or at least I'm pretty sure I do.
It's currently on 2.3.3, with an H-boot version of 6.16.1002, the software version is 4.24.651.1, and CWM revolutionary 4.0.1.4.
I'm looking to flash a new rom that is very well functioning. I'm just wondering if I've got everything done right so far, and if there is an official version of Cyanogen out (I'm leery about nightlies), and how well it works. The only other rom I've seen that I'm really interested in is this
So have I got everything rooted properly, before I flash are there any thing I need to avoid, and precautions I need to take?
flim flamin said:
I've got my evo rooted, or at least I'm pretty sure I do.
It's currently on 2.3.3, with an H-boot version of 6.16.1002, and CWM revolutionary 4.0.1.4.
I'm looking to flash a new rom that is very well functioning. I'm just wondering if I've got everything done right so far, and if there is an official version of Cyanogen out (I'm leery about nightlies), and how well it works. The only other rom I've seen that I'm really interested in is this
So have I got everything rooted properly, before I flash are there any thing I need to avoid, and precautions I need to take?
Click to expand...
Click to collapse
Cyanogenmod has stable releases at http://download.cyanogenmod.com/?device=supersonic&type=RC
I would always do a backup in recovery just in case...other than that you should be good to go.
Thanks, I found the latest stable release.
I've done my fair share of flashing on my Droid X, but just to make sure I don't wake up to bootloops for breakfast, what are the recommended install instructions for CM?
Also, does CM include a custom kernel, and do you recommend the latest stable, or the latest RC?
Wipe data 3x
Wipe cache 3x
Wipe dalvik 3x
Flash CM
Flash gapps?
(I don't remember if you need to flash gapps with CM)
Not sure if doing each 3x is really needed but that is how I was taught and have never had issues thus far, unless it was a specific rom related issue.
As for kernel since CM is AOSP, I would say it is custom since you can not use a sense kernel on an AOSP rom.
Hope this helps!
Sent from my PC36100 using xda premium
Klown80 said:
Wipe data 3x
Wipe cache 3x
Wipe dalvik 3x
Flash CM
Not sure if doing each 3x is really needed but that is how I was taught and have never had issues thus far, unless it was a specific rom related issue.
As for kernel since CM is AOSP, I would say it is custom since you can not use a sense kernel on an AOSP rom.
Hope this helps!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I don't need to wipe the system?
flim flamin said:
I don't need to wipe the system?
Click to expand...
Click to collapse
If you are on stock sense...factory reset
So don't wipe the system, but wipe the data. (factory reset)
Does anyone know if I need gapps, and which one I'd need?
Also, should I use the latest RC, or the latest stable?
flim flamin said:
So don't wipe the system, but wipe the data. (factory reset)
Does anyone know if I need gapps, and which one I'd need?
Also, should I use the latest RC, or the latest stable?
Click to expand...
Click to collapse
I haven't used gingerbread in a while so I am not sure how the latest RC is...gapps link is here https://www.dropbox.com/sh/136ywplkpwiya5r/Skn6qoszOt/CM7/gapps-20110828-vm.zip this includes sprint vvm...let me know if you are using anything else
klharalson said:
I haven't used gingerbread in a while so I am not sure how the latest RC is...gapps link is here https://www.dropbox.com/sh/136ywplkpwiya5r/Skn6qoszOt/CM7/gapps-20110828-vm.zip this includes sprint vvm...let me know if you are using anything else
Click to expand...
Click to collapse
I think I'll start out trying the latest RC.
If that doesn't work out for you, or you just wanna be a whore and flash something else, give Vaelpak GB AOSP a run. I love it
Sent from my Vaelpak Powered OG EVO
burghfan3 said:
If that doesn't work out for you, or you just wanna be a whore and flash something else, give Vaelpak GB AOSP a run. I love it
Sent from my Vaelpak Powered OG EVO
Click to expand...
Click to collapse
I've run into a very odd roadblock...
TiBu keeps freezing before i can even do anything. I've tried reinstalling, using an older version, and fixing permissions, and its still happening the moment I touch the screen.
This isn't too big of a problem as long as I can restore all my apps (including the numerous ones on the sd card) through my CWR backup... is this possible?
I think a lot of my issues I've been having are because I took an OTA update after rooting...
Ummm, yea. The 2 do not mix. Either keep it rooted and no OTAs, or keep it stock with OTA updates (if you choose them).
Sent from my NookColor using Tapatalk 2