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: 160.
Error Reason: MID Not Allowed.
I'm just wondering why I am getting this problem. If someone could help me out to overcome this problem, I will be very happy.
Thanks,
Cori
Do you have the International One X or the AT&T One X?
Related
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
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 .
Hey,
I've been researching the OP3 bootloader and the bootloader warning and I've found a possible method to hide it.
There is a file "emmc_appsboot.mbn" which contains information and strings (see content below). I'm not sure if modifying the file causes booting problems. I've examined the file and found something about verifying various files and blocking the boot process. I'm looking for someone who could help me and explain things. What do you think? If it's going to brick, would it be unbrickable?
Strings:
"Start >"
"< More options"
"Your device has been unlocker and cann't be trusted"
"To learn more, visit: g.co/placeholder"
"If no key pressed:
Your device will boot in 5 seconds"
Something about blocking the boot:
This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support.Please note that repair/return for this issue may have additional cost.
boot_verifier: keystore length is invalid
I'm thinking about replacing all these texts with spaces to make the screen look blank. That's the way to "hide" the text, but there's still going to be the 5 seconds delay.
Download link to the file: http://d-h.st/SQID (Uploading attachments wasn't working when I posted this)
EDIT: Feel free to examine the file with a hex editor. Search for those strings to find the position.
There're already two threads dealing with the bootloader warning:
http://forum.xda-developers.com/oneplus-3/how-to/help-how-to-remove-device-unlocked-t3425028/page7
http://forum.xda-developers.com/oneplus-3/help/request-remove-bootloader-unlocked-t3405485
meiser said:
There're already two threads dealing with the bootloader warning:
http://forum.xda-developers.com/oneplus-3/how-to/help-how-to-remove-device-unlocked-t3425028/page7
http://forum.xda-developers.com/oneplus-3/help/request-remove-bootloader-unlocked-t3405485
Click to expand...
Click to collapse
I know, but neither one is dealing with this exact file/method. There is of course the "logo.bin", but I don't think it includes the warning message as I've found it from the file I discovered.
santeri3700 said:
I know, but neither one is dealing with this exact file/method. There is of course the "logo.bin", but I don't think it includes the warning message as I've found it from the file I discovered.
Click to expand...
Click to collapse
the "warning" message is inside the aboot....at the moment there's no way to modify this file....but....we will see.
lance2010 said:
the "warning" message is inside the aboot....at the moment there's no way to modify this file....but....we will see.
Click to expand...
Click to collapse
Isn't it possible to modify the hex codes? Or is it the verification that is the problem in this case?
Edit: I've seen that people edit this file with success.
santeri3700 said:
Isn't it possible to modify the hex codes? Or is it the verification that is the problem in this case?
Edit: I've seen that people edit this file with success.
Click to expand...
Click to collapse
where did you see it running?
editing is not the problem, flashing it back is not the problem...but the phone won't start, even if you change a single bit !
there's an checksum active even if you set your phone to unlock_critical...
lance2010 said:
where did you see it running?
editing is not the problem, flashing it back is not the problem...but the phone won't start, even if you change a single bit !
there's an checksum active even if you set your phone to unlock_critical...
Click to expand...
Click to collapse
It was a Samsung and a Xiaomi device (partition and bl unlocking stuff, so not exactly related to this). The checksum is what I'm after.
Unfortunately I don't have enough experience and I don't know if it's even possible to do this.
I'm wonder what exactly happens if I edited the code to have only "spaces" or "NBSP".
Would I get any response from the device? Would I see any error codes on the screen?
I'm too unsure to risk my device. But thanks for the answer!
if you not know how to use the OP3 unbrick tool, let it be..in result you got an unbootable device if you change anything inside the bootloader.
It can't be changed.
i am using htc desire 820s when i tried to unlock bootlader the htc dev website displaying error 152
i tried whole process several times but its not working
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: 152.
Error Reason: Token Information not complete (CID)
please help me how can i fix this
title. i keep getting errors saying Failed to write to pipe followed with some letters and numbers