hi...
after i went for a swim with my defy, i had to give it for service and i believed they have replaced some thing in my phone, probably the touch screen which is still showing bit or non responsiveness here and there.
now almost all my apps are crashing/foreclosing... cant play a game or normal apps too... all are foreclosing and recently i have noticed a serious lag in all functions... i tied cm10, wiui, etc... and now back on stock... still same issue...
can anyone suggest anything???
could it be something about the kernel??? but that also should've been rectified once i flashed a fixed stock sbf for 2.2 version.
firmware - 2.2
baseband - epu93_u_00.59.02
kernel - 2.6.32.9-g0671d13
build - jem_3.4.3-36-1
Have you done a Fullwhipe between the Rom Changes?? Have you already flashed another Full Froyo SBF?
Steveletack said:
Have you done a Fullwhipe between the Rom Changes?? Have you already flashed another Full Froyo SBF?
Click to expand...
Click to collapse
i always do a full wipe between ROM...
1. factory reset > cache wipe > dalvik wipe > install zip > wipe cache > wipe battery info...
this is how i normally do between roms...
i have flashed only one full froyo sbf, which is http://forum.xda-developers.com/showthread.php?t=1093352
can anyone help???
Please ask all questions in the Q&A section. Thread moved there.
can anyone help me rectify this issue... now not just my apps are foreclosing, phone is rebooting..!
what can be done??? should i flash another kernel or sbf???
anyone faced similar issues before???
Related
Hi all,
This is probably a pretty basic question for you, so please bear with me, and if it is basic, hopefully there is a straightforward answer .
Having settled on the awesome CM-6.1.0-RC1, I haven't looked to change ROM.
However, with CM-7.0.0-RC1 being released, its time to upgrade .
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
I appreciate there is a lot of info in ali ba's dev thread [ [ROM] CyanogenMod experimental builds] however, there is approx 235 pages there, and the OP is a little lite.
Would it be possible to have guide here, as I presume many people will be wanting to follow the same upgrade path.
I am wondering how we can 'save' apps, [i.e. Angry Birds status, web browser installation, general settings/config,] during the upgrade... because I am guessing a full wipe is required and therefore a Nandroid backup won't really help...or will it?
Anyone that can help?
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
c_man said:
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
Click to expand...
Click to collapse
First question should be:
Do we need to wipe when upgrading from CM6.1?
If we need wipe, I suggest you to:
- do a nandroid backup
- backup all apps with titanium backup
- wipe + flash 7.0 RC1
- download and install gapps
- restore apps with titanium backup
If no wipe required:
- do a nandroid backup
- flash 7.0 RC1
Question: does UOT kitchen (for circle mod battery) works with 7.0?
gilliu00_ said:
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/15838-cyanogenmod-7-for-legend-v700-rc1-2152011/
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full ourput.
Please use Pastebin when possible
Skardy said:
First question should be:
Do we need to wipe when upgrading from CM6.1?
Click to expand...
Click to collapse
Yep, true.
Anyone?
Upgrading from earlier version of CyanogenMod 7?
* Perform a NANDroid backup of your current ROM.
* Flash CyanogenMod (your Google Apps will be backed up & restored automatically)
Click to expand...
Click to collapse
So no, you do not need to wipe before upgrading,
The backup is just for security reasons. You never know what could go wrong, so it's good to have a backup in place.
Just flash the new CM 7 and you should be good to go.
^ Mastacheata - thats if you're upgrading from earlier version of CyanogenMod 7
That question we are asking here is what if you're upgrading from CM6.1.
Oh I'm sorry, I misread that the whole time.
Gonna try it now and report back in a few minutes.
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
I'm thinking I may just do a full on Titanium backup, full wipe, then go for CM7.0RC1.
easyonthev said:
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
Click to expand...
Click to collapse
GPS not working in CM7.0 RC1 ??
Do we even have a list of things not working in CM7.0RC1? Again, the OP in the dev thread is a little lite with respect to 'known issue' and similar.
My test was unsuccessful.
I was neither able to install directly over 6.1 nor with prior wipe.
My phone would always end up in a boot loop.
Logcat did tell some Exceptions for unknown permissions.
Detailed explanation will follow in the developer thread.
i accidentally flashed cm7 build 0 over cm6.1 stable before. was able to boot but my phone was laggy & some features were broken, as far as i can remember. so i guess the best path is:
TI backup
complete wipe
flash cm7
TI restore
cliche by now, i know. but it never fails...
As we start the RC phase of CM7, many of you are now taking the leap from CM6 stable to the new RC's.
Some of you may be able to get away with doing this without a wipe; however, most of you will not be that lucky.
Differences in the rom, files system, and even Google Addons will likely throw most of you into boot loops.
Therefore, here is my recommended upgrade path:
1) Nandroid backup your current rom
2) Update your recovery to the latest available (CWR is my choice)
3) Format system via recovery
4) Wipe/Factory reset
5) Flash CM7 then Google addon 1/20
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM and/or Market.
Click to expand...
Click to collapse
Here is what CM Team recommends
Skardy said:
Here is what CM Team recommends
Click to expand...
Click to collapse
Perfect, I shoud've found that myself .
Now its just a question as to whether to go to CM7.0RC2 - lots of people still reporting bugs...
I have a problem with all 2.2.1 ROMs.
I can't install any application, neither from market nor from my sd card.
In the market when I press OK (to accept permissions) nothing happens.
When I try to install from my sd my phone stucks at "installing" screen...
I tried factory reset, format cache, wip cache/dalvik cache, fix permissions...
None of them worked. I searched for solutions but the only thing I found was to clear cache...What can I do??
ps: In older miniCM builds I didn't have that problem...
and sorry for my English, I hope you understand...
EDIT* SOLVED..
I'm not sure because i'm not a developer, but don't you need to update your baseband when your switching to newer Android custom roms?
I've met the same problem the other day,it seems that it is my not wiping my phone before i switch to newer rom that causes it.Im not sure and im not a developer,too.
@deoxx
My baseband is always 015. I mean it doesn't change... Right now I'm using racht's cm7-54 and I don't have this kind of problem...
@Rrc111
Because I didn't understand exactly what you said, you mean that I don't have to wip cache or that I have to wip cache before install the new ROM??
anant123 said:
@deoxx
My baseband is always 015. I mean it doesn't change... Right now I'm using racht's cm7-54 and I don't have this kind of problem...
@Rrc111
Because I didn't understand exactly what you said, you mean that I don't have to wip cache or that I have to wip cache before install the new ROM??
Click to expand...
Click to collapse
after installing from xrecovery, do a factory reset before restarting the phone
treebill said:
after installing from xrecovery, do a factory reset before restarting the phone
Click to expand...
Click to collapse
I tried but it didn't help...
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Click to expand...
Click to collapse
Are you wiping data and cache in recovery?
"wipe data/factory reset"
It will then say:
Code:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
Then:
"wipe cache partition"
It will say:
Code:
-- Wiping cache...
Formatting /cache...
Cache wipe complete
(second option is overkill)
Have you still got the setting to backup to Google servers ticked? Or any other app that you have backed things up with?
Whilst the last option wouldn't be instant (they would download again and take a good 5 minutes to appear).
And yes, you will probably experience issues if this is due to a missed wipe.
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Click to expand...
Click to collapse
Yes, you should always do the "wipe data/factory reset" before installing any new ROMs or if the dev has advised it, also between major update revisions.
You don't need to reboot. If using recovery to install the ROM just do the wipes then flash the ROM using menu.
Awesome. Thanks for the help.
Will try it now and I hope everything goes well. Hope I won't get stuck since am not in front of my pc.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Well, I did it again. Everything wiped out, started as new.
But still, new apps in market and battery history in spare parts give me a process termination...
Oh well, I guess that Lee will release an update.
Oh, something else I would like to ask. There is a new kernel for the Rom. Do I flash it the same way I flash everything? Through recovery?
Thanks again guys
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
I use Leedroid and don't have this problem. Today I have installed from scratch and gone back and forth between ROM's. i turned off all the processes that backup and restore apps and I get a blank fresh install.
I have to ask, the last time you installed Leedroid, did you use the downloaded one or a copy from your sdcard? is it possible you are restoring a copy rather than flashing a fresh copy?
And you don't have any apps that have backed up your apps such as Titanium? And you have turned off Google Backup and restore feature?
The thing is, it is handy not to lose data but we need to make sure your wipe is being done. Did you see the same messages in Recovery as I showed above?
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
GeorgeKps said:
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
Click to expand...
Click to collapse
You have tried fix permissions in ROM Manager, yes?
eeeeeeeeeerm.... you got me. that is something i totally forgot to do :-(((
gosh.. i flashed the radio, sweet. tried to flash a kernel using jkoljo's tool and it stayed on the white screen (and of course cold sweat was all over the place )
but i flashed the rom again after clearing cache and the likes and (thank god) i'm in.
but the most weird thing is that, after all these, the kernel is flashed :-S
i checked in the phone info and the kernel is there..
anyway, am gonna do the fix permissions thingy and reflash once more. if it stays the same way, i'll have to live with it. it's late here in greece.
thanks again for your help guys, i really appreciate it )))
Cheers !!!
i did it all again but nothing happened.
did the permissions, rebooted to recovery, factory reset, cache wipe, install new rom and nothing.
i have to tell you guys though.. the problem with the market started when i was on the revolution rom. and it started just like that. one day everything was fine, next, bam. it didn't budge.
do you think there might be something wrong with the phone itself? (probably not and i'm paranoid)
other than that, everything works nice.
oh, and some other thing. there is this "full wipe 1.3" zip i had put in my SD card but never really used it.
should i use it this time?
this app should clean everything in the cache but not my files, right?
Cheers !!!
YouTube clip of how to manually full wipe everything.
http://www.youtube.com/watch?v=fCwr6Ru0yko
When using this method I've never had a problem.
Sent from my HTC Desire HD using XDA App
I did the wipe as shown in the video. The problem remains the same. New market apps list gives an error followed by a restart of it and spare parts battery history does the same (without the restart though)
I don't know, I'm thinking of trying a different Rom even though I like the one Lee released.
(could all this mean that I have a problem with the phone?.......)
Anyway, thank you guys for spending time helping me.
Cheers !!!
Do I have to clear anything to go from say CM7 Nightly #94 back to the last stable release? I got bored & tired of waiting for a new stable & installed some nightlies & need to back up to fix what they broke.
Thanks,
kev
The big problem is that you came from a stable 2.3.3 to nightlies 2.3.4 and now back to 2.3.3 I read somewhere that going back can cause some FCs if I remember the fix was to go into setting / applications / manage applications / and then clean the cache and data in the app that is giving you the FC. good luck
You should format system before installing the stable. That should help with any problems. Just remember to flash gapps again.
DeadStiff said:
You should format system before installing the stable. That should help with any problems. Just remember to flash gapps again.
Click to expand...
Click to collapse
sorry, but do you mean wipe /system?
format before install seems to imply a fresh install, basically doing everything over again?
thanks.
I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.