Update: Unfortunately, this exploit no longer appears to be working. People are having trouble flashing the appropriate firmware and cannot get back to an unlock state, so this method does not currently work and we don’t recommend using it. A new method is in the works.
When XDA Elite Recognized Developer AdamOutler released the bootloader unlock for the Verizon Galaxy Note II, most assumed this heralded the end of unlock struggles with the device. However, users have been heading back to the forums in a small panic because the bootloader managed to re-lock itself. Always ready to jump on such a matter, AdamOutler has already released a fix.
A symptom of the re-lock is users getting an understandably frightening message saying to return their devices to Verizon. Thankfully, no such thing is needed, and a fix is already available. Here is Adam’s take on the subject:
Previously unlocked devices will display a clear message instructing users to return the device to Verizon. Don’t do it. The OTA just relocked your device. Flash back to the provided bootloader baseline with this PIT file, then unlock as usual.
Apparently, what’s going on is that Verizon has been sneaking new bootloaders onto devices via over-the-air updates. This replaces the hacked bootloader and re-locks it. According to Adam, this is because it refreshes the Samsung keys that were broken during the initial unlock. While it may sound alarming, re-hacking the bootloader is pretty simple.
As AdamOutler stated, the easiest way to fix this problem is to flash a bootloader baseline and PIT file that are provided by Adam in the link below using Odin 3. Then, it’s a matter of using CASUAL to unlock the device again. It’s exactly the same method as the first time around. If you can’t remember, we’ve posted Adam’s unlock video at the bottom and Adam links to the original unlock in the thread (also linked below).
For the full details and the download link for the tools needed, check the original thread.