1. senarc's Avatar
    I've done all the prerequisites, Android SDK & USB drivers. While bootloader screen is on phone, I enter, from the "platform-tools" directory, into the command window, "Flashboot Devices" and the serial number is returned as expected. When I enter "Flashboot Flashing Unlock", a list of commands are returned in the command window and nothing happens on the phone. Listed, with the other stats, on the bootloader screen of the phone, it says "Device is LOCKED". No matter what I do, I cannot get past this point. I then tried to run in the command window, "fastboot flash recovery twrp-2.8.7.2-angler.img" and it returned:
    sending 'recovery' (16880 KB) ... OKAY
    writing 'recovery' ... FAILED (remote: device is locked. Cannot flash images)

    Any clues on how to get past this point?

    Thanks
    11-22-2015 04:18 PM
  2. davey11's Avatar
    Same thing happened to me. Leads me to believe the SDK itself is not recognizing the flashing command. My SDK is pretty old version.

    I just gave up and did it with skipsoft's toolkit. First time using skip's. It worked fine.

    6p 👌
    11-22-2015 04:35 PM
  3. mustang02's Avatar
    Update your sdk tools.


    The command is

    Fastboot flashing unlock
    11-22-2015 05:10 PM
  4. C5Longhorn's Avatar
    I had the same issue and it turned out be that I didn't have the latest adb tools.

    I had to download the latest version from Google and then it worked like a charm.

    Make sure you are using version 1.0.32 (I was on 1.0.31).

    Also, the command is fastboot flashing unlock

    Rick

    Posted via the Android Central App
    11-22-2015 05:14 PM
  5. segler's Avatar
    Agree. If you use the older adb, the command is fastboot oem unlock. With the newer adb, the command is fastboot flashing unlock.

    Why they had to change that is beyond me.
    11-22-2015 09:30 PM
  6. mustang02's Avatar
    Agree. If you use the older adb, the command is fastboot oem unlock. With the newer adb, the command is fastboot flashing unlock.

    Why they had to change that is beyond me.
    But the old command doesn't work on our new phones. They changed it with the security.
    11-22-2015 09:34 PM
  7. senarc's Avatar
    Thanks, that was the problem. However, now after doing the final step of rooting my n6p, I flashed the file "BETA-SuperSU-v2.52.zip" and selected Reboot. They say it may take a few minutes, but my phone has been rebooting now for the past 30 minutes. It just keeps showing 4 colorful circles spinning as it normally does during booting, but it won't get past that point. Should I use a different file for rooting? Not sure what else to do...
    11-22-2015 11:17 PM
  8. C5Longhorn's Avatar
    You have to first install the new boot.img file, then install root 2.52.

    Check out Heisenberg's sticky thread on XDA under the 6p general section.

    I just installed TWRP and rooted my 6p about an hour ago. I just finished taking a Nandroid backup and Ti backup.

    Posted via the Android Central App
    11-22-2015 11:50 PM
  9. BillA#AC's Avatar
    I've done all the prerequisites, Android SDK & USB drivers. While bootloader screen is on phone, I enter, from the "platform-tools" directory, into the command window, "Flashboot Devices" and the serial number is returned as expected. When I enter "Flashboot Flashing Unlock", a list of commands are returned in the command window and nothing happens on the phone. Listed, with the other stats, on the bootloader screen of the phone, it says "Device is LOCKED". No matter what I do, I cannot get past this point. I then tried to run in the command window, "fastboot flash recovery twrp-2.8.7.2-angler.img" and it returned:
    sending 'recovery' (16880 KB) ... OKAY
    writing 'recovery' ... FAILED (remote: device is locked. Cannot flash images)

    Any clues on how to get past this point?

    Thanks

    You must first enable OEM Unlock under Settings > Developer Options.
    If Developer Options doesn't show then go to Settings > Info/About Phone > tap the Build line 7 times quickly then go back to Settings > Developer Option and enable OEM Unlock and USB Debugging. After that you should be able to send flash unlock commands (some may fail but at least one should work):
    fastboot oem unlock
    fastboot flashing unlock
    fastboot flashing unlock_critical

    Then finally send your flashing command
    Laura Knotek likes this.
    06-23-2018 04:41 PM

Similar Threads

  1. Gmail passcode unlock help
    By AC Question in forum Ask a Question
    Replies: 1
    Last Post: 11-23-2015, 01:59 PM
  2. How long does it take to go into Doze mode?
    By PaulQ in forum Nexus 6P
    Replies: 3
    Last Post: 11-22-2015, 07:18 PM
  3. Replies: 6
    Last Post: 11-22-2015, 05:44 PM
  4. how to protect bezel
    By noteiii007 in forum Samsung Gear S2
    Replies: 1
    Last Post: 11-22-2015, 04:17 PM
  5. How do I get the lock screen to stay dark?
    By AC Question in forum Displays
    Replies: 0
    Last Post: 11-22-2015, 03:49 PM
LINK TO POST COPIED TO CLIPBOARD