Trouble getting marshmallow! - One (M8) Q&A, Help & Troubleshooting

Trouble getting marshmallow! - One (M8) Q&A, Help & Troubleshooting

Hello,
I have a second hand AT&T htc one m8, and it is running kit kat right now. It obviously had superSU and it was probably rooted as well. When I talked to htc, they made me follow some steps and apparently my phone is "s-off". I went into SuperSU after some research online to unroot the phone, and ive succeeded, but the phone is still "s-off" and I think I need it to be s-on for me to get the marshmallow update. Ive looked everywhere online and I still can't find a solution. I don't have a PC and I want to do it locally on the phone. Does anybody know how to get everything back to the way it was out of the box, so that I can just simply update the phones operating system? This is the first time for me to use android and I'm not very used to the operating system.
It would be great if somebody can help me.

No need for s-off. Just find appropriate RUU or update zip for your model . Flash via bootlader(update.zip) if dnt want to use computer or run RUU via pc
Sent from my htc_m8 using Tapatalk

sonnu0100 said:
No need for s-off. Just find appropriate RUU or update zip for your model . Flash via bootlader(update.zip) if dnt want to use computer or run RUU via pc
Sent from my htc_m8 using Tapatalk
Click to expand...
Click to collapse
Will you be able to direct me through the process please? I'm new to android.

Without a PC is kind of hard to do things. It is not imposibble but you need someone to upload things for you.
Before someone can direct you further .. first thing that is important, are you in US and on AT&T network ?
If yes, maybe it is bit easier to help
If no, it's best to totally convert it to non-AT&T

I am not on at&t right now. I don't really want to mess with my phone too much too. I have a Mac is it possible with that without getting windows on it?

At least you have a Mac ... that's good enough but you have to get things done different way as the RUU supplied by HTC is in exe format.
Let's get to know your device first. Put the device to bootloader/fastboot mode and connect to PC. You need to post here fastboot getvar all result (without serial & imei no.)
For Mac (I don't have a Mac) .. I think the command in terminal is
./fastboot getvar all

hihaalex said:
I went into SuperSU after some research online to unroot the phone, and ive succeeded, but the phone is still "s-off" and I think I need it to be s-on for me to get the marshmallow update.
Click to expand...
Click to collapse
You're guessing here, and guessing incorrectly. Good rule of thumb working with these devices: don't guess, or it will end poorly for you (possibly even a permanent brick). Only go by specific information and instructions from experienced users. As mentioned, s-off has nothing to do with getting OTA. There are several factors which may be causing you not to get the update:
1) The AT&T version (if its still configured as one, more on that later) will only OTA update when connected to the US AT&T network.
2) Even if you are connected to AT&T's network, you can only OTA update, if you have the proper stock never rooted ROM. Unrooting by removing SuperSU, or unroot option in SuperSU or similar, is not enough (you haven't been specific how you "unrooted"). You also need the proper stock recovery.
As ckpv5 touched upon, how to proceed depends on several factors, such as what carrier you are actually using. As it may be beneficial to "convert" to a non-AT&T version, which is not that hard to do since you are already s-off.
Also, a lot depends on the current status of the device, so do as directed by ckpv5 above, so we can get more info about the device. With s-off some modifications may already have been done to the device (like changing the carrier version). But we need to know the current status, before we can proceed.

As my one m8 is already got s-off, is there a way I can just get a zip file of the marshmallow update and go to the recovery, from phone storage part of the phone?

How can I find out the current status of the phone?

hihaalex said:
As my one m8 is already got s-off, is there a way I can just get a zip file of the marshmallow update and go to the recovery, from phone storage part of the phone?
Click to expand...
Click to collapse
Nope, it doesn't work that way. If you are talking about OTA when you say "update" (and you really should be as specific as possible when posting), there is no way that would work. For several reasons: Marshmallow update would require you being on Lollipop (OTAs need to be installed sequentially, and you typically cannot skip an OTA). Also, you need be on the stock (never rooted) ROM and stock recovery. Also, the OTA checks the M8 version: carrier ID (CID) and model ID (MID), so you need to use the proper files for your MID/CID. Which is why were are asking for info about the current device status (which you have not provided).
If by "update" you mean RUU, it can be done (RUU does not need to be installed sequentially, you can go right from KitKat to Marshmallow). However, again the proper RUU depends on the current status (CID/MID) of the phone, plus what country you are in (which you didn't answer). Also, you can't run RUU from the phone's internal storage; although you can from an SD card.
---------- Post added at 09:28 AM ---------- Previous post was at 09:26 AM ----------
hihaalex said:
How can I find out the current status of the phone?
Click to expand...
Click to collapse
ckpv5 already described how, in Post #6 above.
Although, you will need an adb/fastboot environment setup on your computer. And I'm not at all familiar with doing that on a Mac.

Related

the htc one S-OFF via java card support thread

not wanting to wait for a software exploit that may never come,user Sonic2756 has stepped up and purchased an htc service card,or java card,to provide the vzw one community with a "right now!" s off option. make sure yuo thank him in this thread: Purchased a JavaCard for S_OFF
this method uses an official htc java card to turn off the phones security data. the card exists as a legitimate tool for cell phone shops and re-sellers,primarily for the purpose of removing the phones simlock.
since this method of s off is somewhat unusual,this thread is intended to help support folks that are unsure of the differences and similarities.
first and foremost,these are my words,sonic has not helped with these posts,tho i hope he will let me know if theres anything he wants changed. if any info you see here and use melts your phone into a little pile of aluminum goo,its not sonics fault,nor is it mine. use this info at your own risk.
in this first post,i thot a few FAQs needed to be put in one place,as they are being asked over and over again in the thread.
Frequently Asked Questions
Q: what is s off?what does it do for me?
A: in a nutshell,s-off=security off. it removes all security checks and allows access to all partitions of the phone this means you can:
-change hboot
-change splash inage
-change radios
-flash unsigned files
-go backwards in firmware versions
-other things that maybe ill add later
Q: is this legit??
A:yes,it is. as mentioned above,the java card is a legitimate tool used by some large cell phone repair shops and re-sellers.
Q: how does this work?
A:the java card is plugged into a USB On The Go cable,and plugged into the phone. the java card contains htc-signed diagnostic files wich are used to clear security data. when the phone is booted to hboot with the java card plugged in,it finds the diagnostic file and jumps to a mode where the user can clear "s58" data. this removes any simlock,changes the CID to a generic "supercid",and most importantly,turns off the phones radio secure flag. hooray!
this not sonic,nor is this an htc one. it is a one X using the same method,it will give you a good idea what the process looks like:
HTC One X S-OFF
Q: what exactly is a java card?
A: simply,a java card is an sd card with a microprocessor in it. if someone wishes to provide a more detailed definition,id be happy to put it here. a bit more info here
Q: can we clone the java card so everyone can have s off?
A: yes. but its complicated,and the card to begin with is expensive. there have been some technical discussions about this in sonic's original thread. the simple answer is that it is not easy,or practical to clone the java card.
Q: why do i have to pay for this?? shouldnt s off be free?
A: if you have a prollem paying for this service,you are welcome to purchase your own java card and offer the service for free. as has been stated,the java card is expensive- upwards of $1000 depending how may credits are included.
further,even if a software exploit was available,it is good custom to donate to the devs who brought you the tool. remember,no one here owes you custom roms,s-off,etc. support your devs and what they bring you. in this case,sonic has purchased an expensive htc tool,shipping supplies,and has to invest a great deal of time getting your phone s-offed,packed up,and hauled back to the post office. not to mention the website he has set up for the service. there is nothing wrong with making his $$ back,and a bit extra for his time and efforts.
Q: is the card good forever?
A: NO! the java card has a limited number of uses. he has stated he can sell about 250 s off services,and do 10 developer phones for free. after those credist are gone,you are SOL unless a new exploit is found,or there is enuff interest for sonic to buy a second card.
Q: how do i know how many credits are left?
A:Sonic's website shows the number of avaiable spots left, right above the quantity select/add to cart,in the "product description". simply go to the website,then click the htc one picture.
Q: if im allready unlocked,should i still get s off?
A: in my opinion,yes. s off is better. it allows more options to recover soft-bricked devices,and allows access to all partitions. an s on phone is still doing plenty of security checks. it also allows a permantly installed recovery to install the boot image. the downside is that your phone WILL let you brick it if your not careful. know what your flashing and why. double check md5 sums to verify the integrity of your downloads. a corrupt bootloader ot radio can damage your phone,potentially unrecoverably. if you just asked "what is an md5sum?" stop and google it now. there are numerous md5summers avaialable for free on the vast interweb,download one and start using it.
Q: if im allready unlocked and running a custom rom and recovery,do i need to take any precautions?
A: yes. the diag file is designed to work on stock software and firmware. i would strongly recomend to:
-restore a bone stock nandroid,or flash a bone stock rom
-reflash your stock recovery
-reflash your stock boot image if you were running a custom kernel
-select 'factory reset' option from hboot
Q: will this wipe my phone?
A: yes it will. so back up your sd card to the pc,and be prepaired to have to re-set everything up when you get it back.
Q: does my phone need to be active?
A: no it does not.
Q: do you need my sim card?
A: no he does not.
Q: what is the turn around time?
A: again,these are my words. from the thread,5-7 days. please remember sonic has real life activities to attend to,so you may want to wait until the initial wave has subsided. if he has alot of phones to do,it may take him longer.
Q: im a tight ass,can i use cheaper shipping?
A: yes,you can. the initial shipping is picked and paid for by you. be as tight as you want. the return shipping is priority mail with $600 worth of isurance. if you have such faith in the united states post office,and humanity that you do not feel this is needed,then you can chose the cheaper return shipping option sonic has provided.
Q: how do i activate a spare phone while mine is away?
A:it depends on the phone. if you have another 4g vzw phone,you can simply swap over your active sim. if the sim is larger in the spare phone,adapters do exist for extremely cheap on ebay and amazon. alternately,you can call vzw or go to their website to activate an older 3g device.
Q: how do i activate my phone when it comes back?
A: like you normally would. s off by itself does not change anything about the phone or how it oporates. its what you do afterward/modify that can have an impact on "normal" operation. so if you moved your sim into another phone,just move it back. if you mailed your phone directly to sonic with the protective film still on it,then take everything out of the box and activate just like you would if it had just come from vzw.
Q: will i be able to unlock the bootloader if my phone is s off?
A: yes. when the phone comes back,it will have "supercid". this ignores the mid(model id) check that htcdev does on the phone,and will let you get a token and unlock.
Q: are there advantages to unlocking the bootloader?
A: you have a couple extra fastboot commands you can use:
fastboot flash partition imagename.img
and
fastboot boot imagename.img
these commands are useful to install recovery,and boot images into phone memory. with fastboot bootfor example,you can temporarily launch recovery on the phone to flash su if you dont want to permantly install it.
Q: so do i NEED to unlock the bootloader to install recovery?
A: no,you do not. you can install recoveries and all other partitions as zip files. more info on that later.
Q: does superCID give you any benefits?
A: in a word,no. on a gsm device where you have multiple carrier and regional firmwares that will work,supercid is of value. with a device on vzw,you can only use vzw ruus anyway since this is a unique cdma/lte device. further,accepting an OTA with supercid could leave you unrecoverably bricked,plus it may interfer some some verizon functions(i remember inc 4g users having issue,but the details escape me)
IMO,after unlocking your bootloader,if you choose to do so,you should change your CID back to stock VZW__001 (thats 2 underscores- cid is always 8 digits)
Q: is my cid unique to my particulare phone?
A: no,it is not. it is unique to a carrier or region. all verizon phones ever made have a cid of VZW__001
Q: how do i change my cid back to stock?
A: with this fastboot command:
fastboot oem writecid VZW__001
Q: why is my cid always present on the hboot screen?
A: i dont know htc's logic,but this is simply what the phone does while its s off. it will display whatever your cid is,and is not dependent of your bootloader being locked or unlocked.
Q: what about the TAMPERED and unlocked/relocked badges?
A: if your phone was unlocked when you sent it in, youll get it back factory fresh locked. the tampered badge,i am unsure of at this time,and will update as more info is obtained.
if you sent in a brand new phone,it obviously wont be different(with exception of s off)
one of the big advantages of s off,is that the tampered flag is not triggered by adding a custom recovery or kernel,and since s off removes the various write protections that exist,it is posible to reset either flag. more info on the lock status flag here
Q: will an OTA change my s-off or lock status?
A: it is possible. altho,it is highly unlikely since turning the radio secure flags on via an OTA would also do so on legitimate pre-release test phones.
however...
it really is not reccomended that you try and take an OTA while rooted. a custom recovery is unable to install HTC's OTA pacakage,and attempting to do so ca jam you up horribly. taking an OTA with bloat and system files remove will typicaly result in failure,and taking an OTA with supercid could lead to a processor "do not boot" mode,wich is very effectively a hard brick only recoverable via jtag. or a new device.
the best way to update a rooted device is to update the rom with a recovery-flashable zip file,and the firmware extracted from the OTA package. this will update you just like taking the OTA. there is nothing magical about over the air updates. please,just do it manually. leave the OTAs for the stock crowd.
last and not least!
Q: im convinced! what do i do once i get back my stock,s-off phone?
A: please see post 2
_____________________________________________________________________________________________
the above was just off the top of my head,ill add to them later as they come to me,feel free to post if you have further questions,costructuve criticism,or feedback.

once you have recieved your stock,s off device back,your basic steps are:
1)change CID back to stock verizon
2)install a recovery
3)install a rom or root access
you have 2 options to install recovery:
1)unlock the bootloader and use fastboot commands
2)leave the bootloader locked,and flash a recovery as a zip file in RUU mode
either way works. i personally always keep my bootloader unlocked so i can use fastboot commands,but we dont know for sure if the lock status flag can be reset,so the bootloader screen reads locked again.
its remotely possible that it may be difficult to reset the lock status flag,so if being locked for a possible warranty exchange is important to you,dont unlock just yet. relocked is the best you can do without some trickery.
to "root by recovery" is not a new concept. once there are no write protections,its easy to install a custom recovery,and use that recovery to either insert the superuser files into the stock rom,or replace the rom entirely.
1) change cid back to stock verizon
this is actually very easy. simply put the phone in fastboot,change to fastboot directory,and enter in a cmd window:
fastboot oem writecid VZW__001
yes,those must be capital letters,and there are 2 underscores.
2) install a recovery
via one of these 2 methods:
1)unlock the bootloader
your phone has come back from sonic with "supercid",wich will allow you to unlock the bootloader natuarally via the htcdev website. see this post for a bit more info on that.
unlocking the bootloader is fairly straightforward,just make sure you use a vzw one specific image. download from one of the following threads:
twrp
clockworkmod touch or classic
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
for example,recovery named CW_touch_recovery:
fastboot flash recovery CW_touch_recovery.img
the image must be in your fastboot working directory.
if you need more specific help with unlock/recovery flashing you can use this guide.
2) keep locked bootloader
the bootloader can stay locked for this method. you can in fact use this to install a new image to any partition,as long as the image is packed up in a proper file.
this assumes a working adb/fastboot and drivers installed. if you dont have these things,you can use this guide from above,downloading the files in post 1,and following the set up adb and prepair to root part in step 2.
once you have adb and fastboot working,download one of the following recovery zip files. do NOT unzip or extract.
twrp: http://www.mediafire.com/download/6gbk9s5y6angyf9/openrecovery-twrp-2.6.0.1-m7vzw.zip
CW touch: http://www.mediafire.com/download/43h8k47blfboci9/recovery-clockwork-touch-6.0.3.6-m7vzw.zip
CW classic: http://www.mediafire.com/download/w57cqx7cpmxbz44/recovery-clockwork-6.0.3.6-m7vzw.zip
your zip file is flashed in the following manner:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
Click to expand...
Click to collapse
3) install a rom or root access
this is a simple matter of using recovery to either flash superuser,or flash a new rom. in either case,MAKE A BACKUP OF YOUR STOCK UNROOTED ROM!
flash superuser just as you would a rom,after a cache/dalvik wipe. theres tons of info out there on using recovery,so im not going in to great detail on that here.
i dont have this device(well,i dont have the vzw version) so dont ask me whats the best rom to flash. browse the development and original development sections and pick a couple out to try.
if you wish to just run rooted stock,i perosnally prefer superSU to other versions of superuser. you can download it from this thread
_____________________________________________________________________________________________
optional:
if you sent in your phone with a custom recovery installed,and it still is displaying the tampered banner,see this thread to remove it: http://forum.xda-developers.com/showthread.php?p=46182709#post46182709
if you want to lock,or unlock your bootloader without messing with htcdev,see this thread for those directions: http://forum.xda-developers.com/showthread.php?t=2470340
if you want to restore your supermid from PN073**** back to stock verizon,see this thread:
http://forum.xda-developers.com/showthread.php?t=2490777
_____________________________________________________________________________________________
*work in progress. there will likely be some revisions,but i wanted to get something up for the folks whose devices are coming back

mine too!

thanks for this. Guess I need to order a sim adapter so I can mail my phone off.

nrfitchett4 said:
thanks for this. Guess I need to order a sim adapter so I can mail my phone off.
Click to expand...
Click to collapse
your welcome. ill get some more added to it,how tos and such in the next day or 2. but for now im tired and 5am comes early,lol.
for what its worth,ive used sim adapters like these:
http://www.amazon.com/Micro-card-ad...=1378950374&sr=8-14&keywords=sim+card+adapter
and these:
http://www.amazon.com/eForCity-Micr...=1378950374&sr=8-13&keywords=sim+card+adapter
and personally found the ones with an open back to be a lil easier to use. i switch my sim around alot(to the point its wearing out and ill prolly need a new one soon )

saved
thank you!

Thanks
Sent from my HTC6500LVW using Tapatalk 4

scotty1223 said:
your welcome. ill get some more added to it,how tos and such in the next day or 2. but for now im tired and 5am comes early,lol.
for what its worth,ive used sim adapters like these:
http://www.amazon.com/Micro-card-ad...=1378950374&sr=8-14&keywords=sim+card+adapter
and these:
http://www.amazon.com/eForCity-Micr...=1378950374&sr=8-13&keywords=sim+card+adapter
and personally found the ones with an open back to be a lil easier to use. i switch my sim around alot(to the point its wearing out and ill prolly need a new one soon )
Click to expand...
Click to collapse
yeah, just found one that has adapters for nano up to mini. Will be here friday. Will have to live with the rezound for a week.

Thanks so much for making this!
I'm working with Sonic on this (mainly setting up and maintaining the website), but I would like to offer some insight on the JavaCard:
A Javacard is a special type of microsd card (smart card, this is the same thing as those NFC wallets or whatever that use a smart cards) that contains a microprocessor. It also has a signed and encrypted java applet that is set up to run whatever the maker wants it to. In this case HTC set it up to communicate with the phone for diagnostic services. It is also capable of carrier unlocking the phone. Due to digital signatures (when this card is almost burned I'm planning on taking a look at it) the card only has a certain number of phones that can be s offed or unlocked (it works on a credit system - 2 credits s off 1 credit carrier unlock). Everything on the card is locked up like fort knox to my knowledge but we shall see!
We also currently have the diag files needed for several other phones and can S-off them too. Not sure of all of them atm but Sonic posted it in the other thread a few days ago.
Cheers!
Sent from my SGH-M919 using xda app-developers app

Question, If where s-offed then HTCdev unlock with super sid then change the sid to VZW but somehow get locked again I.e. OTA update, is it possible to unlock again or change the sid back to super sid to unlock?
Sent from my ADR6425LVW using Tapatalk 2 - my one is out getting' s-offed

RebelShadow said:
Question, If where s-offed then HTCdev unlock with super sid then change the sid to VZW but somehow get locked again I.e. OTA update, is it possible to unlock again or change the sid back to super sid to unlock?
Click to expand...
Click to collapse
+1 I had the same question.

And again, why would you take said OTA to begin with? It goes against every principle of rooting. If you root, you NEVER take OTA's.
If you get it, either post the ota zip or link and wait for someone to patch the base up with it. It doesn't make the update better if you take the one that downloads to your phone versus flashing an updated rom.
I don't know what it is about OTA's that makes people willing to jump through hoops just to take the "official" one.

CNexus said:
And again, why would you take said OTA to begin with? It goes against every principle of rooting.
If you get it, either post the ota zip or link and wait for someone to patch the base up with it. It doesn't make the update better if you take the one that downloads to your phone versus flashing an updated rom.
I don't know what it is about OTA's that makes people willing to jump through hoops just to take the "official" one.
Click to expand...
Click to collapse
I can't speak for RebelShadow but I meant more along the lines of if we S-OFF and something happens - via VZW - that reestablishes S-ON.. can it be S-OFF'd again without the Java Card?
I mean I don't know if there is anything VZW could do to reestablish S-ON, and I've heard even if they could they wouldn't because they would mess with legitimate developers.
It's not that I want to take OTA's, I'd refuse them and wait for the community to provide it. It was more of a 'what happens if S-OFF is switched back to S-ON'?

If S-OFF ever gets toggled back to s-on, the game is over. You would need some updated exploit or another java card round.
It's like leaving your house with your keys inside. There's no way back in unless you find some back door.

So I originally had an unlocked bootloader with Twrp recovery and sent it to sonic for s-off. He did his java card magic and now I'm good. Mine has tampered now and just curious what is the best way, if possible right now, to get rid of it?

isoh said:
Thanks so much for making this!
I'm working with Sonic on this (mainly setting up and maintaining the website), but I would like to offer some insight on the JavaCard:
A Javacard is a special type of microsd card (smart card, this is the same thing as those NFC wallets or whatever that use a smart cards) that contains a microprocessor. It also has a signed and encrypted java applet that is set up to run whatever the maker wants it to. In this case HTC set it up to communicate with the phone for diagnostic services. It is also capable of carrier unlocking the phone. Due to digital signatures (when this card is almost burned I'm planning on taking a look at it) the card only has a certain number of phones that can be s offed or unlocked (it works on a credit system - 2 credits s off 1 credit carrier unlock). Everything on the card is locked up like fort knox to my knowledge but we shall see!
We also currently have the diag files needed for several other phones and can S-off them too. Not sure of all of them atm but Sonic posted it in the other thread a few days ago.
Cheers!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
your quite welcome! just my little part to help you guys out,this is a great service that is being offered. sonic has done my one x,but i was unsure the extent that he is willing to do other devices,i figure folks can contact him prior to purchasing the service if they wish for other models to be done. better way to say it,i was unsure how much he wanted to advertise the other models he had the diags for. if the vzw s-offs slow down,id be happy to add the list of phones to the OP,and replicate this in other forums. im sure the tegra 3 one x and x+ crowds would have some interest,those devices have been out a long time with no exploit for s off,and no real hope on the horizon.
my one x is one of my favorite all time devices. i use it at work,and use my one in the evenings. im actually considering seeking out a black one x to send him as well
thanks for the insight on the java card,ill add it,or a link to it,in the OP
RebelShadow said:
Question, If where s-offed then HTCdev unlock with super sid then change the sid to VZW but somehow get locked again I.e. OTA update, is it possible to unlock again or change the sid back to super sid to unlock?
Sent from my ADR6425LVW using Tapatalk 2 - my one is out getting' s-offed
Click to expand...
Click to collapse
one4thewings said:
+1 I had the same question.
Click to expand...
Click to collapse
an OTA is unlikely to change your lock status,or your radio secure flag. while it is technically possible,this would also break legitimate test devices functionality,so the chances of it are slim to none.
there is not much reason to relock your bootloader with s off. you can run an ruu with the phone unlocked. to directly answer your question,however,if you did relock the bootloader,you can easily change the cid back to 11111111 with the same comand and re-unlock
fastboot oem writecid xxxxxxxx
or
fastboot oem writecid 11111111
to re-supercid

Thank you for answering without the "OTA" rant. I not not concerned with taking an OTA as I'm planning on using a custom ROM but was asking as a what if / just in case scenario.
Sent from my ADR6425LVW using Tapatalk 2

deleted due to dumb post

andybones said:
so once we get the phone back and we have unlocked with htc dev to get unlocked bootloader, and want to go back to stock CID
the fastboot command is
"fastboot oem writecid xxxxxxxx"
and not just "fastboot oem writecid"
or do you have to have those (8) "x"'s?
Click to expand...
Click to collapse
Not quite sure if I know what you're saying, but to go back to the stock CID is:
fastboot oem writecid VZW__001
I think the x's he put are just to show that you can put in any 8 numbers, as long as they're all the same (ie. 22222222, 77777777) to get Super-CID back.
Nevermind, 11111111 is Super, VZW__001 is stock.

PapaSmurf6768 said:
Not quite sure if I know what you're saying, but to go back to the stock CID is:
fastboot oem writecid VZW__001
I think the x's he put are just to show that you can put in any 8 numbers, as long as they're all the same (ie. 22222222, 77777777) to get Super-CID back.
Click to expand...
Click to collapse
ahh sh*t I am a dumb$$, thank you
I see now that the "VZW__001" is the 8 x's and different for each carrier, thank you!
got confused for a second there.

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

Help ! Trying to find a non rooted, or stock 5.1.1 ROM

I removed the red text ... that went surprisingly well.
Now I wanted to unroot, convert to stock, and be able to get OTA's again, but it's not simple (for me).
Current situation is ...
S-Off
CID - 11111111
OS - 4.20.631.2
On a 5.1.1 version of Resurrection ROM, rooted of course.
Is there an easy way (newbie ish here) to go back?
Phone goes out tomorrow morning

Use an inexpensive phone such as Leon from metropcs. But insurance, keep old phone for reference, report phone lost for quick replacement.

That's not an option. It's not going out for warranty work, just giving phone to another individual, and they want a stock ROM - Preferably unrooted.
Can I flash a GPe rom? And be ok? I'll lose SENSE that way though. No?

ChrisDuffy20 said:
I removed the red text ... that went surprisingly well.
Now I wanted to unroot, convert to stock, and be able to get OTA's again, but it's not simple (for me).
Current situation is ...
S-Off
CID - 11111111
OS - 4.20.631.2
On a 5.1.1 version of Resurrection ROM, rooted of course.
Is there an easy way (newbie ish here) to go back?
Phone goes out tomorrow morning
Click to expand...
Click to collapse
Okay.
You are S-Off, so why do you want OTAs? I'm a Canadian user as well, and I am on WWE/International firmware. It is compatible with Rogers as well as Telus (my carrier).
Since you are S-Off and superCID, you should just run that. WWE updates WAY FASTER than Telus or Rogers (or any North American carrier for that matter).
If you want to go back to stock, find a nandroid backup and stock recovery. If you go to this thread, you can get that. It isn't listed there, but in post #3 he states that what you are seeking is available on request.
@ckpv5 is a very helpful member on XDA. He has what you need.
If you really decide to go back to stock, that is.

The kid taking this phone isn't tech savvy, so I'm trying to get as close to stock as possible 5.1.1, not 6.0. I see that conversion being hard. I'm no good with ADP or ADB, or whatever.
Essentially, I just want a stock looking, sense toting, 5.1.1 ROM.
Thank you xunholyx

ChrisDuffy20 said:
The kid taking this phone isn't tech savvy, so I'm trying to get as close to stock as possible 5.1.1, not 6.0. I see that conversion being hard. I'm no good with ADP or ADB, or whatever.
Essentially, I just want a stock looking, sense toting, 5.1.1 ROM.
Thank you xunholyx
Click to expand...
Click to collapse
Yeah, but WWE isn't 6.0 That's GPE you're thinking of. WWE is still on 5.0.1 (.2?).
So is Rogers/Telus/Bell/AT&T/Verizon/Sprint/T-Mobile......
But the link I gave you will help you get back to stock Rogers.
Good luck!

Ugh, this'll be a ****ty process. I don't even know where to begin. Haha

Ok So ! Here's where I am.
Trying to flash 4.32.598.1_recovery to the phone to complete this mess. How in the hell do I get into ADB? I downloaded the SDK and Android as it required, but I cannot figure out how to get into fastboot to put this in.
Quick tip?

So, everyone vanished? Ugh. Just need to get the stock recovery put back on !

ChrisDuffy20 said:
So, everyone vanished? Ugh. Just need to get the stock recovery put back on !
Click to expand...
Click to collapse
We ain't getting payed to be here on the forum ! Have patience and be thankful for the given help so far........relax !
Hint :
Open a command prompt inside the folder where the fastboot exe file is located, put the recovery there too and flash it via fastboot command while the phone is in the bootloader-fastboot usb menu !

Sorry, have been up for a long time ... getting aggravated haha.
All I get is error: cannot load 4.32.598.1_recovery
Any idea?

Rename the file to just :
Recovery.img (look at the extension that it is NOT Recovery.imgimg !!!)
Then flash :
Fastboot flash recovery Recovery.img

Thank you.
I will give that a shot now.
Stand By - I need to delete TWRP too.

So, little progress, but when I try to do an OTA, I get "installation aborted".
From what I see, missing bitmap a few times over and a line that says package expects fingerprint of htc/rogers bah bah blah, this device htchtc_la_amx and a bunch more.
Now I'm lost.

You have a Rogers and you installed a Latin American stock recovery image ??
On your post #1 you mentioned your OS is Rogers 4.20.631.2 so install Rogers 4.20.631.2 stock recovery .. Canada and Latin America won't match
Also make sure your current ROM is non-rooted to apply OTA.

they aren't labled with regions .... only numbers.
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I'm using this guide

Yeah ... the numbers are important .. some people may have an Asian region device in Canada. They cannot install a Canada recovery but must be Asian recovery even though they are in Canada.
That is why numbers are listed. And that is why your number 4.20.631.2 is there.
There are four different type for Canada .. if "canada" is listed instead of numbers .. then it will be another problem .. like Rogers and Telus won't match too.

CID ROGER001
MID 0P6B16000
3.34.631.4
So I would select the matching number for recovery?

That is not correct too.
You need to choose matching number as your current OS 4.20.631.2 as what you written here - http://forum.xda-developers.com/showpost.php?p=63916840&postcount=1
And this is repeating what have been said in earlier posts by others and myself.

Ah yes. I should have elaborated on this. Forgive me, I'm am not amazing at this.
When I erased the red text, I was on that particular build. After that, I moved on to the stock ROM recovery. The 4.20 was PREVIOUS to actually flashing that file. I've been trudging on without guidance as I waited for help, and as I found on the net.

I've been struggling with this phone for a while.

I have a problem with my HTC one M8 At&t (It's unlocked to any provider) it's also rooted so if you can help me either unroot it or add a ROM that would be so helpful.
Well the problem with my phone is.
1) It won't update to 6.0 its stuck on 5.0.2
2) ROMS won't install at all. Maybe because it doesn't have TWRP (I don't know where to get that)
3) The phone is S-on relocked and it says "This device has been tampered' then a warning
I asked HTC and they didn't help at all. I asked people that I know but they are IOS.
So this is the last resort. I was recommended by a friend to ask you wonderful people. I mean i have some knowledge but it don't have anyone to show me the ropes of how to do it. But please if you guys can help add link with steps.
Thank you and have a good day dudes.

PTP012 said:
I have a problem with my HTC one M8 At&t (It's unlocked to any provider) it's also rooted so if you can help me either unroot it or add a ROM that would be so helpful.
Well the problem with my phone is.
1) It won't update to 6.0 its stuck on 5.0.2
2) ROMS won't install at all. Maybe because it doesn't have TWRP (I don't know where to get that)
3) The phone is S-on relocked and it says "This device has been tampered' then a warning
I asked HTC and they didn't help at all. I asked people that I know but they are IOS.
So this is the last resort. I was recommended by a friend to ask you wonderful people. I mean i have some knowledge but it don't have anyone to show me the ropes of how to do it. But please if you guys can help add link with steps.
Thank you and have a good day dudes.
Click to expand...
Click to collapse
I'd suggest you watch this video to install TWRP: https://www.youtube.com/watch?v=9HWj_1KHbuY
And then I'd also recommend installing CM13 since it's really stable. It can be found here: http://forum.xda-developers.com/htc...m-cyanogenmod-13-0-nightlies-htc-one-t3256696

PTP012 said:
I have a problem with my HTC one M8 At&t (It's unlocked to any provider) it's also rooted so if you can help me either unroot it or add a ROM that would be so helpful.
Well the problem with my phone is.
1) It won't update to 6.0 its stuck on 5.0.2
2) ROMS won't install at all. Maybe because it doesn't have TWRP (I don't know where to get that)
3) The phone is S-on relocked and it says "This device has been tampered' then a warning
I asked HTC and they didn't help at all. I asked people that I know but they are IOS.
So this is the last resort. I was recommended by a friend to ask you wonderful people. I mean i have some knowledge but it don't have anyone to show me the ropes of how to do it. But please if you guys can help add link with steps.
Thank you and have a good day dudes.
Click to expand...
Click to collapse
1. If it is AT&T, it won't update on non-AT&T network.
2. Unlock bootloader and install TWRP
3. The phone was unlocked before and now it is relocked.
Post fastboot getvar all without serial & imei no to confirm which device variant that you have and what to do with it.

Ragarianok said:
I'd suggest you watch this video to install TWRP: https://www.youtube.com/watch?v=9HWj_1KHbuY
Click to expand...
Click to collapse
I would suggest the OP not follow that video. Followed literally, it will not only direct the OP to install a horribly obsolete version of TWRP, but also one that is not intended for his version of the M8. The "wlv" version TWRP in the video is for Verizon, and would install TWRP to the wrong partition, maybe even brick the phone. TWRP has since been updated and unified to identify the M8 version, and install on the proper partition accordingly; but such was not the case at the time the video was created.
This is one of the main reasons I don't recommend rooting by watching YouTube videos. They aren't detailed enough to point out all the nuances and potential pitfalls of the process. They just spoonfeed enough knowledge to you get you into big trouble, without any knowledge or skills to get you out of that hole.
Also, the random "root" website referenced in the video doesn't appear to have any downloadable files any longer, anyway. At least not that I can find, upon examination. So if the OP that route, they would have hit a dead end. I also personally don't recommend such "root" websites, as they almost always just steal content from XDA, without giving proper credit.
All the info the OP needs is right here on XDA. An excellent guide for unlocking the bootloader and installing custom recovery is here. Although the guide is dated (hard for anything for this phone to not be dated at this point - it is over 2 years old) and I have the following additional advice:
- HTC drivers on the guide are dated. But if you plug the phone into your PC, it should auto-install HTC Sync and the required drivers
- You can get TWRP right from the source here. I'm not sure if your existing firmware will play well with the latest version (TWRP 3.0.x), but I'm pretty sure version 2.8.7.0 will work well (and known to be very stable).
- Only need to follow the guide through "ROOTING YOUR DEVICE" Step 8, that is unlocking the bootloader and installing custom recovery (don't flash SuperSU). From there, get the desired custom ROM on the phone, boot into TWRP, backup the current stock ROM, then do default wipe (data, cache, Dalvik) in TWRP and flash the ROM.
---------- Post added at 10:01 AM ---------- Previous post was at 09:48 AM ----------
An alternative would be to flash the Marshmallow RUU to update to full stock image. But in order to do so, the OP will have to update to Marshmallow firmware (which requires some knowledge of using fastboot) and then run the Marshmallow RUU. The RUU in listed on my AT&T M8 Index thread here (along with a lot of other useful info), with the info/link for flashing firmware highlighted in red text.

New thread, new question. Wifi or service, not both.

Ok, same phone, AT&T HTC M9, now S-Off, TWRP 3.0.2.0, 3.38.502.41 firmware. Tried ARHD 20.0, had no service, flashed boot.img, got service but lost wifi. Tried Viperone M9 4.3, same issue. ICE, same issue. If I have Wifi, I have no service. If I flash boot.img, I get service, but lose Wifi. I'm pulling my hair out right now, as I've searched high and low and I've been looking at my PC and M9 for about 14 hours now. Anyone have any insight?

Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
manlavi95 said:
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object
Click to expand...
Click to collapse
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.

Flippy498 said:
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.
Click to expand...
Click to collapse
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.

manlavi95 said:
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.
Click to expand...
Click to collapse
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.

Flippy498 said:
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.
Click to expand...
Click to collapse
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always

manlavi95 said:
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always
Click to expand...
Click to collapse
You don't need an SD card with less than 32gb if you're on firmware 3.x (and that is what you currently are). With firmware 3.x and above HTC enabled the usage of exfat formatted SD cards for RUU flashing.

Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j

manlavi95 said:
Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j
Click to expand...
Click to collapse
Correct.

IT WORKS. IT WOOOOOORKS. Thank you so much.

Develop Bugs

welcome