Nexus Root Toolkit 2.0.5 is out – Now with Proxy Support

New version of Nexus Root Toolkit is now out.  I rebuilt the entire downloader system to be based off a wget instead of AutoIT’s in-built InetGet functions.  This should improve overall reliability and also enabled me to code in proxy support.  Many international users, and people who wanted to use NRT at work were unable to do so smoothly because of network restrictions, now it’s possible to configure proxy settings so all the auto-downloading and updating is done through that instead.  You will see a new section in the toolkits options menu where you can setup proxy config:

Check out the full changelog for the other changes in this release.

And head over to the main download page to grab it.

 

Enjoy! ^_^

{{ WugFresh }}

New LMY47I Builds For N5 and N6 Added

Factory images for LMY47I 5.1.0 were just released for the Nexus 5 (hammerhead) and Nexus 6 (shamu).

I just updated the NRT masterlists now to extend full automated support for this new build.

To update, just hit use the “Automatic update” (hotkey Ctrl+U) or “Import Update Pack” from the Update menu:

That’s it!

Quick Tip: In the future, “Other/Browse” feature in flash stock can be used to flash new builds before I even update the masterlists.  Also, setting your build to “Any Build” should always work for rooting.

“Enable OEM Unlock” setting auto disables on N6 and N9

On the Nexus 6 and Nexus 9, some of you may have noticed that the “Enable OEM Unlock” security setting in developer options seems to auto-reset to disabled.

I asked around and found more info about this behavior.  The auto-resetting of “Enable OEM Unlock” to disabled is an intentional security feature by Google, and it happens after a certain number of reboots.

Significance? Nothing you need to worry about, or constantly keep trying to re-enable once you are unlocked already.

If you are unlocked already, its fine if “Enable OEM Unlock” is disabled.

Just make note of this setting and behavior if you intend on relocking your bootloader (which should only be done if you are reselling/returning).  More specifically, if you plan on relocking, you should first flash stock, and make sure everything is running smoothly, so if you need to re-enable this setting to unlock again, you can do so easily.

Quick Tip: Re-locking the bootloader is not required for receiving OTA updates.

Main point: don’t bother relocking your bootloader unless you absolutely need to, and are sure your device is healthy before doing so.

I will be adding a little notice about this in the relock info message in the kit in the up-coming v2.0.5 release.

Stay tuned, and happy flashing.

 

{{ WugFresh }}