Let's start this with a disclaimer: I do not believe there is significant meaning behind synthetic benchmarks in correlation with real-world use. We've seen, time and again, some high-scoring phones output questionable performance. In this regard, Samsung is one of the usual culprits, and despite having opted for some of the highest spec configurations on each and every one of their flagships, many of them still managed to lag. Other top-tier devices, including the latest Nexus phone and tablet, managed to output...
Verizon Note II Re-Locked? Don’t Panic, Bring a Towel, and Look Here
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.
Want something on the XDA Portal? Send us a tip!
Android 5.0 Lollipop is a great release. It’ has improving usability with material design, given us quick access to our notifications on our home screen, and more. However, there are some very unique idiosyncrasies regarding the notification sounds and silent mode. Basically, it’s not truly silent. In this episode of XDA Xposed Tuesday, XDA TV Producer TK reviews an Xposed Module that helps you truly silence your Lollipop device. XDA Recognized Developer tonyp created the True Silent Mode module. TK shows off...
There are a number of different apps on the Play Store that make browsing the XDA portal and forums a fun experience on mobile, but we want to know: What's your favorite way to access the XDA forums? Do you prefer browsing on the desktop, mobile app, or mobile browser? If you use a mobile app, which one? Let us know how you connect with our community in the comment section below.