yashsingh1/xdaforums huggingface dataset:
[AT&T HTC One (M9)] d-pak:
True dat! I finally broke down after tryin everything i could. Restore via TWRP, restore voia htc_fastboot, restored boot and recovery as well. No luck. Rerooted and unfroze all apps, unrooted, restores again. No matter what I tried., no luck. Figured, best to start fresh again. The sucky part is that the last time I did it was July 15. and in 1.5 months here we are again. If another update drops by the end of the year... then it will be another. Not sure if its worth rooting anymore.
[AT&T HTC One (M9)] ghosttown242:
That's why I didn't root no more after the first ota that I couldn't get
[AT&T HTC One (M9)] clsA:
Well even if you did have to RUU, it's not the end of the world. All you have to do is do a TWRP backup of your current setup on your ex-sd and copy your internal SD to your PC before flashing the RUU. Then after the RUU is complete simply Flash TWRP / Restore your backup / copy the internal SD back and your done.

Of corse this isn't always true, on a major update like 1.xx.xxx.xx to 2.xx.xxx.xx it's best to start fresh
[AT&T HTC One (M9)] nkk71:
easiest way is to restore via TWRP system_image backup (make sure "Mount system as read only" is checked in TWRP->Mount)

upon reboot TWRP should detect an untouched system partition and inform you.

you can then check sha1sum within an adb shell in twrp

adb shell
sha1sum /dev/block/bootdevice/by-name/system

the output hash should be the same as found in the OTA updater script,

for example:

version sha1sum
2.6.502.16 -> d3f10796c5cebbccc86f90205e4d8c2b94afdec5
2.6.502.18 -> beaf70469d8ba1760f7bf96319f120155a54117e

as for fastboot flashing, I've had to use htc_fastboot version 3.0.9.2, example output:

C:\ADB_HTC>[B][COLOR="Blue"]htc_fastboot_3.0.9.2.exe flash system StockNandroid_1.40.401.8\system_image.emmc.win"[/COLOR][/B]
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.469s]
sending sparse 'system' (697746 KB)...
OKAY [ 46.598s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 21.421s]
sending sparse 'system' (771035 KB)...
OKAY [ 51.405s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 24.193s]
sending sparse 'system' (770298 KB)...
OKAY [ 50.890s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 23.388s]
sending sparse 'system' (771800 KB)...
OKAY [ 78.987s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 24.810s]
sending sparse 'system' (763678 KB)...
OKAY [ 79.603s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 25.845s]
sending sparse 'system' (31420 KB)...
OKAY [ 5.158s]
writing 'system'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system@100%
(bootloader) Update partition OK
(bootloader) end@Done
OKAY [ 2.847s]
finished. total time: 435.630s
htc_fastboot finished. total time: 746.798s

C:\ADB_HTC>

[MENTION=2895182]clsA[/MENTION] have you or anybody else already tried the 2.6.502.18 RUU ? does it work?

cause decrypting it is very weird, everything goes well, except there is 1 extra byte in chunk 227 of system_01.img (and obviously not easy to figure out which one, or even why)

I guess, I could try flashing the encrypted system files, and see what gives, but was just wondering.
[AT&T HTC One (M9)] d-pak:
Where to get 3.0.9.2? Can you please share it?
[AT&T HTC One (M9)] clsA:
It's linked in my post on page 25
[AT&T HTC One (M9)] d-pak:
Thanks.

So I RUUed last night. Ran updates to latest .617.15.

This morning instead of manually installing everything, flashed twrp, decided to do a fresh system image backup (after enabling mount read only).

Re-rooted then used Titanium to restore apps+data (except system)

After reboot the phone decided it needs to install the update again i.e. 617.15 even though the system version was already on that already. Ugh

Tried cache and davlik cache erase no luck.

So I went into twrp to restore the backup I had just made and while restore succeed, the device is stuck in a boot loop now.

Also tried the new fast_boot version:

C:\AndroidRoot>htc_fastboot_new flash system system_image.emmc.win

htc_fastboot v3.0.9.2 (2015-05-29)

target reported max download size of 536870912 bytes

Invalid sparse file format at header magi

erasing 'system'...

OKAY [ 0.826s]

sending sparse 'system' (8 KB)...

OKAY [ 0.040s]

writing 'system'...

OKAY [ 0.025s]

finished. total time: 0.891s

htc_fastboot finished. total time: 3.996s

Old htc_fastboot still only does 393216KB

Back to RUU again :crying: Is there a link to the .617.15 RUU yet?
[AT&T HTC One (M9)] nkk71:
http://xdaforums.com/showpost.php?p=62589675&postcount=454

EDIT:

1- that's a stock system-image, also includes kernel, and stock recovery (don't restore stock recovery if you want to keep TWRP), dont forget to set read-only before restoring

2- to get rid of the notification (since you already did the OTAs, Settings->Manage Apps->ALL, then clear data on "Checkin" and "Updater" (or whatever their full names are)

3- were you flashing in download mode?
[AT&T HTC One (M9)] clsA:
Sure the RUU.EXE is in the first post >> http://www.htc.com/us/support/htc-one-m9/news/

easier to just use the Rom.zip you already downloaded

rename the RUU.zip to 0PJAIMG.ZIP,
place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work),
reboot into DOWNLOAD_MODE,
agree and it should flash.
[AT&T HTC One (M9)] clsA:
No I only use the developer edition files. I only post the AT&T files here for those that may need them.

I can test the RUU in a couple hours if you really need a guinea pig ;)
[AT&T HTC One (M9)] nkk71:
depends how bored you are or will be... but I wouldnt hold my breath, that RUU just seems wrong :eek: :eek: :eek:

probably easier, to flash the previous one, apply OTA, and get a decent system_image (EDIT: restore previous system_image & stock recovery -> then apply OTA, then get a decent backup, all without even wiping anything)

or let ATT know something is very finicky with that ruu :p:laugh:
[AT&T HTC One (M9)] clsA:
OK I downloaded the AT&T RUU direct from HTC

Changed my CID to CWS_001

The Retail RUU Failed

Tried the Rom.zip renamed 0PJAIMG.zip on my 32gig sdcard - FAILED at System.img_01

The AT&T 2.6.502.18 RUU is Broken

(last picture) I put the Developer Edition Rom.zip (renamed 0PJAIMG.zip) on the same sdcard and changed my CID back and it flashed first try

Pictures below
[AT&T HTC One (M9)] nkk71:
Thanks for confirming, sorry to have wasted your time, at least now we know for sure ATT RUU == No Go :cyclops:

and it's only 1 teeny tiny byte extra in there, but finding which one to remove would be ludicrous, best to just flash old system_image, apply OTA, do a new system_image backup.

Oh, and BTW, for all those using htc_fastboot.exe to flash a system_image, just a quick note, before flashing, make sure you have "Mount system as read only" selected in TWRP, if you don't, even after an htc_fastboot flash, if you reenter TWRP, it will mount it r/w and break the OTA capability, if on the other hand you "Mount read only", then htc_fastboot flash, and reenter TWRP, it will pop up with the "unmodified system partition" message.

Just wanted to let you know.
[AT&T HTC One (M9)] d-pak:
1 - If the backup with TWRP was done after TWRP was loaded, will that not be a TWRP in recovery vs Stock? Either way I was fine with it going back to stock recovery.

2- Didn't realize that in enough time, should have done that. Now I know for next time. Could have saved me a boot loop and second RUU.

3- I was flashing in download mode.

Did that, Thanks!

Agreed. This is important TWRP does say when first loaded that it can keep system as r/o and one must swipe to make it r/w.

For my procedure when I first made a system image backup, I made sure that twrp did not mount system as r/w and also went into mount option in twrp and checked the box for system as R/O. I subsequently did that whenever in twrp. Even after a htc_fastboot flash of the system image, going back into twrp brought back the screen that system was R/O, swipe was needed to mount r/w.

As fr he restore using htc_fastboot. If I boot into download mode. Flash system image then immediately flash stock recovery, I should not have to worry about twrp touching the freshly flashed system image?

All in all the process was not smooth for me at all. I ended up performing an RUU twice (once to get the update) and the second time because I got the "update pending notice" also though I would try to perfect the system image restore method for next time an update drops and I failed miserably.

By the way the new htc_fastboot did not work at first under Windows 10, had to write click the exe and mark the exe as "trusted" and run n Windows 8 mode.
[AT&T HTC One (M9)] nkk71:
above in blue :)
[AT&T HTC One (M9)] dragang:
latest firmware for HTC M9

Hi I have one question My HTCM9 info is_

htc download mode

***LOCKED ***

htc_himaulatt PVT S-OFF

CID-11111111

LK-1.0.0.0000

RADIO-01.01_U11440221_59.04.50303G_2_F

OpenDSP-v20.2.6-00452-M8994_0216

OS-1.32.617.6

Mar 4 2015, 23:00:55 (493992)

I need latest firmware if someone have please?
[AT&T HTC One (M9)] nkk71:
thread: http://xdaforums.com/one-m9/development/firmware-t3068243

firmwares (not added yet to the OP spreadsheet): http://xdaforums.com/showpost.php?p=62587611&postcount=653

PS: why are you LOCKED?? you shouldnt be, imho
[AT&T HTC One (M9)] xanadu1979:
Can you elaborate on this? I'm getting an error running the new htc_fastboot in Windows 10. When I right click on it, I don't see any options to mark it as "trusted". I've tried just setting the compatibility to Windows 8 (also tried 7) and that doesn't make a difference.

It gives me an error about a missing .dll, MSVCR100.dll. Which is present on my system. I even copied the .dll into the same folder and then it just gives me a different more generic error.
[AT&T HTC One (M9)] dragang:
Thank you.

I have problem and need some help because I first time use HTC phone

Before I been on :

Android version 5.0.2

HTC Sense version 7.0

Sofware number 1.32.617.6 ,

kernel 3.10.49

Build number 1.32.617.6 CL493992 release-keys

htc download mode

***LOCKED ***

htc_himaulatt PVT S-OFF

CID-11111111

LK-1.0.0.0000

RADIO-01.01_U11440221_59.04.50303G_2_F

OpenDSP-v20.2.6-00452-M8994_0216

OS-1.32.617.6

Mar 4 2015, 23:00:55 (493992)

Someone on another forum tell me that need to change firmware to 2.10.401.1 and via fastboot I do that and get in download mode next:

htc download mode

***LOCKED ***

htc_himaulatt PVT S-OFF

CID-11111111

LK-1.0.0.0000

RADIO-01.04_U11440601_71.02.50709G_F

OpenDSP-v29.2.6-00492-M8994_0702

OS-2.10.401.1

Jul 9 2015, 20:20:56 (576582)

But I thik that is wrong because my phone is htc_himaulatt. But after that I have problem with my phone when I dont use it some time and try to wake up phone go to restart . ., why?

I try to instal custom ViperONE rom but get nfs error and phone go to restart non stop.

I restore backup from TWRP recovery to first software

Android version 5.0.2

HTC Sense version 7.0

Sofware number 1.32.617.6 ,

After that I come here and flash firmware that you give me M9_2.11.617.15_NoWipe_TWRP_2871b1_rename_to_ROM.zip

and I am still on Sofware number 1.32.617.6 , but still have problem with phone when I dont use it some time (a few minutes) and try to wake up phone go to restart.

What is solution for fixing my phone, PLEASE SOME HELP ME, because need functional phone

Can I just flash newest rom from the first post:

New 8/30/15 - Developer Edition RUU 2.11.617.15 RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11. 617.15_Radio_01.01_U11440601_76.03.50611G_F_releas e_445910_signed_2.Rom.zip

Is this solve the problem?

Do I need unlock bootloader for that?

if real problem for restarting phone is because is bootloader locked and I am on S-OFF

Thanks
[AT&T HTC One (M9)] nkk71:
First, about the LOCKED status

: now that HTC have added the feature to enable/disable bootloader unlocking see below screenshot, and which is disabled by default, in the event you ever go S-ON and don't have a way to get to this setting, you will no longer be able to unlock bootloader

as long as you remain S-OFF, it's not a big deal, you can use this method from within TWRP or a rooted ROM to change the flag

Second,

, the restarts are caused by a kernel/firmware/ROM version mismatch. you can use the 2.10.401.1 (WWE) on an ATT phone just fine, with no problems; make sure to get a "Combined" one such as the ones found in this thread

you can also use any GSM variant you like (WWE, ATT, US Dev Edition, etc), the ones you want to stay away from are Sprint and Verizon stuff (CDMA)

Once you have a proper firmware in place, you can then flash the ROM corresponding to you firmware version

(eg 1.32 ROM on 1.32 firmware; 1.40 ROM on 1.40 firmware, 2.xx ROM on 2.xx firmware)
[AT&T HTC One (M9)] nkk71:
[MENTION=2895182]clsA[/MENTION]

added some new files here: http://xdaforums.com/showpost.php?p=62661172&postcount=470

if you need any of them.
[AT&T HTC One (M9)] xanadu1979:
I figured it out. If you're getting an error running the new htc_fastboot.exe on Windows 10, you need to install the Visual C++ 2010 redistributable.

You can download it here:

http://www.microsoft.com/en-us/download/details.aspx?id=5555

Note that you need to install the x86 version, even if your OS is x64.
[AT&T HTC One (M9)] LLegion:
jusrt to know...i have read that the 2.11 Ruu ZIP to use with the SD Card Flash Method is not working correctly, I have the 2.8 but i would need to OTA if I want to get 2.11....i dont mind flashing and restart phone from point 0...my question is......is it safe to use the Ruu ZIP pulled from Ruu Exe? (2.11 version) is it 100% functional? Thanks in advanced for the answer pals!
[AT&T HTC One (M9)] nkk71:
if you mean the 2.11. 617.15 RUU it should be fine; the one that's broken is the AT&T 2.6.502.18 RUU
[AT&T HTC One (M9)] LLegion:
Yess I mean the 2.11. 617.15 RUU, but my question is to know if the Ruu-Zip is not broken, the Ruu-EXE i dont care since i use the SD card method to flash from download mode, so i would like to be 100% sure the 2.11. 617.15 Ruu-ZIP is nor broken.

Thnaks a lot again!
[AT&T HTC One (M9)] nkk71:
the ruu.zip comes from the ruu.exe, and yep, it's fine

---------- Post added at 20:26 ---------- Previous post was at 19:51 ----------

if it makes you more comfortable:

Large zip format detected containing 7 zipfile(s)
Decrypted RUU (zip) written to: 01_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 02_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 03_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 04_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 05_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 06_2.11.617.15_decrypted.zip
Decrypted RUU (zip) written to: 07_2.11.617.15_decrypted.zip

nkk71@ubuntu:$ unzip -t '*_2.11.617.15_decrypted.zip'
Archive: 01_2.11.617.15_decrypted.zip
testing: android-info.txt OK
testing: aboot_signed.img OK
testing: radio.img OK
testing: rcdata.img OK
testing: splash1.nb0 OK
testing: adsp.img OK
testing: ramdisk.img OK
testing: modem_st1.img OK
testing: modem_st2.img OK
testing: android-info2.txt OK
testing: sensor_hub.img OK
testing: emmc_appsboot.mbn OK
testing: persist.img OK
testing: dt.img OK
testing: bootloader OK
testing: gpt_main_32g.img OK
testing: pg2fs_ship_signkey.img OK
testing: apppreload.img OK
testing: cota.img OK
testing: gpt_main_64g.img OK
testing: sbl1-8994-1.img OK
testing: sdi.img OK
testing: hosd_signed.img OK
testing: rpm-8994-1.img OK
testing: pmic-8994-1.img OK
testing: boot_signed.img OK
testing: recovery_signed.img OK
testing: cpe.img OK
testing: tz-8994-1.img OK
testing: hyp-8994-1.img OK
testing: tp_SYN3351.img OK
testing: tp_MXM11876.img OK
testing: cir.img OK
testing: backup_android-info.txt OK
No errors detected in compressed data of 01_2.11.617.15_decrypted.zip.

Archive: 02_2.11.617.15_decrypted.zip
testing: system.img_00 OK
testing: android-info.txt OK
No errors detected in compressed data of 02_2.11.617.15_decrypted.zip.

Archive: 03_2.11.617.15_decrypted.zip
testing: system.img_01 OK
testing: android-info.txt OK
No errors detected in compressed data of 03_2.11.617.15_decrypted.zip.

Archive: 04_2.11.617.15_decrypted.zip
testing: system.img_02 OK
testing: android-info.txt OK
No errors detected in compressed data of 04_2.11.617.15_decrypted.zip.

Archive: 05_2.11.617.15_decrypted.zip
testing: system.img_03 OK
testing: android-info.txt OK
No errors detected in compressed data of 05_2.11.617.15_decrypted.zip.

Archive: 06_2.11.617.15_decrypted.zip
testing: system.img_04 OK
testing: android-info.txt OK
No errors detected in compressed data of 06_2.11.617.15_decrypted.zip.

Archive: 07_2.11.617.15_decrypted.zip
testing: android-info.txt OK
testing: dzdata_16g.img OK
testing: dzdata_32g.img OK
testing: dzdata_16g.hdr OK
testing: dzdata_32g.hdr OK
testing: dzdata_64g.hdr OK
testing: dzdata_64g.img OK
testing: boot_signed.img OK
No errors detected in compressed data of 07_2.11.617.15_decrypted.zip.

7 archives were successfully processed.
[AT&T HTC One (M9)] LLegion:
Thanks a lot bro!!! :D you are great! That the answer i was looking for, i totally know that Ruu ZIP comes from Ruu EXE, i was just wondering if somehow by any reason in the process creating the Ruu Zip, it got broken, now im 100% sure it is not, thanks again!
[AT&T HTC One (M9)] nkk71:
no problem, that one looks just fine, the only broken RUU I've seen is the AT&T one, and that's not due to decryption or anything else, comes "factory broken" :p

though kinda overkill to go for a full RUU, stock system/boot/recovery backup are available (that will allow a normal OTA, to go through fine), and if you're S-OFF (I'm assuming you are from your signature firmware), then pretty easy to update anything you like

but your call, maybe nice to have a "clean" phone again :D
[AT&T HTC One (M9)] slvrhwk:
I have a dev edition on 2.8.617.4 with root and s-on. Yesterday, I flashed 1.32.617.30 system and recovery to go back to stock. Now my phone is stuck on htc logo. The OS in download mode still says 2.8.617.4 and I can boot to recovery. How do I get back to working condition? Can I flash system and recovery for 2.8.617.4? Please help.

Edit: I downloaded 2.8.617.4_rom.zip from the first post in this thread, as well as the corresponding recovery. Can I go ahead and flash it using fastboot flash system <system> or do I have to place it on an ext sd and rename it and flash that way?

Edit2: Mentioning [MENTION=2605798]nkk71[/MENTION], since he might be able to help.
[AT&T HTC One (M9)] nkk71:
the phone probably got stuck on boot logo because you didnt flash the kernel (boot.img)

but in either case, I'm not sure exactly what you're trying to do and whether or not it's succeeding.... I'd recommend full 2.11.617.15 RUU, especially since you're S-On... if you were taking OTA updates, you may have missed some firmware (since they are incremental)

so my suggestion would be to use a full RUU (yes, it will wipe the phone, but better than having a phone "in limbo")
[AT&T HTC One (M9)] GTIM2L8:
I flashed the latest RUU for the developer edition and I am trying to do a system backup.

I tried EXT4 and NTFS using Paragon but it doesn't recognize the SD card.

It doesn't recognize the SD card and seems to only reformat to FAT32.

Any help would be appreciated.

Thanks in advance.

T.I.
[AT&T HTC One (M9)] clsA:
System.img backup is done with twrp-2.8.7.1_CPTB-B1-hima recovery and then transferred to the PC for safe keeping

But it's kinda of pointless as [MENTION=2605798]nkk71[/MENTION] already has them backed up here >> https://www.androidfilehost.com/?w=files&flid=37609

and all my Developer Edition files are here >> https://www.androidfilehost.com/?w=files&flid=28824
[AT&T HTC One (M9)] c0de_junkie:
Hello everyone, I just got an M9 today and I have already got the bootloader unlocked and supersu installed and I have also ran sunshine so I am now S-OFF, I also changed the cid to supercid my mid is 0PJA11000 and I would like to flash the ViperOne rom which requires firmware 2.10 and my phone is at 1.32 so I should just need to update the firmware to 2.10 and then I should be able to flash the rom, correct? my other question to you guys is, is there anyone here that is on Telus here in Canada that is running 2.10 on there M9? and if so then did you need to change your mid to 0PJA10000 in order to upgrade the firmware? or did you just leave it the way it was? thank you very much for any help guys...

**UPDATE** nvm guys, got things figured out..
[AT&T HTC One (M9)] krazyace35:
Sorry wrong link will post new link in a few

Sent from my HTC One M9
[AT&T HTC One (M9)] krazyace35:
[MENTION=2895182]clsA[/MENTION] here is the 2.11.502.18 rom.zip if you want to add it to the OP

OPJAIMG

http://1drv.ms/1kIro4b
[AT&T HTC One (M9)] clsA:
Thanks a lot.. I'll put it on my AFH for a mirror and post it

it's the OTA cool, is the RUU updated too ?
[AT&T HTC One (M9)] krazyace35:
This is the rom.zip pulled from the 2.11.502.18 RUU which is updated here

http://dl3.htc.com.s3.amazonaws.com...51_SENSE70_ATT_MR_Cingular_US_2.11.502.18.exe

Sent from my HTC One M9
[AT&T HTC One (M9)] austriak:
Thank you to those that documented this process. I'm new to Android stuff like this and I was able to do it with minimal set backs.
[AT&T HTC One (M9)] clsA:
Your welcome, thanks for posting
[AT&T HTC One (M9)] johnnybravo2:
Hi Guys. I've been reading through this thread and still have a few questions. I have my at&t m9 root and loaded twrp. Is there a walk-through on how to flash the files or use the files listed in the initial post?

Also once converted to developer, do the ota updates work?

Thanks for your help.
[AT&T HTC One (M9)] Tikerz:
I just converted to the developer edition and tried to install v75 x64 Xposed Framework but it just hangs on the HTC One screen. Anyone get this to work?

---------- Post added at 10:31 AM ---------- Previous post was at 10:26 AM ----------

Everything you need is in the first post. This is a how-to thread.
[AT&T HTC One (M9)] blaten22:
My flash went ok, though in download mode it has started something new. In downloadmode, it will lock out the internal sd card and gives a message saying flashing a rom other than from HTC is a security risk *short version*. Just curious if this is normal behavior. It hasn't stop me from doing what I want to do with the phone, may be a Windows 10 thing. Hoping to ditch this for Linux very soon. I did a MD5 checksum on the zip file to make sure it was up to spec. Checked out fine. Here in the op is the file I used as it said updated and it matched HTC website.

New 8/30/15 - Developer Edition RUU 2.11.617.15 RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11. 617.15_Radio_01.01_U11440601_76.03.50611G_F_releas e_445910_signed_2.Rom.zip

Just double checking my findings. Thanks again.
[AT&T HTC One (M9)] clsA:
if that's the RUU you used your up to date for now

everything in your post is totally normal
[AT&T HTC One (M9)] Saga3282:
HTC One M9 Unlocked International

Hello guys, thanks for posting this, I was wondering if I can convert my international HTC One M9 with this guide following the same directions? Mine is not from AT&T. Thanks in advance!
[AT&T HTC One (M9)] dincdoes.me:
I don't know if the whole ruu conversion would work but just flashing like viper hit Att or flash a Att ROM they are the same phones Att has added bloat and a different texting feature built into the htc SMS app