"FAILED (remote: 'Please flash unlock token first.') - OnePlus Nord N100 Questions & Answers

Hello everyone!
I am brand new in this community and just recently purchased a OnePlus Nord N100 (Unlocked) from amazon. I thought I would be able to root it myself but i've run into a few problems that I was able to overcome and now i've just hit a wall. I have enabled USB debugging and the OEM Unlock option. In the cmd panel, I entered fastbootflashing unlock but I am getting the message "FAILED (remote: 'Please flash unlock token first.')". Is this supposed to happen? Any suggestions would be appreciated. Sorry for the noob question, I have tried to look over a lot of post regarding this but I can't seem to find an answer or solution. I have submitted a claim to oneplus to try to get an unlock token, is it just a waiting game or am I doing something wrong and dont actually need the token? Thanks all!

Related

[Q] [HELP] Trouble with unlock identifier token

I have searched but couldn't find anyone with the exact same problem as mine.
This is the message I got from HTCDev.com
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I have all the requirements (HTC Drivers, adb and fastboot files, JRE) and I am 100% sure I copied the code correctly as I have helped friends unlock their HTC phones before.
Also its definitely not the carrier disallowing me to unlock.
Can anyone help me figure out what's wrong here?
Servers down !?
http://www.isitdownrightnow.com/htcdev.com.html
More info here

Device not detected in bootloader mode.

Help.
I need help unlocking my bootloader, I can type adb devices while the device is powered on & my unique I.D number comes up in cmd, but whenever I boot into bootloader, the device doesn't come up in cmd what gives? All my drivers are up to date & installed correctly, though I get an MTP driver issue, could that be causing this? This is my second M8 (T-Mobile this time), first one was the dev edition s-off & converted to GPe.
You never said what command you used in the bootloader ?
It's :
Fastboot devices (not adb devices)
adb devices for adb wile phone is booted in OS
fastboot devices in fastboot/hboot mode
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
EternalAndroid said:
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
Click to expand...
Click to collapse
Please state the error if you would [emoji12]
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
jball said:
Please state the error if you would [emoji12]
Click to expand...
Click to collapse
Sorry guys just frustrated & keep forgetting, "error reason token decryption fail (cannot generate result)."
But I think I figured out my issue, so my computer's internet is off right now & I'm trying to do all this from my N5. I'm typing the code on my phone, reading it letter for letter, number for number.
BerndM14 said:
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
Click to expand...
Click to collapse
Oh wow I see
Copy the text to notepad. Copy it to your phone. Open it in your phone using any file manager. Copy and paste .

Motorola G (2015) get stuck on logo while starting. How to root and unlock?

Dear Community!
I need your help! After factory resetting my Motorola G3 it stucks on logo. I can access bootloader and recovery mode, but even after doing factory reset again it gets stuck on the same place. I can run adb and fastboot and it recognizes my device, but I can't install new OS because the phone is locked. I also cannot unlock - after entering "fastboot oem unlock" and the unlock key from Motorola, I get the message
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote: '')
Finished. Total time: 0.020s
Probably, because I can't access the device's menu and allow rooting. I would appreciate any help! I am sorry, probably I made some mistakes in my explanations... Thank you!
overtones said:
Dear Community! I need your help! After factory resetting my Motorola G3 it stucks on logo..........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/2015-moto-g
Also, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3387661
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

Redmi Note 5 blocked

Hi, i'm a user from France.
After installing the last Android version proposed by Mi on the 7th of June 2019 my phone is now stucked on the black screen with the red mention " this miui version can't be installed on this device " - I made the choice to wipe all the data - after restarting nothing changed and I'm stucked to the same black screen.
First big loss. I didn't do any thing solo, I've just being installing the official update proposed by the company like I always do when notification comes. I don't do extra stuff that I have no knowledge about, I'm a regular user.
Now I'm trying to wipe the data through my computer using XiaomiFlash, however I'm getting this error alert : Flash antirbpass error.
What does it mean ? I have read about Google protection briefly on the internet but now it's getting really complicated for me to swim in these waters,
none of the solution worked for me, from the ADB thing to the CMD thing - I also downloaded a "dummy" file which I don't know how to use. After installing ADB I don't get any file of that name in my ":c" repertory and when typing the command "fastboot etc" in CMD it says that it's not recognized. I don't know what I'm doing and I don't know what to do, I don't have a car to get to the nearest phone repair shop and it's like i'm in an alien world with all the technical vocabulary in front of me when search the solution online.
All help would be really appreciated for an ignorant beginner like me.
1.Connect phone to PC, backup important data.
2.Reboot phone to bootloader(fastboot,Power+Volume Down).
Goto PC CMD
fastboot flash antirbpass dummy.img
fastboot flash recovery twrp-3.3.1-0-whyred.img
3.Reboot to TWRP (Power+Volume UP).
Wipe DalvikCache, Cache, Data, Internalstorage, System, Vendor.
Install miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0.zip.
Wipe Cache, Data and do Factory reset.
4.Reboot to system.
Just try abovementioned steps, good luck!
Thanks garyemail for your help.
I'm halfway done with this problem, but another thing came on the way which is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-0-whyred.img
target reported max download size of 536870912 bytes
sending 'recovery' (38924 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.942s
Apparently my phone is locked after being checked :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.014s
I know there is no way for unlocking it through "official" method by using whatever Xiaomi is throwing away, do you have a particular way to get that unlocked ?
I know Xiaomi and Google would scream out of hysteria by reading this post but I'm not trying to unlock my phone for the pure sake of adrenaline.
They putted out that Android Update, not me. It didn't work. Rather it blocked my phone.
Now that the only way to solve the problem is to unlock the phone, what do you know, they decide to put a lock on the phone that basically doesn't allow the user to officially and directly restore the phone.
What is wrong with these people ? Are we just supposed to throw the phone away and buy a new one whenever they are making an uncorrect move resulting in a broken phone ?
I learned now what I'm paying when adding a high price difference for an iPhone, I'm paying for avoiding all that torture which Google and Xiaomi together are dragging me into.
Buy a 1€ phone and spend 1000€ worth of time in searching the remedee in case of a problem. -> Android logic -> money saved at first look, whatever happen you are entirely on your own. A small rock hiding a mountain.
Buy a 1000€ phone and spend 1€ worth of time in searching for the remedee to the sickness. -> Apple logic -> expensive at first look, but client satisfaction guaranteed - time and energy saved.
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Wiguna77 said:
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Click to expand...
Click to collapse
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
RebornSAGA said:
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
Click to expand...
Click to collapse
There is no "non-xiaomi way" you have to flash the chinese official rom with miflash and then unlock your phone, thats the only way.
btw you can try the "EDL-Method".
Thanks Gerr1 and thanks anyone else who helped. Really appreciated.
[How To] Unlock Bootloader on Your Redmi Note 5 Pro
Try abovementioned link!...
First unlock your phone bootloader, then do the #2 setps again!...
Hi
Whenever, Irey to turn on the device, it freezes in the mi logo and can only access the FASTBOOOT. I tried to flash the device but ut says "Flashing is not allowed in Locking State" Also, I treid unnlocking the phone through the mi Unlock software but once it says "You've exceeded the number of verification attempts allowed within 24 hours" and I can login twice in a day to that aoftware it seems. Also, I tried to unblock the device through CMD but it says failed. Please Help. Its hard to work without a phone
Please help

Question OEM unlock data has 24 extra bytes

Hi all,
I have some experience rooting Motorolas, but am having trouble now.
I've got the unlock data and submitted it to the Motorola page, but the page keeps telling me that "my input is not recognized as a valid dataset".
I did some searching and found out that parts 1, 3 and 4 of the device id should have exactly 16, 40 and 32 digits. However, my part 3 has 64 digits!
I tried to bypass the form on the site by submitting the request directly to the API, but it still replies that "there is an error with my request".
"fastboot getvar cid" returns 0x0032, which I understand means that my phone could be unlocked, right?
Has anyone seen this before? Is there anything else I could do?
Thanks!

Categories

Resources