yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M9)] hallstevenson:
The first 2 days with a "new" ROM shouldn't be used for judging battery performance. Odds are you spend a lot more time than usual playing with it, doing lots of updates, etc.

FWIW, I'm at 83% right now and took it off the charger almost 8 hours ago... I get close to 18-20 hours normally and on a quiet or slow day, could no doubt get 24+ hours.
[Verizon HTC One (M9)] btstarcher:
I was running NuSenSe on my old Thunderbolt, way back in the day; did I see a mention of this being made available for the M9? Currently running Venom but not entirely happy with it. I'll probably go ahead and flash the stock rooted ROM in the interim.

Thanks so much for your hard work!
[Verizon HTC One (M9)] baune7:
Yeah... I get it about the first few days with any new ROM and battery performance and how long they take to "settle". I've probably done over a hundred ROMs from my OG droid, RAZRs, M8, M9, and my galaxy tabs. This was like nothing i've ever seen. I mean 35% loss in about 2.5-3 hours AFTER everything was re-installed and synced a couple days after installing. Crazy.

I did a full wipe yesterday from TWRP, re-installed the stock rooted ROM, wiped cache, re-booted, restored everything and everything seems to be going much, much better! Everything is so much smoother, no lag, and battery is still at 70% after 16 hours and 45 minutes since pulling it off the charger. I can live with that. Whatever was left over from the previous stuff, this new one didn't like at all.
[Verizon HTC One (M9)] longboardskier:
Well, I was hoping this was going to be fixed in MM, but I'm still getting "cell standby" battery drain it seems. I've been on airplane mode all day, and cell standby is at 41% of my battery usage. Anybody know of a working MM xposed module to fix it?
[Verizon HTC One (M9)] MrTrip:
Flashed firmware, flashed no red text boot, wiped and installed ROM, sitting at red Verizon loading screen.... been sitting here for a long time. Thoughts? Already reflashed once.
[Verizon HTC One (M9)] matteebee:
First boot takes a while be patient.
[Verizon HTC One (M9)] MrTrip:
ETA on first boot? Like, is 10-15 minutes too long?

Edit: Just started boot at 12:30...going to see how long it takes...

Edit2: 1:04 AM now, still at red screen. Suggestions?

Edit3: Reflashed the firmware using HTC_Fastboot and tried 6.0 again, still sitting at red Verizon screen... Just not working out at all for me it looks like. RUU Link has been removed too?

Edit4: Waited for it to boot until the battery died. I've tried starting completely over with the entire process about 4 times. Re-Downloaded files also. I'm kind of at a loss...any suggestions?

Edit5: I can't seem to go back to 5.1....so...I have no phone... Now I'm really confused, and pissed at myself for not doing this on a Friday night instead of a work night...

Edit6: Flashed http://xdaforums.com/verizon-one-m9/development/stock-5-1-resources-2-6-605-15-t3183752, specifically 3.10.605.7 custom firmware zip and now I can boot into 5.1 again. I guess I'll try this all again over the weekend when I can afford the downtime...
[Verizon HTC One (M9)] aer0zer0:
Minimallistic kernel from Sprint M9 forum works on our devices. Couple different governers, and tcp schedulers, and I/o schedulers
[Verizon HTC One (M9)] longboardskier:
I had the endless Verizon screen when I first tried this update, but I flashed the wrong firmware file, so I just want to make sure you didn't do what I did.

In the Firmware thread, make sure you either flash "3.37.605.7_NoBoot-NoRecovery_firmware.zip" or "3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip". I flashed "3.37.605.7_FULL_firmware.zip" at first and got the same issue you're having. I used the one with TWRP and it was all good.

Also, after you flash and while still in recovery, that's when you flash the Rom. It almost sounds like you flashed the firmware for 6.0, then tried to boot into 5.1 ROM (which is what I did....).

Might be basic and I apologize if it is to you, but it wasn't obvious to me at first until somebody told me.
[Verizon HTC One (M9)] MrTrip:
Hey no apology needed! Any advice is good advice. I'm going to give it a shot again and see what I can get done. I'm on a working 5.1 right now, so I'll upgrade firmware again then flash 6.0 immediately after again.

I'll report back with progress, thanks!
[Verizon HTC One (M9)] longboardskier:
No problem! Also, for what it's worth, I did the whole thing via TWRP instead of fastboot.
[Verizon HTC One (M9)] MrTrip:
Followed instructions again, this is the method I'm using and it is still sitting on the red Verizon screen, and the phone is warm.

Reboot to Downloader Mode

"fastboot oem rebootRUU"

*Phone reboots*

"fastboot flash zip 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip"

*Zip file flashes*

*Have to reflash it per instructions*

"fastboot flash zip 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip"

*Flash complete*

"fastboot reboot-bootloader"

Enter Recovery

Wipe

Flash the deodexed ROM provided in this thread

Flash complete and successful.

Reboot, stuck at red Verizon logo.

I do have S-OFF.

I've re-downloaded all files, using my macbook now, and a new USB cable. I have flashed many items from my macbook, especially when working with the CM devs with my old devices, and have never had an issue..

So, what now?
[Verizon HTC One (M9)] longboardskier:
Well, damn. That's what I did and it ended up working, so I'm not really sure what could be wrong now. Unfortunately I've exhausted my expertise. Hopefully someone who knows more can chime in. Sorry dude.
[Verizon HTC One (M9)] MrTrip:
Yeah I'm at a loss right now, sitting on a red screen still and waiting. I'm going to go get lunch and come back and see if it just magically pops up.
[Verizon HTC One (M9)] gris1016:
Bad download perhaps??

Did you verify the MD5 of all of your packages you are flashing?
[Verizon HTC One (M9)] MrTrip:
HOLY CRAP IT FINALLY STARTED!

I had to flash the FULL firmware and then flash TWRP manually from their image (3.0.0-2), then flash the ROM.

The Firmware with TWRP bundled did NOT work for me.

And yes, I did verify MD5 sum, sorry, as I was typing the reply it got past the red screen.

Finally time to debloat and customize, ah I'm so excited :)
[Verizon HTC One (M9)] btstarcher:
Mine took over an hour to finally install the first time. Possibly 2 or 3 even; I was busy at work and didn't keep track.
[Verizon HTC One (M9)] MrTrip:
Mine finally started, but now the apps are loop crashing over and over... I can't complete setup because Google Services Framework, Caller ID and a bunch of other apps keep crashing over and over again.
[Verizon HTC One (M9)] btstarcher:
I think mine had issues too, it was really hot. I ended up flashing the latest Viper.
[Verizon HTC One (M9)] MrTrip:
Ohh...Viper... I will have to try this out...

Can debloat right? I hate all the Verizon apps...

Edit: Comes debloated, works great, thanks!! :D
[Verizon HTC One (M9)] MrTrip:
Okay update... I have no root. I try installing SuperSU (The Beta for Marshmallow) and it says its doing some boot image patch, but it is not appearing to work.

I'm having awful luck here with any of this, I don't know what to do at all anymore.
[Verizon HTC One (M9)] aer0zer0:
Flash 2.65
[Verizon HTC One (M9)] MrTrip:
I've tried 2.64 2.65 and 2.67, none install the APK, none give root? I'm just about to say screw 6.0, I have had nothing but zero luck with it, and I'm not exactly retarded when it comes to this stuff.

I need to know, a configuration that works, what do I flash in what order and with what tools and what should I expect? Because right now I either get loop crashing ROM (This ROM) or I get a ROM with no Root and no way to obtain Root...
[Verizon HTC One (M9)] santod040:
Flash the firmware I posted with Twrp included.

Swipe to wipe in twrp, flash odexed or deodexed stock rooted roms.

I assure you they both work and come pre rooted with SuperSu v2.65 already.
[Verizon HTC One (M9)] MrTrip:
And I've done this, I used the HTC_fastboot you provided in case fastboot was the issue. I let it sit at the red Verizon screen for an hour and a half until the phone shut off from a 0% battery.

I'll do it one more time, I'll do wipe and give it one more shot and report back. I'll provide logs of the flash too.
[Verizon HTC One (M9)] aer0zer0:
Use the RUU, then do factory reset
[Verizon HTC One (M9)] MrTrip:
The link to the RUU is gone now.
[Verizon HTC One (M9)] longboardskier:
What about this one?

http://xdaforums.com/showthread.php?t=3137397
[Verizon HTC One (M9)] MrTrip:
I shall try that, thanks!
[Verizon HTC One (M9)] santod040:
Link to the RUU is still right where it's been since I posted it.

In the firmware/RUU thread, post #4:

http://xdaforums.com/showthread.php?p=65358513
[Verizon HTC One (M9)] MrTrip:
Ah apologies, confused that with the link to the OTA package which was removed.
[Verizon HTC One (M9)] MrTrip:
Here is the output from the flash.

c:\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 14(ms)

c:\adb>htc_fastboot flash zip 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
sending 'zip'... (65327 KB) OKAY
sending time = 4.202 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) start@13
(bootloader) aboot_signed.img@100%
(bootloader) adsp.img@BYPASS
(bootloader) hosd_signed.img@100%
(bootloader) hyp-8994-1.img@100%
(bootloader) pmic-8994-1.img@100%
(bootloader) recovery.img@BYPASS
(bootloader) rfg_1.img@BYPASS
(bootloader) rpm-8994-1.img@100%
(bootloader) sbl1-8994-1.img@100%
(bootloader) sensor_hub.img@BYPASS
(bootloader) tp_MXM11876.img@BYPASS
(bootloader) tz-8994-1.img@100%
(bootloader) radio.img@BYPASS
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
For "hboot-preupdate" response, restart the same procedure for device HT54DSV054
60...
< waiting for device >
sending 'zip'... (65327 KB) OKAY
sending time = 4.212 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) start@13
(bootloader) aboot_signed.img@100%
(bootloader) adsp.img@100%
(bootloader) hosd_signed.img@100%
(bootloader) hyp-8994-1.img@100%
(bootloader) pmic-8994-1.img@100%
(bootloader) recovery.img@100%
(bootloader) rfg_1.img@100%
(bootloader) rpm-8994-1.img@100%
(bootloader) sbl1-8994-1.img@100%
(bootloader) tz-8994-1.img@100%
(bootloader) radio.img@100%
(bootloader) sensor_hub.img@BYPASS
(bootloader) tp_MXM11876.img@BYPASS
(bootloader) Update zip file OK
(bootloader) end@Done
OKAY
Flash Zip Complete
Execution time is 15(s)

c:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 2(ms)

MD5 of the flash -> c:\adb>md5sum 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip

2979ebc4e8b64a7b8fc24e99e6f5a2fb *3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip

Flashed ROM, Long red screen, but now optimizing apps...

And...this time it all worked. I did the exact same process I've done 30 times before. I guess 31 is a charm or something? *sigh* My week has been crud, lol thanks for the help guys!
[Verizon HTC One (M9)] longboardskier:
Awesome, glad it finally worked!
[Verizon HTC One (M9)] MrTrip:
I spoke too soon... I have no Root. I'll provide recovery log...

ui_print

3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!
script succeeded: result was [3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 400MB, free: 21974MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log

Flashing SuperSU 2.65....

Still no root. So now what?

Edit: GOing to RUU then come back.
[Verizon HTC One (M9)] santod040:
Nobody else has had so many issues or troubles with installing or with root on these roms.

So, something you're doing isn't right and no amount of RUU'ing will fix whatever is going wrong for you.

The issue you apparently have, is "no root" on the stock rooted roms. Your recovery log isn't telling me anything.

Flashing the RUU will have absolutely zero effect on this.

Are you restoring apps and/or data during or after initial install?

What makes you think you have "no root"?

What does the SuperSu app say when you open it?
[Verizon HTC One (M9)] lordcheeto03:
Anyone having issues with Bluetooth? I had no trouble with Bluetooth on Viper but I had problems with the phone, this ROM, the phone works right but I keep being "Bluetooth share has stopped working"
[Verizon HTC One (M9)] santod040:
With Marshmallow firmware, this rom, no mods, Bluetooth should function normally.

If you're having issues, I'd suggest to reflash the MM firmware, perform a full wipe and reflash the rom.

There's no reason you'd have Bluetooth issues with current firmware on a clean install of the stock rom.
[Verizon HTC One (M9)] MrTrip:
Well I've followed all the instructions. I have wiped EVERYTHING on the phone and restored NOTHING.

SuperSU says there is no SU binary, and there is no SuperSU app until I install it from the app store.

I've flashed RUU, I started the entire process over again. What do I need to do? If I have to make a video documenting my entire process to get to no root I will do it just to prove I'm doing everything the way it was written out here.

What makes me think I have no root? Any App that required root says it cannot obtain it, and there is no SuperSU app when I flash the ROM.
[Verizon HTC One (M9)] santod040:
Well, then your /data partition is jacked up.

Since phone is already wiped entirely....

Flash stock recovery from my firmware thread and factory reset.

Stay away from formatting internal with Twrp after doing so.

Then reflash the rom.

SuperSu gets installed just fine on my end and the apk is actually placed into /data/app(ie: stays out of /system)

If it's not working while installing the rom, or the SuperSu zip, which is what the rom installer installs anyhow, then your issue is with your /data partition.

Only way I know of making that behave normally, is to do a factory reset/wipe using the "stock" recovery, not TWRP.

Just to be sure, you are not allowing Twrp to install root/supersu for you either if prompted to do so, correct?
[Verizon HTC One (M9)] MrTrip:
I am never prompted to install root by TWRP, and if I were I would click No. I've been told that about 600 times and I finally got a technical answer as to why that shouldn't be allowed anyway.

Alright, I will use stock recovery and do a factory reset, that I have not tried yet. Will report back shortly.

---------- Post added at 06:35 PM ---------- Previous post was at 06:27 PM ----------

I flashed 3.37.605.7_FULL_firmware.zip then did a factory reset in stock recovery, then I flashed the firmware with TWRP inside of it.

Next, I flashed the ROM, waited until I got to my home screen (No accounts added, No data restored, completely fresh).

There is no SuperSU anywhere....
[Verizon HTC One (M9)] andybones:
Just want to say thank you to [MENTION=1331268]santod040[/MENTION]

Had literally 0 issues...

Firmware flashed fully in 1 take.

Flashed TWRP 3.0.0-2

Flashed deodexed ROM, and not a single issue.

Thanks for all your time, my friend.
[Verizon HTC One (M9)] hallstevenson:
Look in /data/app for "eu.chainfire.supersu-1" (or something close). That's what it's called on Viper, at least.
[Verizon HTC One (M9)] MrTrip:
It is not there. There is no SuperSU app on the phone...

---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------

That is fantastic, go over your entire process start to finish so I can exactly mirror it and prove that I'm not an incompetent retard like some people are trying to make me out to be...

SuperSU thinks my boot image is at /dev/block/mmcblk0p65 is this correct? Something is not happy with this entire process...

Edit: There is a SuperSU.apk in my /data folder....why is this there?
[Verizon HTC One (M9)] andybones:
SuperSu is in data/app as that's where it's installed too.

If it's in data/app... You have SuperSu app installed.

I'm on phone but my process is quite simple and the same as any ROM.

Wipe, flash.

Nothing special I am doing. Santod did an amazing job for us to make this very simple.

Not saying anything bad against you. Just saying that he did a wonderful job, it works, and you must be doing something wrong, if I can help I will.

I'm not trying to prove you are incompetent. Just saying how it worked for me.
[Verizon HTC One (M9)] MrTrip:
Can I PM you? Skype or something? I can literally walk you through the process I am doing with screen sharing and webcam so you can see exactly what I do.
[Verizon HTC One (M9)] andybones:
I'm sorry friend I'm out at bar, ATM.

But yes, you can PM me your process.

My process:

is very simple, Santod did all the hard work.

I simply FULL wipe, flash ROM, let it boot, and not a single issue.

If SuperSU is your issue, have you tried flashing the SuperSU stable.zip in recovery?

It's not needed for me and the rest as it's included (this exact .zip actually), but maybe this will fix it up for you

https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip?retrieve_file=1

I'll attach an image of what you should see in data/app for SuperSu
[Verizon HTC One (M9)] MrTrip:
/data/app does not have this after flashing, nor after flashing the SuperSU Zip file.

The issue is isolated to SuperSU just not installing, even from flashing the SuperSU zip...

How would I troubleshoot this then?
[Verizon HTC One (M9)] andybones:
Honestly, I'm not sure. Doesn't make sense to me, TBH.

Flashing that .zip should give you SuperSu.

You could post in his thread.
[Verizon HTC One (M9)] MrTrip:
I'm just about completely over it, this makes no sense at all, I just did the same process to my girlfriends M9 (I had to S-OFF it first) and it worked flawless.

What can I do to completely and utterly return my phone to 110% stock everything so that I can start this whole process over?
[Verizon HTC One (M9)] andybones:
Well at least we now know it isn't you. ;)

But, personally.

I would flash the RUU that Santod uploaded.

I am not sure if that comes pre-rooted, but if not you can flash that SuperSu.zip at anytime.

We'll get this. :cool:

I know the frustrations my friend. Trying to get a ROM ready and something going wrong. Being so close to getting a MOD done but just missing something.

Don't give up, but don't let it take you over, either. :good:
[Verizon HTC One (M9)] MrTrip:
Flashed RUU, then flashed TWRP and then flashed SuperSU. No Root. I have a completely stock ROM, running smooth I might add I guess, but I have no root.
[Verizon HTC One (M9)] hallstevenson:
Trade phones with your girlfriend
[Verizon HTC One (M9)] MrTrip:
She won't let that happen, there has to be another solution here...
[Verizon HTC One (M9)] andybones:
When I have time, maybe we can chat on Hangouts and figure this out, as I'm a bit baffled myself. :confused:
[Verizon HTC One (M9)] MrTrip:
Alright yeah sounds good, I'm at a total loss. I generated some sulog.txt for the chainfire guy, but I don't think I'll get a response over there, its a really broad forum of help...
[Verizon HTC One (M9)] sidjohn:
*coff coff* -- drop it in the urinal -- use uh-oh
[Verizon HTC One (M9)] MrTrip:
Thought about it...

So I have this file now, can anybody look at it? it looks like SuperSU is literally installing to the WRONG directories. I end up with an su directory in my root / path, and some other odd files everywhere.

Attached is the log file.
[Verizon HTC One (M9)] aer0zer0:
Same here. I found that torque app was causing problems. Nope, still have the issue. I did flash a custom kernel though after thinking it was torque and my bluetooth obd2
[Verizon HTC One (M9)] BouncingObject:
Is there a reason you're using the HTC_fastboot instead of the normal fastboot to flash everything? Just curious as you can put me in the column of having no issues flashing.

My process for your reference:

1) Flashed MM firmware with TWRP 3.0.0-1

2) Downloaded odexed rooted ROM and flashed after wiping /system, /data, /cache and /dalvik.

ROM booted with no issues after about 10-15 min, if I remember correctly.

Hope we can all get this worked out!
[Verizon HTC One (M9)] hallstevenson:
Very true.... At least on this particular phone, it's not working, so maybe an alternative method should be tried. I also flashed the firmware and ROM using TWRP. Worked fine the first time.
[Verizon HTC One (M9)] santod040:
Unless you have /system mounted as "Read Only" in Twrp, (which doesn't really make sense with a rom installing, but not Su) I'm out of ideas...

So far, that's the only phone having an issue, so I'm gonna have to chalk it up to some sort of isolated bad mojo.

Good luck!
[Verizon HTC One (M9)] MrTrip:
Girlfriends phone has no root either, just has app sitting there. The app was there from when I rooted her in 5. I removed it and tried flashing root, not working, same issues I am having. The only thing she has ever had done was S-OFF and SuperSU installed in 5.0. She took the OTA to 6.0.

So what now? Two phones that can't root.

http://xdaforums.com/showpost.php?p=65559640&postcount=637

Posted in the thread above, has recovery.log etc in it.
[Verizon HTC One (M9)] btstarcher:
You must have downloaded the wrong file. I don't see how you could possibly lose root. You were both S-Off and rooted to begin with right?
[Verizon HTC One (M9)] MrTrip:
I was rooted on 5.0, 6.0 I have no root. What files should I download? I'll tell you if I have.

Actually I downloaded a 6.0 rom that is supposed to come rooted, has no root. No 6.0 roms have root for me at all. Root on 6.0 is NOT working on my phone or my girlfriends phone. Same HTC One M9

I am S-OFF.
[Verizon HTC One (M9)] btstarcher:
Dang tapatalk, I remember you posted earlier what you used. I can't remember. Which firmware?
[Verizon HTC One (M9)] MrTrip:
All firmware used in this thread. TWRP version, all versions. I've downgraded to 5.0 and OTA all the way to 6.0 and tried flashign SuperSU again also. I cannot get root on 6.0 with any method available right now. Two phones cannot get root with any method available.
[Verizon HTC One (M9)] btstarcher:
But the 1st one, which did you flash? And is your data partition set to R/O or R/W?
[Verizon HTC One (M9)] MrTrip:
I never changed Data partition. I can flash the firmware fine so shouldn't that mean its all R/W?
[Verizon HTC One (M9)] btstarcher:
I had to change mine to R/W. I'm not sure why. I had flashed Venom and I think the installer asked if I wanted to make it R/W so I did. That was before updating to MM.
[Verizon HTC One (M9)] MrTrip:
Mine was /system being R/W and I always hit yes.
[Verizon HTC One (M9)] btstarcher:
That may have been it...LOL. I'm easily confused and forget almost everything after a day or so.
[Verizon HTC One (M9)] baune7:
firmware flashing aside, and just a thought here.. but did you flash the correct "rooted" ROM.?? I flashed the MM firmware with the newest TWRP. Then flashed the Stock rooted deodexed ROM. Was rooted, but then I had to do factory reset due to some battery drain issues. Did that from within the settings menu. I rebooted and had lost root too. I had to boot into TWRP, do a complete wipe from within TWRP, then rebooted and restored everything and root was back on. Don't know why or how, but that did the trick for me.
[Verizon HTC One (M9)] MrTrip:
Yes. I flashed the rooted DEODEXED version in this thread. I've also tried flashing SuperSU 2.65 directly. Neither will give me Root. Also flashed ViperONE 6.0 and that did not come with Root either.
[Verizon HTC One (M9)] hallstevenson:
Install a ROM using TWRP, not fastboot.