This is new Bug most dangerous bug which brick your iPhone completely.
How to replicate the 1st Jan 1970 bug:
This bug is being seen in iOS 8 – iOS 9.3 beta and only on 64-bit devices, I recommend that you do not try it as it fully bricks your device, you are not able to enter DFU mode, nor recovery mode, you will have to send your device to Apple, who will fix it even if it is not under a warranty as it is a software error, not hardware one. Some users are reporting that it isn’t working on their devices, mainly 6s users, however I still recommend that you do not try it.
The only known solution is removing your device’s battery, which is obviously not easy to do on Apple devices. Removing the battery resets the device’s PRAM, Parameter Random Access Memory and the SMC, System Management Controller. The PRAM holds the date and time information and is non-volatile, therefore needs all it’s power to be lost for it to be reset.
/u/Ziph0n has released a tweak on his repo called ‘BrickingDate’:
‘It prevents malicious users from replicating this “bug” manually. (The date can still be changed programmatically, but common users (bad friends…) can’t change the date this way)’
Reference:
http://blog.lfcameron7.xyz/2016/02/11/1st-jan-1970-64-bit-ios-bug/
Your Good comments Encourages me to keep posting Nice Articles so keep Commenting & Sharing
DANGER, Do NOT Try this. New iOS 9 & iOS 8 Bug Completely Bricks Your iPhone, iPad or iPod. Restoring Won't Fix This.
- Simply open Settings
- Go to General -> Date and Time
- Uncheck ‘Set Automatically’
- Change the date to 1st Jan 1970 (Scroll up to get to year 2000, then go back, into date settings again, repeat until it reaches 1970)
- Reboot
- Your Device should be bricked.
Why does this happen?This is to do with something called ‘Unix Time‘, Unix Time is simply a way to track time, counting only in seconds. Unix Time counts the number of seconds that have elapsed since 1st Jan 1970 and is used universally across the world of technology. So therefore changing the date to 1st Jan 1970 would set this Unix Time to a value of ‘0’. Now, the bricking could be caused by the fact that iOS is dividing by this value to calculate the time and date and we all know that diving by 0 = RIP, it will cause a fault in the kernel which will make the device unable to boot. On the other hand, this could be due to using an unsigned int to represent the value, an unsigned int can only be using to hold values of positive numbers, and after calculations executed to calculate the date & time, the value could end up as a negative number.
This bug is being seen in iOS 8 – iOS 9.3 beta and only on 64-bit devices, I recommend that you do not try it as it fully bricks your device, you are not able to enter DFU mode, nor recovery mode, you will have to send your device to Apple, who will fix it even if it is not under a warranty as it is a software error, not hardware one. Some users are reporting that it isn’t working on their devices, mainly 6s users, however I still recommend that you do not try it.
The only known solution is removing your device’s battery, which is obviously not easy to do on Apple devices. Removing the battery resets the device’s PRAM, Parameter Random Access Memory and the SMC, System Management Controller. The PRAM holds the date and time information and is non-volatile, therefore needs all it’s power to be lost for it to be reset.
/u/Ziph0n has released a tweak on his repo called ‘BrickingDate’:
‘It prevents malicious users from replicating this “bug” manually. (The date can still be changed programmatically, but common users (bad friends…) can’t change the date this way)’
Reference:
http://blog.lfcameron7.xyz/2016/02/11/1st-jan-1970-64-bit-ios-bug/
Your Good comments Encourages me to keep posting Nice Articles so keep Commenting & Sharing