Downgrade from CM 10.1 to 10.0? - Nexus S Q&A, Help & Troubleshooting

I accidentally installed the 10.1 nightly (it was erroneously offered via auto-update)
Notifications and WiFi tether don't work, so I need to return to 10.0.
Is there any non-destructive way to do this downgrade? I'm getting really sick of wiping and re-installing everything!

z0s0 said:
I accidentally installed the 10.1 nightly (it was erroneously offered via auto-update)
Notifications and WiFi tether don't work, so I need to return to 10.0.
Is there any non-destructive way to do this downgrade? I'm getting really sick of wiping and re-installing everything!
Click to expand...
Click to collapse
Yes, re-install the rom from recovery. Wipe cache + dalvik and re-install JB 4.1.2 gapps if needed. Then fix permissions and reboot.
Don't need to wipe data/factory reset.

I checked my claims because I was curious. You will need to wipe. :/

Hmm.. yeah I suspected as much.
Damn.

z0s0 said:
Hmm.. yeah I suspected as much.
Damn.
Click to expand...
Click to collapse
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.

polobunny said:
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.
Click to expand...
Click to collapse
Something is definitely changed after NS lost support from JBQ and his boys. 4.1.2 which is based on actual sources for the NS from Google definitely still runs better than some zomgfastbatterysaving 4.2 ROMs.

Here a how I've dirty flashed ROMs without issues. Of course I make a backup first. Then, I wipe cache, wipe dalvik cache, and format system. Then I flash the ROM, gapps, and reboot. Learned this from the1dynasty. Hope it works.
Sent from my Nexus S 4G using xda app-developers app

PartimusPrime said:
Here a how I've dirty flashed ROMs without issues. Of course I make a backup first. Then, I wipe cache, wipe dalvik cache, and format system. Then I flash the ROM, gapps, and reboot. Learned this from the1dynasty. Hope it works.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
This works for most upgrades, but not for most downgrades...

OK thanks for the info
Sent from my Nexus S 4G using xda app-developers app

polobunny said:
On the upside, CM10 is sooooo much better than CM10.1. My phone feels new.
Click to expand...
Click to collapse
10.1 does not run well, glad to know it's not just me.

onehitch said:
10.1 does not run well, glad to know it's not just me.
Click to expand...
Click to collapse
I'm on the last version (I think) of cm10. cm-10-20121220-NIGHTLY-crespo. This had been removed from cm download. only stable remains though.
With marmite v7.2 kernel (no overclock), my nexus s is running without hiccup. Without marmite, I get sporadic ram overran problem with crappy voice calling (in and out calling not working) and sluggishness.

Related

[Q]How to flash a new update to current rom

Ok, I'm sorry if this has been answered somewhere else on here, however I can not seem to find it and I want to make sure I do this properly! I have rooted my Galaxy Skyrocket and installed the ICS 4.2-5A rom version 4.0.4 and I want to install Seans new update 6B and I wanted to know the steps to apply the update. From what I read I know I do not need to completely wipe my phone and reinstall the rom. Also, will I have to reinstall my radio after I install the update? Thank you to anyone that can help me!
Should be update instructions on the first post of the ROM thread. If not the first post, at least the first page.
it doesn't show me on seans thread.....here it is...http://forum.xda-developers.com/showthread.php?t=1722828
I am just trying to figure out what I need to wipe, if anything. I know I need to put it on my sd card and boot into recovery, just not sure what to do at that point.
Post 2
SKY ICS NONWIPE UPDATES
UPDATE A
IF YOUR STARTING FRESH (PICK A BASE THEN FLASH THIS UPDATE.. )
(DO NOT FLASH A THEN B)(ITS POINTLESS)
Click to expand...
Click to collapse
Just flash, don't wipe.
the only thing is is that i am not starting fresh. im already on the current rom he has up there. so i think i need to pick the B update...so do i still just open the zip file and run it or do i need to wipe something? I thought I needed to atleast wipe the cache and possibly the delvik, but that's why I'm asking! Thanks for your help!
For the update, wipe cache/dalvik then flash the zip. Reboot and enjoy
Sent from my SGH-I727 using Tapatalk 2
Thank you for the help...i will go ahead and do that!
Always make backups just in case it doesnt go as planned. :good:
gsxrchick said:
the only thing is is that i am not starting fresh. im already on the current rom he has up there. so i think i need to pick the B update...so do i still just open the zip file and run it or do i need to wipe something? I thought I needed to atleast wipe the cache and possibly the delvik, but that's why I'm asking! Thanks for your help!
Click to expand...
Click to collapse
You can just flash away. No cache clearing is necessary. I just did it to update from 4.5A to 5B a mere 10 minutes ago.
Mike on XDA said:
You can just flash away. No cache clearing is necessary. I just did it to update from 4.5A to 5B a mere 10 minutes ago.
Click to expand...
Click to collapse
i recommend you wipe cache and dalvik.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
i recommend you wipe cache and dalvik.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Same here
Sent from my SGH-I727 using Tapatalk 2
OK guys I am on 4.2F-6B...thanks for all the help! The smart stay app will not open and says the beta testing is over...any ideas how I can get this to work? Also the screen keeps flashing no front camera detected, however the front camera works when I go into the camera. Why would this be flashing on the screen?
Sorry to be such a newbie, but I guess we all have to start somewhere!
gsxrchick said:
OK guys I am on 4.2F-6B...thanks for all the help! The smart stay app will not open and says the beta testing is over...any ideas how I can get this to work? Also the screen keeps flashing no front camera detected, however the front camera works when I go into the camera. Why would this be flashing on the screen?
Sorry to be such a newbie, but I guess we all have to start somewhere!
Click to expand...
Click to collapse
On the Sky ICS thread (2 days ago) someone posted a link to a new version. U can probably search on xda / Google to find it or manually go back some pages. It is a .apk so you install it using astro file manager. Hope this helped.
Sent from my Skyrocket i727 running Sky ICS
Here is the new version. http://www.mediafire.com/?5wokm0nh8ym9vza
Sent from my Skyrocket i727 running Sky ICS
gsxrchick said:
OK guys I am on 4.2F-6B...thanks for all the help! The smart stay app will not open and says the beta testing is over...any ideas how I can get this to work? Also the screen keeps flashing no front camera detected, however the front camera works when I go into the camera. Why would this be flashing on the screen?
Sorry to be such a newbie, but I guess we all have to start somewhere!
Click to expand...
Click to collapse
As for saying no front camera I only saw that one time and it was when trying to open the smart stay beta when no longer available. Its nothing to worry about. If your front camera works then in the camera app there isn't anything to worry about. Its just a glitch
Sent from my Skyrocket i727 running Sky ICS

Not enough storage?

Had anyone got this error before? Is there a fix? I got 7gb left of internal storage so this shouldn't be happening.
Sent from my Paranoid Android Galaxy S III
Anyone?
Sent from my Paranoid Android Galaxy S III
fr8cture said:
Anyone?
Sent from my Paranoid Android Galaxy S III
Click to expand...
Click to collapse
You don't need to bump your post every hour because you haven't gotten an answer yet. Not everyone is on at the same time.
Far as a solution:
First, have you cleared the cache and data for the market app and you still get the same error?
Are you running a ROM - If so, did you dirty flash(just wipe cache and flash the zip) or did you do a full wipe?(factory reset + Davlik cache)
If not running a ROM try to clear your cache anyways via CWM or TWRP see if that helps.
Brian Gove said:
You don't need to bump your post every hour because you haven't gotten an answer yet. Not everyone is on at the same time.
Far as a solution:
First, have you cleared the cache and data for the market app and you still get the same error?
Are you running a ROM - If so, did you dirty flash(just wipe cache and flash the zip) or did you do a full wipe?(factory reset + Davlik cache)
If not running a ROM try to clear your cache anyways via CWM or TWRP see if that helps.
Click to expand...
Click to collapse
I did everything except clear cache for market. How do i do that?
Go to 'Manage Apps' in settings then click the market. There you'll see four options; force stop, uninstall, clear data, clear cache. Clear the data and the cache. This will make you agree to the TOS again but may solve your problem.
Brian Gove said:
Go to 'Manage Apps' in settings then click the market. There you'll see four options; force stop, uninstall, clear data, clear cache. Clear the data and the cache. This will make you agree to the TOS again but may solve your problem.
Click to expand...
Click to collapse
Nope didn't work :/
fr8cture said:
I did everything except clear cache for market. How do i do that?
Click to expand...
Click to collapse
I think this is an option in most "cache cleaners"...atleast mine is showing the option.
are you rooted? on custom rom? need more info
luke1333 said:
are you rooted? on custom rom? need more info
Click to expand...
Click to collapse
Yes im running Paranoid Android.
EDIT: The problem seems to happen with random apps.
fr8cture said:
Yes im running Paranoid Android.
EDIT: The problem seems to happen with random apps.
Click to expand...
Click to collapse
try reinstalling rom and rewiping everything again?
Do you have a directory called "LOST.DIR" on your sdcard that's ridiculously big? If you do, you can delete it - it's essentially the 'Recycle Bin' of Linux.
Also, try removing ALL your google accounts from the phone then clearing the market cache like mentioned above and then add your google accounts back. This is a fix for a different market problem but may work on this one as well.
Brian Gove said:
Also, try removing ALL your google accounts from the phone then clearing the market cache like mentioned above and then add your google accounts back. This is a fix for a different market problem but may work on this one as well.
Click to expand...
Click to collapse
tried it no success
I'm out of ideas then. Re-flash your ROM after doing a full wipe see if that fixes it. If not try a different or stock ROM.
Brian Gove said:
I'm out of ideas then. Re-flash your ROM after doing a full wipe see if that fixes it. If not try a different or stock ROM.
Click to expand...
Click to collapse
Dang, i really dont wanna reflash.
Alright went to a backup i had of this rom and everything seems to be fine now, i installed KT Kernel last night and then today i had the problem. Do you think the kernel had something to do with it?

No response

Hi everyone,
I recently started to experience a problem with CM 10 on my Xperia miro. I am using the unofficial builds provided by the FreeXperiaTeam. During random times, when the phone is locked, it stops responding. I am not able to unlock the phone nor see anything on the screen. The buttons on the device also show no response. I am able to turn it back on only after I remove the battery, and put it back in. This issue occurs at least once everyday.
I would really appreciate it if somebody could provide me with a solution for this problem. I would prefer to not factory reset my device.
Thank you very much!
Sent from my Xperia Miro using xda app-developers app
nightfireblaze8 said:
Hi everyone,
I recently started to experience a problem with CM 10 on my Xperia miro. I am using the unofficial builds provided by the FreeXperiaTeam. During random times, when the phone is locked, it stops responding. I am not able to unlock the phone nor see anything on the screen. The buttons on the device also show no response. I am able to turn it back on only after I remove the battery, and put it back in. This issue occurs at least once everyday.
I would really appreciate it if somebody could provide me with a solution for this problem. I would prefer to not factory reset my device.
Thank you very much!
Sent from my Xperia Miro using xda app-developers app
Click to expand...
Click to collapse
wipe dalwik and chack. not sure about it but give it a try.
>??
did it work ??
imharshadpatel said:
wipe dalwik and chack. not sure about it but give it a try.
Click to expand...
Click to collapse
Anytime your running into issues like this on any Custom ROM the best practice is to start over, don't be lazy to save Data ..and Don't do a Factory Reset on a Custom ROM it never fairs well. You can as mentioned wipe dalvik and cache then fix permissions but if your still having issues the get away from that build or redownload it and do a full wipe and fresh install you will save yourself time and headaches. Things go wrong from time to time just start over and do a clean install
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Anytime your running into issues like this on any Custom ROM the best practice is to start over, don't be lazy to save Data ..and Don't do a Factory Reset on a Custom ROM it never fairs well. You can as mentioned wipe dalvik and cache then fix permissions but if your still having issues the get away from that build or redownload it and do a full wipe and fresh install you will save yourself time and headaches. Things go wrong from time to time just start over and do a clean install
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Plus, be choosy about what rom you are flashing. Better stay with official/stable releases if you want to avoid problems, and never do a dirty flash. It's better to be careful than lazy.
Thank you all for the help! I don't know how, but the problem has stopped. Sorry about the late reply.

[Q] Periodic Freezes/Crashes with Cyanogenmod 10.1.3

Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Windstorm1981 said:
Has anyone had problems with the new Cyanogenmod 10.1.3 freezing and crashing periodically?
I did a brand new clean full reinstall (not an upgrade). Still have the problem.
Any thoughts on what might be causing this?
Thank you.
Click to expand...
Click to collapse
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
epagib said:
Are you under-volting?
... and why not try CM 10.2?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not familiar with volting. How do I know/check to see if I'm doing that?
I was running CM 10.2 and it was working. Suppose I could go back. I'd just prefer to stay at 10.3 if I can fix this. Reason is that I would want to do a clean install of 10.2 and that would require all the formatting, app set up etc. Don't want to load up from my nandoid since I simply installed updates from CM 10.1 up through 10.2 and things started to get corrupted.
Thanks.
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
epagib said:
Chances are you're not undervolting then. Custom kernels allow us to do that.
Sounds like you've been taking the nightly updates and after awhile the problem arise?
I'd try to clean cache, clean dalvik cache, and fix permissions. Then reboot.
Of that doesn't work, then would have to do a clean reinstall
Click to expand...
Click to collapse
No - haven't been taking the nightlies. Only the stable versions.
In installed CM 10.1.3 as a clean install twice - including cleaning the cache and the dalvik cache.
I actually saw another mention on the web about another GSIII user seeming to have the same problem.

[Q] Hardware issue?

Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel
I guess no one's ever had this problem before? =[
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]

Categories

Resources