iOS 7.1 and iPhone 4/4s - corrupt system file or incapacitating passcode bug?

Question

Level 1

0 points

iOS 7.1 and iPhone 4/4s - corrupt system file or incapacitating passcode bug?

Anybody having issues with your iPhone 4/4s after iOS 7.1? If no, have you successfully enabled an alphanumeric passcode longer than four characters and been able to log back in after locking it?

Have been eagerly anticipating an iOS update, so when iOS 7.1 was made available it was downloaded and applied on the same night - admittedly a huge mistake; should have exercised caution and patience: the 4s device started rebooting repeatedly. Several times I was able to access the settings and been battling over a week with the device. Tried to restore the 4s in a variety of ways including erasing all content and settings, putting it in a recovery mode, and performing a backup from iTunes - the latter was attempted on two different machines just in case the original iOS 7.1 download was corrupted; however, that did not resolve the issues. Had also noticed that when [Wallpapers & Brightness] was pressed from [Settings] it was automatically triggering a reboot. The last time I was able to access the Settings, I had enabled an alphanumeric passcode. When it was time to unlock it the keyboard was partially rendered

Currently, every time I attempt to enter a passcode the device reboots before completing the proper entry of the code. Moreover, the backspace and the space automatically trigger a reboot. iTunes requires authorization from the device itself but since I can no longer log back in it is not accessible by it. Consequently, the device is unusable...

Btw. had updated my wife's iPhone 5 with iOS 7.1 enabling a 4-digit passcode (not an alphanumeric) - it worked OK.

Ref. sample segments from the 4s logs:

awd-2014-03-13-000100-747.c

awd-2014-03-13-000729-749.c

awd-2014-03-13-000100-751.c

model: "iPhone4,1"

softwareBuild: "11D167"

firwareVersion: "iBoot-1940.10.58"

basebandVersion: "5.2.00"

LatestCrash-SpringBoard.ips

{"name":"SpringBoard","bug_type":"109","os_version":

"iPhone OS 7.1 (11D167)", "bundleID":"com.apple.springboard",

"version":"50 (1.0)", "app_name":"SpringBoard"}

Hardware Model: iPhone4,1

Process: SpringBoard [1792]

Path: /System/Library/CoreServices/SpringBoard.app/

SpringBoard Identifier: com.apple.springboard

Version: 50 (1.0)

Code Type: ARM (Native)

Parent Process: launchd [1]

Date/Time: 2014-03-15 13:41:25.687 -0400

OS Version: iOS 7.1 (11D167)

Report Version: 104

Exception: Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Subtype: KERN_INVALID_ADDRESS at 0x00000024

Triggered by Thread: 0

Thread 0 Crashed:

0-15 SpringBoard

16,17 CoreFoundation

18 Foundation

19-24 SpringBoard

25-27 libdispatch.dylib

28-31 CoreFoundation

32 GraphicsServices

33 UIKit

34 SpringBoard

35 libdyld.dylib

Thread 1:

0 libsystem_kernel.dylib

1,2 libdispatch.dylib

Thread 2:

0 libsystem_kernel.dylib

1 libsystem_platform.dylib

2 libdispatch.dylib

3 EventKit

4,5 CalendarProvider

6-10 libdispatch.dylib

11,12 libsystem_pthread.dylib

Thread 3:

0,1: libsystem_kernel.dylib

2-5 CoreFoundation

6,7 Foundation

8 UIKit

9 Foundation

10-12 libsystem_pthread.dylib

Thread 4:

0 libsystem_kernel.dylib

1 libdispatch.dylib

2-9 BulletinBoard

10-14 libdispatch.dylib

15,16 libsystem_pthread.dylib

Thread 5 name: com.apple.coremedia.player.async

Thread 5:

0 libsystem_kernel.dylib

1 libdispatch.dylib

2 MediaToolbox

3 CoreMedia

4-6 libsystem_pthread.dylib

Thread 6

0 libsystem_kernel.dylib

1 libdispatch.dylib

2 MailServices

3,4 MailDataProvider

5-7 BulletinBoard

8 libdispatch.dylib

9,10 BulletinBoard

11-13 libdispatch.dylib

14,15 libsystem_pthread.dylib

[up to thread 18]

Thread 0 crashed with ARM Thread State (32-bit):

r0: 0x00000000

r1: 0x00000024

r2: 0x00000009

r3: 0x0000001e

r4: 0x27d4a568

r5: 0x00000000

r6: 0x00000000

r7: 0x27d4a488

r8: 0x40000000

r9: 0x00000fff

r10: 0x1815cd00

r11: 0x16d80a60

ip: 0x3c772200

sp: 0x27d4a474

lr: 0x3a2103ad

pc: 0x0028a518

cpsr: 0x60000030

Binary Images:

[...]

SpringBoard_2014-03-15-13394...

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Subtype: KERN_INVALID_ADDRESS at 0x00000024

Triggered by Thread: 0

...

Thread 0 crashed with ARM Thread State (32-bit):

r0: 0x00000000

r1: 0x00000024

r2: 0x00000009

r3: 0x0000000a

r4: 0x27d04568

r5: 0x00000000

r6: 0x00000000

r7: 0x27d04488

r8: 0x40000000

r9: 0x00000fff

r10: 0x177d7200

r11: 0x15d66030

ip: 0x3c772200

sp: 0x27d04474

lr: 0x3a2103ad

pc: 0x002d0518

cpsr: 0x60000030

SpringBoard_2014-03-15-13412...

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Subtype: KERN_INVALID_ADDRESS at 0x00000024

Triggered by Thread: 0

...

Thread 0 crashed with ARM Thread State (32-bit):

r0: 0x00000000

r1: 0x00000024

r2: 0x00000009

r3: 0x0000001e

r4: 0x27d4a568

r5: 0x00000000

r6: 0x00000000

r7: 0x27d4a488

r8: 0x40000000

r9: 0x00000fff

r10: 0x1815cd00

r11: 0x16d80a60

ip: 0x3c772200

sp: 0x27d4a474

lr: 0x3a2103ad

pc: 0x0028a518

cpsr: 0x60000030

stacks+SpringBoard-2014-03-15...

{"os_version":"iPhone OS 7.1 (11D167)",

"bug_type":"188"}

Hardware Model: iPhone4,1

OS Version: iPhone OS 7.1 (11D167)

Kernel Version: Darwin Kernel Version 14.0.0: Fri Feb 21

10:33:44 PST 2014; root:xnu-2423.10.67~1/

RELEASE_ARM_S5L8940X

Date: 2014-03-15 13:41:44 -0400

Exception Code: 0xfaded321

Reason: Watchdog timeout: 120.028519s since last successful ping: 2400m0/0 2400m0/1...

Thermal data unavailable

Frontmost process PID: 1802

Jetsam Level: 0

Free Pages: 43400

Active Pages: 8495

Inactive Pages: 19011

Purgeable Pages: 2

Wired Pages: 22280

Speculative Pages: 35105

File-backed Pages: 25690

Compressions: 0

Decompressions: 0

Compressor Size: 0

Busy Buffer Count: 1

Pages Wanted: 0

Pages Reclaimed: 0

Process 0 info:

resident memory bytes: 75001856

page faults: 5343

page-ins: 0

copy-on-write faults: 0

times throttled: 1869

time did throttle: 678

user time in task: 91475.094641 seconds

system time in task: 0.000000 seconds

thread 0x1 TH_WAIT|TH_UNINT 0x8037aa6c

thread priority: 92

Base thread priority: 92

thread sched flags: none

kernel cont: 0x800fe309

user time in thread: 20.316492 seconds

system time in thread: 0.000000 seconds

Process: SpringBoard [1792]

Path: /System/Library/CoreServices/SpringBoard.app/

SpringBoard Identifier: com.apple.springboard

Version: 50 (1.0)

Code Type: ARM (Native)

Parent Process: launchd [1]

iPhone 4S, iOS 7.1

Posted on Mar 18, 2014 8:38 AM

Reply

Answer 1

Top-ranking reply

makgi Author

Level 1

0 points

Mar 22, 2014 1:52 PM in response to makgi

Updates and resolution:

Had re-attempted a restoration of a 4s backup to an iPhone 4, thus the phone got updated to 7.1 but when it was done it was exhibiting the same reboot symptoms minus the passcode issues (after a restore that needs to be set up again). Attempted a reset by holding the Sleep/Wake and Home buttons for 10sec, then connected it to iTunes. The key difference: this time it was "Set Up as New iPhone". Then added a second keyboard and a alphanumeric passcode: tested it OK. After three days of light usage it has not crashed. At this point I am assuming the whole ordeal was due to a corruption propagated by image backups.

Q: does a backup image contain any system files?

Proceeded to reset my stubbornly uncooperative 4s, after several lengthy tries it got reset and also setup as a new iPhone. No apps have been added - it has been sitting idle for three days. There has been no crash but all the apps, accounts, configs etc have to be manually re-applied. Considering the previous issues reported as resolved.

Reply

Answer 2

Rectify

Level 1

0 points

Mar 22, 2014 4:14 PM in response to makgi

i have been receving problems too. prior to my update from ios 5.1.1 to ios 7.1, it was working well.when i updated it when i went to sleep via my phone,when i woke up the next morning it went into recovery mode by itself.Could I do anything other than restore to get my phone to work functionally again?

Reply

Answer 3

makgi Author

Level 1

0 points

Mar 22, 2014 6:32 PM in response to Rectify

No, unfortunately you'll have to go through a Restore but luckily you won't have to rebuild it from scratch:

Update your iTunes to the most up to date version, then connect it, you'll probably see the relevant message confirming that's in Recovery Mode, select the Restore in the Summary page, then it should give you an option to perform a Backup, perform the Restore, the phone should display a progress bar, when that is done select the most recent backup (it will let you know that that there's a more recent version available, if you select a different one), and then leave it running for as long as it takes -- it might take up all night...

Reply

Answer 4

makgi Author

Level 1

0 points

Mar 22, 2014 6:37 PM in response to makgi

In answer to my previous question regarding the presence of system files in the backup image - the answer is affirmative, a backup would have some system files but not ones related to an iOS update...

Reply