remote: oem unlock is not allowed - Nextbit Robin

Hi,
I am using my Nextbit Robin Oem Unlock from last 1 year but today i decided to go back to stock with locked Oem.
I flashed the stock rom and locked the Oem at the same time but when i restarted the phone it got stuck at the boot.
So I went ahead with the 'fastboot oem unlock' command, and here's the problem. All flashing command returns FAILED <remote: device is locked...>.
fastboot oem device-info reads: Device tampered: false, Device unlocked: false. So bootloader is locked. At this point I assume that the bootloader is unlocked, but revert back to locked after reboot (the phone automatically rebooted after executing oem unlock command, so can't get around that).
Tried numerous other methods, using different adb files, no dice. Can't even flash TWRP. Tried adb sideload, same. Tried executing fastboot oem unlock with various different parameter, still locked after reboot. I cannot flash anything into locked bootloader.
Google researched it for few hours, same problem happened to other phones from other manufacturers that came returned from warranty replacement with modified motherboard; OR tampered/broken eMMC/NAND flash. But no such case for Nextbit Robin (yet?).
Pretty hopeless right now since I just found out that Nextbit Robin support ended on Aug 1st.
Guess I'm stuck with locked bootloader and no cell signal phone. Unless someone can help. One can always hope.
Anyway, thanks for reading.

Mukul_Meena said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76659814
Click to expand...
Click to collapse
If you bootloader is unlocked I think you can give a try to the Nextbit's Unbrick Tool
As you want to go back to stock , I think this is a good idea.
Now if your bootloader isn't unlocked there is unfortunately nothing I can do for you , unless you unlock it .
Edit #1: If your bootloader is locked , go to bootloader mode by pressing volume down + power button for about 20 seconds and try to see the bootloader state with fastboot commands. If it is unlocked , follow the process in the @nextbitKhang's thread .

Yes that's the main issue. Oem is Locked.
Is there any Oem unlock code i can use to unlock from ADB?

I don't think so ,I'm not sure, but I hope you'll find one.

On your Robin go to settings > system > about phone > tap build number until it shows developer options.
Go into developer options which is in settings > system > developer options.
Make sure OEM unlocking is enabled. (for good measure disable then re-enable)
Also make sure usb debugging is enabled. Have the Robin plugged into a computer so you can enable to pop-up on Robin asking for access for the computer.
Once they are both enabled shut down your phone. Turn it back on while pressing vol down+power and plugged into your computer.
In adb run command fastboot oem unlock

please i'm experiencing the same issue not on nextbit but on GIonee.
i have re-activate both OEM unlocking and USB debugging several times but it all void
same error: Remote: OEM unlock is not allowed
please kindly help

Related

Soft-bricked MediaPad M2 803L

Hi everyone,
It seems I was stupid enough to choose a wrong model (MediaPad M1) in TWRP Manager (downloaded from Google Play) while attempting to install TWRP recovery.
This resulted in an infinite bootloop where the "Huawei MediaPad" logo keeps appearing, the tablet restarts and again the same.
I do have access in Recovery and Bootloader mode, but all my attempts did not yield any results. Things I have tried so far:
- Download the Stock ROM from needrom.com (versions B009 and B019), extracted them and loaded the "dload" folder onto an SD card and executed recovery (by pressing both Vol UP/DOWN and starting the tablet). Even though the procedure seems to be perfoming normally, indicator reached successfully 100%, when the tablet restarts after the supposed successful recovery I am still left with the same bootloop.
My SD is a 64GB one, formatted with exFAT if this makes any difference.
- I have tried extracting UPDATE.APP using Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454) and tried to push via fastboot all necessary parts (i.e. BOOT.img, RECOVERY.img, SYSTEM.img, etc) but I get the "FAILED (remote: Command not allowed)" error message.
My bootloader was unlocked from the beginning (at least that's what showing when I enter bootleader/rescue mode with red letters - "PHONE UNLOCKED").
Any suggestions would be greatly appreciated! Thanks!
What commands are you using? It is peculiar that fastboot mode fails to flash. It may be that your bootloader is not properly unlocked even though it shows that it is.
If you have a bootloader unlock code for your device, I would suggest that you try explicitly unlocking the bootloader when in fastboot mode (it won't hurt to do this even if your bootloader is already unlocked):
Code:
fastboot oem unlock <YOUR_BOOTLOADER_UNLOCK_CODE>
Then you can verify that the bootloader is actually unlocked by issuing the following command:
Code:
fastboot oem get-bootinfo
If your bootloader is properly unlocked, then the previous command should return output similar to the following:
Code:
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.002s
At this point, let's try to restore your original BOOT partition and RECOVERY partition.
Now, gather the following partition images from your OEM firmware package:
BOOT.img
RECOVERY.img
SYSTEM.img
USERDATA.img
Only BOOT.img and RECOVERY.img should be needed to solve your issue, but we'll have SYSTEM.img and USERDATA.img ready and available here just in case our efforts fail with just boot and recovery alone.
Now erase and flash boot and recovery as follows (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot erase cache
fastboot reboot
Hopefully, at this point your bootloop issue is resolved and your ROM boots normally. If not, then read on.
Uh oh, time to flash SYSTEM.img and USERDATA.img too and see if that makes a difference. While we're at it, let's also reflash BOOT.img and RECOVERY.img. Use the following commands (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot erase system -w
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot flash userdata </path/to/oem/USERDATA.IMG>
fastboot flash system </path/to/oem/SYSTEM.IMG>
fastboot erase cache
fastboot reboot
...and hopefully now you're back up and running.
Good luck!
In case you don't have a unlock code and *already* bricked it, you can get the imei from fastboot as well. Simply send the following command from fastboot:
fastboot oem get-psid
Using the imei you can then request an unlock code from huawei on their web site.
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck. This is the log from that attempt:
===================================================================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type *#*#2846579#*#* for Qualcomm and Kirin based models, or *#*#14789632#*#* for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
===================================================================
DC - Unlocker 2 Client 1.00.1322
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI M2-803L
Model : Huawei phone in fastboot mode
Serial NR. : YVF4C15928000296
Firmware : V100R001C00B000
unlocked
Battery state: 3648mv
===================================================================
Factory reset protection Erase start
unknown error (398)
===================================================================
Since I already paid the €15 at DC Unlocker I decided to give a go using their other piece of software, DC Phoenix. This one allowed me to flash pieces of the UPDATE.app package while in fastboot mode, without complaining about locks. It seemed to be flasing normally (I tried flashing all contents of the latest UPDATE.app package) and then (as per DC’s instructions) I tried re-flashing everything using the second option (Upgrade Mode) while in Repair mode (i.e. Vol +/- pressed while powering the tablet).
No success either – Tried various combination of DC Phoenix – even only the files you suggested (BOOT & RECOVERY, BOOT & RECOVERY & USERDATA & SYSTEM).
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
manowar666 said:
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Click to expand...
Click to collapse
I did contact Huawei for an unlock code, myself - I sent emails to [email protected] and [email protected] and received a reply back from them the next day. Here is what they said:
Dear User,
Huawei Customer Service is pleased to be at your service.
Apology for any inconvenience.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website http://emui.huawei.com/en/ on your phone.
2.Log in your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than twice within 6 months.If you meet the criteria,please go to http://emui.huawei.com/en/ and click the 'download'button to login your Huawei ID other than any other third party ID to apply for the unlock code.Please contact us by mail or local service hotline as following if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, SN, IMEI/MEID and erro message in your e-mail.We also need to know that your phone is rooted, it can be out of the best working state and some of the functions may not be able to work normally. In additon, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. For the lack of testing,third party software may not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think twice.
If you have any other problems, please send your feedback to us. We will be at your service to help you to solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team
Click to expand...
Click to collapse
I didn't want to faff around with all that logging in nonsense for two weeks, and also the Huawei bootloader code site seemed to be offline (kept getting "Page not found" errors with the error page in Chinese characters and what was ostensibly an HTTP 600 error, which was why I contacted Huawei support over email), so I just ponied up about $4.25 for 4 dc-unlocker credits (4 euros) and got my bootloader unlock code from the dc-unlocker software. Neat, clean, easy and non-messy.
manowar666 said:
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
Click to expand...
Click to collapse
Yes, that does seem very odd. I would expect it to take at least some time in userspace (the "total time" field).
manowar666 said:
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck.
Click to expand...
Click to collapse
I find it very peculiar that your bootloader is unlocked but FRP is activated. I think that dc-unlocker does not give you the option to unlock the bootloader because FRP protection is still active - according to all guides, FRP must first be deactivated if you want to unlock the bootloader.
What does your phone say in the bootloader screen for the FRP? You'll find it directly under the "Phone Unlocked" text. It should say either "FRP Locked" in green or "FRP Unlock" in red.
manowar666 said:
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
Click to expand...
Click to collapse
There isn't, directly, but you can try to issue the fastboot command
Code:
fastboot oem frp-erase
although at this point I am not very hopeful that it will work.
FRP is nothing but the developer option to allow an OEM unlock of the phone - it is the option mentioned in this image in the Huawei "Unlock bootloader" guide thread.
Like I said, I find it very peculiar that FRP is enabled but the bootloader is "unlocked". Did you at any point reset the developer options or reflash the stock ROM before you soft-bricked the device? Did you pick up this phone second-hand/used or something?
I think that the root (excuse me, I couldn't resist) of all your problems is that FRP is still enabled, and this is what is causing your flash attempts to fail.
Here is the dc-unlocker guide to repair a bricked Huawei phone even if the bootloader and FRP are locked. If you follow this guide very carefully, maybe it can save you. Since you already seem to have tried "Method 1" of the guide, maybe you can try "Method 2".
Another suggestion I have is that you can contact the dc-unlocker guys for online chat support (when you see that the chat is online). They are very helpful, and since you've thrown so much money at them (be sure to mention that, just in case they don't know), they should be able to do something to help you out. Good luck, and I hope that you can get your phone back online...
I've been faced with all the same issues as the OP for the last 24 hours and thought all was lost. I had been through all the same stuff - every fastboot command and every key combination possible. I'd tried different tools and apps to get some life out of the device but no luck. I had even downloaded the ROM from beast.in.black's thread and extracted it to the SD card but it didn't do anything for me.
Worse still, the tablet was now out of juice. And as soon as I plugged it into the mains, the screen lit up and the all too familiar fastboot screen would stay on, meaning the tablet was barely charging long enough for me to try anything new with adb / fastboot or whatever.
So in trying to get the screen off and charge the tablet, while it was plugged in I held vol up / vol down / power together for 10 seconds. I was hoping this would leave the screen off (I had managed this earlier while plugged into USB) but instead it booted again. So I walked away for a minute, then came back expected to see the fastboot screen but no, it was in the middle of an EMUI software install. Huzzah! I left it to do its thing but at the end, it came up and said install failed and my only option was to press power to reboot. Sigh. So I pressed power and then got another surprise. The Huawei boot logo. The tablet was booting. A few seconds later I'm at the "Choose your regional settings & language" screen in the setup wizard. After trying everything under the sun, it turns out all I needed was the ROM on the SD card and to give the tablet the three-finger-salute while plugged into mains.
Happy days!
I found the Official M2-803L ROM!
For anyone who needs it, I've found an official download (direct from the Huawei China support site) for the M2-803L.
I've posted the ROM details here for anyone who needs this ROM.
Status update for anyone that might be interested: I was able to restore the tablet with the help of DC-Unlocker. I highly recommend them for any unlocking/restoring needs.
More specifically, I contected them via email and they were kind enough to give me credits (since I already paid them) in order to try again with Method 2 as per https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Step 2 of this method did not work for me (i.e. flashing in upgrade mode) but I was able to replace this step simply by re-flashing with DC Phoenix in fastboot mode.
After this, my IMEI was zeroed-out (that was a problem since this tablet is 4G-enabled thus I couldn't register on my provider's network) but I was also to fix that by using HCU-Client (had to purchase 8 more credits from DC-Unlocker).
All are working fine now.
Special thanks to @beast.in.black for pointing me towards the right direction!

How to re-lock bootloader

I recently purchased a used Pixel C. The previous owner stated that the bootloader is unlocked but he never flashed anything. It is running stock. I want to re-lock to the bootloader to do away with the annoying message upon boot up. What is the appropriate fastboot command? Some posts make mention of new fastboot commands. Thanks
reboot on fastboot mode
type: fastboot flashing lock
wait for format userdata
done
Solved
Thanks. That worked perfectly.
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
geekdaddy said:
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
Click to expand...
Click to collapse
Settings>Developer options>Enable OEM Unlocking
tabormeister said:
Settings>Developer options>Enable OEM Unlocking
Click to expand...
Click to collapse
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
geekdaddy said:
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
Click to expand...
Click to collapse
I just flashed LOS17.1 yesterday and HOLY crap it's great. Good call.

Boot into RUU if you're unable to get bootloader unlock token in bootloader mode

So... I have been stuck with a HTC One E9+ for many months with a lock screen that I literally can't unlock, and flashed TWRP but can't be used because of locked bootloader, I had finally discovered a way to get the unlock token. Here's a little bit of story. I tried to run 'fastboot oem get_identifier_token' in bootloader mode, but the phone returned unknown command. I had tried that when everything was normal. I had check the settings in developer options, and there is nothing related to unlocking bootloader inside there. Until recently, I had discovered 'fastboot oem rebootRUU' from other blog post.
All in all, if you couldn't get the bootloader unlock token in bootloader mode, try to get it in RUU mode.
Good luck!
Hi, i tried to run the command "fastboot oem rebootRUU" but no code appeared.

Can someone help me? GOD!

My razer phone, after the OEM unlock, unlocked it using two-party commands, wrote it into the lineage OS system, and then, cheap, used "fast boot flashing lock_critical" FastBoot flashing lock " After locking the mobile phone, it was found that the "Developer Options" had changed to not allow OEM to unlock. Now the mobile phone is restarted indefinitely, using the "fast boot flash unlock" FastBoot flashing unlock_critical " It can't be unlocked. Unable to write to the official firmware, nor can it start properly! Help, gods! Help me!:crying::crying::crying:

[Guide] Unlock Bootloader: T-Mobile [Nord N10 5G] (BE2025)

Prep
Download Android SDK
Enable Developer Options
Enable USB Debugging mode (Optional)
Enable OEM Unlocking
Info Needed
IMEI number
Dial
Code:
*#06#
Serial # (also listed with unlock code step)
Settings/About Phone/Status/Serial number
Unlock Code from bootloader/fastboot mode
Enter Fastboot mode (2 options)
USB Debugging (adb reboot bootloader)
from Power Off or Reboot
Fastboot command
Code:
fastboot oem get_unlock_code
OnePlus Site
https://account.oneplus.com/signup/
Create an Account
Oneplus/T-mobile Unlock Bootloader Page
https://www.oneplus.com/unlock_token
Enter Device info
Note: It took OnePlus 7 days to send my Unlock token
Send unlock Token to Device
Reboot to bootloader/fastboot
Send Unlock Token (Use full Filename)
Code:
fastboot flash cust-unlock unlock_token.bin
Unlock Bootloader
Code:
fastboot oem unlock
Confirm unlock
Select Unlock the bootloader
Scroll with the Volume button
Select with the Power button
Warning: Device will reboot and factory reset (wipe user data)
​
Options
Root
Root N10 5G using Magisk for factory stock
More
https://forum.xda-developers.com/t/oneplus-nord-n10-5g-hardware-variants.4221237/
Oneplus Nord N10 5G hardware variants
Does anyone have the full list of hardware variants? BE2025 - Metro, maybe t-mobile? Be2026 - NA BE2028 - EU? BE2029 - Global I bought the BE2026 straight from oneplus in the US and realized that the situation isn't quite like it is with the...
forum.xda-developers.com
Credits
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
Reboot to Bootloader/Fastboot
Reboot or Power Off
Hold Volume Up and Power Buttons
Select Restart
When the screen goes black
Hold the Volume Down button till you see the language screen
Select your language (English) with touch or Scroll (volume buttons) Select (Power button)
Select Advanced
Select Reboot to fastboot
Confirm Reboot to fastboot
Enable Developer Options
Select Settings/About phone/Build number
Tap Build number till you see
You are now a developer!
Go back to the Settings page
Select System
Developer Options will now be available.
Enable USB Debugging mode
Enable OEM Unlocking
Unlock Code from bootloader/fastboot mode
Screenshots
I was able to get the OEM unlock toggle to show after running a debloat script in another thread. I applied for my token so I'm super stoked for finally getting to unlock. I planned to make a toolkit for this device as well written in Python
So I was able to finally unlocky bootloader now that I have my token. I tried to install a custom ROM, followed the steps exactly, and upon ADB failing at 47% on the side load I reboot to get into fastboot and ended up in 900E mode (semi-brick state). I flashed stock in EDL and reunlocked again... This time I switch the slot from a to b and it did this same thing again! I'm not even sure why this happens if others haven't experienced it
Looks like I'll be sticking with stock root. Trying to flash any rom via adb sideload as shown in the instructions fails at 47%. After trying to reboot to bootloader after that it just semi-bricks. Trying to switch slots after unlocked also causes it to brick. I'm sorry, but this pisses me off a little bit. I'm not sure how others aren't running into this issue.
EDIT:
Turns out because I didn't take the OTA to Android 11 that's what caused it. It was because of the Android 10 bootloader. All is working finally! I'm truly sorry for the troubles..
Does this work with Metro By T-Mobile OnePlus Nord N10 5g?
So, I'm a little confused. The unlock code from fast boot, is it both lines as a single code? I tried to submit like that and the oneplus page says must be 64 characters. What am I missing?
nkolvek said:
So, I'm a little confused. The unlock code from fast boot, is it both lines as a single code? I tried to submit like that and the oneplus page says must be 64 characters. What am I missing?
Click to expand...
Click to collapse
Yes the unlock code is both lines put together with no spaces. Make sure all the 0 are zeros. I would triple check that you copied the code down right. The code should be 64 characters long. I had trouble with the unlock token link not working so I had to contact the Oneplus support on their website. To save you time I would find your serial number, unlock code, Imei number and your PCB number. This way you don't have to do the back and forth that I had to do for over a month. Even if they don't ask for it, just give them the info, it should save you time. Or if you are tech savvy I believe you can flash a different version of your phone to bypass the need for a unlock token. You might also try to send a direct message to an active senior member in one of these N10 forums. Good luck

Categories

Resources