How to revert to older Symbian S3 from Symbian ANN...

Hi, I downloaded the Symbian Anna and honestly, it's not as great as it's been made out to be!
Now I want to revert to the earlier S3 version and am unable to do so! What can be done to regain the old version of the OS?
I tried a Restore to factory settings from the phone, but it just goes back to factory settings with ANNA, how do I change the OS back to the earlier one?
Any help will be greatly appreciated!!!

It's not possible, however Anna is a great improvement !! Did you reset the phone before updating ? A reset is always recommended as it will remove any conflict between the new and old software, it's a pain, but worth the effort, my E7 is running great on Anna and all the improvements are worthwhile .
Back up your contacts, calendar and notes ONLY, dial *#7370# followed by 12345 if required, re-install Anna, then set up your phone manually, it is worth the effort 
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution' 

Similar Messages

  • How to revert to older patch version on fresh system

    I have got fresh install Solaris 9 , 117171-07 how can i revert to older patch version.
    I need this for the purpose of testing, i cant find previous release DVD ? any help ?

    I don't think you can.
    You'll have to jumpstart it from an older distribution.
    If you have a support contract, sun should be able to give you the older iso's.

  • How to revert to older version of iTunes

    I'm always apprehensive of updating iTunes to newer versions.
    Just bought an iPhone 5 64GB and I'd like to sync it with music.
    My older phone (32 GB 3GS) had complications when I first bought it, so I'd chosen never to update IT or my iTunes since.
    The 3GS is still running on an older version (3.1.3 [7E18]) and it's been amazing through my 3 years of use.
    The version of iTunes I'm running is 10.3.1 from back in 2011 (I believe) and I'm quite happy with it.
    My iPods AND iPhone have given me no problems these past few years.
    In order to sync my new phone, I'm expecting that iTunes will require the update.
    So... Is there a way to SAVE my current version of iTunes (10.3.1) in case the current one is not to my liking?
    I was hoping to save a copy of it to a USB key.
    I'd also appreciate instruction on how to revert back to this older version if I need to later.
    I'm using a MacBook Pro with Mac OS X Version 10.5.8
    2.53 GHz Intel Core 2 Duo, 4 GB 1067 MHz DDR3
    Thanks in advance, and have a Safe & Happy New Year!

    You can restore much of the look & feel of the previous version with these shortcuts:
    ALT to temporarily display the menu bar
    CTRL+B to show or hide the menu bar
    CTRL+S to show or hide the sidebar
    CTRL+/ to show or hide the status bar (won't hide for me on Win XP)
    Click the magnifying glass top right and untick Search Entire Library to restore the old search behaviour
    Use View > Hide <Media Kind> in the cloud or Edit > Preferences > Store and untick Show iTunes in the cloud purchases to hide the cloud items. The second method eliminates the cloud status column (and may let iTunes start up more quickly)
    If you don't like having different coloured background & text in the Album view use Edit > Preferences > General and untick Use custom colours for open albums, movies, etc.
    If you still feel the need to roll back to iTunes 10.7 first download a copy of the 32 bit installer or 64 bit installer as appropriate, uninstall iTunes and supporting software, i.e. Apple Application Support & Apple Mobile Device Support. Reboot. Restore the pre-upgrade version of your library database as per the diagram below (click on it to enlarge), then install iTunes 10.7.
    See iTunes Folder Watch for a tool to scan the media folder and catch up with any changes made since the backup file was created.
    tt2

  • How to revert to 10.6.2 from 10.6.3 ?

    Hi,
    Could someone please help me with the procedure to revert to 10.6.2 from 10.6.3 on my late 2009 mac mini.
    I have the 10.6.2 combo dmg file.
    Thanks

    Meherally wrote:
    It is just that this 6.3 delta has thrown up problems with some users, and almost everyone has reported success after applying 6.3 combo. I am not a computer professional so unable to explain why.
    The explanation is fairly simple, but users not aware of it often draw the wrong conclusion about what a combo updater can do to avoid or repair post-update problems. Basically, it is that if there is damage in one or more of the currently installed OS component files, or if one or more is missing, then an updater that contains an updated version of the affected files will replace whatever is or should be there, repairing the problem.
    For example, say that there is undiscovered corruption in some obscure component file buried in one of the bundle or application packages in /System/Library/CoreServices. (Packages are folders that look like single files, but actually contain many items, often including other packages.) That file may rarely if ever used by the currently installed OS version in day-to-day operation so the user may be unaware that there is a problem with it.
    If that file has been updated in say 10.6.2 but not further updated in 10.6.3, then the delta version of the 10.6.3 updater won't replace it, but the combo version will (because it contains replacements for all files updated since 10.6). Thus, the combo will repair the damage but the delta won't.
    However, if the damaged file has not been updated since 10.6 was first released, neither version of the updater will replace it, & thus neither will repair the damage. To repair it, the user can reinstall Snow Leopard from the DVD & update it as needed to the current version. In this case, it won't matter what updater type is used since the damage has already been repaired.
    Another example: Say the damaged file is used +by the update process itself+. Depending on when & how it is used, it may not matter a bit if a replacement is included in the update package -- if it isn't already installed when it is needed, the update will fail. In fact, depending on the kind of corruption in the file & how its used, it may end up damaging other, already installed OS files. Again, the remedy for this is reinstalling the OS from the DVD & updating it as needed.
    These examples illustrate why the combo update is not certain to avoid or repair problems, & one reason users sometimes attribute problems to an update that are actually caused by unnoticed pre-existing problems.

  • How to degrade to Nokia Symbian Anna from Symbian ...

    Hello,
    I need an help regarding degrading Symbian Belle to Symbian Anna OS. Because, currently with Symbian Belle i have noticed many of my "Most used" applications are not working with Belle (Skype, Fring, etc).
    I want to understand the procedure to follow for degradation.
    Thanks for your help in advance.

     This question has been asked multiple times already and the answer is always the same. The procedure for downgrading to Anna can't be discussed on the official Nokia support site as it involves illegal software that will invalidate the warranty.
    Ray.

  • How to revert to diagnostics.wadcfg configuration from wad-control-container blob.

    Hello all,
    In our project at some point in the past we have enabled Diagnostics module for getting our log entries in Azure Storage. We added <Import moduleName="Diagnostics" /> to ServiceDefinition.csdef file and then enabled logs transfering and performance
    counters gathering in WebRole.OnStart method via DiagnosticMonitor.Start():
    DiagnosticMonitorConfiguration cfg = DiagnosticMonitor.GetDefaultInitialConfiguration();
    cfg.OverallQuotaInMB = 8192;
    cfg.Logs.ScheduledTransferLogLevelFilter = LogLevel.Verbose;
    cfg.Logs.ScheduledTransferPeriod = TimeSpan.FromSeconds(30);
    cfg.Logs.BufferQuotaInMB = 1000;
    // Define performance counter configuration.
    foreach (var counterName in PERFORMANCE_COUNTERS_NAMES)
    PerformanceCounterConfiguration perfCounterConfiguration = new PerformanceCounterConfiguration();
    perfCounterConfiguration.CounterSpecifier = counterName;
    perfCounterConfiguration.SampleRate = TimeSpan.FromSeconds(5);
    cfg.PerformanceCounters.DataSources.Add(perfCounterConfiguration);
    cfg.PerformanceCounters.BufferQuotaInMB = 1024;
    cfg.PerformanceCounters.ScheduledTransferPeriod = TimeSpan.FromMinutes(1);
    DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", cfg);
    Then using Windows Azure Management Portal we activated Verbose monitoring mode and added several additional performance counters there in order to try the feature. I assume that doing that through the portal we actually modified wad-control-container blob
    so we got new performace counters configuration.
    Later we've realized that it would be better to manage all diagnostic configuration in diagnostics.wadcfg. We removed the code from role start and added diagnostics.wadcfg file to the project that declares the same we did before via code. When we redeployed
    we saw that the configuration remained as it was before - it didn't change at all. It still included new performance counters we added through the portal. It is because the order of precedence, where wad-control-container blob has the highest priority. So
    we deleted all the blobs from wad-control-container in order to revert back to diagnostics.wadcfg and redeployed the service. New blob was created in wad-control-container. It included everything from diagnostics.wadcfg as we expected and
    again we saw these custom performance counters we added via portal time ago. See below the blob content:
    <?xml version="1.0"?>
    <ConfigRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DataSources>
    <OverallQuotaInMB>8192</OverallQuotaInMB>
    <Logs>
    <BufferQuotaInMB>1024</BufferQuotaInMB>
    <ScheduledTransferPeriodInMinutes>1</ScheduledTransferPeriodInMinutes>
    <ScheduledTransferLogLevelFilter>Verbose</ScheduledTransferLogLevelFilter>
    </Logs>
    <DiagnosticInfrastructureLogs>
    <BufferQuotaInMB>1024</BufferQuotaInMB>
    <ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
    <ScheduledTransferLogLevelFilter>Warning</ScheduledTransferLogLevelFilter>
    </DiagnosticInfrastructureLogs>
    <PerformanceCounters>
    <BufferQuotaInMB>4096</BufferQuotaInMB>
    <ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
    <Subscriptions>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\Memory\Available Mbytes</CounterSpecifier>
    <SampleRateInSeconds>10</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\Processor(_Total)\% Processor Time</CounterSpecifier>
    <SampleRateInSeconds>10</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Requests/Sec</CounterSpecifier>
    <SampleRateInSeconds>5</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Executing</CounterSpecifier>
    <SampleRateInSeconds>5</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Requests In Application Queue</CounterSpecifier>
    <SampleRateInSeconds>5</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Failed</CounterSpecifier>
    <SampleRateInSeconds>30</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Timed Out</CounterSpecifier>
    <SampleRateInSeconds>30</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET\Requests Rejected</CounterSpecifier>
    <SampleRateInSeconds>30</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET\Worker Process Restarts</CounterSpecifier>
    <SampleRateInSeconds>600</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <!-- OLD unnecessary counters that were added manually through the portal START-->
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\Memory\Available MBytes</CounterSpecifier>
    <SampleRateInSeconds>180</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\Web Service(_Total)\ISAPI Extension Requests/sec</CounterSpecifier>
    <SampleRateInSeconds>180</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\Web Service(_Total)\Bytes Total/Sec</CounterSpecifier>
    <SampleRateInSeconds>180</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET Applications(__Total__)\Errors Total/Sec</CounterSpecifier>
    <SampleRateInSeconds>180</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <PerformanceCounterConfiguration>
    <CounterSpecifier>\ASP.NET\Requests Queued</CounterSpecifier>
    <SampleRateInSeconds>180</SampleRateInSeconds>
    </PerformanceCounterConfiguration>
    <!-- OLD unnecessary counters that were added manually through the portal END-->
    </Subscriptions>
    </PerformanceCounters>
    <WindowsEventLog>
    <BufferQuotaInMB>0</BufferQuotaInMB>
    <ScheduledTransferPeriodInMinutes>0</ScheduledTransferPeriodInMinutes>
    <Subscriptions />
    <ScheduledTransferLogLevelFilter>Undefined</ScheduledTransferLogLevelFilter>
    </WindowsEventLog>
    <Directories>
    <BufferQuotaInMB>256</BufferQuotaInMB>
    <ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
    <Subscriptions>
    <DirectoryConfiguration>
    <Path>C:\Resources\directory\ac17d63416cf41c8acfebbbcb3d90052.Mbo.Services.Web.DiagnosticStore\CrashDumps</Path>
    <Container>wad-crash-dumps</Container>
    <DirectoryQuotaInMB>256</DirectoryQuotaInMB>
    </DirectoryConfiguration>
    </Subscriptions>
    </Directories>
    </DataSources>
    <IsDefault>false</IsDefault> <!-- DEFAULT IS SET TO FALSE AGAIN -->
    </ConfigRequest>
    We tried to directly edit this XML. We removed redundant counters and changed IsDefault to "true" value in the XML and updated the blob in the wad-control-container using Azure Management Studio. Next time we redeployed the service - the counters
    again appeared in the configuration and IsDefault reverted to false again.
    Does anyone know how to permanently revert to managing diagnostics configuration only via diagnostics.wadcfg file and force the Azure to forget about manual edits we did via the portal?
    We use Azure SDK 1.4. 
    Thanks in advance for any insights!
    Vitaly

    Hi Vitaly,
    Did you try to change diagnostics configuration in VS? Like this:
    I suggest you could click the "Edit", and select your diagnostics metrics. Also, I want you double check your  re-deployment  project whether is right. Please try it.
    By the way, I suggest you could upgrade your SDK version and refer to this sample:
    http://www.windowsazure.com/en-us/develop/net/common-tasks/performance-profiling/
    http://msdn.microsoft.com/en-us/library/windowsazure/hh411542.aspx
    Any question or result, please let me know.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to revert to 3.4.1 from 3.5RC?

    Hi,
    I made the mistake of trying the RC of 3.5 and now when I hit the print button or choose print settings, Lightroom crashes immediately.  Initially I thought that this was a problem with print drivers but I can print fine from Photoshop or <gasp. Aperture, along with any other applications.
    I was able to print from Lightroom 3.4.1 with great success to a variety of printers but wanted to see the difference in a print with my new Epson 4900 and boom out go the lights whenever I go to print.  I really like Lightroom's print templates and have created enough of them for collage style output that not being able to print from Lightroom is a real PITA. 
    Doing a full uninstall seems to mean do a manual search and destroy through the filesystem followed by an install and then a reinstall of all of my plugins that work just fine now.
    Is there a Print module that I can look to specifically?
    I have deleted the RC application and done a reinstall with 3.4.1 (without ripping out all the prefs etc) but no joy.  It has to be something relatively simple (I hope).  Any help will be sincerely appreciated.
    Thanks,
    Ross

    Good call on the printer driver issue.  Last month I updated the drivers for my Canon photo printers using drivers from Canon and things got odd,  I thought I had it fixed since Lightroom had been printing, but Lightroom does not seem to update the image driver settings until AFTER you actually print something.
    By deleting the printer in System Preferences and then launching Lightroom, it forced Lightroom to revert to a default text printer.  I was then able to use the Print and Print Settings functions to configure Lightroom to print to the Epson 4900, and it is working now.
    Thank you kindly for your diligent thinking and leading me to the solution.  Others may encounter similar challenges and your help will help them too.
    Best,
    Ross

  • How to revert back to Snow Leopard from Lion?

    Foolishly I just jumped straight in, downloaded Lion and installed it, and well... I really don't like it.  It's not a patch on SL.
    So I'm trying to work out the best way of reverting back to Snow Leopard.
    I have:
    My Snow Leopard install disc.
    A SuperDuper, bootable backup from 48 hours pre-upgrade.
    A Time Machine backup from 48 hours pre-upgrade.
    I'm fairly sure that just putting the SL install disc in, isn't going to work.
    I think I have a couple of options.
    1. Erase the hard drive completely, and then do a fresh SL install, then restore the last TM backup.
    2. Boot from the SuperDuper backup, then restore the last TM backup.
    I'd prefer option 1, as this gives me a clean install (I hope).
    Before I go ahead, can anyone:
    a) See any problems with carrying this out, or
    b) Suggest a better, safer method?
    I'm a bit concerned that SL was an upgrade to an existing OS, rather than a complete OS in itself, so I'm very wary of what might happen if I wipe the drive then put the disc in, hoping it'll give me a nice new version of SL.  Might need to go and do a bit more reading up.
    Thanks.

    For ref.
    Dragged and dropped copies of important files (Docs, Pictures, Downloads, Movies etc) to a spare drive.
    Printed off any docs that I absolutely could not afford to lose.
    Shut down Mac.
    Attached USB drive with SuperDuper backup, and powered up drive.
    Powered up Mac, and immediately pressed the option key.
    From the window that popped up, chose my USB drive as the boot disk and pressed return.
    Mac powered up running Snow Leopard from USB drive.
    Started Disk Utility, and erased the disk labelled 250.06 GB Fujitsu.... etc  In the 'name' field, entered 'Macintosh HD'
    Started up SuperDuper! and copied my backup over Macintosh HD.
    Incidentally, the first step it took was to erase Macintosh HD anyway, so I could probably have skipped the first erase.
    Let SuperDuper! do it's thing for 90 mins.
    Once it had completed, closed the machine down (it wouldn't let me eject the USB drive, as presumably it was still using that as the boot disc).
    Detached and powered off USB drive.
    Pressed Mac power button and crossed fingers...
    And goodbye annoying Lion, hello again, good old Snow Leopard!
    Didn't even need to restore the last Time Machine backup.
    I may take another look at Lion again, further down the road, when hopefully Apple will have realised that OS X and iOS are two completely different animals, and that we don't all want our Macs behaving like our iPads.
    For now though, I'm sticking with SL.

  • How to revert to older version of imovie

    I updated to imovie 10.0.2 and I hate it! How can I go back to the older version?

    Look in your Applications folder. You probably have the old version still there.
    But honestly, the new version is pretty nice. It takes some getting used to because it does some things differently, but a trip to youtube.com will likely answer your questions.

  • How to revert back the essbase installation from 'as a service'

    Hi,
    at the time of installing Hyperion essbase ver9.3.1,I installed it as a service, so now I can't see the essbase server window any more. Is there any process to revert back the aforesaid, so that I can start the essbase server manually and can see the server window afront?
    Thanks & Regards.

    Hi,
    Yes, it worked fine. Thanks for your support.
    Regards.

  • How to revert to older version of ipod software

    The latest 1.0.3 iPod upgrade screwed up my iPod. Some artists don't show up under the Artists, All Artists or Genre menus. I have to go under All Albums or All songs under a submenu to find them. In iTunes things are fine, and when I connect my iPod and browse the music on the iPod using iTunes, things are fine. It's only on the iPod things are screwed up. I've tried changing the MP3 tag information on the names, genre, etc. numerous times to no avail.
    And only since 1.0.3.
    Is there a way to revert to the prior (I assume 1.0.2) version of iPod software? Resetting the iPod stupidly puts back 1.0.3 again. I don't see where I can download 1.0.2 or any iPod version anywhere.
    Raul

    Well. go to http://spr33.co.uk/wp/archives/downgrading-apple-ipod-firmware-102-101 and dolwload the "iPod_24.1.0.1.ipsw" then press the shift button when clicking restore locat the file and then you are downgrading!
    The problem is I could only find 1.0.1! I'm serching for 1.0.2 right now!

  • How to revert to older software to play ipod  in car stereo

    I have a Classic I-pod with software version 3.1.1. The manual for my Pioneer DEH-P310UB car stereo says it will play the Classic I-pod version 1.1.2. Can I revert my I-pod software back to 1.1.2 in order to play it in the car? I'm going on a long road trip and wish to play this I-pod on the road.

    Yes I do have a Classic, it's not a nano, it doesn't take photos, and I got it for Christmas 2004.
    The iPod classic was not even released until October 2007.
    The iPod Photo (or 4th gen iPod) and iPod with color display do not take photos but can display photos.
    it tells me the software is 3.1.1
    Yes, because the iPod Photo (or 4th gen iPod) uses firmware 3.1.1. The iPod classic (120 GB iPod) uses version 2.
    The iPod classic (80GB & 160GB) use version 1.1.2.
    Is it possible to revert to 1.1.2?
    Possibly but the manual you are reading is not referring to version 1.1.2 for the iPod Photo (4th gen).
    It is referring to version 1.1.2 for the iPod classic (which are only the 80GB/160GB models).
    If your iPod does not have a 80/160/120Gb drive, it is not an iPod classic. It is a regular iPod.
    See this -> Identifying iPod models

  • How do you eliminate older backups from Time Capsule?

    How do you eliminate older backup copies from a older model of time capsule?

    Randoolpyh wrote:
    How do you eliminate older backup copies from a older model of time capsule?
    You shouldn't have to.  Time Machine will delete them automatically when it needs room for new ones.  If you're running Leopard, though, and have the Warn when old backups are deleted box checked in Time Machine Preferences > Options, it won't.  Just remove the check and run a backup.
    If you have other data on the TC's internal HD, that's going to cause trouble sooner or later.  See #Q3 in Using Time Machine with a Time Capsule for some possible workarounds.
    If you still want to delete individual backups, or all backups of selected items, do not use the Finder.  See #12 in Time Machine - Frequently Asked Questions, and note the pink box there.

  • To revert back a transport request from prd to dev server

    hi experts
        how to revert back a transport request from prd server to
        dev server?
        a transport request has been wrongly transported
        and it has make major changes in production server,
       now  we want to revert back that request , we know the   request no.
    regards
    pankaj

    All you have to do is create an order of transport type "Transport of copies" in PRO.
    I give you the steps to follow:
    1. Go to SE01 and create a new order (remember the type "Transport of copies").
    2. Enter the data of the order of transport that is going to come back.
    3. Enter the target, here is where you asign the target system to carry the request.
    4. Now just add the number of request to the new request you just created.
    5. Finally released the request from this transaction.
    6. Check on the queue of transport in DES, the request must appear there.
    I hope you serve =)

  • How to revert back of secondary indexes created?

    Hi all,
                     I have craeted secondary indexes in development and they have been transported into quality and production. Some dumps are coming in the production because of these secondary indexes.
    Please guide me how to revert back those secondary indexes from production(means to keep original with out that secondary indexes?)
    Please give me solution.
    Regards,
    Lokesh

    Hello,
    The best way to do this is delete the indexes again in DEV and create a transport request.
    Transport this request to QA and PRD and the index will be deleted.
    Via SE14 you can also delete the index immed in PRD.
    SE14 will only delete the index from the database (shortdumps will disappear then).
    Afterwards you can still use SE11 to delete the index from the SAP repository as well.
    Success.
    Wim
    Edited by: Wim Van den Wyngaert on Nov 20, 2009 1:08 PM

Maybe you are looking for