[Q] N9 stuck in fastboot, locked and unlockable - Nexus 9 Q&A, Help & Troubleshooting

Hi all,
I tried to reflash a Nexus 9 with official volantis-lrx22c, the bootloader was updated (3.43.0.0114) but the flash of the other partitions failed and now the device can only boot fastboot mode in locked and unlockable state.
When I try to reflash:
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
And when I try to fastboot oem unlock, I get:
(bootloader) ability is 0
(bootloader) Permission denied for this command!
I cannot boot android, so I cannot enable the the "Enable oem unlock"
Before this, I could falsh a recovery and backup, but the recovery disappeared and I cant flash anything anymore...
Any solution? Any way to force the oem unlock or the flash?
I saw this guy, Jonathan Levin, (I cannot post the link) that checked the effects of this "Enable oem unlock" on PST partition and saw one bit was set after, I was wondering if I could use "fastboot oem i2cw" + correct parameters to flip the corresponding bit, but I dont know if it's possible and what are the parameters to pass...
Thanks,
Pierre

I'm in the exact same position today. It's the first time I really fear about a soft-bricked Nexus thanks to the new "Enable OEM Unlock" option.
What has happened afterwards, pierrestone? Did you find a solution? :-|
EDIT: This was likely the article you were talking about. It looks interesting, maybe somehow its possible to enable OEM unlock from an ADB Shell.
newandroidbook.com/Articles/Nexus9.html

Related

impossible to unlock nexus 9 - adb said "no device"

Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
corkiejp said:
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
Click to expand...
Click to collapse
thanks @corkiejp for your reply
I agree with you for fastboot instead of adb but the result is the same.
I cannot go inside the tablet to change parameters
Some forum said that I can Unlock in recovery mode
Is it true?
when my tablet is in recovery mode (On/off + Vol Up)
the tablet show me device state : locked
I am in state HBOOT
the on my computer I do that
C:\Users\maison>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.015s]
finished. total time: 0.018s
after I go in FASTBOOT mode then :
C:\Users\maison>fastboot oem unlock
< waiting for device >
what can I do to have the Key to unlock
No you need fastboot mode to unlock the bootloader!
Is the command "fastboot devices" listing your device. If not check your drivers for your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT4B6JT00881 fastboot
after that i try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload volantis-ota-n9f27m-ad1aee0f.zip
loading: 'volantis-ota-n9f27m-ad1aee0f.zip'adb server is out of date. killing...
* daemon started successfully *
serving: 'volantis-ota-n9f27m-ad1aee0f.zip' (~0%) * failed to read command: Invalid argument
i think tablet i now connected to computer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.011s]
finished. total time: 0.014s
As suspected the option to unlock is not selected in developer options.
If your successful in sideloading an OTA image in recovery mode (not fastboot mode), you will still encounter FRP on booting the device.
Edit: - As said before ADB commands do not work in fastboot mode. And fastboot commands do not work in Recovery mode!
As said before your only hope is to remember your account and password used (or the very last account you used on the device might work).
If you haven't updated the rom in the last year, you maybe able to use FRP Bypass trick.
jackvig said:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
Click to expand...
Click to collapse
You should not have factory reset if you do not know the account password. It is protected by "factory reset protection". To prevent it from being used if it is stolen. You are most likely going to need the password for the account that was logged in when you reset.
Flashing is not going to help. And as mentioned previously, you cannot unlock the bootloader now since you cannot go into developer options and turn on oem unlocking.

FASTBOOT ERROR "FAILED (remote: fastboot is lock, please run oem unlock with valid pa

FASTBOOT ERROR "FAILED (remote: fastboot is lock, please run oem unlock with valid pa
on ANY fb command i get "FAILED (remote: fastboot is lock, please run oem unlock with valid password)"
ALSO after "fastboot oem unlock" i get:
---
and just a uncloseable shell box that is unresponsive ..iv flashed this device before and same error when any get unlock var or info command any ideas my device is a moto tc700x (is an old symbol\zebra now)
i never put a password in before i flashed my device for IoT and got a freeze during install now i cannot do anything w it even reflash recovery or zips i used previously used before?
any ideas anyone?
metalman1972 said:
on ANY fb command i get "FAILED (remote: fastboot is lock, please run oem unlock with valid password)"
ALSO after "fastboot oem unlock" i get:
---
and just a uncloseable shell box that is unresponsive ..iv flashed this device before and same error when any get unlock var or info command any ideas my device is a moto tc700x (is an old symbol\zebra now)
i never put a password in before i flashed my device for IoT and got a freeze during install now i cannot do anything w it even reflash recovery or zips i used previously used before?
any ideas anyone?
Click to expand...
Click to collapse
You can use "fastboot getvar all" cmd to check whether ur boot loader is locked

[Q] Allow OEM unlock

Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)". I already tried resetting, flashing various factory images and disabling the lockscreen.
Is there a workaround for this?
Thanks for your help!

Cat s31 oem (bootloader) unlock

first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery

Serious bricked device unable to unlock bootloader or flash firmware, stuck in Fastboot - OnePlus 7T Pro (hotdog)

Hello,
I have a OnePlus 7T Pro (codename "hotdog") that is currently in a non-working state. My goal flash my magisk boot.img which I created, however I accidentally locked the bootloader. Unfortunately, I'm currently stuck and unable to progress.
Here is what I've tried:
I attempted to unlock the bootloader via fastboot with fastboot oem unlock, but received a FAILED (remote: Flashing Unlock is not allowed) message. I understand this usually means the OEM Unlocking option in the Developer Options isn't enabled.
The problem is that I can't access the Android OS on the device to enable OEM Unlocking. The device boots directly into Fastboot Mode and I can't navigate anywhere else.
I tried to flash the stock firmware, but I received an error message stating FAILED (remote: Flashing is not allowed in Lock State). This indicates that I can't flash files to the device while the bootloader is locked.
In short, I can't unlock the bootloader because I can't enable OEM Unlocking, and I can't flash the stock firmware because the bootloader is locked. I'm stuck in a loop and unsure how to proceed.
Any help with this issue would be greatly appreciated! I'm open to all suggestions and willing to provide additional details if necessary. Thank you in advance for your assistance.
Best regards,
The only thing I have is that my device is shown as connected in cmd and the command list available, other than, the ability to flash

Categories

Resources