yashsingh1/xdaforums huggingface dataset:
[One (M9) General] crucky:
wil do it now for you ;)

shell@htc_himauhl:/ $ cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 00100000 00000200 "pmic"
mmcblk0p5: 02800000 00000200 "dummy"
mmcblk0p6: 001f7c00 00000200 "reserve_1"
mmcblk0p7: 00040000 00000200 "mfg"
mmcblk0p8: 017afc00 00000200 "pg2fs"
mmcblk0p9: 00080000 00000200 "rpm"
mmcblk0p10: 00200000 00000200 "tz"
mmcblk0p11: 00018000 00000200 "sdi"
mmcblk0p12: 00200000 00000200 "hyp"
mmcblk0p13: 00100000 00000200 "aboot"
mmcblk0p14: 00a00000 00000200 "tool_diag"
mmcblk0p15: 00a00000 00000200 "sp1"
mmcblk0p16: 00100000 00000200 "ddr"
mmcblk0p17: 00100000 00000200 "rfg_0"
mmcblk0p18: 00100000 00000200 "rfg_1"
mmcblk0p19: 00100000 00000200 "rfg_2"
mmcblk0p20: 00100000 00000200 "rfg_3"
mmcblk0p21: 00100000 00000200 "rfg_4"
mmcblk0p22: 00100000 00000200 "rfg_5"
mmcblk0p23: 00100000 00000200 "rfg_6"
mmcblk0p24: 00100000 00000200 "rfg_7"
mmcblk0p25: 00180000 00000200 "fsg"
mmcblk0p26: 03b00400 00000200 "radio"
mmcblk0p27: 01400000 00000200 "adsp"
mmcblk0p28: 00000400 00000200 "limits"
mmcblk0p29: 004f7c00 00000200 "reserve_2"
mmcblk0p30: 01600000 00000200 "persist"
mmcblk0p31: 00a00000 00000200 "ramdump"
mmcblk0p32: 00100000 00000200 "misc"
mmcblk0p33: 00180000 00000200 "modem_st1"
mmcblk0p34: 00180000 00000200 "modem_st2"
mmcblk0p35: 01400000 00000200 "fataldevlog"
mmcblk0p36: 01e00000 00000200 "devlog"
mmcblk0p37: 00040000 00000200 "pdata"
mmcblk0p38: 00004000 00000200 "control"
mmcblk0p39: 00010000 00000200 "extra"
mmcblk0p40: 00100000 00000200 "cdma_record"
mmcblk0p41: 00000400 00000200 "fsc"
mmcblk0p42: 00002000 00000200 "ssd"
mmcblk0p43: 00080000 00000200 "sensor_hub"
mmcblk0p44: 00020000 00000200 "sec"
mmcblk0p45: 00100000 00000200 "abootbak"
mmcblk0p46: 00002800 00000200 "cir_img"
mmcblk0p47: 00140400 00000200 "local"
mmcblk0p48: 00080000 00000200 "frp"
mmcblk0p49: 00200000 00000200 "cpe"
mmcblk0p50: 01400000 00000200 "carrier"
mmcblk0p51: 00040000 00000200 "skylink"
mmcblk0p52: 00020000 00000200 "rfg_8"
mmcblk0p53: 00020000 00000200 "rfg_9"
mmcblk0p54: 00020000 00000200 "rfg_10"
mmcblk0p55: 00020000 00000200 "rfg_11"
mmcblk0p56: 00020000 00000200 "rfg_12"
mmcblk0p57: 00020000 00000200 "rfg_13"
mmcblk0p58: 00020000 00000200 "rfg_14"
mmcblk0p59: 00020000 00000200 "rfg_15"
mmcblk0p60: 01000000 00000200 "absolute"
mmcblk0p61: 00e07000 00000200 "reserve"
mmcblk0p62: 04000000 00000200 "hosd"
mmcblk0p63: 04000000 00000200 "boot"
mmcblk0p64: 04000000 00000200 "recovery"
mmcblk0p65: 14000000 00000200 "cache"
mmcblk0p66: 18000000 00000200 "system"
mmcblk0p67: e0000000 00000200 "userdata"
mmcblk0p68: 12200000 00000200 "apppreload"
mmcblk0p69: 03c00000 00000200 "cota"
mmcblk0p70: 00a00000 00000200 "battery"
shell@htc_himauhl:/ $
[One (M9) General] scotty1223:
excellent! very helpful,thank you.

looks like we will need partitions 2,7,8 if anyone gets a change to dump :)
[One (M9) General] hgoldner:
I may be able to get you this from a Verizon M9.

My name is Harold and I'm a flashaholic.....
[One (M9) General] scotty1223:
Thanks. I forgot to mention,the device needs to be unlocked or relocked in order to verify the flag location
[One (M9) General] hgoldner:
Just noticing that your partition list doesn't match mine. Boot is in 65 for example not 63.
[One (M9) General] scotty1223:
Verizon and Sprint typically are a little bit different from GSM models. your partitions 2, 7, and 8 are the same, correct? Feel free to post yours up.

Sent from my HTC One max
[One (M9) General] hgoldner:
Here are latest Verizon M9 partitions:

mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 00100000 00000200 "pmic"
mmcblk0p5: 02800000 00000200 "dummy"
mmcblk0p6: 001f7c00 00000200 "reserve_1"
mmcblk0p7: 00040000 00000200 "mfg"
mmcblk0p8: 017afc00 00000200 "pg2fs"
mmcblk0p9: 00080000 00000200 "rpm"
mmcblk0p10: 00200000 00000200 "tz"
mmcblk0p11: 00018000 00000200 "sdi"
mmcblk0p12: 00200000 00000200 "hyp"
mmcblk0p13: 00100000 00000200 "aboot"
mmcblk0p14: 00a00000 00000200 "tool_diag"
mmcblk0p15: 00a00000 00000200 "sp1"
mmcblk0p16: 00100000 00000200 "ddr"
mmcblk0p17: 00100000 00000200 "rfg_0"
mmcblk0p18: 00100000 00000200 "rfg_1"
mmcblk0p19: 00100000 00000200 "rfg_2"
mmcblk0p20: 00100000 00000200 "rfg_3"
mmcblk0p21: 00100000 00000200 "rfg_4"
mmcblk0p22: 00100000 00000200 "rfg_5"
mmcblk0p23: 00100000 00000200 "rfg_6"
mmcblk0p24: 00100000 00000200 "rfg_7"
mmcblk0p25: 00180000 00000200 "fsg"
mmcblk0p26: 03b00400 00000200 "radio"
mmcblk0p27: 01400000 00000200 "adsp"
mmcblk0p28: 00000400 00000200 "limits"
mmcblk0p29: 004f7c00 00000200 "reserve_2"
mmcblk0p30: 01600000 00000200 "persist"
mmcblk0p31: 00a00000 00000200 "ramdump"
mmcblk0p32: 00100000 00000200 "misc"
mmcblk0p33: 00180000 00000200 "modem_st1"
mmcblk0p34: 00180000 00000200 "modem_st2"
mmcblk0p35: 01400000 00000200 "fataldevlog"
mmcblk0p36: 01e00000 00000200 "devlog"
mmcblk0p37: 00040000 00000200 "pdata"
mmcblk0p38: 00004000 00000200 "control"
mmcblk0p39: 00010000 00000200 "extra"
mmcblk0p40: 00100000 00000200 "cdma_record"
mmcblk0p41: 00000400 00000200 "fsc"
mmcblk0p42: 00002000 00000200 "ssd"
mmcblk0p43: 00080000 00000200 "sensor_hub"
mmcblk0p44: 00020000 00000200 "sec"
mmcblk0p45: 00100000 00000200 "abootbak"
mmcblk0p46: 00002800 00000200 "cir_img"
mmcblk0p47: 00140400 00000200 "local"
mmcblk0p48: 00080000 00000200 "frp"
mmcblk0p49: 00200000 00000200 "cpe"
mmcblk0p50: 00a00000 00000200 "vzw_quality"
mmcblk0p51: 00a00000 00000200 "vzw_logger"
mmcblk0p52: 01400000 00000200 "carrier"
mmcblk0p53: 00040000 00000200 "skylink"
mmcblk0p54: 00020000 00000200 "rfg_8"
mmcblk0p55: 00020000 00000200 "rfg_9"
mmcblk0p56: 00020000 00000200 "rfg_10"
mmcblk0p57: 00020000 00000200 "rfg_11"
mmcblk0p58: 00020000 00000200 "rfg_12"
mmcblk0p59: 00020000 00000200 "rfg_13"
mmcblk0p60: 00020000 00000200 "rfg_14"
mmcblk0p61: 00020000 00000200 "rfg_15"
mmcblk0p62: 00a00000 00000200 "battery"
mmcblk0p63: 00007000 00000200 "reserve"
mmcblk0p64: 04000000 00000200 "hosd"
mmcblk0p65: 04000000 00000200 "boot"
mmcblk0p66: 04000000 00000200 "recovery"
mmcblk0p67: 40000000 00000200 "cache"
mmcblk0p68: 18000000 00000200 "system"
mmcblk0p69: b8000000 00000200 "userdata"
mmcblk0p70: 12200000 00000200 "apppreload"
mmcblk0p71: 03c00000 00000200 "cota"
[One (M9) General] Sneakyghost:
Sorry I only see this now. There had been a partition table since a while from me.

Find it here:

https://docs.google.com/spreadsheets/d/1yCWtDQ-2tpUzC-JDoVaScllsF3Db96Tr18U1izo7oJM/edit#gid=0
[One (M9) General] webdepp:
Here you go.

All information from my unlocked, o2 branded M9

https://www.dropbox.com/s/c80zkygvlkh3qmy/dump.zip?dl=0

emmc, partitions, mmcblk0p2 / 7 / 8
[One (M9) General] scotty1223:
excellent! just what i needed,things have moved a little bit,but still basically the same

we should be good to go if/when s off is achieved :D
[One (M9) General] webdepp:
Yay, good to hear!

Glad I could help
[One (M9) General] clsA:
scotty do you need the partition dumps from my Developer Edition ?

Here's the getvar all

and here the partition info

and the emmc
[One (M9) General] scotty1223:
It should be the same as the other gsm models,but it definitely wouldn't hurt to verify if you feel like dumping :)
[One (M9) General] jureca:
Waiting when you know tutorial lock and unlock bootloader and M8, thanks for your work!
[One (M9) General] crucky:
now i have a rooted unlocked M9 will do the dumping for you in the evening ! :D

edit:

pm sent to you scotty :)
[One (M9) General] freelockuk:
how do you get this

C:\adb>fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himaulatt

(bootloader) version: 1.0

(bootloader) imei: 35722***********

(bootloader) version-main: 1.32.617.6

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA11000

(bootloader) cid: BS_US002

all:

finished. total time: 0.013s

when i do this-----C:\adb>fastboot getvar all------- i only get this

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) max-download-size: 0x20000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x14000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x5e0000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x118000000

(bootloader) serialno: FA53HY******

all:

finished. total time: 0.097s
[One (M9) General] clsA:
do the same command in Download mode
[One (M9) General] freelockuk:
THANK YOU

---------- Post added at 12:38 AM ---------- Previous post was at 12:38 AM ----------

THANK YOU
[One (M9) General] clsA:
[MENTION=3437245]scotty1223[/MENTION]

Now that we have S-OFF on the M9 can you post the instructions for changing the MID to Developer Edition / International / T-Mobile / Etc ..
[One (M9) General] scotty1223:
yes,i will get those up. the mid change might be a couple days,weve only got a couple options so far. need more getvar alls :)
[One (M9) General] scotty1223:
does anyone want to volunteer to test the commands? i did get an m9,but i dont intend to root it for a few days and i assume you dont want to wait :D
[One (M9) General] clsA:
Yikes .. do i risk a brick ? I'll try it if you think it's safe
[One (M9) General] scotty1223:
i think its safe. i would try it on my phone,but fastboot boot still does not work,and i dont want to install a recovery until we get an OTA so that i have a stock one to put back.

as always,there are no gaurantees,and folks are welcome to wait until ive gotten a change to try it on my own device.

ill go ahead and put them out here,test at your own risk:

lock bootloader

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796

unlock bootloader

echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796

return to software status:normal

echo -ne '\x00' | dd of=/dev/block/mmcblk0p8 bs=1 seek=4228100

well save the mid change for now,ill ive got is yours,and mine(us t mobile)

edit:

there is no need to report that the tamper/software status flag change is not working. htc has introduced write protections that prevent us from changing things from within the OS or recovery,so a slightly different path is needed. to further complicate this p8 is phone specific and should not be shared across devices.

hang in there,and ill get a thread up with some user friendly directions when i get them worked out and tested.

thanks to everyone who has jumped in to test :cool:
[One (M9) General] scotty1223:
report back,if you try them please.

also, [MENTION=2895182]clsA[/MENTION] ive got an OTA downloaded and cant find it in my phone to capture it :mad:
[One (M9) General] jureca:
OK OTA download and no where :(
[One (M9) General] scotty1223:
i cant find it either :mad:
[One (M9) General] migascalp:
look in /data/data/com.htc.updater/files
[One (M9) General] scotty1223:
have to be rooted for that... they used to appear in the downloads folder so that they would be captured by stock phones

ive located a t mous OTA file,so ill go ahead and update/root later
[One (M9) General] Mutasek24:
[MENTION=3437245]scotty1223[/MENTION]

lock bootloader- works perfectly

unlock bootloader - works perfectly

status (normal)modified to official - don't work

Great job :good:
[One (M9) General] scotty1223:
awsome. what variant do you have? let me have a getvar all and a copy of p8
[One (M9) General] clsA:
look here >> data/data/com.htc.updater/files

oops too late see it's already posted
[One (M9) General] Mutasek24:
[MENTION=3437245]scotty1223[/MENTION]

moment please ;)
[One (M9) General] clsA:
The T-mobile OTA is here >> https://www.androidfilehost.com/?fid=95916177934556684
[One (M9) General] Mutasek24:
fastboot getvar all bootloader + download mode:

C:\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) max-download-size: 0x20000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x14000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x5e0000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x118000000

(bootloader) serialno:

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) imei:

(bootloader) version-main: 1.32.401.15

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: HTC__102
[One (M9) General] Black-FR:
The best is, you delete the ota again, then start a logcat and restart the download of the ota.

So you could find the download address, in the logcat.

Because without root, you won´t find the ota, on the device.

It´s saved in /data/data/com.htc.updater/files/
[One (M9) General] scotty1223:
Thanks.am out running a few errands,will check when I get home
[One (M9) General] Black-FR:
I could confirm, that lock / unlock works perfectly.

Tampered flag, didn´t work.

Download-Mode:

fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) imei:

(bootloader) version-main: 1.32.401.15

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: 11111111

all:

finished. total time: 0.031s

Bootloader:

fastboot getvar all

(bootloader) version: 0.5

(bootloader) max-download-size: 0x20000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x14000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x5e0000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x118000000

(bootloader) serialno:

all:

finished. total time: 0.109s
[One (M9) General] Rydah:
Hey Scotty, you do know I have a huge support thread for the T-Mobile variant right? Got everything you need there.

Sent From My HTC One (M9)
[One (M9) General] scotty1223:
yes,i found it shortly after the other post. thanks! downloaded the ruu as well
[One (M9) General] scotty1223:
seems neither of you have written 00 to the flag location. did anything look strange when you wrote the command? if you have a custom recovery installed,try issuing the command from there
[One (M9) General] Black-FR:
[MENTION=3437245]scotty1223[/MENTION]

Also executing the command, within TWRP, didn´t change it.

The screenshot of the cmd, is attached.
[One (M9) General] scotty1223:
hmmm. try writing the whole modified partition back:

https://www.mediafire.com/?vm6ndjmc0kwhcgw

no one else should use this file!!
[One (M9) General] Mutasek24:
Confirmed.
[One (M9) General] scotty1223:
also,i wouldnt mind seeing p2 from both of you
[One (M9) General] Black-FR:
I tried it, with the modified file, but it still says, software status modified.

edit:

p2 will follow in a few moments

Edit:
[MENTION=3437245]scotty1223[/MENTION]

p2 is now attached.
[One (M9) General] scotty1223:
thanks. let me have p8 one more time as well,to confirm that your write didnt "stick". its starting to look like there are some extra write protections in place here,despite the s off status.
[One (M9) General] Black-FR:
Thanks already, for your work.

And p8 is attached.
[One (M9) General] scotty1223:
awsome,thanks-you have been most helpful. sure enough,the flag is still there. at first glance,it appears that p8 is being protected somehow. ill know a bit more after i root my own phone,wich is still software status normal. ill work on that sometime in the next couple days.
[One (M9) General] Mutasek24:
[MENTION=3437245]scotty1223[/MENTION]

p2 attached
[One (M9) General] clsA:
bah never mind .. nothing to see here
[One (M9) General] Mutasek24:
[MENTION=3437245]scotty1223[/MENTION]

Take a look PM . Thanks
[One (M9) General] minotauri:
Attempted this on TMO USA with OTA (rooted):

Lock Bootloader: did not work

Unlock Bootloader: did not attempt

Return Software Status: did not work

shell@htc_himaul:/ $ su

su

root@htc_himaul:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=

1 seek=33796

-ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796 <

4+0 records in

4+0 records out

4 bytes transferred in 0.006 secs (666 bytes/sec)

root@htc_himaul:/ # reboot bootloader

reboot bootloader

C:\sdk\platform-tools>fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himaul

(bootloader) version: 1.0

(bootloader) imei:

(bootloader) version-main: 1.32.531.33

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA12000

(bootloader) cid: T-MOB010

all:

finished. total time: 0.020s
[One (M9) General] Behold_this:
Are you s off? You must be s off to do this
[One (M9) General] minotauri:
Oh nope. :)

I will s-off tonight when I get home from the office.
[One (M9) General] scotty1223:
just a small update... mid change thru adb has become obsolete. you can

fastboot oem writemid xxxxxxxxx in download mode on an s off device. eng bootloader no longer needed :)

[MENTION=1335001]Mutasek24[/MENTION] has confirmed
[One (M9) General] kangconsumer:
What are the advantages if i change my mid?
[One (M9) General] clsA:
Very Cool thanks

---------- Post added at 08:12 PM ---------- Previous post was at 08:11 PM ----------

it completes the conversion from a carrier phone to a Developer Edition or International one
[One (M9) General] Rydah:
After changing your CID And MID, you can 100% convert to any variant. Changing the CID will allow to flash updates or RUU's intended for other variants and MID changing will allow OTA updates to be sent to the device.

CID 11111111 will allow you to flash any RUU file.

Sent From My HTC One (M9)
[One (M9) General] minotauri:
OK looks like I get the lock/unlock to work and the bootloader still says MODIFIED on it.
[One (M9) General] scotty1223:
thats correct. p8 has write protections in place so going back to status original will be more difficult with m9
[One (M9) General] Rydah:
Cool, so now we need a list of device MID's. Lol

Sent From My HTC One (M9)
[One (M9) General] scotty1223:
not a prollem :) looks like we can write a new product id as well,but ive never seen a need for that. aboot seems much more versatile than a ship(non-eng) hboot
[One (M9) General] Behold_this:
...there are more.

Also as a temporary workaround for getting official software status back, for anyone that's doesn't already know, you can flash your device RUU, which will reset the software status flag. While you are s-off, the modified flag will not trip again.
[One (M9) General] Rydah:
Kinda looking to switch to Dev edition, but I love my WiFi calling... Decisions. Lol thanks!

Sent From My HTC One (M9)
[One (M9) General] Sh0X31:
"lock bootloader" worked

"return to software status:normal" nothing happens
[One (M9) General] overon37:
So. To mid change like cid change? Fastboot oem ..... ???

fastboot oem writemid xxxxxxxx

EDIT

i did it and works :)
[One (M9) General] scotty1223:
the tamper flag/software status change is not working. htc has introduced write protections that prevent us from changing things from within the OS or recovery,so a slightly different path is needed. to further complicate this, p8 is phone specific and should not be shared across devices.

hang in there,and ill get a thread up with some user friendly directions when i get them worked out and tested.

thanks to everyone who has jumped in to test :cool:
[One (M9) General] Mutasek24:
At this moment only possible option to return - ***Software status: OFFICIAL*** is flash RUU vi SD card ( flash RUU vi fastboot NOT RESTORE status official)
[One (M9) General] Behold_this:
Well it worked fine for me plus both methods flash the exact same zip. Perhaps you forgot to reboot bootloader after flashing via fastboot to confirm the status change.

Also let's be clear, the rom zip it is not a RUU. RUU means ROM update utility and it is actually the tool through which the rom zip is delivered. When I said flash your device RUU, that's exactly what I meant. I didn't mean flash the zip through fastboot and I didn't mean flash it through SD card. I suggested to use the actual utility.

Now, that being said, the zip being delivered is exactly the same whether you use a RUU, fastboot or SD card and the end result is no different on any of them.
[One (M9) General] Mutasek24:
OK I understand rom.zip ( called RUU) is not RUU ( ROM update utility) :) I lokked after flashing ROM.zip via fastboot ( WWE .15 and .8) vi fastboot status Softwre ( bootloader) and remained unchanged ( ***modiefied***) only when i used ROM.zip and copy SD ( changed name to 0PJAIMG.zip) Status has changed .... I don"t know why?
[One (M9) General] Behold_this:
Did you do getvar or did you actually verify in the bootloader AFTER rebooting? You have to reboot your device to see the change. Your device usually gets rebooted a couple times on its own when you use SD card.

In any event at least you're squared away. Personally I would recommend doing SD card or actual ruu. I don't recommend using fastboot. Why? You have to have a very specific version of fastboot to enable the automatic reboots and larger file size transfers. There are too many elements involved that could go wrong with fastboot, not the least of which is bad USB cord/connection. The RUU has safety checks involved to warn about bad USB connection and the SD card method well that doesn't use one at all. That's just one example of potential hazards and there are more. I always recommend using the methods that include added safety and that is real ruu or SD card. I'm not suggesting fastboot doesn't work, of course it does, but if I were suggesting to somebody what to do that would not be the preferred method.
[One (M9) General] Mutasek24:
Yes, I did a few restarts but no channges... end of its ends SD everything will succeed, also recommended method via SD card. :) Thanks
[One (M9) General] Behold_this:
Ok. Thanks for following up. Moral of this story, to avoid potential issues, SD card ftw

**edit.

Did you fastboot flash from download mode, or RUUmode? You need to flash from RUU mode for the flag to reset.

fastboot oem rebootRUU
[One (M9) General] Mutasek24:
Yes, I flashed RUU.zip in download mode/ rebootRUU + htc_fastboot.exe
[One (M9) General] Behold_this:
Your post is a little confusing do you mean you tried it in download mode and RUU mode? They are two different things. I'm only questioning you in the interest of getting absolutely every bit of information we can available. Again, my flag reset. It's not outside of the realm of possibility that there are differences from device to device. HTC is not going to tell us that and its on the community to figure it out.
[One (M9) General] Mutasek24:
OK I undertand :)

This means:

adb reboot download

fastboot oem rebootRUU

htc_fastboot flash zip rom.zip
[One (M9) General] Behold_this:
Perfect, thanks.
[One (M9) General] minotauri:
Which RUU did you flash? The T-Mobile one that's posted in the tmobile forum? I wasn't able to get my status to go back. It still says MODIFIED. I used HTC_Fastboot method. For some reason, my SD was not mounting in Download Mode.
[One (M9) General] Behold_this:
I did fastboot, yes. Is your SD card a fat32 formatted card? It must be for you to properly flash that way.
[One (M9) General] minotauri:
Thanks for the reminder. Haha. I forgot I switched out sdcards this weekend, and was using my new 64gb one not my Fat32 8gb one I was using. I reflashed the original stock TMO USA rom using SDCard method, and I now have status OFFICIAL. Thanks.
[One (M9) General] danlat1415:
If I have S-OFF, but modified status, will going through to stock RUU change the 'modified' status back to 'official' and stay like that when I root again?

I saw that you mentioned that it won't trip back again if you're S-OFF.
[One (M9) General] minotauri:
i am rooted, unlocked, and official with s-off.
[One (M9) General] danlat1415:
Thanks.

Also is this 'modified' work around the same as getting back the ability to flash OTA updates, or is this a separate w/r modification issue that's covered in a different thread?

The reason I ask, is will we need to do this every time there is and OTA update, or do we have to follow the process in one of the other threads about backing up the system partition etc..