Develop Bugs

[Q] Going in circles trying to find s-off/unlock/root information

Greetings,
New owner of an HTC one and I've been searching for days on a way to get my phone in a state where I can flash ROMS.
From what I've read, if you have Android 4.3 you are out of luck. My phone has 4.2.2. and OS-1.10.605.15 HBOOT - 1.54 . It seems like every resource I've found requires either s-off , root, or unlocked bootloader . HTCDEV no longer an option? so where do I start?
I ran rumrunners tool thinking that was a good place to start and got "device not rooted OR insecure kernal".
Sorry if I'm blind and not searching enough but could someone point in the right direction?
Thanks,
Jen

heres your info
http://forum.xda-developers.com/showthread.php?t=2417043&highlight=unlock+bootloader
thats what followed and have had no issues

bregga said:
http://forum.xda-developers.com/showthread.php?t=2417043&highlight=unlock+bootloader
thats what followed and have had no issues
Click to expand...
Click to collapse
So you were able to unlock the bootloader with HTCdev.com?

i used rumrunner
when the 4.3 update came out I went through the lock unlock bootloader tut on here because i thought bootloader had to be locked to get ota and locked my bootloader from what i was told it was a mistake
so what i did was changed my cid to the super one something like 111111 then went to htc dev and got a token then changed my cid back to verizons it was no biggie but it did work for me i think because i was s offed already
Here is with out htc dev
http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader

Thank you Bregga! (and rumrunner rules:good
I failed to read the fine print on the homepage, NOT to use the universal one but the one for my specific sw version.
:cyclops:

bregga said:
when the 4.3 update came out I went through the lock unlock bootloader tut on here because i thought bootloader had to be locked to get ota and locked my bootloader from what i was told it was a mistake
so what i did was changed my cid to the super one something like 111111 then went to htc dev and got a token then changed my cid back to verizons it was no biggie but it did work for me i think because i was s offed already
Here is with out htc dev
http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader
Click to expand...
Click to collapse
How did you change the super cid? Don't you have to be soff for that? I'm on 4.3 but when I tried it I got unable to change or something like that. It could read it fine though.
Sent from my HTC6435LVW using Tapatalk 2

selayan said:
How did you change the super cid? Don't you have to be soff for that? I'm on 4.3 but when I tried it I got unable to change or something like that. It could read it fine though.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You do need to be s-off. It won't let you change it otherwise. From personal experience with s-on and confirmed with threads like this: http://forum.xda-developers.com/showthread.php?t=2317536

Yeah I thought so myself although with the bootloader now locked for good because of vz you can't get soff that easily. This of course would work if you use the java card because that will give you soff and in turn you can change cid to go to the site and unlock the bootloader.
Sent from my HTC6435LVW using Tapatalk 2

thought you were on 4.2
1st post said you were on 4.2.2 if your on 4.3 gotta wait for new rumrunner or another work around
---------- Post added at 07:52 AM ---------- Previous post was at 07:48 AM ----------
selayan said:
How did you change the super cid? Don't you have to be soff for that? I'm on 4.3 but when I tried it I got unable to change or something like that. It could read it fine though.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I was already s offed i just thought bootloader had to be locked to take ot thats why i was able to change cid and get token i think

[Q] Please HELP Me, this isn't just another Sprint M8 factory reset thread! TRUST ME

Hi people I hope one of your intelligent folk can help me out. Basically I bought a M8 on eBay at good price. The problem with it is it is STUCK in BOOTLOADER.
When I got the phone it was rooted, boot loader unlocked, and TWRP recovery. So after spending close to 7 hours trying to get this thing back to 100% STOCK, I think I am running of options. So after doing a LOT OF research I learnt that I need RUU to take back to stock but in order to do that I needed to UNROOT, so I CMD; "OEM lock" which made the phone "Relocked" "Tampered". So I thought I was done but now I am still having the same issue as I had before which is in RUU I keeping getting "131 Customer ID Error". Apparently that errors means I am using the wrong region RUU, but how is that possible when I am using the Sprint RUU found on XDA?!? So basically, I believe my solution is that to get my S-off but how can I get my S-off if the only thing I can access is the Bootloader?
Someone please help me! I am willing to paypal money if needed. Thank you.

Check the CID by going into fastboot and type the command:
fastboot getvar all
Are you sure it the Sprint variant? Does the Sprint version have the carrier's logo on it somewhere?

redpoint73 said:
Check the CID by going into fastboot and type the command:
fastboot getvar all
Are you sure it the Sprint variant? Does the Sprint version have the carrier's logo on it somewhere?
Click to expand...
Click to collapse
This is what I get:
Also, i am positive this is Sprint version and I should also mention that when I first got the phone I was able to flash roms since it had twrp on it, but everytime i would flash a rom it would keep rebooting about 10 seconds into the os. Which is why I went the RUU route. The RUU i am using can be found here: http://forum.xda-developers.com/showthread.php?t=2729173
The EXE version gives me the 131 error and the ADB version also give me an error.

@YungMoola15 hey man, delete your imei from the post. Your imei should be private.

stathis95194 said:
@YungMoola15 hey man, delete your imei from the post. Your imei should be private.
Click to expand...
Click to collapse
To OP, its true you should never post IMEI. In any case, just for the record I never told you to post the info returned from "getvar all" (although the vast majority of that info aside from IMEI is not personal info); I just told you to check the CID using that command.
Does the device's CID match that of Sprint (don't personally know what that is)?
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
YungMoola15 said:
The RUU i am using can be found here: http://forum.xda-developers.com/showthread.php?t=2729173
The EXE version gives me the 131 error and the ADB version also give me an error.
Click to expand...
Click to collapse
Is says right in the first post of that thread that you need SuperCID to run this RUU; and even gives the fastboot command to change to SuperCID.

Trying to root HTC One X but keep getting this error message: (Bootloader) FAILED

As the title says, I'm trying to root my HTC One X. I currently am on 4.0.4 Android version, 4.0 HTC Sense version, and software number is 2.20.502.7 710RD. I found a video tutorial with this exact software and phone and I followed all of the steps. I figured out how to install adb and fastboot so I could use fastboot commands. I changed my CID to 11111111 and got my HTC dev code. However when I go to type in the command: fastboot flash unlock Unlock_code.bin I keep getting the same error message. The error message is (Boootloader) FAILED (signature verify fail). In the tutorial this did not happen so I don't really know what to do at this point. If someone could please help that would be much appreciated.

Hello
Are you sure you have the correct unlock code?
Did you copy it correctly?
Did you place the unlock code in the fastboot folder on your PC before executing the command?
Try a different cable and/or USB port. Dont connect via a HUB
Why did you need to change the CID?
Have a look at http://onexroot.com/one-x-root/how-to-root-one-x/
Dont change to S-OFF in case you do something wrong, this will save you by keeping S-ON

Reply
grwalker said:
Hello
Are you sure you have the correct unlock code?
Did you copy it correctly?
Did you place the unlock code in the fastboot folder on your PC before executing the command?
Try a different cable and/or USB port. Dont connect via a HUB
Why did you need to change the CID?
Dont change to S-OFF in case you do something wrong, this will save you by keeping S-ON
Click to expand...
Click to collapse
Yes I copied the unlock token correctly and everything. I have not tried different USB ports. I needed to change the CID because on the One X the CID needs to be 11111111 in order to root. I haven't changed to S-OFF yet. Any other help?

The One X does not need to be 11111111 to root.
I really believe that your bootloader is still locked. Please double check and make sure the unlock code was copied exactly as per the procedure in the link i sent. Even the slightest mistake in copying will cause a fail
In fastboot mode, what does it say at the top of the screen
Also try fastboot oem unlock

grwalker said:
The One X does not need to be 11111111 to root.
I really believe that your bootloader is still locked. Please double check and make sure the unlock code was copied exactly as per the procedure in the link i sent. Even the slightest mistake in copying will cause a fail
In fastboot mode, what does it say at the top of the screen
Also try fastboot oem unlock
Click to expand...
Click to collapse
I copied the code down correctly undoubtedly, at the top it says
*** TAMPERED***
*** LOCKED ***
Hboot 1.14
Should my bootloader say unlocked???

Yes it should say unlocked.
What I think has happened is that you used an incorrect/incomplete unlock code to unlock the bootloader. Hence the word TAMPERED. Perhaps even changing your CID also didn't help. Not sure.
You said you followed a video? send link of method you used
What was your original CID?
Try unlocking bootloader again. In post #2 there is a link to a tutorial. Follow this exactly.
Also double check in fastboot mode to see it it says S-OFF. To change your CID i am sure you must have changed to S-OFF?
Unlocking boot loader does not root the phone. It's just the first step
Also (but not a problem) you have an old bootloader. 1.14. That will need to be updated if you want to flash custom ROMS

grwalker said:
Yes it should say unlocked.
What I think has happened is that you used an incorrect/incomplete unlock code to unlock the bootloader. Hence the word TAMPERED. Perhaps even changing your CID also didn't help. Not sure.
You said you followed a video? send link of method you used
What was your original CID?
Try unlocking bootloader again. In post #2 there is a link to a tutorial. Follow this exactly.
Also double check in fastboot mode to see it it says S-OFF. To change your CID i am sure you must have changed to S-OFF?
Unlocking boot loader does not root the phone. It's just the first step
Also (but not a problem) you have an old bootloader. 1.14. That will need to be updated if you want to flash custom ROMS
Click to expand...
Click to collapse
I can't post a link here but if you google "how to root htc one 2.20" it should be the first one and it is by max lee. I don't have S-OFF because I used a one click method to change my CID and to get the code.

Do you an AT&T phone?
I hope so. This method is for an AT&T HTC One X

grwalker said:
Do you an AT&T phone?
I hope so. This method is for an AT&T HTC One X
Click to expand...
Click to collapse
Yes I have that exact one

Then i can only suggest that you copied the token incorrectly.
Watch the tutorial again and then try it again

not able to change MID of verizon htc one m8

modelid: 0P6B20000konoto
how to change the modelID of verizon one m8. adb method not working and i am stuck with this model id.
I want to convert it back to stock verizon. please help.
device is s off and bootloader is unlocked with latest firmware running on viperone m8

Hello
I had mounted the viperOne without backup m8 with tim cid, to return stock I had to find a tim backup with the same cid and installation is successful, need to change anything.
Why you have to change mid?
you have to change mid or cid?
however I'm not sure but they should s-off to make these changes, and the only way it should be app sunshine at 20€
Inviato dal mio HTC One_M8 utilizzando Tapatalk
---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------
I found my backup there
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Inviato dal mio HTC One_M8 utilizzando Tapatalk

As I clearly mentioned I am talking about the MID here. My MID is messed up and I want the ways to repair it. aDB method ain't working.
P.S- I am on super cid so cid is not an issue

shkhr1 said:
aDB method ain't working.
Click to expand...
Click to collapse
What do you mean that it's not working? Did you get an error message? Do you have adb connectivity?
Did you change the MID in the first place (or was it done by someone else)? Changing the MID on the Verizon device is not a good idea. Nothing good can come from it. Folks usually change, in order to flash another version's firmware or RUU. But these are not compatible with the VZN version, and can lead to permanent damage.
MatteoMarsala said:
I found my backup there
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
As the OP already noted, what he is asking (how to change MID) has nothing to do with restoring a TWRP backup.
Also, the thread you linked doesn't apply to the Verizon version.
I know you are new to the forum. But please make sure you understand the question, and the proper answer, before trying to help.
In particular, giving someone the wrong advice on a Verizon device, can lead to permanent damage.

I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL. But now my modelID is somewhat like that I mentioned in the title.
Any suggestions?
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.

redpoint73 said:
What do you mean that it's not working? Did you get an error message? Do you have adb connectivity?
Did you change the MID in the first place (or was it done by someone else)? Changing the MID on the Verizon device is not a good idea. Nothing good can come from it. Folks usually change, in order to flash another version's firmware or RUU. But these are not compatible with the VZN version, and can lead to permanent damage.
As the OP already noted, what he is asking (how to change MID) has nothing to do with restoring a TWRP backup.
Also, the thread you linked doesn't apply to the Verizon version.
I know you are new to the forum. But please make sure you understand the question, and the proper answer, before trying to help.
In particular, giving someone the wrong advice on a Verizon device, can lead to permanent damage.
Click to expand...
Click to collapse
I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL. But now my modelID is somewhat like that I mentioned in the title.
Any suggestions?
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.

shkhr1 said:
I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL.
Click to expand...
Click to collapse
So you actually changed to Sprint MID, and then went through HTCDev.com process to unlock the bootloader?
Yeah, I know bootloader unlock is not available through HTCDev.com for the Verizon M8. But I've never seen anyone do that way (change to Sprint MID) before. Do you see someone else do it this way, or advise you to?
It seems roundabout to do it that way. Since with s-off, all you need to do is change the bootloader flag with a few adb command (HTCDev.com not needed): https://forum.xda-developers.com/showthread.php?t=2708571
shkhr1 said:
But now my modelID is somewhat like that I mentioned in the title.
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.
Click to expand...
Click to collapse
So you ran the command exactly as described in this thread? https://forum.xda-developers.com/showthread.php?t=2708581
You sure there was no typos (cut and paste to be sure)?
If so, maybe change back to Sprint, then run the command to make it VZN MID again? That is all I can think of. No other way to get to VZN MID, that I know of.

yeah my commands were exactly same and output too as shown on the thread. all process ran fine but when i check again no change in MID . IDk what's the problem here . is there any other method you know apart from adb method.

shkhr1 said:
is there any other method you know apart from adb method.
Click to expand...
Click to collapse
I already answer that.

boot loader . .

How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.

jconradb said:
How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571

Aimless Rambler said:
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Yes my comment is vague, I want to unlock my boot loader but cannot. All settings on the M8 are set such as USB debugging and I have the unlocking code from HTC. When I proceed to unlock the phone and choose option to unlock the phone, phone reboots but the boot loader is still locked. On the HTC web site it states with Marshmallow this can happen and you must go to developers options and highlight OEM option to unlock the boot loader but the option is not there and I'm stuck. Thank you for your reply

Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Thank you so much I will try that later today and get back to you. Again thanks for the reply ?

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
jconradb said:
If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.

redpoint73 said:
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.
Click to expand...
Click to collapse
Here you go and thanks

jconradb said:
Here you go and thanks
Click to expand...
Click to collapse
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?

redpoint73 said:
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?
Click to expand...
Click to collapse
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU. Plus rooting would be nice

jconradb said:
I want to change to EU RUU
Click to expand...
Click to collapse
I should have been more specific. What RUU number, and where did you get it from?
jconradb said:
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU.
Click to expand...
Click to collapse
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).

redpoint73 said:
I should have been more specific. What RUU number, and where did you get it from?
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).
Click to expand...
Click to collapse
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue. You see the RUU I had before which was Kit Kat camera worked but many other issues. The marshmallow RUU was downloaded from a member of this forum forget his name

jconradb said:
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue.
Click to expand...
Click to collapse
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
jconradb said:
The marshmallow RUU was downloaded from a member of this forum forget his name
Click to expand...
Click to collapse
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).

redpoint73 said:
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).
Click to expand...
Click to collapse
Ckpv5 was his name on this forum he uploaded the file

jconradb said:
Ckpv5 was his name on this forum he uploaded the file
Click to expand...
Click to collapse
So to do your install I can do this with the standard recovery and model id I have

jconradb said:
So to do your install I can do this with the standard recovery and model id I have
Click to expand...
Click to collapse
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.

redpoint73 said:
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.
Click to expand...
Click to collapse
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t

jconradb said:
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t
Click to expand...
Click to collapse
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK I will follow your advice thank you for your time and effort

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer

jconradb said:
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer
Click to expand...
Click to collapse
oem unlocking being "missing" is not the problem. It wasn't on most OS builds for the M8, and was only added later. In fact, I'm not sure it was ever present on this device (or maybe just some versions). If it's not there, you don't need to enable it. Unlocking the bootloader should work normally.
So clearly, something is wrong, if you are doing the bootloader unlock, and it doesn't work. Let's try to run the RUU, and go from there.