How to Lock (re-lock) my Nextbit Robin?

Hello Nextbit user community,

I purchased a Nextbit Robin from a seller about a year ago and it shipped unlocked (every time you turn it on/restart it there's a black caution screen that states the device has been tampered with and it is unlocked), the phone boots up fine after the warning and I like the phone so far, bought it because i wanted a decently powerful phone for a budget that i can use on my carrier network Metro PCS (T-Mobile). Since I got rthe sim and activated it works fine but I want to use G Pay and other NFC services that require that phone wasn't "tampered" with. I'm a little confused on how to do this successfully and correctly. Is there a way to "re-lock/Lock the phone?. Does it interfere with my sim/data/cell service? will it wipe everything on the phone?

Basically I'm asking for some help on doing this because I really want enable G Pay, Can anyone give me me a super detailed and technical step-by-step on how to do this SAFETY without bricking my phone? I'd really appreciate it thanks a bunch.

 

1. You have to setup adb and download and install nextbit usb driver on ur PC.
2. On ur robin go to developer options and enable usb debugging and oem unlocking
3. Connect your robin to PC
4. A prompt will appear on ur robin asking for the permission to allow changes via PC, allow it
5. Open command window in abd folder by pressing shift + right click and type "adb devices"(if this does not work type ".\abd devices" if this is the case then u have to type ".\" before every command)
5. On ur robin go to fastboot mode(first power off ur robin and then press and hold power + volume down button untill the fastboot window appears)
6. On ur PC, in command window type "fastboot -i 0x2c3f oem lock-go"

Note: this will delete all the files you have on ur robin so take a backup before following these steps

Via adb commands u can also use some apps like navigation gestures and custom navigation bar by giving them access to secure settings

 

Thanks so much for answering! A few question though. Do I need to "flash to stock"? Do I need any factory images of the Nextbit Andriod version? What "adb" do you recommend i download? The one from the Andriod website, just the command tools only? (sdk-tools-windows-4333796.zip) or something else?

This guy has a video on it but doesn't mention what adb to download and does a "flash" process first before what you mentioned, is this required (lol i just want to do it the right way) :

 

U do not need to flash
U can download adb here https://developer.android.com/studio/releases/platform-tools
Extract it in a specific folder and in this folder u have to open command window

 

oh wow thank you again! I just download the adb/sdk tool for windows and I'm going to try your instructions super soon after i back up my stuff and get over my nervousness. (first time trying this bear with me lol!)

a few side questions; is there a difference between the command: " 'fastboot -i 0x2c3f oem lock-go' " and 'fastboot -i 0x2c3f oem lock' " ?

Also, for Step 5a when I type adb devices ,am I just confirming the device is recognized first then i go directly to 5b or should i turn it off, turn to fastboot mode then plug it back it to PC, or just keep it connected after Step 3 and through out the whole process? I ask because the video I linked shows something different.

I just Extracted the zip to my desktop open the platforms-tools folder and reveled some files, i held shift and right clicked and i'm only seeing a "Open PowerShell window here". Is this the same as a "Open Command window here" option?

 

Yes it is

 

ok cool thanks again! re-posting this previous post in case you didn't see:

So I just download the adb/sdk tool for windows and I'm going to try your instructions super soon after i back up my stuff and get over my nervousness. (first time trying this bear with me lol!)

-a few side questions; is there a difference between the command: " 'fastboot -i 0x2c3f oem lock-go' " and 'fastboot -i 0x2c3f oem lock' " ?

-Also, for Step 5a when I type adb devices ,am I just confirming the device is recognized first then i go directly to 5b or should i turn it off, turn to fastboot mode then plug it back it to PC, or just keep it connected after Step 3 and through out the whole process? I ask because the video I linked shows something different.

 

adb devices command is to check if the PC recognises the smartphone and changes can be made

fastboot oem lock/unlock
fastboot -i 0x2c3f oem lock-go
fastboot -i 0x2c3f oem lock
First command works on every other device and the rest two only works on robin

 

tried both adb device commands pressed enter and both don't work, it also said the USB device malfunctioned and is not recognized when I plug it in

this is what comes up after i press enter:
.\abd : The term '.\abd' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ .\abd devices
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (.\abd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Windows says the last device you plugged in malfunctioned and windows doesn't recognize it, I'm pretty sure downloaded the right Usb driver, I'm currently stuck.

 

Its adb not abd

 

omg ok so just tried adb first then .\adb, adb again and then .\adb and got this:

PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
NBQGLMBXXXXXXXXX unauthorized

PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\adb devices
List of devices attached
NBQGLMBXXXXXXXXX device

so now that I know it only reads commands the start with ".\". So the next step would be (with the phone still plugged in the PC) to turn off phone, enter fastboot mode and then enter this command into PowerShell ".\fastboot -i 0x2c3f oem lock" and press enter, correct? This will also wipe my files and reset to Nougat 7.1.1.?

 

Yes

 

Thanks for replying, I'm going to try this out as soon as I get home. Does the USB mode matter or no? Should it be on file transfer (MTP), photo transfer, or charging only? It's funny because I think the original USB cable was the cause of the device not being able to be recognized I changed the cable and haven't received that notification.

 

No usb mode doesn't matter

 

I'd figured I'd mention this before I start, there was an OTA update for the the phone as soon after I got it on the mail in January (7.1.1 I believe?), that I downloaded while the phone was unlocked, will that interfere with locking the bootloader? Will it go back to the previous versions (not 7.1.1) after the reboot? I ask because every guide seems to do this a different way for the Robin, in the video above the guy uses the factory image stock files to lock the phone.Do the adb folder and factory image fike folder (in the video) contain the same script/files need to lock the phone back to stock?

 

You are already on stock software u just need to lock it

 

PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\fastboot -i 0x2c3f oem lock
C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools\fastboot.exe: unknown option -- i
PS C:\Users\Stephan\Desktop\platform-tools_r28.0.0-windows\platform-tools>

This is what happened when i pressed enter, did i miss something? Do I install the full Google ADB pack ,not just to tools? Did I install the Nextbit Driver wrong, says it's there?

 

If in adb window
Your device is recognized then you are using the right driver
Also try all three(One may work)
fastboot oem lock
fastboot -i 0x2c3f oem lock-go
fastboot -i 0x2c3f oem lock

 

Also if u have latest factory images the flash it

If you have a factory image(older than 7.1.1)and u flashed it, do not update via OTA(it will go into bootloop)