New ios upgrade issue

My iphone after the last upgrade 6.0.1 is hung up all the time when I try to reach the settings and apps on it. FYI. Can I downgrade it to the previous version. Let me know.

Try user troubleshooting restart, reset http://support.apple.com/kb/HT1430, then restore from backup, restore as new. http://support.apple.com/kb/HT1414

Similar Messages

Does anyone know if Sprint Wireless will be allowing the hotspot on the devices for free instead of having to pay with the new iOS upgrade?

Does anyone know if Sprint Wireless will be allowing the hotspot on the devices for free instead of having to pay with the new iOS upgrade?

Sprint probably knows. Ask them.

2960s IOS Upgrade Issue

Hi
I have a issue when i try to upgrade the IOS of WS-C2960S-48TS-L, the curretn version is 12.2(58)SE2 , the verison im trying to upgrate to is 15.2.SE6.
I do the "archive tar /xtract tftp" command to extract all the files to the flash, then i do the "boot system flash:" command to change to the new but when i reboot the switch it loads the new ios then loads the old ios and boot using the old ios, how can i change to ignore the old ios ?

Here i am again...and with new weird news.
I've made new tests and analisys on my six WS-2960S-48LPS-L.
Cables are ok (said by TDR).
Five on six no way to upgrade, from CLI, upper 15.0.1-SE. This is the newest working IOS i found, tested:
c2960s-universalk9-mz.150-2.EX
c2960s-universalk9-mz.150-2.SE6
c2960s-universalk9-mz.150-2.SE6 <-- suggested by Cisco
c2960s-universalk9-mz.150-2.SE7
c2960s-universalk9-mz.152-2a.E1
no way to boot, always the same error i've already posted.
Tried to format the rom also, always same things.
Anyway with 15.0.1-SE that should have fixed the poe problems, poe doesnt work...So i guess it's a hardware problem. Well ...5/6... i must say i have really bad luck...
But now, give me your attention please.....
One of them works, every port do its job with my voip cisco 7912 phones, with an old IOS also (12.2.58-SE2). So, i checked if it is a 2960S-48LPS-L for sure, serial number on case is the same i have on the package. It says it's a LPS-L. So, from CLI, i tried a show version....look at this:
Cisco IOS Software, C2960S Software (C2960S-UNIVERSALK9-M), Version 12.2(55)SE8, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 26-Jun-13 11:40 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01B00000
ROM: Bootstrap program is Alpha board boot loader
BOOTLDR: C2960S Boot Loader (C2960S-HBOOT-M) Version 12.2(53r)SE, RELEASE SOFTWARE (fc3)
Vigili uptime is 6 days, 21 hours, 54 minutes
System returned to ROM by power-on
System restarted at 12:01:56 UTC Wed Apr 1 2015
System image file is "flash:/c2960s-universalk9-mz.122-55.SE8/c2960s-universalk9-mz.122-55.SE8.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C2960S-48FPS-L (PowerPC) processor (revision H0) with 131072K bytes of memory.
Processor board ID FOC1726Z0GN
Last reset from power-on
1 Virtual Ethernet interface
1 FastEthernet interface
52 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address       : 84:80:2D:0D:F8:00
Motherboard assembly number     : 73-11908-09
Power supply part number        : 341-0393-02
Motherboard serial number       : FOC183811TD
Power supply serial number      : LIT183101SG
Model revision number           : H0
Motherboard revision number     : A0
Model number                    : WS-C2960S-48LPS-L
Daughterboard assembly number   : 73-11933-04
Daughterboard serial number     : FOC18376CNB
System serial number            : FOC1726Z0GN
Top Assembly Part Number        : 800-30945-04
Top Assembly Revision Number    : C0
Version ID                      : V04
CLEI Code Number                : COMGZOOARD
Daughterboard revision number   : A0
Hardware Board Revision Number : 0x01
Switch Ports Model              SW Version            SW Image
*    1 52    WS-C2960S-48FPS-L 12.2(55)SE8           C2960S-UNIVERSALK9-M
now i'm really confused...
I called Cisco, gave them the serial number and they confirmed must be a LPS-L.
Ideas?

IPhone new iOS upgrade

I recd a msg saying I can upgrade my iPhone 3G to new iOS 4.2. I connected to the PC & it said the upgrade was easy. Just go to iTunes & follow the instructions. There are no instructions on how to upgrade on iTunes that I can find. This is my first time to download an upgrade. What am I doing wrong? Where do I go in iTunes to access the upgrade?

Virginia Fischer wrote:
When I select iTunes on my phone it takes me to a page that lists Podcasts, Audiobooks, iTunes U, Downloads, Ping. At the bottom I can select from Music, Video, Ringtones, Search, More.... I don't see anything called Summary?
Turn on your computer.
Open itunes on your computer.
Connect iphone.
Got to the summary tab.
Click check for updates.
It may help you to look at the manual:
http://manuals.info.apple.com/enUS/iPhone_iOS4_UserGuide.pdf

Iphone ios upgrade issue

I am unable to upgrade my iphone 3g Model number MB489HN. i STILL HAVE IOS VER 4.1. Please advise.

I am having the same issue on my Macbook Pro running 10.6.6, and the latest iTunes 10.2.1.
I have iOS4 4.2 and I'm trying to upgrade to 4.3. I get the exact same message. This happens on my internet connection at the office as well as at home.

HT4528 Is anybody having problems receiving text messages since the new iOS upgrade?

People have told me that they have sent me a text message but yet I am not receiving anything.

Did you already try to reset the phone by holding the sleep and home button for about 10sec, until the Apple logo comes back again? You will not lose data by resetting.
If this did not work, and to rule out a software issue, setting it up as new device would be the next step:
iOS: How to back up your data and set up your device as a new device

IPad IOS upgrade issue

I have the original iPad. The IOS is 5.1.1. It tells me that this is the latest version. I can not upgrade to the latest IOS version 7.x and therefore can not use new apps. Any insights?

The hardware for your iPad only supports up to iOS 5. You cannot upgrade to iOS 6 or iOS 7.

ASR 1001 IOS upgrade issue

Hi I am changing IOS of Cisco ASR 1001 from asr1001-universalk9.03.07.02.S.152-4.S2.bin
to asr1000rp1-adventerprisek9.03.04.02.S.151-3.S2.bin but everty time it boot up with old IOS universalk9.
Is it becaused of Licence issue.
Router#sh bootvar
BOOT variable = bootflash:asr1000rp1-adventerprisek9.03.04.02.S.151-3.S2.bin,12;bootflash:asr1001-universalk9.03.07.02.S.152-4.S2.bin,12;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
License Level: advipservices
License Type: Permanent
Next reload license Level: advipservices
cisco ASR1001 (1RU) processor with 1155941K/6147K bytes of memory.
Processor board ID SSI1607042B
4 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7741439K bytes of eUSB flash at bootflash:.
Configuration register is 0x2102

You downloaded the wrong file. The file you wanted to run has "rp1" but the original file doesn't. You downloaded a file for a different model. Your router is an ASR 1001 with fixed RP but you've downloaded a file for a different sub-model of ASR, like the 1002 or 1004.
Go here instead: http://software.cisco.com/download/release.html?mdfid=282993672&softwareid=282046477&release=3.10.3S&relind=AVAILABLE&rellifecycle=ED&reltype=latest

3750 IOS Upgrade Issue

So I have a bunch of 3750s in my network...upgrade them all the same way. Today I recieved 3 new ones...upgraded the first one no problem...during the second I recieve the following:
Switch#$overwrite /reload tftp://10.20.11.15/c3750-i5k91-tar.122-20.SE3.tar
Unable to create temp dir "flash:update"
Switch#$overwrite /reload tftp://10.20.11.15/c3750-i5k91-tar.122-20.SE3.tar
Anybody have any clue how to get around this?
bc

Alok,
I gave that a whirl and it was a no go. I recieved the following error msgs:
Switch#rmdir flash:update
Remove directory filename [update]?
Delete flash:update? [confirm]
%Error Removing dir flash:update (Unknown error 93)
Switch#rmdir flash:update
Remove directory filename [update]?
Delete flash:update? [confirm]
%Error Removing dir flash:update (Unknown error 93)
Switch#
Let me know if you have any clue what is gonig on!
bc

Update the iPad 2 with new iOS uppgrade, but after the screen only show the apple and nothing else. has been the case since yesterday. have turned off the iPad and turned it on again many times, but still only apple shown. What should I do?

UPdate the iPad wjith new iOS upgrade that where shown under settings on the iPad, but after I did the upgrade the screen has only shown the apple and I can't get back. This has been the case since yesterday. Have turned off t.he iPad many times, but every timebwkhen Ibturn it on again the screen onöy show the apple icon and nothing else happends. What should I do? Anyone having the same problem and how can this be solved?

Did you try to connect in recovery mode, explained in this article?
iOS: Unable to update or restore

Ipad ios upgrade, now ipad shuts off constantly

I updated to the new ios upgrade, now ipad shuts off within a few minutes, every few minutes then turns itself on. Any suggestions?

Try Reset iPad
Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
Note: Data will not be affected.

WHEN I SYNC MY IPHONE MY SONGS DO NOT SORT IN ORDER. MY MOST LISTENED TO SONGS ON ITUNES APPEAR AT THE BOTTOM OF MY PLAYISTS WHEN THEY SHOULD BE APPEARING AT THE TOP. THIS ISSUE ONLY STARTED HAPPENING SINCE UPGRADING TO THE NEW iOS PLATFORM. please help!!

when i sync my iphone to my computer to update my music, it syncs as normal to my phone but it re-arranges the most played songs and puts them at the bottom of the app rather in the exact order its appearing as in itunes. this only started happening when i updated to the new iOS platform. can somebody else? i need them to sync so that my most played songs remain at the top and not the opposite!!
PLEASE HELP!

You may have to try deleting all the music from your phone (by going to Settings>General>Usage>Music, swipping All Music and tapping Delete), then sync it all back on with iTunes in order to fix this.

HT4061 I have an iphone 3gs - the new ios 6.1 (?) upgrade has inabled my phone. I get a white apple on the screen. can't reset phone - doesn't work. what can I do besides take phone into Apple?

I have an iphone 3gs - yes, an older iphone.
This morning apple had a msg that asked if I wanted to upgrade to the new ios 6.1 (?). I said yes. Now I can't use my phone. I've tried hitting the power and other buttons. I get a white apple on the screen. can't reset phone - doesn't work. what can I do besides take phone into Apple? This *****! I realize (now from reading internet) that my phone/system may be uncompatible. Help!

I have a 3GS (a true classic design!) and have upgraded it to 6.1 today. The process did not go without a glitch - it took a few attempts to get the app's to sync but after detecting the ones causing an issue and deleting them it works - so far! I have had issues about 50% of the numerous times a new OS is uploaded to this phone and always take the new OS with trepidation. But at least you know there is a 3GS with 6.1 working OK.
I suggest you do a fresh restart to the phone several times - without it being connected to the computer - to see if it gets its act together and starts. I think it will. Hold down the top 'power' button and front round control button until it shuts down - goes blank and dead. Then press the top power button to re-activate - reboot - it.
If that does not work then plug into your itunes computer, navigate in iTunes to see your iPhone and hopefully you will be able to sync it or at least 'restore iPhone' from the 'summary' tab.
If you can not get onto the iphone perhaps you will still be able to sync if in iTunes by going - 'file' - 'devices' - 'sync iphone' or failing that try transfer purchases' and ultimately 'restore from back-up'.
I had technical problems with my old 3GS (suffered a failed wireless antenna) so I took it to an Apple Store and they issued me with a service-replacement/reconditioned phone for a very modest charge. So if worst come to the worst get a new phone that way!

Upgraded to new iOS 8.0.2

Upgraded to new iOS & iPad keeps freezing, several minutes at a time. Before upgrade I never had even 1 issue with the iPad. Need some solutions for this very irritating & time consuming problem.

Try some basic troubleshooting:
(A) Try reset iPad
Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
(B) Try reset all settings
Settings>General>Reset>Reset All Settings
(C) Setup as new (data will be lost if you do not have backup)
Settings>General>Reset>Erase all content and settings

Cisco 4500X IOS upgrade through ISSU

Hi,
I am having 2 number of cisco 4500x switch and configured with VSS
so one switch is active and another switch is standby.
I am panning to upgrade IOS through ISSU
i read in document that it required auto boot enable in switch.
My switch current Configuration register = 0x2101
do i need to change config register or this will ok. If need to change then what will be auto boot and after IOS upgrade do i need to change it again.
Please help....

Hello Tarun,
Please find below the steps to perform the ISSU:
ISSU Prerequisites
Before one can perform an ISSU, there are a few prerequisites one must verify for a successful ISSU. The following list explains what is initially required.
• Must be using a redundant Cisco Catalyst 4500 switch with symmetric hardware (that is, supervisors, memory, rommon, NFL daughter card, and so on).
• Both new and old Cisco IOS Software images must be preloaded to the file system on both supervisors.
• SSO must be configured and working properly.
• Config register must be configured to autoboot (that is, the value should have a "2" in the lowest byte).
45010R-203# sh bootvar | i register
Configuration register is 0x2102
Standby Configuration register is 0x2102
Several commands are available to verify if SSO is enabled:
4510R-203# sh module | b Redundancy
Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+-------------------
1   Standby Supervisor   SSO                  Standby hot
2   Active Supervisor    SSO                 Active
45010R-203# sh redundancy states
       my state = 13 -ACTIVE
     peer state = 8   -STANDBY HOT
           Mode = Duplex
           Unit = Secondary
        Unit ID = 2
Redundancy Mode (Operational) =  Stateful Switchover
Redundancy Mode (Configured)  =  Stateful Switchover
Redundancy State              =  Stateful Switchover
             <snip>
4507R-ISSU# sh run | b redundancy
redundancy
mode  sso
As a step prior to the beginning of the ISSU process, the new version of the Cisco IOS Software image needs to be loaded into both the active and standby supervisors' file systems. Both active and standby supervisor need to contain both the new and old images in the file system. In order to store both new and old images, the supervisors should be upgraded to contain sufficient amounts of flash memory prior to the ISSU process.
The new images can be downloaded into both supervisors using commands such as:
copy tftp: bootflash:
copy tftp: slavebootflash:
The example below illustrates this verification:
4510R-203#dir
Directory of bootflash:/
1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
4510R-203#dir slavebootflash:
Directory of slavebootflash:/
1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
Once this check is verified, one can now proceed with the ISSU process.
The ISSU process is started by typing the "issu loadversion" command on the active supervisor. This command directs the active supervisor to begin the ISSU process. The active supervisor, through intersupervisor communications, checks that the requested image has been downloaded into both the active and standby supervisors' file systems. If the required images are not present, the command is rejected, and an appropriate warning is generated.
If the "issu loadversion" command is successful, the switch transitions into the "Load Version" ISSU state. The standby supervisor will reset and boot with the new version of the Cisco IOS Software image loaded into the file system.
The following actions take place when the command is implemented:
1. The standby supervisor (B) is reset.
2. The standby supervisor (B) is booted with the new Cisco IOS Software image: Release 12.2(31)SGA1.
3. If both Cisco IOS Software images are declared as compatible, the standby supervisor moves into SSO mode and is fully stateful for all compatible clients and applications. Compatibility allows for in-service software upgrade or downgrade between two versions to succeed with minimal service effect.
4. If both Cisco IOS Software images are incompatible, the system moves into RPR mode, and the ISSU process is terminated with an appropriate message to the user. Images are declared incompatible when "required" clients or applications are not interoperable between two Cisco IOS Software releases.
5. Standby "B" reaches the standby HOT state.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
7. The "issu loadversion" command also supports a "forced" option that allows the operator to force the system into entering RPR mode when incompatibility is detected.
Note: When performing an ISSU, disable manual switchovers. Performing manual switchovers during the issu process is strongly discouraged. The current implementation does not prevent it, but it does display a warning to the user.
An example of the CLI for implementing the issu loadversion command is displayed below.
On the active supervisor, one would issue the following command:
4510R-203#issu loadversion 1 bootflash:cat4500-entservices-mz.122-31.SGA1 2 slavebootflash: cat4500-entservices-mz.122-31.SGA1
Syntax - issu loadversion active-slot active-image-new standby-slot standby-image-new
The second step of the ISSU process is to perform the issu runversion CLI.
The user can issue the " issu runversion" command when:
1. The ISSU state is "Load Version"; this can be verified with the "show issu state detail" CLI.
2. The standby supervisor is running the new version of the software.
3. The standby supervisor has moved into the "Standby Hot " state.
The following actions take place when the " issu runversion" command is executed:
1. A switchover occurs; that is, the standby (B) becomes the new active, and the old active (A) is rebooted and comes up as a standby.
2. A timer called "Rollback Timer" is started with a previously configured value.
3. Move both supervisors to "Run Version" state.
4. If the command "issu acceptversion" is not issued before the "Rollback timer" fires, then the entire ISSU process is aborted via the automatic rollback.
5. If the active supervisor console connectivity is established and the "issu acceptversion" command is issued, then the rollback timer is stopped.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
An example of the CLI for implementing the issu runversion command is displayed below:
On the active supervisor, one would issue the following command:
4510R-203#issu runversion 2 slavebootflash:cat4500-entservices-mz.122-31.SGA1
Syntax - issu runversion standby-slot [standby-image-new]
Prior to issuing the `issu acceptversion' command the system will be counting down the rollback timer. If `issu acceptversion' is not completed before rollback timer expires an automatic abort will occur. This command stops the "Rollback Timer." This command serves as a feedback mechanism. This is an optional command and can be skipped in the ISSU process with the "issu commitversion" CLI.
If this command is not issued within 45 minutes (default) from the time the standby supervisor moves into the "Standby Hot" state, it is assumed that the new active supervisor is not reachable and the entire ISSU process is rolled back to the previous version of the software. The acceptversion is not intended for long-term network operation. It is also important to note that none of the features available on the new version will work yet.
The following actions take place when the command is implemented:
1. The "Rollback Timer" is terminated. This means that the rollback timer is not looked at anymore. Therefore, the system can run in this state for an extended period.
2. The user has an option to abort the ISSU process by issuing the command "issu abortversion."
Aborting the ISSU process now causes the newly active supervisor (B) to fail over to the standby supervisor (A) running the old image and will also cause the rebooting supervisor (B) to load the original image. The issu acceptversion halts the rollback timer and helps ensure the ISSU process is not automatically aborted during the process.
An example of the CLI for implementing the issu acceptversion command is displayed below:
On the "New" active supervisor, one would issue the following command:
4510R-203#issu acceptversion 2
% Rollback timer stopped. Please issue the commitversion command.
Syntax - issu acceptversion active-slot-number
This is the last stage of the ISSU procedure. Once the user is satisfied with the new version of software, this must be committed by issuing the "issu commitversion" command. This command resets the standby supervisor and boots it with a new version of the software (same as the active supervisor). This concludes the ISSU process, and the new version of software is permanently committed on both supervisors. Since this is the conclusion of the ISSU process, the system can not be reverted back to the previous version of the software from this point onward as a part of this upgrade cycle. However, if for any reason users wish to go back to the previous version of the software, they can do so by starting a new upgrade/downgrade process.
The following actions take place if the command is implemented:
1. The standby supervisor (A) is reset and booted with the new version of Cisco IOS Software image.
2. The standby supervisor (A) moves into the "Standby Hot" state in SSO mode and is fully stateful for all clients/applications that are compatible.
3. Both supervisors are moved into "Final State," which is the same as "Initial State."
4. Users can initiate switchovers from this point onward.
An example of the CLI for implementing the issu commitversion command is displayed below:
4510R-203#issu commitversion 1
Syntax - issu commitversion standby-slot-number
ISSU Process: issu abortversion
One can abort the ISSU process at any stage manually (prior to issuing the issu commitversion command) by issuing the exec-level issu abortversion command. The ISSU process also aborts on its own if the software detects a failure.
If a user aborts the process after issuing the issu loadversion command, then the standby supervisor engine is reset and reloaded with the original software.
If the process is aborted after a user enters either the issu runversion or issu acceptversion command, then a second switchover is performed to the new standby supervisor engine that is still running the original software version.
The supervisor engine that had been running the new software is reset and reloaded with the original software version. The command is accepted only in "Load Version" or "Run Version" states. In "Load Version" state, the active supervisor is running an old image and the standby supervisor is running new image.
Syntax - issu abortversion active-slot [active-image-new]
Let me know if you have any questions.

New ios upgrade issue

Similar Messages

Maybe you are looking for