Develop Bugs

[S-ON] Return back to full stock S-ON

This method is to take your device back to full stock for whatever reason you may need.
This will make your phone s-on and locked again without tamper notification.
Must have ADB drivers installed. If you s-off then you should have these.
These procedures will EASILY BRICK you device if not done exactly. Copy and paste each command exactly. Double and triple check your entries to ensure you typed or copied them exactly.
1. Change CID back to stock.
Code:
reboot into fastboot
fastboot oem writecid CWS__001
^^This command is important. Make sure you type 8 characters in CWS__001
2. Remove tampered flag and relock.
Code:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
3. Flash RUU from here.
4. Turn back to s-on. Reboot to fastboot
Code:
fastboot oem writesecureflag 3
5. Check in fastboot you are s-on and locked

jmztaylor said:
This method is to take your device back to full stock for whatever reason you may need.
This will make your phone s-on and locked again without tamper notification.
Must have ADB drivers installed. If you s-off then you should have these.
These procedures will EASILY BRICK you device if not done exactly. Copy and paste each command exactly. Double and triple check your entries to ensure you typed or copied them exactly.
1. Change CID back to stock.
Code:
adb shell
su
echo -ne "CWS__001" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
2. Remove tampered flag and relock.
Code:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
3. Flash RUU from here.
4. Turn back to s-on. Reboot to fastboot
Code:
fastboot oem writesecureflag 3
5. Check in fastboot you are s-on and locked
Click to expand...
Click to collapse
another way to change cid while s off is to
Code:
fastboot oem writecid CWS__001

there is also a zip to relock:
http://androidforums.com/droid-dna-all-things-root/691712-how-reset-your-lock-status-flag.html
be aware it has not been tested on the one vx,since i dont have this device. id dump mmcblk0p3 and check the lock flag location if your interested in pursuing this option. if it works,it makes things pretty noob proof:
-fastboot oem writecid xxxxxxxx
-flash lock zip
-run ruu
-fastboot oem writesecureflag 3
no copy/pasting commands that can brick your device if typed or copied wrong

Stock RUU no longer available at link
scotty1223 said:
there is also a zip to relock:
http://androidforums.com/droid-dna-all-things-root/691712-how-reset-your-lock-status-flag.html
be aware it has not been tested on the one vx,since i dont have this device. id dump mmcblk0p3 and check the lock flag location if your interested in pursuing this option. if it works,it makes things pretty noob proof:
-fastboot oem writecid xxxxxxxx
-flash lock zip
-run ruu
-fastboot oem writesecureflag 3
no copy/pasting commands that can brick your device if typed or copied wrong
Click to expand...
Click to collapse

noobsaibot34 said:
Stock RUU no longer available at link
Click to expand...
Click to collapse
With a bit of searching im sure you can find stock ruus for your device. I have faith
The important part of my post and the link I posted was the zip file to lock your bootloader.
Sent from my HTC PG09410 using Tapatalk 2

[Q] Proper Method to Unroot and Remove all flags?

I want to make my m8 turn back to stock so I can claim the free screen replacement
I am rooted, and currently S-Off with the sunshine method.
So the first step would 've to flash the firmware following this guide
First I would have to relock the device with the command
Code:
fastboot oem lock
Then I would open the executable file in this guide to flash the RUU (I have T-Mobile):
http://www.android.gs/downgrade-t-mobile-htc-one-m8-to-official-stock-firmware-with-ruu/
Then I would enter this( My boot loader doesn't say tampered as in the guide, since I have a newer version, it says software modified, I assume it would still work)
Code:
adb devices
adb shell
su
echo -ne ‘\x00′ | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
exit
exit
adb reboot bootloader
from this guide:
http://www.andromods.com/tips-trick/htc-one-m8-remove-tampered-flag-easy.html
Then to relock the device I would follow this
Code:
adb shell
su
echo -ne ‘\x00\x00\x00\x00′ | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
then
Code:
adb reboot bootloader
from:
http://www.andromods.com/unroot-locking/reset-unlocked-to-locked-htc-one-m8-bootloader-status.html
And then set s on. Should I reflash again? Just to make sure so I don't accidentally brick it?
Code:
fastboot oem writesecureflag 3
I just want to know if I'm doing this correctly, I'm pretty new to android.

Honesty just a stock non root ruu will do as it will flash stock recovery and get rid of root for you.
So when the ruu finishes you will be completely stock with an unlocked bootlooader so "fastboot oem lock" and now you will have zero flags
It don't even have to be your carriers ruu,it can be Dev Edition with OTA support (search Google for that conversion if interested)

jball said:
Honesty just a stock non root ruu will do as it will flash stock recovery and get rid of root for you.
So when the ruu finishes you will be completely stock with an unlocked bootlooader so "fastboot oem lock" and now you will have zero flags
It don't even have to be your carriers ruu,it can be Dev Edition with OTA support (search Google for that conversion if interested)
Click to expand...
Click to collapse
Won't it say Relocked?

please STOP making new threads every time ! this is the third already and the second got closed for the same reasons. learn from it and please use the existing one !

Yepix said:
Won't it say Relocked?
Click to expand...
Click to collapse
You know what it will huh.

Mr Hofs said:
please STOP making new threads every time ! this is the third already and the second got closed for the same reasons. learn from it and please use the existing one !
Click to expand...
Click to collapse
I'm sorry, it won't happen again

Help a Newbie to rid GPE RUU

Hi folks
I have recently bought a HTC One M8 on ebay which was converted to play edition by the seller using GPE RUU. I know very little about this but would like to attempt to return to stock whilst ensuring no flagged messages are left on.
I have searched and only come across guides that are specific to specific circumstances. Does anyone have or know of a general and safe guide that would work in my case?
Any help greatly appreciated.
Thanks in Advance
Sid

Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?

EddyOS said:
Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?
Click to expand...
Click to collapse
model: OP6B100
No idea what it was running before.

OK, going by that ID we can assume it's an EU unbranded handset. Or we can at least we can treat it as such. So, assuming you want to go back to 100% stock Sense (but keep S-OFF) do the following:
First, download the following to your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249
1.54.401.5 FW ZIP - http://www.androidfilehost.com/?fid=23329332407589439 (rename it firmware.zip)
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (rename it to recovery.img)
HTC Sync Manager (for the drivers) - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it and then uninstall Sync Manager but leave the drivers)
1. First things first, change the CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader to confirm it's showing the Super CID - fastboot reboot-bootloader
3. Once confirmed it's set, we now need to set the right MID in case this was changed by the seller. To do this, we can use TWRP. Flash TWRP (downloaded earlier) - fastboot flash recovery recovery.img
4. Once flashed, boot into TWRP and connect the phone to your PC
5. Once the drivers are installed, make sure the PC sees the phone by typing adb devices
6. So long as it's been shown as a connected device, type adb shell
7. We can now change the MID to the EU unbranded one by using the following command (copy/paste this as it has to be exact)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
8. Once done, we can now 'lock' the bootloader using the following command (whilst still in adb shell)
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
9. And we can also reset the tamper flag at the same time
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
10. Once all that is done, type exit to leave adb shell and then reboot the phone into the bootloader through the reboot menu in TWRP
11. Once back at the bootloader, you should find the phone is now 'LOCKED' and it shouldn't say 'TAMPERED' at the top either but should still have the black bootloader interface that the GPe has. We can now set it all back to Sense
12. Reboot the phone into RUU mode - fastboot oem rebootRUU
13. Once in RUU mode, flash the firmware ZIP - fastboot flash zip firmware.zip
14. The process will fail the first time and reboot. Run the same command again once it's rebooted - fastboot flash zip firmware.zip
15. Once finished, reboot the phone to the bootloader to confirm you now have the white 'Sense' bootloader - fastboot reboot-bootloader
16. Assuming it's correctly flashed, reboot back into RUU mode - fastboot oem rebootRUU
17. We can now flash the RUU using the htc_fastboot package - htc_fastboot flash zip ruu.zip
18. Once finished, reboot back to the bootloader one last time - fastboot reboot-bootloader
19. Once back in the bootloader, change the CID to HTC__001 - fastboot oem writecid HTC__001
20. Reboot the bootloader to confirm the change has been successful - fastboot reboot-bootloader
21. Once back at the boot loader, disconnect the phone and boot into recovery and do a factory reset
22. Once the reset finishes, reboot the phone
That should get it all working but any issues obviously let us know

Fastboot folder? I did say i was a newbie! thanks

OK, perhaps it might be worth reading up on fastboot/adb before doing anything as the above isn't for the faint-hearted!
EDIT: I've attached my 'fastboot' folder. Extract it to the root of your C: drive so it's easy to get to. All the commands in my guide are done through a command prompt in Windows starting in that folder, e.g. C:\platform-tools\fastboot oem rebootRUU
https://drive.google.com/file/d/0B8L4pkbzdlR3Z3dsNGZfSWhCeTA/view

ok, I have installed fastboot adb andi have a folder called adb in my c:. I am now downloading all the items listed above and renaming as appropriate and moving to the folder named adb. am I on the right track?

Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK

i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.

tonytdc1000 said:
i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.
Click to expand...
Click to collapse
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running

I know your getting help here, but...Can I ask..
When you bought the One M8 on eBay, did the ad or photos say you were buying an M8 unlocked and Converted from Sense to GPE.
If Not, you do know youve been sold an incorrect product and you have a case against the seller for false advertising, so save yoursewlf the issues, exersize your rights and send it back.
Plus, you say you are new to flashing / unlocking, so if you brick this M8, you dont have any returns room.
Just wanted to say that and hope it helps. Good Luck

EddyOS said:
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running
Click to expand...
Click to collapse
Ok i will... thanks

EddyOS said:
Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK
Click to expand...
Click to collapse
Hi Eddy
Thanks for all your support, i have successfuly completed step 1, 2 and 3. Now I need some assistance in flashing TWRP. How do i do this and what do i use?
regards

3 was flashing TWRP so if you've done that you now enter recovery via the bootloader.

[Q] Help ! Not Able to Flash Custom Recovery on S-OFF Htc One M8

As Shown in Attached Screen Shots My HTC One M8 is S-OFF, CID-11111111 But Written ***LOCKED***...
Q.1 -What Does This " ***LOCKED*** " Means?
Q.2 - If this Phone has S-OFF .. and i want to flash TWRP Recovery.. then why this error coming everytime i try o flash ? (Failed (Remote: Not Allowed) as Shown on ADB Screen Shot...
am i missing any step... or should i have to still use sun shine ?
Thanx in Advance ...

Unlock the bootloader via the HTC dev site, then you can flash custom recoveries. It's free and you are s-off so you can set the flag back to LOCKED anyway.

Mr Hofs said:
Unlock the bootloader via the HTC dev site, then you can flash custom recoveries. It's free and you are s-off so you can set the flag back to LOCKED anyway.
Click to expand...
Click to collapse
Hasn't there also been an echo command to set the flag to unlocked, or am I mistaken?! With S-OFF at hand this should work and he should be able to flash the custom recovery in faceboot mode after this has been done.
EDIT: when device is fully booted, edit installed and adb debugging enabled one can do as follows:
Unlock
adb devices
adb shell
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot bootloader
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Mr Hofs said:
Unlock the bootloader via the HTC dev site, then you can flash custom recoveries. It's free and you are s-off so you can set the flag back to LOCKED anyway.
Click to expand...
Click to collapse
thank you... actually i just did S-OFF and did not unlock boot loader.. thank you

HTCNerdYoda said:
Hasn't there also been an echo command to set the flag to unlocked, or am I mistaken?! With S-OFF at hand this should work and he should be able to flash the custom recovery in faceboot mode after this has been done.
EDIT: when device is fully booted, edit installed and adb debugging enabled one can do as follows:
Unlock
adb devices
adb shell
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot bootloader
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
Problem Solved by unlocking boot loader via "htcdev".... but thanks anyways

M8 4.4.2 to 6.00 Advice

Hi
I manually updated my M8 (un rooted) to 6.00 using google play addition. i live in UK but think this update is US version don't know if that matters.
had to update manually as kept getting no updates available message. bought phone from ebay over a year ago now and was told by HTC representative on their site chat that phone is genuine but software is not original (don't know what that means and he wouldn't give much away)
Kernel 3.4-perf-gd7aafa47 android gpe#1
build number MRA58K.H15 release keys
so now I've updated i can no longer see my version of sense as it no longer gives me that info. so I am thinking maybe it needs installing. Have lost my motion gesture options. i only have double tap to wake (can no longer double tap to sleep)
also lost the HTC music player which i thought was superb as i could change tracks without unlocking screen. tried installing that with an apk but wouldn't work.
could you please advise me

@ZZ77
build number MRA58K.H15 release keys
i believe you convert your device to GPE by accident
if you want to go back to sense
can you post getvar all after removing serialno and imei ??
someone could help you if i can't :good:

hi
I did update from SD card was this one - 6.0 Stock Non-Rooted GPE RUU - 6.0 MRA58K.H6 - 5.07.1700.6
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.23.213311491.A13G
OpenDSP-v50.2.2-00591-M8974_FO.0810
OS-5.07.1700.15
eMMC-boot 2048MB
Android version 6.0 build number MRA58k.H15 release-s
I hope that's enough info for you guys to help me out. I want to have marshmallow and keep sense too

The info you provided, was not what was asked for. And not sufficient to provide proper guidance.
You need to do fastboot getvar all, and post the results, deleting IMEI and serial number. He was not asking for IMEI and serial number.
Meaning you should not have posted your IMEI and serial number. Those are personal info, which should never be posted online. And further, they are not needed in order for us to help you.
ZZ77 said:
so now I've updated i can no longer see my version of sense as it no longer gives me that info. so I am thinking maybe it needs installing. Have lost my motion gesture options. i only have double tap to wake (can no longer double tap to sleep)
Click to expand...
Click to collapse
GPE by definition does not include Sense, and you just can't "install it" on a GPE converted phone. As previously commented, you would need to reverse the conversion, and convert back to Sense using RUU.
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
ZZ77 said:
I manually updated my M8 (un rooted) to 6.00 using google play addition.
bought phone from ebay over a year ago now and was told by HTC representative on their site chat that phone is genuine but software is not original (don't know what that means and he wouldn't give much away)
Click to expand...
Click to collapse
That means it wasn't a GPE phone originally (from the factory), and either you or a previous owned hacked (software modifications) to make it s-off, SuperCID 11111111, and GPE.
As you mention you "manually updated" to GPE, it to me implies you did the modifications. But if that is not the case, you should clarify what you meant by that.
Was it GPE when you received/bought the phone?

cant work out fastboot getvar all. followed instructions but not getting anywhere. I pasted cmd in platform-tools folder then commands adb devices not getting anywhere with that
I only installed 6.0.0 on phone did nothing else. I didn't hack anything and was not told that phone had been hacked when I bought it.
don't know if it was GPE previously. sorry but I'm a complete beginner so Tuesday was the first time I went into bootloader and updated to 6.0.0 that way

after spending ages I think I got the info you guys asked for
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.23.213311491.A13G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 5.07.1700.15
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: REMOVED
INFOimei: REMOVED
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B13000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 11459804
INFOhbootpreupdate: 11
INFOgencheckpt: 0

ZZ77 said:
I only installed 6.0.0 on phone did nothing else. I didn't hack anything and was not told that phone had been hacked when I bought it.
Click to expand...
Click to collapse
It was definitely hacked/modified, if not by you, then the previous owner.
Not necessarily a bad thing. But you'll need to go through some steps to get it back to Sense. You'll probably need to change your MID, then flash the desired Marshmallow firmware, then RUU. What version firmware and RUU depends on what version (CID) you want to "convert" to. Unbranded Euro may be the best bet. But it depends on what bands your carrier uses for 3G and LTE.

@ZZ77
your mid belong to T-Mobile US device
you need to do as @redpoint73 said
change the mid to WWE mid then flash stock MM WWE firmware and flash stock MM RUU in this order
redpoint73 please correct me if i'm wrong

ahmed.ismael said:
@ZZ77
your mid belong to T-Mobile US device
you need to do as @redpoint73 said
change the mid to WWE mid then flash stock MM WWE firmware and flash stock MM RUU in this order
redpoint73 please correct me if i'm wrong
Click to expand...
Click to collapse
I agree.

redpoint73 said:
It was definitely hacked/modified, if not by you, then the previous owner.
Not necessarily a bad thing. But you'll need to go through some steps to get it back to Sense. You'll probably need to change your MID, then flash the desired Marshmallow firmware, then RUU. What version firmware and RUU depends on what version (CID) you want to "convert" to. Unbranded Euro may be the best bet. But it depends on what bands your carrier uses for 3G and LTE.
Click to expand...
Click to collapse
thanks guys appreciate the help.
I would like to go with unbranded euro I'm with EE so will that be okay?
I will have to research changing MID and flashing with RUU. cause I haven't a clue what that means hopefully not too complicated.

ZZ77 said:
I would like to go with unbranded euro I'm with EE so will that be okay?
Click to expand...
Click to collapse
Most likely, yes. Do you know what bands EE uses for 3G and LTE?
ZZ77 said:
I will have to research changing MID and flashing with RUU. cause I haven't a clue what that means hopefully not too complicated.
Click to expand...
Click to collapse
Its slightly complicated. You'll need to use adb and fastboot. Make sure you understand all the steps, before you do them. Enter all commands exactly as stated in the guides.
Guide for changing MID is here: http://forum.xda-developers.com/showthread.php?t=2708581
6.12.401.4 firmware zip, and instructions on how to flash are here: http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Obviously, you should be sure that you want to "convert" back to Sense before undertaking what is a significantly lengthy process. The good thing about being on the Sense partitions scheme, is that you can still flash GPE based custom ROMs, you just won't have the GPE partitions scheme (smaller OS/system partitions makes user data partition slightly larger) or GPE updates (although there probably won't be any major updates at this point, anyway).

Just had a look online
EE 3G 2100MHz & 4G LTE 1800MHz & 2600MHz
I will have a look at those links tomorrow when I have a few hours. I'm not very technical so will take my time with it.

I am having trouble with changing the MID
C:\Users\LB>cd c:\miniadb_M8
c:\miniadb_M8>adb devices
List of devices attached
SERIAL NUMBER device
c:\miniadb_M8>adb reboot bootloader
c:\miniadb_M8>fastboot devices
SERIAL NUMBER fastboot
c:\miniadb_M8>fastboot reboot
rebooting...
finished. total time: 0.020s
c:\miniadb_M8>adb shell
error: device offline
c:\miniadb_M8>
c:\miniadb_M8>adb shell
[email protected]_m8:/ $ echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\
x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
dd: /dev/block/mmcblk0p5: Permission denied
1|[email protected]_m8:/ $
getting permission denied message. please advise

ZZ77 said:
c:\miniadb_M8>adb shell
error: device offline
Click to expand...
Click to collapse
The phone should be booted into OS when you issue this (or any adb) command. Is that the case (booted into OS)?
You also need to have Debugging toggled on in Settings>Developer Options. But I think you already do, since the command "adb devices" seemed to return the proper response (otherwise, the would not list the device, or list it as "offline").

hi
after following those instructions fastboot reboot took me back to OS so not sure what I did wrong

ZZ77 said:
hi
after following those instructions fastboot reboot took me back to OS so not sure what I did wrong
Click to expand...
Click to collapse
you forget (( su ))
to get root access

ahmed.ismael said:
you forget (( su ))
to get root access
Click to expand...
Click to collapse
just tried that same problem
C:\miniadb_M8>adb devices
List of devices attached
Removed device
C:\miniadb_M8>adb shell su
/system/bin/sh: su: not found
C:\miniadb_M8>adb shell
[email protected]_m8:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]_m8:/ $ ((su))
((su))
1|[email protected]_m8:/ $ echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x3
0\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
dd: /dev/block/mmcblk0p5: Permission denied
1|[email protected]_m8:/ $

ZZ77 said:
/system/bin/sh: su: not found
Click to expand...
Click to collapse
I forgot you were not rooted. You need to be rooted to do this, that is what su (superuser) means.
You'll need to flash custom recovery TWRP, using the instructions here (also use the latest version TWRP 3.0.2 at the "Downloads" link): https://twrp.me/devices/htconem8gsm.html
Then download the SuperSU zip 2.78 from here (use the link for TWRP flashable zip): http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
After that, you will be rooted, and should be able to proceed with changing MID.
Suffice it to say, "converting" this device back to Sense is not for the faint of heart! You'll be an "expert" with fastboot and adb by the end of this!

@ZZ77 @redpoint73
if he flashed twrp recovery no need to flash supersu as he can running the command while booting into the twrp without "su"

flashed TWRP 3.0.2.
downloaded zip (TWRP / FlashFire installable ZIP) installed with TWRP from SD card. after installation got a message saying done and also updating partition details.... failed to mount '/carrier' (invalid argument) also tried this from internal storage and had same outcome
still cant access SU. please advise