只需一步，快速开始
后使用快捷导航没有帐号？
在线时间 小时
立即注册，加入爱黑武论坛的大家庭！爱黑武，爱上搞机生活！
才可以下载或查看，没有帐号？
解锁错误提示check-Enable-oem-unlock怎么办？usc版已经升级到5.02
(47.1 KB, 下载次数: 0)
11:12 上传
爱黑武，爱上搞机生活！
在线时间 小时
设置-开发者选项 中 启用 OEM 解锁 打钩。
爱黑武，爱上搞机生活！
在线时间 小时
解锁失败提示bootloader Check Enable OEM Unlock怎么解决？
(出处: 爱黑武论坛)
爱黑武，爱上搞机生活！
在线时间 小时
file:///D:\Program Files\Tencent\QQ\Users\\Image\C2C\D5AE2DD48F180E734ACFD50.jpgfile:///D:\Program Files\Tencent\QQ\Users\\Image\C2C\F86AE016D5660C.jpg能找到那条勾上我就不来了。。。
(107.74 KB, 下载次数: 0)
12:54 上传
(111.79 KB, 下载次数: 0)
12:54 上传
(123.2 KB, 下载次数: 0)
12:54 上传
(99.6 KB, 下载次数: 0)
12:54 上传
组图打开中，请稍候......
爱黑武，爱上搞机生活！
在线时间 小时
你这个还真没有啊，是什么原因呢？
爱黑武，爱上搞机生活！4 (quote) Not possible. The
stock recovery can only
flash zips &efrant4 I've released the new
BootUnlocker Script zip
with support for &osm0sis3Nexus 9 unlock.img (quote) (quote) (quote)
Hi, playahate...
I've &GedBlake3 (quote) Unless you're
using the dd command to
unpack the images &danarama3 (quote)
Try flashing
this zip in TWRP, reboot
directly to &osm0sis
Suggested Apps
The XDA App is the fastest way to access the forums on mobile.
One-Handed Mode replicates the useful iOS "Reachability" feature without root.
Labs is an independent app store that gives developers full control over their work.
The ultimate, most complete theming solution for Android.
The best way to get cutting edge news about your device!
Top Forum Discussions
[INFO] Nexus 6 / Nexus 9 Enable OEM Unlock [GUIDE] Unlock via TWRP/CWM
This thread and the method described is dedicated to bricked Nexus 6 and Nexus 9 that has TWRP installed but locked bootloader.
No wipes are helpfull, ROMs flashes (or not) but gives permanent bootloop.
If no other methods work, then here is your chance:
IMPORTANT!!! The unlockN6.img file is only for NEXUS 6! The unlockN9.img file is only for NEXUS 9!
The script will work on both N6 and N9.
1. Boot to TWRP. If you didn't wipe the userdata trying to ressurect the device, you can get all your files with
adb pull sdcard d:\sdcard\
You can use any folder instead of d:\sdcard\
but you must create the folder first.
1.1 If the TWRP logo blinks but doesnt boot you are still good to go as users report that adb still work even in that case.
1.2 With the blinking TWRP logo you can boot to bootloader and perform
fastboot -w
This will wipe the cache and USERDATA. all your data will dissapear but TWRP will boot normally
2.1 Download the unlockN6.img file from the attachments at the bottom of the post and place it to adb folder on PC.
In case the folder is c:\android perform the following:
adb push c:\android\unlockN6.img /sdcard/unlockN6.img
adb shell dd if=/sdcard/unlockN6.img of=/dev/block/mmcblk0p18
Reboot to bootloader and make:
fastboot oem unlock
After that you are able to to flash the stock firmware with flash-all.bat or manually file-by-file.
As we don't know how some hash in the beginning of the unlockN6.img file influence the device. We didn't notice any difference though, but Prefferred way is use the script.
Instead of making dd, push and flash the script made by @, in the end of the post. For both N6 and N9.
then unlock bootloader and flash ROM.
2.2 Download the unlockN9.img file from the attachments (all the credits go to @ for providing us the file) at the bottom of the post and place it to adb folder on PC.
In case the folder is c:\android perform the following:
adb push c:\android\unlockN9.img /sdcard/unlockN9.img
adb shell dd if=/sdcard/unlockN9.img of=/dev/block/mmcblk0p27
Reboot to bootloader and make:
fastboot oem unlock
After that you are able to to flash the stock firmware with flash-all.bat or manually file-by-file.
If you are interested in additional information, all the prosses of gaining the information is given below... Othervise
- skip to the dowload.
As many of you already know, last Nexus devices (and all that will come after N6&N9) have new option in developers settings - Enable OEM Unlock.
New security feature from Google gives regular users new level of keeping their data in private space. And in case of lost (stolen) stock device with keyguard/pin enabled the villian can't even make the device work. The &old& Nexus devices can be easily unlocked/wiped and used as normal. But now, with the new feature, if someone will try to run fastboot oem unlock, will get the following:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
with the Device is LOCKED Status Code: 2
Is it good or bad?
Definetly good for regular users.
But sometimes it turnes against some &want to be advanced& users. As many of the &unlock/flash custom rom& manuals has the line &You can lock the bootloader with the command fastboot oem lock&
many users do this thing. Some of the users make it, as it guarantees the security (as many people think).
But sometimes something goes wrong and system doesn't boot. Many of the manuals say that if one perform fastboot oem lock and
fastboot oem unlock again - everything wipes and there is normally booted stock device again... And it is a good method, that ended with the Nexus 5/7. Because now if you lock the device and the system doesnt boot, you will not be able to unlock it as you need to check the 'Allow OEM Unlock' in Developer Options.
INFO. How does it work?
I'll start with the changes, commited in development_prefs.xml, DevelopmentSettings.java and Utils.java from the :
Enable OEM unlock checkbox in Developer Settings
For Volantis+ devices, we will give users
the ability to enable OEM unlock through
Developer Settings. To do so, we must write
the value to the last byte of a special partition
that does not get erased even after factory reset.
This feature will only be available on devices
with the persistent data partition, thus the checkbox
is only visible for devices that meet this requirement.
So the new devices have that spesial partition that influens wether the device can be unlocked.
If we go deeper in the docs, we can see how all that thing is working.
public void onStart() {
enforceChecksumValidity();
formatIfOemUnlockEnabled();
publishBinderService(Context.PERSISTENT_DATA_BLOCK_SERVICE, mService);
private void formatIfOemUnlockEnabled() {
if (doGetOemUnlockEnabled()) {
synchronized (mLock) {
formatPartitionLocked();
doSetOemUnlockEnabledLocked(true);
private void formatPartitionLocked() {
DataOutputStream outputS
outputStream = new DataOutputStream(new FileOutputStream(new File(mDataBlockFile)));
} catch (FileNotFoundException e) {
Slog.e(TAG, &partition not available?&, e);
byte[] data = new byte[DIGEST_SIZE_BYTES];
outputStream.write(data, 0, DIGEST_SIZE_BYTES);
outputStream.writeInt(PARTITION_TYPE_MARKER);
outputStream.writeInt(0); // data size
outputStream.flush();
} catch (IOException e) {
Slog.e(TAG, &failed to format block&, e);
} finally {
IoUtils.closeQuietly(outputStream);
doSetOemUnlockEnabledLocked(false);
computeAndWriteDigestLocked();
private void doSetOemUnlockEnabledLocked(boolean enabled) {
FileOutputStream outputS
outputStream = new FileOutputStream(new File(mDataBlockFile));
} catch (FileNotFoundException e) {
Slog.e(TAG, &partition not available&, e);
FileChannel channel = outputStream.getChannel();
channel.position(getBlockDeviceSize() - 1);
ByteBuffer data = ByteBuffer.allocate(1);
data.put(enabled ? (byte) 1 : (byte) 0);
data.flip();
channel.write(data);
outputStream.flush();
} catch (IOException e) {
Slog.e(TAG, &unable to access persistent partition&, e);
} finally {
IoUtils.closeQuietly(outputStream);
public void setOemUnlockEnabled(boolean enabled) {
// do not allow monkey to flip the flag
if (ActivityManager.isUserAMonkey()) {
enforceOemUnlockPermission();
enforceIsOwner();
synchronized (mLock) {
doSetOemUnlockEnabledLocked(enabled);
computeAndWriteDigestLocked();
public boolean getOemUnlockEnabled() {
enforceOemUnlockPermission();
return doGetOemUnlockEnabled();
Many lines are skipped, you can find them by the link above. As we can see, there is one byte with 1 - allow oem unlock and 0 -do not allow.
private static final String ENABLE_OEM_UNLOCK = &oem_unlock_enable&;
private CheckBoxPreference mEnableOemU
public void onCreate(Bundle icicle) {
super.onCreate(icicle);
mEnableOemUnlock = findAndInitCheckboxPref(ENABLE_OEM_UNLOCK);
if (!showEnableOemUnlockPreference()) {
removePreference(mEnableOemUnlock);
private void updateAllOptions() {
final Context context = getActivity();
updateCheckBox(mEnableOemUnlock, Utils.isOemUnlockEnabled(getActivity()));
private static boolean showEnableOemUnlockPreference() {
return !SystemProperties.get(PERSISTENT_DATA_BLOCK_PROP).equals(&&);
So those lines give us the information, that users try to find out in other threads... So here it is:
The checkbox goes to &off& after every reboot.
So you can't just allow oem unlock and use it sometimes in the future. It will work only with the first reboot to bootloader. And if you reboot the phone without changes - it will reset the option in settings.
UPD: With the 5.1.1 update, it remains enabled after reboot.
Getting things done
If you look into the PersistentDataBlockService.java, you can find the line:
private static final String PERSISTENT_DATA_BLOCK_PROP = &ro.frp.pst&;
And if we go to the /system/build.prop on the device, we will get the following:
ro.frp.pst=/dev/block/platform/sdhci-tegra.3/by-name/PST for the Nexus 9
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/frp for the Nexus 6
The next step is running
adb shell busybox fdisk /dev/block/mmcblk0
So we can see for the Nexus 6:
Number Start (sector) End (sector) Size
The PST partition of the Nexus 9 is 27.
What can we do about it?
Well. Thats simple. All we need is TWRP/working adb.
Actually some users with blinking TWRP logo still can use adb. Some can perform fastboot -w
or fastboot format cache and fastboot format userdata to make TWRP work, wipe and boot.
But sometimes there is no system and nothing can be flashed (as it was with one device on russian forum).
So with all the information written above we made the following:
Asked the guy with the live device to check the allow oem unlock and reboot to recovery.
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/unlock.img
to copy the partition on sdcard and send us the file.
on the &bricked& device run:
adb push c:\android\unlock.img /sdcard/unlock.img
Where c:\android - is the folder with the adb and file itself.
adb shell dd if=/sdcard/unlock.img of=/dev/block/mmcblk0p18
and after reboot to bootloader we succesfully performed the fastboot oem unlock.
Hope the information is usefull and will help someone.
IMPORTANT!!! The unlockN6.img file is only for NEXUS 6! The unlockN9.img file is only for NEXUS 9!
The script will work on both N6 and N9.
If you dd the wrong file your device will not boot, you will not be able to use TWRP after thatAnd ones again: the BEST way is to use @ UPDATE-Nexus.BootUnlocker.zip from
post (or newer is exists).
Attached Files
(512.0 KB, 2650 views)
(512.0 KB, 1020 views)
Sponsor Content
Philadelphia, PA
Senior Member
Oxenhope, West Yorkshire, UK
My Devices: ,
Good effort and very thorough. Problem is not a problem if you have twrp though. Only an issue if you have stock recovery.
My Devices: ,
Originally Posted by rootSU
Good effort and very thorough. Problem is not a problem if you have twrp though. Only an issue if you have stock recovery.
Yap. I thougt so...
But we couldn't make it boot... Tried to flash CM, Chroma, stock.zip- nothing... he wiped or erased the system before the lock, so nothing helped after. Ether we got the error, or flashed with 10 seconds and a bootloop. All the wipes from recovery and format (fastboot) didn't help...
Senior Member
Oxenhope, West Yorkshire, UK
My Devices: ,
Originally Posted by playahate
Yap. I thougt so...
But we couldn't make it boot... Tried to flash CM, Chroma, stock.zip- nothing... he wiped or erased the system before the lock, so nothing helped after. Ether we got the error, or flashed with 10 seconds and a bootloop. All the wipes from recovery and format (fastboot) didn't help...
We've maybe been lucky on the n6. So far everyone with twrp, even if twrp boot looped, were able to format cache and data and then boot twrp and flash.
None-the-less, very interesting.
Recognized Developer / Recognized Contributor
My Devices: , , , , , ,
So are these frp partition dumps you got from a N6 so I can examine them for the offset?
Edit: The offset is 07ffff and there are 2 lines of data at the beginning of the file, which could be a hash or security token, so I would NOT advise against flashing any of those images whole if they don't come from your device. The N9, for comparison was 07fffc and was reportedly otherwise empty.
We can flip the byte at that offset and see if it works like with the N9, but I'm worried the hash might interfere. I'll post a test zip once you confirm those are from the N6 and then we'll see!
My Devices: ,
Originally Posted by osm0sis
So are these frp partition dumps you got from a N6 so I can examine them for the offset?
I'll post a test zip once you confirm those are from the N6 and then we'll see!
Ok. Those 2 files are from the Nexus 6, that was booting normally and we used it as a donor.
And here is another stock.img in attachment. Its from the device, that we tried to recover (and succeeded at the end), when it wasnt booting. So you can compare those two stock.img of the frp partition from different devices.
Attached Files
(512.0 KB, 186 views)
Recognized Developer / Recognized Contributor
My Devices: , , , , , ,
Originally Posted by playahate
Ok. Those 2 files are from the Nexus 6, that was booting normally and we used it as a donor.
And here is another stock.img in attachment. Its from the device, that we tried to recover (and succeeded at the end), when it wasnt booting. So you can compare those two stock.img of the frp partition from different devices.
Yup, that data is different between the two.. As I said, not sure if it'll have any effect but we can try anyway. Here's the zip to test flipping the byte, it's got support for shamu and flounder/founder_lte added. If we get successful reports of it toggling the oem lockout then I'll sign and publish it in my Odds and Ends thread. Great work and thanks for all the help!
[ Attachment removed - test complete ]
Recognized Developer / Recognized Contributor
My Devices: , , , , , ,
14 people have downloaded.. Any reports?
@, you still rocking a N6?
Developers Relations / Senior Moderator
My Devices:
Originally Posted by osm0sis
14 people have downloaded.. Any reports?
@, you still rocking a N6?
I just downloaded it and tried it.
My initial state was: bootloader unlocked and &Allow OEM unlock& set to off.
I then ran your script. See the attached screenshot from TWRP.
My end state was bootloader unlocked and &Allow OEM unlock& set to off, i.e., no change at all from the initial state.
Attached Thumbnails
Developers Relations / Senior Moderator
My Devices:
Just as an aside, @ & I already determined that the lock state is stored in the &sp& partition. So if someone dumps that partition when in an unlocked state, flashing that to your device when the bootloader is locked will unlock the bootloader. (Tested and confirmed by me.) It would likely work across shamu devices as well, but as osm0sis said, there may be a hash in there that could affect something.
Recognized Developer / Recognized Contributor
My Devices: , , , , , ,
Originally Posted by efrant
I just downloaded it and tried it.
My initial state was: bootloader unlocked and &Allow OEM unlock& set to off.
I then ran your script. See the attached screenshot from TWRP.
My end state was bootloader unlocked and &Allow OEM unlock& set to off, i.e., no change at all from the initial state.
Originally Posted by efrant
Just as an aside, @ & I already determined that the lock state is stored in the &sp& partition. So if someone dumps that partition when in an unlocked state, flashing that to your device when the bootloader is locked will unlock the bootloader. (Tested and confirmed by me.) It would likely work across shamu devices as well, but as osm0sis said, there may be a hash in there that could affect something.
Damn must be the hashing at the beginning of frp messing this up too.. Thanks for trying. Maybe flip the byte back for yourself to make sure it's back to its untouched state. Unless anyone has any other ideas I guess I'll have to limit the &Allow OEM Unlock& toggle support to founder*
@ Oh well, it was worth a try. @ mention me if you guys come up with anything else.
Guest Quick Reply (no urls or BBcode)
Search this Thread:
Linear Mode
-- XDA Classic
-- XDA 2010
-- XDA 2013
---- XDA 2013 Beta - 1024
-- XDA 2015
---- 2015 - Dark Theme
');}else if(xda_ad_choice=="sortable"){document.write('\x3Cscript src="//tags-cdn.deployads.com/a/xda-developers.com.js" async >\x3C/script>');document.write('');(deployads=window.deployads||[]).push({});}}
We're Social解锁失败提示bootloader Check Enable OEM Unlock怎么解决_百度知道
解锁失败提示bootloader Check Enable OEM Unlock怎么解决
我有更好的答案
38:55 - INFO
- 前设备 : SGP341 - CB5A1RYD84 - _R9A - .1.1.A.1.273 - CHINA-HSPA_10.1.1.A.1.27301/038/:59 - INFO
检查文件01&#47: ROOTABLE01/ - INFO
- 现移除手机并进入fastboot模式01&#471/038/:39:00 - INFO
- 设备已连接至强刷模式（绿灯）01/039/:38:59 - INFO
刷写数据.: S1_Root_5ca3 - 版本 ;:15 - INFO
- 设备已连接至fastboot模式（蓝灯）01/039/..01/039/&#47:55 - INFO
- 读取设备信息01/038/:00 - INFO
- 结束刷机操作01/039/:06 - INFO
- 设备已断连接01/039&#47:39:00 - INFO
- 始读取数据 01/039/;:55 - INFO
- 设备已绪.01&#47:00 - INFO
- 读取TA已结束.01&#47:39:00 - INFO
- L039&#47:39:04 - INFO
- 设备已连接至强刷模式（绿灯）01/039/:55 - INFO
- 设备已连接至强刷模式（绿灯）01&#47: APQ8064_30 / Bootloader状态 ;4 12:15 - INFO
- Bootloader解锁已取消01/039/;038/038&#47:59 - INFO
- 扎起处理 loader.sin01/038/;039// - INFO
- 设备已断连接01/:55 - INFO
- Opening device for R/W01/038/;038&#47
为您推荐：
其他类似问题
bootloader的相关知识
换一换
回答问题，赢新手礼包
个人、企业类
违法有害信息,请在下方选择后提交
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。后使用快捷导航没有帐号？
其他登录方式
—— 新手入门 ——
—— 智友精华 ——
查看: 8337|回复: 188
在线时间1100 小时最后登录阅读权限55UID14188注册时间积分10253精华0
, 积分 10253, 距离下一级还需 1747 积分
主题帖子 金币3814 元 智豆0 点
解锁提示如下信息：
(bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s复制代码
其实这是让你开启【开发者模式】的允许OEM解锁的选项而已。
解决方案：
游客，查看隐藏内容请或一键去隐藏
附件: 你需要才可以下载或查看附件。没有帐号？
楼主很赞！赏波666
打赏排行榜
楼主共收获打赏：
虚位以待打赏
虚位以待打赏
虚位以待打赏
在线时间5 小时最后登录阅读权限20UID1864007注册时间积分203精华0
, 积分 203, 距离下一级还需 197 积分
主题帖子 金币83 元 智豆0 点
这个解决方案好简洁
在线时间17 小时最后登录阅读权限10UID9271422注册时间积分37精华0
, 积分 37, 距离下一级还需 13 积分
主题帖子 金币162 元 智豆3 点
{:203:}{:198:}{:223:}{:223:}{:223:}{:223:}{:223:}{:223:}
在线时间3 小时最后登录阅读权限20UID391335注册时间积分117精华0
, 积分 117, 距离下一级还需 83 积分
主题帖子 金币263 元 智豆113 点
{:243:}{:243:}{:243:}{:243:}{:243:}{:243:}{:237:}{:237:}{:237:}
在线时间2 小时最后登录阅读权限10UID注册时间积分2精华0
, 积分 2, 距离下一级还需 3 积分
主题帖子 金币20 元 智豆0 点
谢谢分享。。。。。。。。。
在线时间0 小时最后登录阅读权限10UID注册时间积分0精华0
, 积分 0, 距离下一级还需 5 积分
主题帖子 金币12 元 智豆0 点
wo xiang kankan ni de jiejuefang an
在线时间0 小时最后登录阅读权限10UID注册时间积分0精华0
, 积分 0, 距离下一级还需 5 积分
主题帖子 金币14 元 智豆0 点
正愁如何解决
在线时间1722 小时最后登录阅读权限90UID676626注册时间积分18421精华4
主题帖子 金币8143 元 智豆832 点
顶楼主啦..希望楼主多发精品好帖啦.....
在线时间86 小时最后登录阅读权限20UID5724035注册时间积分250精华0
, 积分 250, 距离下一级还需 150 积分
主题帖子 金币565 元 智豆4 点
其实这是让你开启【开发者模式】的允许OEM解锁的选项而已
在线时间1 小时最后登录阅读权限10UID注册时间积分2精华0
, 积分 2, 距离下一级还需 3 积分
主题帖子 金币22 元 智豆0 点
顶！！！！！
众测1岁生日勋章
申请众测一周年5款产品自动发放
进群0元拍卖手机 你还在等什么？