https://github.com/CruelKernel/backtothefuture

OS Patch Level changer for Android Boot && Recovery partitions
https://github.com/CruelKernel/backtothefuture

android boot os-patch-level recovery rollback-protection twrp

Last synced: about 1 year ago
JSON representation

OS Patch Level changer for Android Boot && Recovery partitions

• Host: GitHub
• URL: https://github.com/CruelKernel/backtothefuture
• Owner: CruelKernel
• License: lgpl-3.0
• Created: 2020-04-20T19:30:05.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2020-11-11T21:39:05.000Z (over 5 years ago)
• Last Synced: 2024-10-24T00:21:14.519Z (over 1 year ago)
• Topics: android, boot, os-patch-level, recovery, rollback-protection, twrp
• Language: C
• Homepage:
• Size: 14.6 KB
• Stars: 11
• Watchers: 2
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: change_os_version.c
  • License: LICENSE

Awesome Lists containing this project

README

          
# Back to the Future

OS Patch Level changer for boot and recovery partitions. Flash in TWRP. You can set desired date in filename. Date format: YYYY-MM. For example: backtothefuture-2021-12.zip If there will be no date in the filename, max possible date 2127-12 will be used. If you select a wrong date, then don't reboot, rename the zipfile and flash it again.

Downloads: https://github.com/CruelKernel/backtothefuture/releases

If someone wants to know more about why it's not possible to rollback to normal date, here is the official documentation: https://source.android.com/security/keystore/version-binding#hal-changes. Short answer: because all your security keys are cryptographically updated with new os_patch_level date once you boot with "new date" kernel.

So, once you installed a kernel with os_patch_level in future you are doomed to use greater or equal os_patch_level date for all your next kernels. However, full wipe will help.