![]() ![]() This happens because the kernel verifies the rootfs as each block is read from the SSD, so it may not encounter a modified block until sometime later. If you've made changes to the rootfs partition but not the kernel, the Cr-48 may appear to boot normally, but may later suddenly reboot and/or display the recovery screen. You'll have to create a recovery USB drive to restore your Cr-48 to the factory condition. If you've made changes to the kernel partitions, the Cr-48 will refuse to boot that kernel and will display a recovery screen. If you haven't modified the original kernel or rootfs partitions in any way, you should have no problems. Second, verified boot will be enabled, meaning that only Google-signed images will be bootable. This is a much faster erase process than when enteringĭeveloper mode, usually only 30 or 40 seconds, and only happens with the In normal mode after leaving developer mode, the stateful partition willīe erased. There are a couple of things to note, however.įirst, assuming you haven't modified anything, the first time you boot Returning to normal mode is as simple as entering developer mode: shut down, remove the battery, flip the switch, reboot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |