05-14-2016 11:10 AM
05-14-2016 11:31 AM
@david Yeah, I kind of figured it wasn't a virus considering no one else had mentioned any problems with it and windows defender couldn't tell me exactly why it was so 'severe'. I went ahead and restarted my computer just in case, redownloaded the exe, and did a check to make sure my phone is recognized as an ADB device, and it is.
05-14-2016 11:37 AM
@david Yep. Gives me a weird name for the device, but it's the Robin. Unplugged, did a check, then replugged in to double check. Even got the toolkit running on admin just in case.
05-14-2016 03:44 PM - edited 05-14-2016 03:54 PM
Well it's telling me oem unlock is not allowed when I force it to, and it won't show up in fastboot devices. Fastboot won't recognize it and i can't use get_identifier_token. Your toolkit does not recognize that adb is installed either or see my device. Adb can see it fine and use all commands but fastboot will not see the device, and no matter what I try I have not been able to get it to see my Robin so far. I will continue trying, but any help is appreciated.
Ninja edit, reinstalling fastboot and adb with a clean machine worked, your toolkit still does not see it and it again is saying oem unlock not allowed.
05-14-2016 04:01 PM
05-14-2016 04:21 PM
You've got it. I can now get fastboot to recognize the phone when starting it from the standalone installation I did but with a regular command prompt it sees nothing. Adb is fine, nothing wrong with it. Here's a screenshot of two command prompts using fastboot while the phone is waiting. I don't know what's wrong but I'll keep giving it a shot. Maybe I can figure it out after work tomorrow.
05-14-2016 04:35 PM - edited 05-14-2016 04:39 PM
That worked, gotta run out of the house now, simple fix, thanks man, appreciate it.