yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M9)] imonxda:
@santod040 Sorry, please dissregard all of the above. I've had the M8 for so many years and now on this M9 I'm not used to the differences - my problem was bootloader was locked, even tho I have S-Off. All I did was follow instructions here: https://xdaforums.com/t/how-to-lock-unlock-your-bootloader-without-htcdev-s-off-required.3092036/

Now all problems described above are gone - I can install boot and recovery img with TWRP, and MultiROM works :)

Sorry for all the paragraphs above, I'm just a jackass sometimes, but I usually learn fast. This post also serves the purpose for all those other jackasses that don't try first to find the answers they seek on their own, this post should lead them unlock bootloader is NOT the same as S-Off, or, getting S-Off does NOT automatically unlock the bootloader.

Thanks again for answering.
[Verizon HTC One (M9)] BACHIROU786:
j'ai besoin d'aide j'ai un htc m9 verizon s-off nougat oem unclock non visible dans les options de développement impossible de mettre un recovery personnalisé, rom....

2- s'il n'est pas possible d'obtenir le déverrouillage OEM dans le paramètre, comment rétrograder pour revenir à Android 6

3- the phone information

HTC download

HTC HIMAWL PVT S OFF

CID 11111111

MID 0PJA30000

RADIO 2.15.C1144077@70710

0S 4.49.605.11

IMEI 990005693981426

Bootloader 1.0.0.0000

Reply

Report

I need help I have a htc m9 verizon s-off nougat oem unclock not visible in the developer options impossible to put a custom recovery, rom .... 2- if not possible to get OEM unlock in setting, how to downgrade back to android 6 3- the phone information htc download HTC HIMAWL PVT S OFF CID 11111111 MID 0PJA30000 RADIO 2.15.C1144077@70710 0S 4.49.605.11 IMEI 990005693981426 Bootloader 1.0.0.0000
[Verizon HTC One (M9)] santod040:
Follow the link in the last post right before yours, to unlock the bootloader.

The oem unlock option won't appear in settings on a Vzw device. You have to use adb as instructed in the link.
[Verizon HTC One (M9)] imonxda:
Like santod040 said, just follow the link in my post above, but FYI, you must install TWRP and Magisk root first using fastboot in download mode, that's what I did when I found the unlock bootloader thread. On my VZW M9, TWRP versions above 3.3.1.0 didn't work right, but I am using the 3.1.1.0 MultiROM TWRP right now and you would only need 3.3.1.0 version if you plan on flashing an Oreo or higher AOSP rom, since the highest sense android available is Nougat, and I think no AOSP roms offer Advanced Calling (required by VZW for voice/sms service) so you're stuck on Sense Nougat anyway.

Firstly, you will need to have ADB and FASTBOOT installed on your PC. After you flash TWRP with fastboot in D-Load mode, then use it to make an uncompressed backup of the boot partition, then you can install the latest Magisk apk in your stock OS then use it to manually patch the backup of the boot partition you made earlier in TWRP - you may have to rename the backup file extension to .img so Magisk can recognize it as a boot image file, just navigate using a file manager to the TWRP backup directory (I'm not 100% sure about the need for .img extension, I can't remember), save the output Magisk-patched img file to a PC using MTP USB, then flash the patched img with fastboot in D-load mode - You will have Magisk root, now you can follow the directions in the unlock bootloader thread above, you can run those adb commands with your phone booted in stock Magisk-rooted rom with DevOptions>USB-debugging ON connected to your PC w/ USB.

BTW, the ElementalX Nougat and MM kernels work perfect on this VZW M9, after you get your bootloader unlocked, I would recommend you flash ElementalX kernel (Sense roms only). If you do this, you'll have to rename Magisk.apk installer to Magisk.zip, then flash the zip in TWRP - it will Magisk root the newly installed ElementalX kernel - Flashing SuperSU instead of Magisk in TWRP also works, use the last SuperSU version 2.8.2 SR5 zip configured for systemless install (default).

Hope that helps.
[Verizon HTC One (M9)] BACHIROU786:
Thank you for the quick response to remind me I am an amateur in the field currently I do not have my machine next door 1- you said to flash twpr 3.1.1.0 by following the link if above once install twpr I will let you know for the rest
[Verizon HTC One (M9)] BACHIROU786:
thank you for the quick response and support here is the message I get when I put fastboot flash recovery twpr.img cannot load twpr.img the phone is in download mode I put twpr in the adb fastboot folder then open command prompt in the same folder
[Verizon HTC One (M9)] imonxda:
Hmm, I will try it on my system and paste the commands I use so you can compare - but I can't do it right now, in about 1-2 hours from now.

Did you install the ADB USB drivers?
[Verizon HTC One (M9)] imonxda:
So I just tried it and it the driver I gave you that link is no good. You should uninstall that driver and download this one instead:

https://nerdschalk.com/download-htc-driver-4-16-0-001/ get the 4.17.0.001 version, that worked on my system in download mode with TWRP.img file located in ADB/fastboot directory (didn't have to use 'full path to .img')

Command I used is:

fastboot flash recovery TWRP_3.1.1-0_multirom_hima_20171026-01.img

I also did it using twrp-3.1.1-0-hima.img and that worked too.

Try fastboot reboot-bootloader first, then the flash command - if it still doesn't work, it may be your USB cable isn't good enough to flash stuff even though it works for charging and MTP, I've had that happen to me before using some cheap USB cable, I switched to a quality cable and all fastboot flashing problems went away.

Also, try a different USB port, sometimes using a USB 2.0 slot behaves differently than using a USB 3.0 slot - on my system I use USB 3.0 slot, but I have a laptop that only works right with fastboot if I use the single USB 2.0 slot, so that's worth a shot.

I sent you a PM, FYI.
[Verizon HTC One (M9)] BACHIROU786:
Thank you for your quick response when I put adb abuse s displays the phone number but I will also try another
[Verizon HTC One (M9)] BACHIROU786:
Thank you for your quick response when I put adb devices s displays the phone number but I will also try another
[Verizon HTC One (M9)] j33zy:
I tried doing HTC Sync Manager repair a few times without any luck. It would just report 'Repair was unsuccessful' and phone would continue to boot to Verizon splash screen.
[Verizon HTC One (M9)] Tommydorns:
I lost volte with this firmware. Anyone else?
[Verizon HTC One (M9)] santod040:
Advanced Calling? Or VoLTE?

Advanced Calling Works fine:
[Verizon HTC One (M9)] Tommydorns:
I have this too. However, whenever I make a call, it goes to 1x and I can't use data on a call.
[Verizon HTC One (M9)] herculesbaloosh:
i try to update my stock htc with sideload when it reach 50% its says cannot read & reboot , i try with sd card no lock same thing it reach fine OTA_xxxxx_v13 some thing like that its reboot & my bootloader & recovery showing im on 6.0 but my phone is stuck in verizon booting logo please help
[Verizon HTC One (M9)] jsaxon2:
I lost VoLTE/Advanced Calling also. I haven't had time to mess with it though. I'm not sure if it if the firmware or Viper 4.2.1. I flashed the firmware and then flashed Viper right afterwards so I have nothing to compare. I'll have time in a couple days to RUU back and see if it helps. If not, I'm not really that worried about it.
[Verizon HTC One (M9)] Tommydorns:
I've done the same thing, you have. Let me know what you find. Call quality sucks for me now.
[Verizon HTC One (M9)] sidjohn:
Just tried again to confirm - Doesn't work on Viper 4.2.1 but does work again when I restore Neo's Adrenaline based on Lollipop 5.1 (Still on this FW though) so I don't think it's a FW issue.

I expect it's a ROM issue and should be sorted with the release of a Verizon based Marshmallow ROM
[Verizon HTC One (M9)] santod040:
Correct, has absolutely nothing to do with the firmware.

It's entirely a result of the rom and rom base you're using.

Things like VoLTE on Vzw and Wifi Calling on T-Mobile have to be ported into a WWE based rom for them to function properly.

These issues should be addressed in your respective rom thread of choice.
[Verizon HTC One (M9)] hallstevenson:
Viper is based on an international base, so there are a couple of things that won't work. I believe T-Mobile users run into similar things that won't work 100% too.
[Verizon HTC One (M9)] vedru:
OK letting you guys know that it is not that isolated issue, I am in the same boat there. Initially I thought it was just taking a long time, so I left it on a charger overnight. 12 hours later it was still on that red Verizon logo and pretty hot. So I checked the bootloader. That one appears to be updated to the new version and same for recovery. Ran the OTA package from recovery again, it does all the same steps just goes through the percentages way faster but gets stuck on that verizon logo after a few reboots. I tried clearing cache and resetting to factory and re-running the OTA package with same results. Tried to load an older RUU but that refuses to load as the firmware is updated so will have to wait for the new official RUU to be out before can see if I can salvage that phone unless someone comes up with a better idea :)
[Verizon HTC One (M9)] hgoldner:
I believe there is an incompatibility between the Marshmallow's boot.img and some Lollipop ROMs. My M9 was recently used to assist with the TWRP development and was returned to me with the latest TWRP *and* the latest firmware. I did a Nandroid restore of \system and \data (but not \boot) of my former Lollipop ROM (Fluent) to try to get a few things from it before the complete update to Marshmallow, but the device would not boot. Then I restored the \boot and tried again and after a long period (less than an hour) the cache rebuild process started and we were off to the races.

YMMV, but that was my experience earlier today.

UPDATE: [MENTION=6093703]Captain Throwback[/MENTION] has pointed out that he installed an AOSP boot.img so that would definitely bork things for a Sense ROM. Again, not a firmware issue.
[Verizon HTC One (M9)] Captain_Throwback:
I already told someone what to do, but it seems no one wants to do it . . . :rolleyes:.

If the ROM never got updated, but the firmware did, that explains why it won't boot up.
[Verizon HTC One (M9)] vedru:
That incompatibility should not really apply to the my phone or the others with this issue, as we are S-ON, Locked and Official ROM and firmware with never having unlocked or changed anything besides the previous OTA updates. so completely Official state on the phone. The OTA update should update the Firmware and ROM both to a level where they are compatible. It appears to do the firmware, bootloader and recovery just fine, however the ROM part appears to not load.

I also tried running the Verizon Software Repair Assistant, but that detects the phone fine, gives Software number: 3.37.605.7 however when trying to run repair says: "No software available". So my guess is that they have not released that version to the repair assistant yet. Will have to see which comes out first the Official RUU or the Repair assistant ROM :)
[Verizon HTC One (M9)] herculesbaloosh:
6.0 verizon screen stuck

same issue with my m9 now im phoneless my old laptop has evil smile

is there RUU for 6.0

---------- Post added at 12:14 AM ---------- Previous post was at 12:09 AM ----------

when new RUU comes up any idea buddy ?cuz i have no other phone to use

---------- Post added at 12:30 AM ---------- Previous post was at 12:14 AM ----------

thank you sir ! im stuck with Verizon screen after updating 6.0 i guess its not fully update my phone with like lot of other folks & huh i have only phone sound funny right but sir when RUU comes up cuz hmm i told you every thank for for giving your busy time sir
[Verizon HTC One (M9)] aer0zer0:
Will [MENTION=3211855]cmlusco[/MENTION] 5.1 signed ruu get them back to 5.1, then run a factory restore?
[Verizon HTC One (M9)] santod040:
Not if they are s-on, which some of them are...

Looking into something now to try and help them out.

Not what I intended on doing right now, but I hate seeing folks stuck.
[Verizon HTC One (M9)] aer0zer0:
Hopefully it all works out for them
[Verizon HTC One (M9)] dottat:
Did you try manually reflashing just the signed firmware via fastboot?

And if you'd like I can try a few things via team viewer
[Verizon HTC One (M9)] im_high_tech:
In SOFF and I flashed the FIRMWARE through fastboot perfectly :)
[Verizon HTC One (M9)] herculesbaloosh:
no!

how i can do that?

its s-on
[Verizon HTC One (M9)] dottat:
Install team viewer on your PC and pm me the user id and passcode. We can try a few things.
[Verizon HTC One (M9)] santod040:
Keyword: "signed"

That's how, you can flash a signed firmware, just as you flashed the signed OTA.

The "signed" firmware is the one listed as: 3.37.605.7_FULL_firmware.zip
[Verizon HTC One (M9)] herculesbaloosh:
i did that but no luck

still setting on verizon boot screen
[Verizon HTC One (M9)] vedru:
I had to do that about 5 times before it went through. It appeared to get stuck after anywhere between 25 and 58% on the first 4 tries. But did not fix the issue. Could it be that firmware went on fine just that the updating ROM part went bad?
[Verizon HTC One (M9)] dottat:
It could be. Does your stock recovery have an option to wipe cache?
[Verizon HTC One (M9)] vedru:
I feel your pain mate, I am really fortunate to have an old Galaxy Tab with sim socket in it, so i moved my sim card across and my phone is a 10' tablet until I get the HTC fixed. Slightly awkward doing phone calls on it, but at least it woks :)

---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------

Yes. I have done wipe cache about 4 times now and also done reset to factory about 3 times.

The Stock recovery now is a newer version. The new recovery no longer has option to load from internal memory but it allows selecting zip files from sdcard to load when the one from 5.1 only loaded the ones it found automatically.
[Verizon HTC One (M9)] herculesbaloosh:
tried also
[Verizon HTC One (M9)] dottat:
One last thing for both of you. Boot phone into download mode and attempt to flash the 5.1 signed ruu posted in the general section. If it fails please post the output from it here.
[Verizon HTC One (M9)] vedru:
OK, hTC download mode

has the security warning

then press volup to start flash, after pressing vol up starts ui_updating then gets the folliwing output and fails:

19 RU_MAIN_VER_FAIL os-version in android-info missing or i

19 RU_MAIN_VER_FAIL os-version in android-info missing or i

FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i

press power to continue

when pressing power it just powers down.
[Verizon HTC One (M9)] dottat:
10-4. So this phone checks the second field too then.
[Verizon HTC One (M9)] herculesbaloosh:
here you go

:silly:
[Verizon HTC One (M9)] herculesbaloosh:
so bud what should we do to fix this?
[Verizon HTC One (M9)] aer0zer0:
Try putting the signed ruu on the SD card, fat32 formatted, and rename it 0PJAIMG. Then flash it that way
[Verizon HTC One (M9)] herculesbaloosh:
ok ill try btw thnx
[Verizon HTC One (M9)] vedru:
The guys here are awesome and might find us a fix. But they are doing this of their own time and have other commitments like work and family and the issue might not be easy or quick to locate and fix. So expect to have to wait for the new RUU to become available and if the guys perform a miracle and provide a fix before that, be pleasantly surprised :)
[Verizon HTC One (M9)] aer0zer0:
sorry, im fresh outta good ideas.
[Verizon HTC One (M9)] dottat:
If either of you guys are near me I do have a javacard and can fix these if s-off (even if only temporarily s-off)
[Verizon HTC One (M9)] vedru:
I'm in Australia, so no go on that one, but thanks for offering. My location is also the reason I am still S-ON and complete stock.
[Verizon HTC One (M9)] santod040:
So, conclusion at this point regarding the OTAPkg.zip

Those who are s-on who tried to apply the OTAPkg.zip from a location other then where the OTA would download to:

The update will evidentlynot successfully apply from any location other then /cache/fumo/OTAPkg.zip (where the Official OTA downloads)

There is no way to access this "read-only" partition while s-on and locked.

So the OTA now only will apply itself from this location, as it knows if you try from elsewhere, it may not be official, signed, or secure.

This is something new I've yet to see on any HTC phone/update.

Likely to do with recent changes made to Android Security as a whole.

Unfortunately what happens, when the zip is applied from an alternate location, is it does manage to flash the firmware portion, but it never manages to install your rom/system software files.

Leaving you with an unbootable device/bootloop.

Luckily this is not a permanent brick, but a soft brick that you will have to recover when the current updates RUU is made available.

There are a couple of us who will be checking for it, multiple times daily and I will touch base with a few contacts tomorrow and see what can be done to get that file pushed out.

Those of you who are s-off, can just RUU back to the previous software/OTA version and then simply take the OTA if you wish, or just flash a rooted rom of choice.

(whether it's a custom rom port or one of these stock ones I intend to get posted ASAP, time permitting)

So firmware is perfectly safe to update, but the OTAPkg.zip file that I pulled, really isn't very useful for anyone.
[Verizon HTC One (M9)] LibertyMonger:
Hi thanks for sharing. Might be a stupid question but can this be rooted yet?
[Verizon HTC One (M9)] hallstevenson:
Only known method is to use a Java card or clip. I thought I recall jcase offering to root and/or S-Off a phone but you have to send it to him. He wasn't using either of the 2 methods above either, but not sure how he was doing it.
[Verizon HTC One (M9)] LibertyMonger:
I have S-Off just wanted root before I update. Thanks.
[Verizon HTC One (M9)] aer0zer0:
Twrp 3.0.0.1 and Supersu 2.65. You're in business
[Verizon HTC One (M9)] aer0zer0:
xposed framework runs on odexed OTA just fine, version 80, 23 - arm64
[Verizon HTC One (M9)] herculesbaloosh:
mine is s-on so , no luck

---------- Post added at 11:04 PM ---------- Previous post was at 10:34 PM ----------

so bud how we fix our s-on htc wait for another new RUU which size is 2GB+ or there is other thing? buddy i have not any another phone to please let me know thanks for your time.
[Verizon HTC One (M9)] hgoldner:
So I'm clueless as to why you tried to flash ANYTHING while S-ON, but we'll leave that for another day. Yes, you will have to wait for an RUU, or you can run HTC Sync from your PC and factory reset your device and start from scratch. Be sure you use YOUR region's apps/ROMs', etc. I didn't note where you were in the world, but USA versions are not the same as other WW versions, etc., even if both are Verizon.

For the obvious newbies here, flashing a ROM is not rocket science, but a couple of fundamental things should be so obvious as to be unnecessary to say regarding the Verizon M9: You need to be bootloader unlocked and S-OFF and the only way to do that is with a java card. Sunshine does not work on the Verizon M9.

Remember, "search" is your friend; before you undertake to flash a ROM or an update or anything, you should have ALREADY done your homework. Don't do it in the thread for the ROM or mod.

S-On. Good grief.
[Verizon HTC One (M9)] santod040:
As I said, you are gonna have to wait for the Official RUU or get s-off.

Those are the only options you have right now, aside from returning to Verizon, stating that it failed to take the OTA and is now stuck.

If/when an official RUU appears, I'll surely let folks know.

Until then, the options I mentioned above, are your only course of action.

Nothing has changed since last night...and isn't going to.

I wish there was some magic solution I could provide you, but there isn't, sorry.
[Verizon HTC One (M9)] herculesbaloosh:
ok sir thnx!

im gonna wait for Official RUU & thank again for your update.
[Verizon HTC One (M9)] hallstevenson:
Be thankful that a one-click-root doesn't exist for the M9!
[Verizon HTC One (M9)] michaelbsheldon:
I'm the only one with this problem, but my stock M9 was rooted as you suggest.

All other root-needing apps work fine, however, Titanium cannot delete apps.

They always return after a reboot, and I'm working on an xda Member suggestion to

fix this, but so far, no luck at all with Titanium and deletes.
[Verizon HTC One (M9)] aer0zer0:
you need to hand delete the apps in data\app and system\app & priv-app. Its crappy, but its the only way to keep them from manifesting themselves
[Verizon HTC One (M9)] herculesbaloosh:
how i can s-off my htc its Verizon ?
[Verizon HTC One (M9)] michaelbsheldon:
Agreed. But I can't locate all the google apps I want to plink.
[Verizon HTC One (M9)] santod040:
I don't use Titanium Backup personally, never cared for it. (just my own preference)

Though it may work with SeLinux set to permissive.

However, here's a suggestion for you:

On a stock rom you can't effectively mount system as rw while booted into system.

So you can't delete stuff unless you have a custom kernel with write protection disabled or a module compiled for the stock kernel.

So uninstall will miss its last step/deleting the apk, so every reboot it installs itself again.

But you can boot into TWRP, mount system and have your way with it...or create a flashable zip/script to delete the files of your choosing.

Point being, while booted in recovery, you can do as you wish.
[Verizon HTC One (M9)] santod040:
You quoted the answer to your question.

Find someone with a java card, go pay them a visit or mail them your phone.

There is a thread for this very subject in the General section of the Verizon M9 forum.
[Verizon HTC One (M9)] herculesbaloosh:
sorry for that im kinda new here so!

im dubai

i know in here no one has the s-off that no java card
[Verizon HTC One (M9)] cliefan:
Anxiously awaiting those Rom uploads :) Gonna try stock until viper has volte fixed. Santod040, thank you!!
[Verizon HTC One (M9)] hallstevenson:
You're in Dubai and have Verizon?
[Verizon HTC One (M9)] vedru:
Well hgoldner, as some of us dont really have any other options. I bought my phone last year when I spent almost 2 months in USA, from US at Verizon, then came back to Australia expecting to unlock it and found out that I can not S-Off it here as no one here has javacards, can not unlock bootloader as HTCdev does not do that for Verizon ones, can not get OTA updates as there is no Verizon network here, so I plugged my Australian SIM into it and have been downloading the OTA updates from XDA since and manually installing them.

I have learned a valuable lesson that Verizon really hates people who do not live in the USA.
[Verizon HTC One (M9)] hgoldner:
Key words here are "expecting to unlock." Might want to check that out before dropping a few US dollars on a phone. As far as Verizon being evil, they don't discriminate. That's what we concede for their coverage.
[Verizon HTC One (M9)] DSGONDREZ:
The software upgrade assistant is updated. You can now fix s-on devices through this method. Thank you to all the members for your help through this process of trying to find something. No more red verizon screen freeze!
[Verizon HTC One (M9)] billd1954:
Hi All,

I am currently rooted and Soff by [MENTION=3472611]dottat[/MENTION]'s magic. My phone just downloaded the OTAupdate from verizon! Should I accept the update? Will it reset my S off and rooting? Just thought I'd ask!

Thanks
[Verizon HTC One (M9)] santod040:
Nothing can change your s-off status but you.

Taking an OTA while rooted, will fail.

If you're not currently rooted, but have s-off, you can take the OTA, you'd have to have stock recovery.

Then you'd reflash twrp and supersu to get back to a rooted state.

FWIW, full stock rooted rom will be up today after work, for sure.
[Verizon HTC One (M9)] billd1954:
Thanks Santod - I am rooted and will wait for new ROM - No rush here new phone is awe sum. Good to see you on the M9. Thanks again!